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
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -345,7 +345,7 @@ To avoid this issue, make sure to use the latest version of the Terraform [azure
345
345
346
346
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.
347
347
348
-
We strongly encourage updating to the [new API](resource-manager-app-resource.md) for better control over resource creation.
348
+
We strongly encourage updating to the [new API](create-workspace-resource.md) for better control over resource creation.
349
349
350
350
### Should I migrate diagnostic settings on classic Application Insights before moving to a workspace-based AI?
351
351
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.
@@ -385,6 +437,10 @@ Unique customizations that commonly need to be manually re-created or updated fo
385
437
> [!NOTE]
386
438
> If the resource you're creating in a new region is replacing a classic resource, we recommend that you explore the benefits of [creating a new workspace-based resource](#workspace-based-application-insights-resources). Alternatively, [migrate your existing resource to workspace based](./convert-classic-resource.md).
387
439
440
+
### Can I use providers('Microsoft.Insights', 'components').apiVersions[0] in my Azure Resource Manager deployments?
441
+
442
+
We don't recommend using this method of populating the API version. The newest version can represent preview releases, which might contain breaking changes. Even with newer nonpreview releases, the API versions aren't always backward compatible with existing templates. In some cases, the API version might not be available to all subscriptions.
0 commit comments