The template deployment error show that "pergb2018" is not a valid option for price tier now.

[ericcwk]

New-AzureRmResourceGroupDeployment : 12:34:33 PM - Resource Microsoft.OperationalInsights/workspaces 'AIAPOC' failed with message '{
"error": {
"code": "BadRequest",
"message": "Pricing tier doesn't match the subscription's billing model. Read http://aka.ms/PricingTierWarning for more details."
}

Noted that i have just executed the same template last week. This option is still valid on last week

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e7651b7e-278e-2839-e9f4-cee3d8c8d60b
• Version Independent ID: 45386b9f-a8e3-a398-c0da-880fbdd76abb
• Content: Use Azure Resource Manager templates to Create and Configure a Log Analytics Workspace
• Content Source: articles/azure-monitor/platform/template-workspace-configuration.md
• Service: log-analytics
• GitHub Login: @MGoedtel
• Microsoft Alias: magoedte

[KrishnaG-MSFT]

@ericcwk Thanks for the Comment. We are actively investigating and will get back to you soon.

[KrishnaG-MSFT]

Thanks for letting us know on this @ericcwk.
Looks like it is related to #6901 issue. Check if this can help you to resolve the issue.
In other words, the error "Pricing tier doesn't match the subscription's billing model. Read http://aka.ms/PricingTierWarning for more details" is seen if you try to create a log analytics workspace by opting pricing tier as "Per GB" (in Azure portal) or "PerGB2018" (in ARM template) by having your subscription currently in an older pricing model (with access to multiple pricing tiers). To resolve the error, change the monitoring pricing model from the subscription on the Pricing model selection page under Monitor > Usage and estimated costs.
Please find below screenshots for reference.

[KrishnaG-MSFT]

@ericcwk At this point it appears that there's no edits or updates needed for the documentation. Closing this issue for now. If there are further questions regarding this matter or questions or feedback on the documentation, please do let us know and we will gladly continue the discussion.