This article is contributed. See the original author and article here.
Final Update: Saturday, 30 January 2021 00:45 UTC
We’ve confirmed that all systems are back to normal with no customer impact as of 1/30, 00:30 UTC. Our logs show the incident started on 1/29, 02:00 UTC and that during the 22 hours and 30 minutes that it took to resolve the issue some customers could have experienced Data Latency with Activity Logs that are generated from Azure Resource manager as well as delayed Activity Log Alerts.
-Eric Singleton
We’ve confirmed that all systems are back to normal with no customer impact as of 1/30, 00:30 UTC. Our logs show the incident started on 1/29, 02:00 UTC and that during the 22 hours and 30 minutes that it took to resolve the issue some customers could have experienced Data Latency with Activity Logs that are generated from Azure Resource manager as well as delayed Activity Log Alerts.
- Root Cause: The failure was due to a backend dependency.
- Incident Timeline: 22 Hours & 30 minutes – 1/29, 02:00 UTC through 1/30, 00:30 UTC
-Eric Singleton
Update: Friday, 29 January 2021 22:27 UTC
Root cause has been isolated to a misconfiguration from a backend dependency. To address this issue the team is currently implementing a hotfix to decrease the latency. Some customers may experience Data Latency with Activity Logs that are generated from Azure Resource Manager as well as delayed Activity Log Alerts.
Root cause has been isolated to a misconfiguration from a backend dependency. To address this issue the team is currently implementing a hotfix to decrease the latency. Some customers may experience Data Latency with Activity Logs that are generated from Azure Resource Manager as well as delayed Activity Log Alerts.
- Work Around: None
- Next Update: Before 01/30 02:30 UTC
Initial Update: Friday, 29 January 2021 20:36 UTC
We are aware of issues within Activity Logs and are actively investigating. Some customers may experience Data Latency with Activity Logs that are generated from Azure Resource Manager. Investigation points to a start time of 1/29 02:00 UTC.
-Eric Singleton
We are aware of issues within Activity Logs and are actively investigating. Some customers may experience Data Latency with Activity Logs that are generated from Azure Resource Manager. Investigation points to a start time of 1/29 02:00 UTC.
- Work Around: None
- Next Update: Before 01/29 23:00 UTC
-Eric Singleton
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
Recent Comments