Skip to content

Commit 0fa0e38

Browse files
Merge pull request #273687 from vamckMS/docs-editor/dedicated-hosts-how-to-1714399884
updated-adh-redeploy-section
2 parents 074d941 + 7ff53a1 commit 0fa0e38

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-machines/dedicated-hosts-how-to.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -330,7 +330,7 @@ If you want to manually choose which host to deploy the scale set to, add `--hos
330330

331331
## Reassign an existing VM
332332

333-
You can add reassign an existing multitenant VM or dedicated host VM to a different dedicated host, but the VM must first be Stop\Deallocated. Before you move a VM to a dedicated host, make sure that the VM configuration is supported:
333+
You can reassign an existing multitenant VM or dedicated host VM to a different dedicated host, but the VM must first be Stop\Deallocated. Before you move a VM to a dedicated host, make sure that the VM configuration is supported:
334334

335335
- The VM size must be in the same size family as the dedicated host. For example, if your dedicated host is DSv3, then the VM size could be Standard_D4s_v3, but it couldn't be a Standard_A4_v2.
336336
- The VM needs to be located in same region as the dedicated host.
@@ -730,7 +730,7 @@ $hostRestartStatus.InstanceView.Statuses[1].DisplayStatus;
730730

731731

732732

733-
## Redeploy a host
733+
## Redeploy a host [Preview]
734734

735735
If a VM or the underlying host remains unresponsive after following all the potential troubleshooting steps users can trigger service healing of the host and not wait for the platform to initiate the repair. Redeploying a host will move the host and all associated VMs to a different node of the same SKU. None of the host parameters would change except for the ‘Host asset ID’, which corresponds to the underlying Node Id.
736736

0 commit comments

Comments
 (0)