classic alerts fail to deploy (for example 301-insights-alertrules-application-insights.json)

{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"BadRequest","message":"{\r\n \"code\": \"BadRequest\",\r\n \"message\": \"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. \"\r\n}"}]}

Start with 301-insights-alertrules-application-insights.json and reproduce the deployment failure described in the issue. Read the linked classic-alert retirement and metric-alert guidance to determine the required replacement or removal; done means the affected template deploys without the classic-alert BadRequest.

Written by the indexing model from the issue text.