Skip to content

Commit 963ef00

Browse files
authored
Merge pull request #120160 from CourtGoodson/patch-7
Update convert-classic-resource.md
2 parents edb7061 + 795e631 commit 963ef00

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

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

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -295,10 +295,9 @@ If you don't wish to have your classic resource automatically migrated to a work
295295

296296
### Is there any implication on the cost from migration?
297297

298-
There's usually no difference, with a couple of exceptions:
298+
There's usually no difference, with one exeception - Application Insights resources that were receiving 1 GB per month free via legacy Application Insights pricing model will no longer receive the free data.
299299

300-
- Migrated Application Insights resources can use [Log Analytics commitment tiers](../logs/cost-logs.md#commitment-tiers) to reduce cost if the data volumes in the workspace are high enough.
301-
- Grandfathered Application Insights resources no longer get 1 GB per month free from the original Application Insights pricing model.
300+
The migration to workspace-based Application Insights offers a number of options to further [optimize cost](../logs/cost-logs.md), including [Log Analytics commitment tiers](../logs/cost-logs.md#commitment-tiers), [dedicated clusters](../logs/cost-logs.md#dedicated-clusters), and [basic logs](../logs/cost-logs.md#basic-logs).
302301

303302
### How will telemetry capping work?
304303

@@ -344,7 +343,7 @@ To avoid this issue, make sure to use the latest version of the Terraform [azure
344343

345344
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.
346345

347-
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.
346+
We strongly encourage updating to the [new API](resource-manager-app-resource.md) for better control over resource creation.
348347

349348
### Should I migrate diagnostic settings on classic Application Insights before moving to a workspace-based AI?
350349
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.

0 commit comments

Comments
 (0)