Experienced Management Operation failures for Activity Log Alert Rules - 10/22 - Resolved
Final Update: Thursday, 22 October 2020 09:24 UTC We've confirmed that all systems are back to normal with no customer impact as of 10/22, 08:30 UTC. Our logs show the incident started on 10/22, 01:30 UTC and that during the 7 hours that it took to resolve the issue some customers may have experienced failure notifications when accessing or performing service management operations for Azure Activity Log Alert Rules. Root Cause: The failure was due to issues with one of our dependent services. Incident Timeline: 7 Hours - 10/22, 01:30 UTC through 10/22, 08:30 UTC We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused. -SandeepExperiencing Data Access in Activity Log Alerts rules and Activity Logs- 09/29 - Resolved
Final Update: Tuesday, 29 September 2020 15:44 UTC We've confirmed that all systems are back to normal with no customer impact as of 09/29, 13:50 UTC. Our logs show the incident started on 09/29, 03:30 UTC and that during the 10 hours 20 Minutes that it took to resolve, Some customers may have received failure notifications when accessing or performing service management operations such as create, update, delete for Azure Activity Log Alert Rules and have issues while viewing Activity Logs in the azure Portal. Root Cause: The failure was due to issue with Azure Active Directory service. Incident Timeline: 10 Hours & 20 minutes - 09/29, 03:30 UTC through 09/29, 13:50 UTC We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused. -VamshiExperiencing Data Latency in Azure portal for Activity Log Alerts - 06/04 - Resolved
Final Update: Thursday, 04 June 2020 19:20 UTC We've confirmed that all systems are back to normal with no customer impact as of 6/4, 18:54 UTC. Our logs show the incident started on 6/4, 12:05 UTC and that during the 6 hours and 49 minutes that it took to resolve the issue customers experienced delayed log search alerts by up to 2.5 hours. Root Cause: The failure was due to the service reaching an operating limit as a result of large unexpected spike in alert notifications across regions. Incident Timeline: 6 Hours & 49 minutes - 6/4, 12:05 UTC through 6/4, 18:54 UTC We understand that customers rely on Activity Log Alerts as a critical service and apologize for any impact this incident caused. -Jeff Update: Thursday, 04 June 2020 17:06 UTC Root cause has been isolated to an extremely large spike in log search alerts across multiple regions which was impacting activity log alerts ability to process alerts in a timely manner. To address this issue we have scaled out the service and the primary incident causing the spike has been mitigated. Some customers may continue experience delayed log search alerts of up to 2 hours. We estimate 2-3 hours before timely log search alerts are being processed again. Work Around: None Next Update: Before 06/04 21:30 UTC -Jeff Initial Update: Thursday, 04 June 2020 13:18 UTC We are aware of issues within Activity Log Alerts and are actively investigating. Some customers may experience delayed alerts. Alerts would have eventually fired. Work Around: None Next Update: Before 06/04 17:30 UTC We are working hard to resolve this issue and apologize for any inconvenience. -AnmolExperiencing Delayed alerts issue in Azure Portal in East US2 and Central US - 05/19 - Resolved
Final Update: Tuesday, 19 May 2020 08:38 UTC We've confirmed that all systems are back to normal with no customer impact as of 5/18, 18:34 UTC. Our logs show the incident started on 5/18, 17:35 UTC and that during the 59 minutes that it took to resolve the issue some of customers may have experienced issues with delayed alerts in East US2 and Central US regions. Root Cause: The failure was due to an issue in one of our dependent services. Incident Timeline: 59 minutes - 5/18, 17:35 UTC through 5/18, 18:34 UTC We understand that customers rely on Azure Monitor Alerts as a critical service and apologize for any impact this incident caused. -Madhuri