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/azure-monitor/app/convert-classic-resource.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -79,18 +79,24 @@ If you don't need to migrate an existing resource, and instead want to create a
79
79
80
80
To migrate a classic Application Insights resource to a workspace-based resource:
81
81
82
-
1.1.From your Application Insights resource, select **Properties** under the **Configure** heading in the menu on the left.
82
+
1. From your Application Insights resource, select **Properties** under the **Configure** heading in the menu on the left.
83
83
84
84

85
85
86
86
1. Select **Migrate to Workspace-based**.
87
87
88
+

89
+
88
90
1. Select the Log Analytics workspace where you want all future ingested Application Insights telemetry to be stored. It can either be a Log Analytics workspace in the same subscription or a different subscription that shares the same Azure Active Directory tenant. The Log Analytics workspace doesn't have to be in the same resource group as the Application Insights resource.
89
91
90
92
> [!NOTE]
91
93
> Migrating to a workspace-based resource can take up to 24 hours, but the process is usually faster. Rely on accessing data through your Application Insights resource while you wait for the migration process to finish. After it's finished, you'll see new data stored in the Log Analytics workspace tables.
92
94
95
+

96
+
93
97
After your resource is migrated, you'll see the corresponding workspace information in the **Overview** pane.
98
+
99
+

94
100
95
101
Selecting the blue link text takes you to the associated Log Analytics workspace where you can take advantage of the new unified workspace query environment.
96
102
@@ -303,13 +309,13 @@ If you can't change the access control mode for security reasons for your curren
303
309
304
310
The legacy **Continuous export** functionality isn't supported for workspace-based resources. Prior to migrating, you need to disable continuous export.
305
311
306
-
1.1.From your Application Insights resource view, under the **Configure** heading, select **Continuous export**.
312
+
1. From your Application Insights resource view, under the **Configure** heading, select **Continuous export**.
307
313
308
314

309
315
310
316
1. Select **Disable**.
311
317
312
-
1.
318
+

313
319
314
320
- After you select **Disable**, you can go back to the migration UI. If the **Edit continuous export** page prompts you that your settings aren't saved, select **OK**. This prompt doesn't pertain to disabling or enabling continuous export.
0 commit comments