Skip to content

Commit 05c24ae

Browse files
Merge pull request #268690 from vamckMS/docs-editor/dedicated-host-retirement-1710193093
update-adh-retirement-page
2 parents df4072e + 0ad6257 commit 05c24ae

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

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

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

7777
### Q: What will happen to my VMs if a Host is automatically deallocated?
7878

79-
A: If the underlying host is deallocated the VMs that were running on the host would be deallocated but not deleted. You would be able to either create a new host (of the same VM family) and allocate VMs on the host or run the VMs on multitenant infrastructure.
79+
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.
80+
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)