Skip to content

Commit a90c044

Browse files
Merge pull request #267986 from AaronMaxwell/aaronmax-classic-resources-retired
Updated wording from deprecated to retired
2 parents d878d2a + a12d933 commit a90c044

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

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

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,9 +21,8 @@ Workspace-based resources:
2121
> - Are available in all commercial regions and [Azure US Government](../../azure-government/index.yml).
2222
> - Don't require changing instrumentation keys after migration from a classic resource.
2323
24-
2524
> [!IMPORTANT]
26-
> * On February 29, 2024, continuous export will be deprecated as part of the classic Application Insights deprecation.
25+
> * On February 29, 2024, Continuous Export was retired as part of the classic Application Insights resource retirement.
2726
>
2827
> * [Workspace-based Application Insights resources](./create-workspace-resource.md) are not compatible with continuous export. We recommend migrating to [diagnostic settings](../essentials/diagnostic-settings.md) on classic Application Insights resources before transitioning to a workspace-based Application Insights. This ensures continuity and compatibility of your diagnostic settings.
2928
>
@@ -289,7 +288,7 @@ This section provides answers to common questions.
289288

290289
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.
291290

292-
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.
291+
We strongly encourage manual migration to workspace-based resources, which is initiated by selecting the retirement 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.
293292

294293
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.
295294

0 commit comments

Comments
 (0)