Experiencing Data Access Issue in Azure portal for Azure monitor – 01/23 – Resolved

This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.

Final Update: Thursday, 23 January 2020 22:45 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/23, 22:00 UTC. Our logs show the incident started on 01/23, 08:00 UTC and that during the 13 hours that it took to resolve the issue some customers in Southcentral US and West US region experienced issues loading certain blades in Azure portal for Azure monitors.
  • Root Cause: The failure was due to a configuration change in one of the hosting stamps.
  • Incident Timeline: 13 hours - 01/23, 08:00 UTC through 01/23, 22:00 UTC
We understand that customers rely on Azure monitor as a critical service and apologize for any impact this incident caused.


Update: Thursday, 23 January 2020 22:04 UTC

We continue to investigate issues within Azure monitor. We are currently working on establishing root cause for the issue. Some customers continue to experience issues while loading certain blades in Azure portal. We are working to establish the start time for the issue, initial findings indicate that the problem began at 01/23 ~08:00 UTC. We will continue providing updates on the developments.
  • Work Around: None
  • Next Update: Before 01/24 00:30 UTC

Initial Update: Thursday, 23 January 2020 20:10 UTC

We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues while loading Logs blade on Log analytics workspaces.
  • Work Around: None
  • Next Update: Before 01/23 22:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.

REMEMBER: these articles are SYNDICATED. Your best bet to get a reply is to follow the link at the top of the post to the ORIGINAL post! BUT you're more than welcome to start discussions here:

This site uses Akismet to reduce spam. Learn how your comment data is processed.