Understand the automatic migration process for your classic alert rules

As previously announced, classic alerts in Azure Monitor are retired for public cloud users, though still in limited use until 31 May 2021. Classic alerts for Azure Government cloud and Microsoft Azure operated by 21Vianet will retire on 29 February 2024.

A migration tool is available in the Azure portal for customers to trigger migration themselves. This article explains the automatic migration process in public cloud, that will start after 31 May 2021. It also details issues and solutions you might run into.

Important things to note

The migration process converts classic alert rules to new, equivalent alert rules, and creates action groups. In preparation, be aware of the following points:

What will happen during the automatic migration process in public cloud?

  • Starting 31 May 2021, you won't be able to create any new classic alert rules and migration of classic alerts will be triggered in batches.

  • Any classic alert rules that are monitoring deleted target resources or on metrics that are no longer supported are considered invalid.

  • Classic alert rules that are invalid will be removed sometime after 31 May 2021.

  • Once migration for your subscription starts, it should be complete within an hour. Customers can monitor the status of migration on the migration tool in Azure Monitor.

  • Subscription owners will receive an email on success or failure of the migration.

    Note

    If you don't want to wait for the automatic migration process to start, you can still trigger the migration voluntarily using the migration tool.

What if the automatic migration fails?

When the automatic migration process fails, subscription owners will receive an email notifying them of the issue. You can use the migration tool in Azure Monitor to see the full details of the issue. See the troubleshooting guide for help with problems you might face during migration.

Note

In case an action is needed from customers, like temporarily disabling a resource lock or changing a policy assignment, customers will need to resolve any such issues. If the issues are not resolved by then, successful migration of your classic alerts cannot be guaranteed.

Next steps