Merge pull request #105772 from tanmaygore/patch-4

Adding and update FAQ & Answers

Author: PRMerger17

includes/virtual-machines-common-classic-resource-manager-migration-faq.md

@@ -11,15 +11,23 @@ ms.custom: include file
 
 ---
 
+## What is the time required for migration?
 
+Planning and execution of migration greatly depends on the complexity of the architecture and could take couple of months.  
+
+## What is the definition of a new customer on IaaS VMs (classic)?
+
+Customers who did not have IaaS VMs (classic) in their subscriptions in the month of Febrauary 2020 (a month before deprecation started) are considered as new customers. 
 
 ## Does this migration plan affect any of my existing services or applications that run on Azure virtual machines? 
 
-No. The VMs (classic) are fully supported services in general availability. You can continue to use these resources to expand your footprint on Microsoft Azure.
+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. 
+There will be no impact to other classic resources like Cloud Services (Classic), Storage Accounts (Classic), etc.   
 
 ## What happens to my VMs if I don’t plan on migrating in the near future? 
 
-We are not deprecating the existing classic APIs and resource model. We want to make migration easy, considering the advanced features that are available in the Resource Manager deployment model. We highly recommend that you review [some of the advancements](../articles/azure-resource-manager/management/deployment-models.md) that are part of IaaS under Resource Manager.
+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 recomment to start planning your migration today and complete it before March 1st, 2023. 
+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. 
 
 ## What does this migration plan mean for my existing tooling? 
 
@@ -35,7 +43,7 @@ You can abort your migration as long as the resources are in the prepared state.
 
 ## Can I roll back my migration if the commit operation fails? 
 
-You cannot abort migration if the commit operation fails. All migration operations, including the commit operation, are idempotent. So we recommend that you retry the operation after a short time. If you still face an error, create a support ticket or create a forum post on [Microsoft Q&A](https://docs.microsoft.com/answers/index.html).
+You cannot abort migration if the commit operation fails. All migration operations, including the commit operation, are idempotent. So we recommend that you retry the operation after a short time. If you still face an error, create a support ticket.
 
 ## Do I have to buy another express route circuit if I have to use IaaS under Resource Manager?