Skip to content

Commit 8d77e28

Browse files
authored
Merge pull request #224783 from oriwolman/patch-3
Update migration-classic-resource-manager-faq.yml
2 parents ffe418b + 9af7e8c commit 8d77e28

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/virtual-machines/migration-classic-resource-manager-faq.yml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ metadata:
1313
title: Frequently asked questions about classic to Azure Resource Manager migration
1414
summary: |
1515
> [!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).
1717
1818
1919
sections:
@@ -42,7 +42,7 @@ sections:
4242
- question: |
4343
What is the definition of an existing customer on IaaS Virtual Machines (classic)?
4444
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.
4646
4747
- question: |
4848
Why am I getting an error stating "NewClassicVMCreationNotAllowedForSubscription"?
@@ -52,14 +52,14 @@ sections:
5252
- question: |
5353
Does this migration plan affect any of my existing services or applications that run on Azure virtual machines?
5454
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.
5656
5757
There will be no impact to other classic resources like Cloud Services (Classic), Storage Accounts (Classic), etc.
5858
5959
- question: |
6060
What happens to my VMs if I don’t plan on migrating in the near future?
6161
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.
6363
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.
6464
6565
- question: |
@@ -185,4 +185,4 @@ additionalContent: |
185185
* [Use PowerShell to migrate IaaS resources from classic to Azure Resource Manager](migration-classic-resource-manager-ps.md)
186186
* [Use CLI to migrate IaaS resources from classic to Azure Resource Manager](migration-classic-resource-manager-cli.md)
187187
* [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

Comments
 (0)