Update classic resource FAQ

Author: AarDavMax

articles/azure-monitor/app/convert-classic-resource.md

@@ -285,6 +285,14 @@ From within the Application Insights resource pane, select **Properties** > **Ch
 
 This section provides answers to common questions.
 
+### What will happen if I don't migrate my Application Insights classic resource to a workspace-based resource?
+
+Microsoft will begin an automatic phased approach to migrating classic resources to workspace-based resources beginning in May 2024 and this migration will span the course of several months. We can't provide approximate dates that specific resources, subscriptions, or regions will be migrated.
+
+We strongly encourage manual migration to workspace-based resources, which is initiated by selecting the deprecation notice banner in the classic Application Insights resource Overview pane of the Azure portal. This process typically involves a single step of choosing which Log Analytics workspace will be used to store your application data. If you use continuous export, you'll need to additionally migrate to diagnostic settings or disable the feature first.
+
+If you don't wish to have your classic resource automatically migrated to a workspace-based resource, you may delete or manually migrate the resource.
+
 ### Is there any implication on the cost from migration?
 
 There's usually no difference, with a couple of exceptions:
@@ -332,15 +340,11 @@ If you're using Terraform to manage your Azure resources, it's important to use
 
 To avoid this issue, make sure to use the latest version of the Terraform [azurerm provider](https://registry.terraform.io/providers/hashicorp/azurerm/latest), version 3.89 or higher, which performs the proper migration steps by issuing the appropriate ARM call to upgrade the App Insights classic resource to a workspace-based resource while preserving all the old data and connection string/instrumentation key values.
 
-### What will happen if I don't migrate my Application Insights classic resource to a workspace-based resource?
-
-Your Application Insights classic resource may continue to work for some time, but Microsoft will only provide support services related to migrating these resources to workspace-based resources.
-
 ### Can I still use the old API to create Application Insights resources programmatically?
 
-We strongly encourage updating to the [new API](https://learn.microsoft.com/azure/azure-monitor/app/resource-manager-app-resource) version to ensure only supported workspace-based resources are created.
+For backwards compatibility, calls to the old API for creating Application Insights resources will continue to work. Each of these calls will eventually create both a workspace-based Application Insights resource and a Log Analytics workspace to store the data.
 
-Calls to the old API for creating Application Insights resources will continue to work, but Microsoft will only provide support services related to the new API version and migrating to workspace-based resources.
+We strongly encourage updating to the [new API](https://learn.microsoft.com/azure/azure-monitor/app/resource-manager-app-resource) for better control over resource creation.
 
 ### Should I migrate diagnostic settings on classic Application Insights before moving to a workspace-based AI?
 Yes, we recommend migrating diagnostic settings on classic Application Insights resources before transitioning to a workspace-based Application Insights. It ensures continuity and compatibility of your diagnostic settings.