We've confirmed that all systems are back to normal with no customer impact at present. Our logs show the incident started on 01/08, 23:00 UTC and that during the 13 days that it took to resolve the issue customers experienced issues while creating Azure monitor metric alerts with aggregation max and min.
Root Cause: Engineers determined that a deployment task introduced a configuration change which failed to include certain scenarios needed for these specific Azure Metrics Alerts.
Incident Timeline: 13 days - 01/08, 23:00 UTC through 1/21, 16:40 UTC
We understand that customers rely on Metric Alerts as a critical service and apologize for any impact this incident caused.
Update: Tuesday, 21 January 2020 11:37 UTC
Hotfix deployment is still in process. Some customers may still experience issues while creating Azure monitor metric alert with aggregation max or min. Initial findings indicate that the problem began from 01/08 23:00 UTC.
Work Around: None
Next Update: Before 01/22 00:00 UTC
Update: Monday, 20 January 2020 23:21 UTC
Root cause has been isolated to previous deployment which was impacting creating alerts with aggregation max or min. To address this issue engineers are working on deploying a fix. Some customers may experience issues while creating alerts with aggregation max or min. We estimate ~12 hours before this issue is addressed.
Work Around: none
Next Update: Before 01/21 11:30 UTC
Initial Update: Monday, 20 January 2020 11:17 UTC
We are aware of issues within Metric Alerts and are actively investigating. Some customers may experience failures in creating Azure Monitor metric alert with aggregations Max or Min.
Work Around: None
Next Update: Before 01/20 23:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience. -Anmol