Azure-docs: Should be marked as Deprecated or Obsolete - can no longer create "Classic" alerts, and they will stop working in June 2020.

[Zhaph]

I attempted to run an ARM template containing some "Classic" alerts this afternoon which failed with the notice that:

> As part of classic alerts retirement, starting Sep 01, 2019, no new classic alerts can be created except on a few metrics listed here https://aka.ms/classic-alerts-exceptions. All classic alerts including the exceptions listed will stop working after June 2020. It is strongly recommended to use new metric alerts. See https://aka.ms/create-metric-alerts.

Following the link to "Create Metric Alerts" takes me to Create, View and Manage Metric Alerts with options to create through the portal or Azure CLI. Following the link in Next Steps on that page for "Create metric alerts using Azure Resource Manager Templates" brings me here - which is what I was trying to create.

---

Document Details

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

• ID: c3b9fa00-b319-daa4-3bd5-1f83f96590d4
• Version Independent ID: 69d25f7e-30e4-0c6a-1d67-25e282d71a3c
• Content: Create a classic metric alert in Azure with a Resource Manager template - Azure Monitor
• Content Source: articles/azure-monitor/platform/alerts-enable-template.md
• Service: azure-monitor
• Sub-service: alerts
• GitHub Login: @rboucher
• Microsoft Alias: robb

[BharathNimmala-MSFT]

@Zhaph Thank you for your feedback, we will look into it and get back to you at the earliest.

[rboucher]

Agreed. New text will be "This article describes creating classic metric alerts using Resource Manager templates. Classic alerts were retired in August 2019. You cannot create new one in public Azure. Some regional versions of Azure may still have the option. Instead, create newer metric alerts using templates. This article provides the details." @harelbr

[rboucher]

Actually updated language to be even stronger. Should be out in the next week if not sooner. Thanks for your comment @Zhaph

[BharathNimmala-MSFT]

@rboucher Thank you for helping enhance the document.

@Zhaph Thanks again for sharing your feedback. Closing this issue for now, feel free to revert back if you have any further queries and will be happy to reopen the thread and continue the conversation.

[rboucher]

update due out around 11am Pacific time 3/10/2020