❌

Normal view

There are new articles available, click to refresh the page.
Before yesterdayMain stream

Active - Managed Service Identity and depended service operation failure in East US and West US

2 February 2026 at 19:15

Impact Statement: Beginning at 00:15 UTC on 03 February 2026, customers utilizing Managed Identity for Azure resources may have encountered issues when trying to create, update, delete, or acquire tokens in the East US and West US regions. These errors impacted dependent services such as Azure Synapse Analytics, Azure Databricks, Azure Stream Analytics, Azure Kubernetes Service, Microsoft Copilot Studio, Azure Chaos Studio, Azure Database for PostgreSQL Flexible Servers, Azure Container Apps, and Azure AI Video Indexer. Please be aware that this is not an exhaustive list of affected services, and further updates will be provided as additional information is obtained.

Current Status: The underlying Managed Identity service has been stabilized, and key mitigation actions-including targeted service restarts and controlled traffic throttling-have been successfully applied.

As a result, most customer workloads are now recovering, and traffic is being safely and gradually ramped up to normal levels while we continue close monitoring. While core functionality has largely been restored, a small number of dependent workloads may still experience intermittent delays or retries as the environment continues to fully stabilize.

We will continue to actively monitor all dependent services and address any remaining tail issues.

The next update will be provided within 60 minutes, or as events warrant.

Multi-service impact in Switzerland North

26 September 2025 at 20:03

Impact Statement:Β Starting at 23:54 UTC on 26 September 2025, customers in Switzerland North may experience service unavailability or degraded performances for resources hosted in the region. Virtual Machines may have shutdown to preserve data integrity.Β 

Current Status:Β We were alerted to this issue by our telemetry informing us in a significant drop in traffic. It was discovered that a recent deployment introduced a malformed prefix in one of the certificates used for connection authorization. We have pinpointed the deployment error involving the certificate prefix and are rolling back the faulty deployment to restore normal traffic flow and service availability.

Majority of the impacted services have been fully recovered, and a subset are nearing completion. We continue to monitor traffic and service stability to ensure full recovery.

❌
❌