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/migration-classic-resource-manager-faq.yml
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ metadata:
13
13
title: Frequently asked questions about classic to Azure Resource Manager migration
14
14
summary: |
15
15
> [!IMPORTANT]
16
-
> Today, about 90% of IaaS VMs are using [Azure Resource Manager](https://azure.microsoft.com/features/resource-manager/). As of February 28, 2020, classic VMs have been deprecated and will be fully retired on March 1, 2023. [Learn more](https://aka.ms/classicvmretirement) about this deprecation and [how it affects you](./classic-vm-deprecation.md#how-does-this-affect-me).
16
+
> Today, about 90% of IaaS VMs are using [Azure Resource Manager](https://azure.microsoft.com/features/resource-manager/). As of February 28, 2020, classic VMs have been deprecated and will be fully retired on September 1, 2023. [Learn more](https://aka.ms/classicvmretirement) about this deprecation and [how it affects you](./classic-vm-deprecation.md#how-does-this-affect-me).
17
17
18
18
19
19
sections:
@@ -42,7 +42,7 @@ sections:
42
42
- question: |
43
43
What is the definition of an existing customer on IaaS Virtual Machines (classic)?
44
44
answer: |
45
-
Customers who had active or stopped but allocated IaaS VMs (Classic) in their subscriptions in the month of February 2020, are considered existing customers. Only these customers get until March 1, 2023 to migrate their VMs from Azure Service Manager to Azure Resource Manager.
45
+
Customers who had active or stopped but allocated IaaS VMs (Classic) in their subscriptions in the month of February 2020, are considered existing customers. Only these customers get until September 1, 2023 to migrate their VMs from Azure Service Manager to Azure Resource Manager.
46
46
47
47
- question: |
48
48
Why am I getting an error stating "NewClassicVMCreationNotAllowedForSubscription"?
@@ -52,14 +52,14 @@ sections:
52
52
- question: |
53
53
Does this migration plan affect any of my existing services or applications that run on Azure virtual machines?
54
54
answer: |
55
-
Not until March 1st, 2023 for IaaS VMs (classic). The IaaS VMs (classic) are fully supported services in general availability. You can continue to use these resources to expand your footprint on Microsoft Azure. On March 1st, 2023, these VMs will be fully retired and any active or allocated VMs will be stopped & deallocated.
55
+
Not until September 1st, 2023 for IaaS VMs (classic). The IaaS VMs (classic) are fully supported services in general availability. You can continue to use these resources to expand your footprint on Microsoft Azure. On September 1st, 2023, these VMs will be fully retired and any active or allocated VMs will be stopped & deallocated.
56
56
57
57
There will be no impact to other classic resources like Cloud Services (Classic), Storage Accounts (Classic), etc.
58
58
59
59
- question: |
60
60
What happens to my VMs if I don’t plan on migrating in the near future?
61
61
answer: |
62
-
On March 1st, 2023, the IaaS VMs (Classic) will be fully retired and any active or allocated VMs will be stopped & deallocated. To prevent business impact, we highly recommend to start planning your migration today and complete it before March 1st, 2023.
62
+
On September 1st, 2023, the IaaS VMs (Classic) will be fully retired and any active or allocated VMs will be stopped & deallocated. To prevent business impact, we highly recommend to start planning your migration today and complete it before September 1st, 2023.
63
63
We are not deprecating the existing classic APIs, Cloud Services and resource model. We want to make migration easy, considering the advanced features that are available in the Resource Manager deployment model. We recommend that you start planning to migrate these resources to Azure Resource Manager.
64
64
65
65
- question: |
@@ -185,4 +185,4 @@ additionalContent: |
185
185
* [Use PowerShell to migrate IaaS resources from classic to Azure Resource Manager](migration-classic-resource-manager-ps.md)
186
186
* [Use CLI to migrate IaaS resources from classic to Azure Resource Manager](migration-classic-resource-manager-cli.md)
187
187
* [Community tools for assisting with migration of IaaS resources from classic to Azure Resource Manager](migration-classic-resource-manager-community-tools.md)
188
-
* [Review most common migration errors](migration-classic-resource-manager-errors.md)
188
+
* [Review most common migration errors](migration-classic-resource-manager-errors.md)
0 commit comments