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 7/13, 12:30 UTC. Our logs show the incident started on 7/13, 11:05 UTC and that during the 1 hour 25 minutes that it took to resolve the issue, some of customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts in Australia Southeast region.
- Root Cause: The failure was due to dependent backend service which Azure Log Analytics relies upon became unhealthy.
- Incident Timeline: 1 Hours & 25 minutes - 7/13, 11:05 UTC through 7/13, 12:30 UTC
-Ashok
We are aware of issues within Log Analytics and are actively investigating. Some customers using Log Analytics and Azure sentinel may experience data access issue and delayed or missed alerts in Australia South East.
- Work Around: None
- Next Update: Before 07/13 14:30 UTC
-Ashok
Published on:
Learn moreRelated posts
November Patches for Azure DevOps Server
Today we are releasing patches that impact our self-hosted product, Azure DevOps Server. We strongly encourage and recommend that all customer...
Configuring Advanced High Availability Features in Azure Cosmos DB SDKs
Azure Cosmos DB is engineered from the ground up to deliver high availability, low latency, throughput, and consistency guarantees for globall...
IntelePeer supercharges its agentic AI platform with Azure Cosmos DB
Reducing latency by 50% and scaling intelligent CX for SMBs This article was co-authored by Sergey Galchenko, Chief Technology Officer, Intele...
From Real-Time Analytics to AI: Your Azure Cosmos DB & DocumentDB Agenda for Microsoft Ignite 2025
Microsoft Ignite 2025 is your opportunity to explore how Azure Cosmos DB, Cosmos DB in Microsoft Fabric, and DocumentDB power the next generat...
Episode 414 – When the Cloud Falls: Understanding the AWS and Azure Outages of October 2025
Welcome to Episode 414 of the Microsoft Cloud IT Pro Podcast.This episode covers the major cloud service disruptions that impacted both AWS an...