Skip to content

Commit f2cabc7

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #278063 from brittanyrowe/attach-detach-spg-updates
Attach detach spg updates + IB
2 parents cd75266 + a8a824e commit f2cabc7

File tree

1 file changed

+10
-6
lines changed

1 file changed

+10
-6
lines changed

‎articles/virtual-machine-scale-sets/virtual-machine-scale-sets-attach-detach-vm.md

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,11 @@ ms.reviewer: jushiman
1515
## Attaching a VM to a Virtual Machine Scale Set
1616

1717
> [!IMPORTANT]
18-
> You can only attach VMs to a Virtual Machine Scale Set in **Flexible orchestration mode**. For more information, see [Orchestration modes for Virtual Machine Scale Sets](./virtual-machine-scale-sets-orchestration-modes.md).
18+
> You can only attach Virtual Machines (VMs) to a Virtual Machine Scale Set in **Flexible orchestration mode**. For more information, see [Orchestration modes for Virtual Machine Scale Sets](./virtual-machine-scale-sets-orchestration-modes.md).
1919
2020
There are times where you need to attach a virtual machine to a Virtual Machine Scale Set to benefit from the scale, availability, and flexibility that comes with scale sets. There are two ways to attach VMs to scale sets: manually create a new standalone VM in the scale set or attach an existing VM to the scale set.
2121

22-
You can attach a new standalone VM to a scale set when you need a different configuration on a specific VM than what's defined in the scaling profile, or when the scale set doesn't have a virtual machine scaling profile. Manually attaching VMs gives you full control over instance naming and placement into a specific availability zone or fault domain. The VM doesn't have to match the configuration in the virtual machine scaling profile, so you can specify parameters like operating system, networking configuration, on-demand or Spot, and VM size.
22+
You can attach a new standalone VM to a scale set when you need a different configuration on a specific VM than what's defined in the scaling profile, or when the scale set doesn't have a scaling profile. Manually attaching VMs gives you full control over instance naming and placement into a specific availability zone or fault domain. The VM doesn't have to match the configuration in the scale set's scaling profile, so you can specify parameters like operating system, networking configuration, on-demand or Spot, and VM size.
2323

2424
You can attach an existing VM to an existing Virtual Machine Scale Set by specifying which scale set you would like to attach to. The VM doesn't have to be the same as the VMs already running in the scale set, meaning it can have a different operating system, network configuration, priority, disk, and more.
2525

@@ -140,13 +140,15 @@ Update-AzVM -ResourceGroupName $resourceGroupName -VM $vm -VirtualMachineScaleS
140140
- The VM can't be in a `ProximityPlacementGroup`.
141141
- The VM can't be in an Azure Dedicated Host.
142142
- The VM must have a managed disk.
143-
- The scale set must have `properties.singlePlacementGroup` set to `False`.
143+
- The scale set must have `singlePlacementGroup` set to `False`.
144+
- Scale sets created without a scaling profile default to `singlePlacementGroup` set to `null`. To attach VMs to a scale set without a scaling profile, `singlePlacementGroup` needs to be set to `False` at the time of the scale set's creation.
145+
- The VM can't be an RDMA capable HB-series or N-series VM.
144146

145147
## Detaching a VM from a Virtual Machine Scale Set (Preview)
146148
Should you need to detach a VM from a scale set, you can follow the below steps to remove the VM from the scale set.
147149

148150
> [!NOTE]
149-
> Detaching VMs created by the scale set will require the VM to be `Stopped` prior to the detach. VMs that were previously attached to the scale set can be detached while running.
151+
> Detaching VMs created by the scale set will require the VM to be `Stopped` before the detach. VMs that were previously attached to the scale set can be detached while running.
150152
151153
### [Azure portal](#tab/portal-3)
152154

@@ -182,6 +184,8 @@ Update-AzVM -ResourceGroupName $resourceGroupName -VM $vm -VirtualMachin
182184
- The scale set must use Flexible orchestration mode.
183185
- The scale set must have a `platformFaultDomainCount` of **1**.
184186
- VMs created by the scale set must be `Stopped` prior to being detached.
187+
- Scale sets created without a scaling profile default to `singlePlacementGroup` set to `null`. To detach VMs from a scale set without a scaling profile, `singlePlacementGroup` needs to be set to `False`.
188+
- The VM can't be an RDMA capable HB-series or N-series VM.
185189

186190
## Moving VMs between scale sets (Preview)
187191

@@ -198,7 +202,7 @@ The limitations for VMs to be [attached](#limitations-for-attaching-an-existing-
198202

199203
| Error Message | Description | Troubleshooting Options |
200204
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
201-
| Referenced Virtual Machine Scale Set '{vmssName}' does not support attaching an existing Virtual Machine to it. For more information, see https://aka.ms/vmo/attachdetach. | The subscription isn't enrolled in the Attach/Detach Preview. | Ensure that your subscription is enrolled in the feature. Reference the [documentation](#enroll-in-the-preview) to check if you're enrolled. |
205+
| Referenced Virtual Machine Scale Set '{vmssName}' does not support attaching an existing Virtual Machine to it. For more information, see https://aka.ms/vmo/attachdetach. | The subscription isn't enrolled in the VM Attach Detach Preview. | Ensure that your subscription is enrolled in the feature. Reference the [documentation](#enroll-in-the-preview) to check if you're enrolled. |
202206
| The Virtual Machine Scale Set '{vmssUri}' referenced by the Virtual Machine does not exist. | The scale set resource doesn't exist, or isn't in Flexible Orchestration Mode. | Check to see if the scale set exists. If it does, check if it's using Uniform Orchestration Mode. |
203207
| This operation is not allowed because referenced Virtual Machine Scale Set '{vmssName}' does not have orchestration mode set to 'Flexible'. | The scale set isn't in Flexible Orchestration Mode. | Try attaching to another scale set with Flexible Orchestration Mode enabled. |
204208
| Referenced Virtual Machine '{vmName}' belongs to an Availability Set and attaching to a Virtual Machine Scale Set is not supported. For more information, see https://aka.ms/vmo/attachdetach. | `VmssDoesNotSupportAttachingExistingAvsetVM`: The VM that you attempted to attach is part of an Availability Set and can't be attached to a scale set. | VMs in an Availability Set can't be attached to a scale set. |
@@ -210,7 +214,7 @@ The limitations for VMs to be [attached](#limitations-for-attaching-an-existing-
210214
### Detach a VM from a scale set troubleshooting (Preview)
211215
| Error Message | Description | Troubleshooting options |
212216
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
213-
| Virtual Machine Scale Set does not support detaching of Virtual Machines from it. For more information, see https://aka.ms/vmo/attachdetach. | The subscription isn't enrolled in the Attach/Detach Preview. | Ensure that your subscription is enrolled in the feature. Reference the [documentation](#enroll-in-the-preview) to check if you're enrolled. |
217+
| Virtual Machine Scale Set does not support detaching of Virtual Machines from it. For more information, see https://aka.ms/vmo/attachdetach. | The subscription isn't enrolled in the VM Attach Detach Preview. | Ensure that your subscription is enrolled in the feature. Reference the [documentation](#enroll-in-the-preview) to check if you're enrolled. |
214218
| The Virtual Machine Scale Set '{vmssUri}' referenced by the Virtual Machine does not exist. | The scale set resource doesn't exist, or isn't in Flexible Orchestration Mode. | Check to see if the scale set exists. If it does, check if it's using Uniform Orchestration Mode. |
215219
| This operation is not allowed because referenced Virtual Machine Scale Set '{vmssName}' does not have orchestration mode set to 'Flexible'. | The scale set isn't in Flexible Orchestration Mode. | Only scale sets with Flexible Orchestration Mode can have VMs detached from them. |
216220
| Virtual Machine Scale Set '{vmssName}' does not support detaching an existing Virtual Machine from it because the Virtual Machine Scale Set has more than 1 fault domains. For more information, see https://aka.ms/vmo/attachdetach. | The detach of the VM failed because the scale set it's in has more than 1 platform fault domain. | VMs can only be detached from scale sets with a `platform fault domain count` of 1. |

0 commit comments

Comments
 (0)