This post has been republished via RSS; it originally appeared at: Azure Compute Blog articles.
Today, we’re making it possible to attach a running Virtual Machine (VM) to an existing Virtual Machine Scale Set (VMSS) with no downtime. VMSS customers can now also detach a VM with minimal to no downtime. Attach and detach actions are available for scale sets with Flexible Orchestration Mode with a Fault Domain Count of 1.
- Let Azure do the work: Easily move from a single VM to VMSS Flex and make use of all the benefits that come from scale sets, like Autoscale, Automatic OS Upgrades, Spot Priority Mix, Instance Repairs, and Upgrade Policies.
- Easily scale: By attaching an existing VM to an existing VMSS Flex, you can grow your Compute architecture without having to rebuild it from scratch.
- No downtime: You can attach running VMs to a scale set with no downtime, thereby creating a frictionless experience to make use of scale sets.
- Isolation: Should you need more detailed troubleshooting of a VM, you can now detach the VM to isolate it from the scale set.
When the VM and the VMSS meet all the qualifications, you can quickly attach the VM to the scale set by updating the VM to use the VMSS ID. Use the REST API, Azure Portal, Azure CLI, or Azure PowerShell to update the VMSS ID parameter on the VM. For example, using PowerShell:
Likewise, to detach the VM, you simply need to update the VM to no longer have a VMSS ID associated with it:
Attach and detach of VMs to/from VMSS Flex is in Public Preview in all regions in public Azure.
To learn more about how to attach or detach VMs to or from a VMSS Flex, please visit the documentation.