Experiencing Data Access Issue in Azure portal for Log Analytics - 07/13 - Resolved
We've confirmed that all systems are back to normal with no customer impact as of 07/13 02:35 UTC. Our logs show the incident started on 07/13 01:30 UTC and that during the 1 hours & 5 minutes that it took to resolve the issue some customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts in North Central US region.
- Root Cause: The failure was due to dependent backend service which Azure Log Analytics relies upon became unhealthy.
- Incident Timeline: 1 hour 5 minutes - 7/13, 01:30 UTC through 7/13, 02:35 UTC
-Samuel Durodolu
Published on:
Learn moreRelated posts
Fundamentals of Azure DevOps with SQL projects
Building automated pipelines with your SQL database projects enables you to build a rich CI/CD ecosystem to ensure that your application is be...
Upcoming Change: NTLM Removal in Git (libcurl) – Impact to Azure DevOps Server Customers
Overview In September 2026, NTLM support will be removed from libcurl, which is used by Git for HTTP(S) operations. As a result, Git operation...
What’s new across Microsoft SQL in 2026 so far (SQL Server, Azure SQL, and SQL database in Fabric)
We’re halfway through 2026, and Microsoft SQL has not slowed down. Since SQLCon/FabCon in March (where we released a ton of things, and those ...
Power Automate Flow — HTTP Trigger to Azure OpenAI
Build the secure Power Automate HTTP trigger flow that receives free text from the portal, calls Azure OpenAI using your smart-form-extract de...
Spring AI 2.0 is GA: Vector Search, Memory, and Agents on Azure Cosmos DB
The wait is over. Spring AI 2.0 is generally available, and Azure Cosmos DB is right there with it. With this release, Spring AI graduates int...