You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/dedicated-host-retirement.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,11 +15,11 @@ We continue to modernize and optimize Azure Dedicated Host by using the latest i
15
15
16
16
## UPDATE: Retirement timeline extension
17
17
Considering the feedback from several Azure Dedicated Host customers that are running their critical workloads on SKUs that are scheduled for retirement, we have extended the retirement timeline from March 31, 2023 to June 30, 2023.
18
-
We don't intend to move the retirement timeline any further and recommend all ADH users that are running on below mentioned SKUs to migrate to newer generation based SKUs to avoid workload disruptions.
18
+
We don't intend to move the retirement timeline any further and recommend all ADH users that are using any of the listed SKUs to migrate to newer generation based SKUs to avoid workload disruptions.
19
19
20
20
## Migrations required by 30 June 2023 [Updated]
21
21
22
-
All hardware has a finite lifespan, including the underlying hardware for Azure Dedicated Host. As we continue to modernize Azure datacenters, hardware is decommissioned and eventually retired. The hardware that runs the following Dedicated Host SKUs will be reaching end of life:
22
+
All hardware has a finite lifespan, including the underlying hardware for Azure Dedicated Host. As we continue to modernize Azure datacenters, hardware is decommissioned and eventually retired. The hardware that runs the following Dedicated Host SKUs is reaching end of life:
23
23
24
24
- Dsv3-Type1
25
25
- Dsv3-Type2
@@ -37,11 +37,11 @@ The current retirement impacts the following Azure Dedicated Host SKUs:
37
37
- Dsv3-Type2
38
38
- Esv3-Type2
39
39
40
-
Note: If you're running a Dsv3-Type3, Dsv3-Type4, an Esv3-Type3, or an Esv3-Type4 Dedicated Host, you won't be impacted.
40
+
Note: If you're running a Dsv3-Type3, Dsv3-Type4, an Esv3-Type3, or an Esv3-Type4 Dedicated Host, you are not impacted.
41
41
42
42
## What actions should you take?
43
43
44
-
For manually placed VMs, you'll need to create a Dedicated Host of a newer SKU, stop the VMs on your existing Dedicated Host, reassign them to the new host, start the VMs, and delete the old host. For automatically placed VMs or for virtual machine scale sets, you'll need to create a Dedicated Host of a newer SKU, stop the VMs or virtual machine scale set, delete the old host, and then start the VMs or virtual machine scale set.
44
+
For manually placed VMs, you need to create a Dedicated Host of a newer SKU, stop the VMs on your existing Dedicated Host, reassign them to the new host, start the VMs, and delete the old host. For automatically placed VMs or for Virtual Machine Scale Sets, you need to create a Dedicated Host of a newer SKU, stop the VMs or Virtual Machine Scale Set, delete the old host, and then start the VMs or Virtual Machine Scale Set.
45
45
46
46
Refer to the [Azure Dedicated Host Migration Guide](dedicated-host-migration-guide.md) for more detailed instructions. We recommend moving to the latest generation of Dedicated Host for your VM family.
47
47
@@ -51,7 +51,7 @@ If you have any questions, contact us through customer support.
51
51
52
52
### Q: Will migration result in downtime?
53
53
54
-
A: Yes, you'll need to stop/deallocate your VMs or virtual machine scale sets before moving them to the target host.
54
+
A: Yes, you would have to stop/deallocate your VMs or Virtual Machine Scale Sets before moving them to the target host.
55
55
56
56
### Q: When will the other Dedicated Host SKUs retire?
A: You'll need to [exchange your reservation](../cost-management-billing/reservations/exchange-and-refund-azure-reservations.md#how-to-exchange-or-refund-an-existing-reservation) through the Azure portal to match the new Dedicated Host SKU.
71
+
A: You need to [exchange your reservation](../cost-management-billing/reservations/exchange-and-refund-azure-reservations.md#how-to-exchange-or-refund-an-existing-reservation) through the Azure portal to match the new Dedicated Host SKU.
72
72
73
73
### Q: What would happen to my host if I do not migrate by June 30, 2023?
74
74
75
-
A: After June 30, 2023 any dedicated host running on the SKUs that are marked for retirement will be set to 'Host Pending Deallocate' state before eventually deallocating the host. For additional assistance please reach out to Azure support.
75
+
A: After June 30, 2023 any dedicated host running on the SKUs that are marked for retirement will be set to 'Host Pending Deallocate' state before eventually deallocating the host. For more assistance, please reach out to Azure support.
76
76
77
77
### Q: What will happen to my VMs if a Host is automatically deallocated?
0 commit comments