Skip to content

Commit 917154b

Browse files
committed
Learn Editor: Update dedicated-host-retirement.md
1 parent 5cba497 commit 917154b

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/virtual-machines/sizes/migration-guides/dedicated-host-retirement.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,4 +78,7 @@ A: After June 30, 2023 any dedicated host running on the SKUs that are marked fo
7878

7979
A: If the underlying host is deallocated the VMs that were running on the host would be either in failed or stopped state but not deleted.
8080

81-
You could stop/deallocate the VM or VMSS and the dissociate the VM or VMSS from the host/host group (depending on explicit vs implicit placement) and then you would be able to either create a new host (of the same VM family) and allocate VMs on the host/host group or run the VMs on multitenant infrastructure.
81+
You could stop/deallocate the VM or VMSS and the dissociate the VM or VMSS from the host/host group (depending on explicit vs implicit placement) and then you would be able to either create a new host (of the same VM family) and allocate VMs on the host/host group or run the VMs on multitenant infrastructure.
82+
83+
Refer to the [Azure Dedicated Host Migration Guide](dedicated-host-migration-guide.md) for more detailed instructions.
84+

0 commit comments

Comments
 (0)