Microsoft Azure

We are investigating an alert where customers may see exceptions or errors during create or update operations on Azure SQL Managed Instance. We identified the root cause and applying mitigation steps to affected resources.We will provide more information as it becomes available. 

Starting at 08:10 UTC on 26 February 2026, a subset of customers using Azure SQL Managed Instance may experience failures during start, stop, or failover operations which led to temporary unavailability of their Azure SQL Managed Instance. We will provide more information as it becomes available.

We are investigating an alert for Azure Communication Services in Australia East and Southeast Asia. More information will be provided as it is known.

We are currently addressing an issue affecting a portion of the West US datacenter following an unexpected utility power interruption. Backup power systems remain active, and the facility has been fully operational since 12:30 UTC. Both power and physical network connectivity have been restored.Most services in the region are operating normally. Some resources that depend on the previously impacted datacenter may continue to experience degraded availability as storage and compute components complete their recovery.Our engineering and datacenter teams are actively validating the health of dependent systems and progressing recovery efforts.We will provide the next update in 60 minutes or sooner if conditions change.

Starting at 08:00 UTC, we became aware of a power outage affecting one of the datacenters in the West US region, resulting in service disruption across multiple Azure services for a subset of customers.Our engineering teams are actively investigating the underlying issue and working to mitigate the impact.As of 10:45 UTC, we have started to observe partial recovery in the region.We continue to monitor regional service health closely and will share more updates as soon as they become available.

Starting at 08:00 UTC, we became aware of an issue affecting multiple services for a subset of customers in the West US region.Our engineering teams are actively investigating and working to mitigate the service disruption impacting the region.We will provide more information as soon as it becomes available.

We are aware of an issue impacting a subset of customers in West US, Our Engineering team is actively investigating and working on mitigation. We will provide more information shortly.

Impact Statement: Starting at 08:00 UTC on 07 February 2026, a subset of customers using Azure services in the West US region may experience intermittent service unavailability or delays in monitoring and log data for some resources hosted in the affected datacenter areas. Impacted services include Web Apps, Application Insights, Azure Confidential Compute, Azure Container Registry, Azure Data Factory, Azure Database for MySQL – Flexible Server, Azure Databricks, Azure IoT Hub, Azure Kubernetes Service, Azure Monitor Essentials, Azure Search, Azure Site Recovery, Azure Stream Analytics, Azure Backup (MAB), and Service Bus. Impacted customers may observe degraded performance, reduced availability, or delayed telemetry as services continue to recover.Current Status: Restoration efforts are mostly complete with a very small subset of resources requiring manual recovery.Services Recovered and Healthy: App Services, Azure Defender for cloud, Azure Container Apps, Azure Kubernetes Service, Azure Storage, Azure Databricks, Azure Database for MySQL – Flexible Server, Azure SQL DW, Azure SQL Managed Instances, Azure Event Hub, Service Bus.Beyond this list, most of the affected downstream services in this region have recovered, with teams running final validations. Customers accessing these services should be observing operations resuming back to normal thresholds.Next Steps: We will continue with targeted communications being distributed via Azure Service Health

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.

Impact statement: We are aware of an ongoing issue causing customers to receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for Virtual Machines (VMs). These issues are also causing impact to services with dependencies on these operations, including Azure Arc Enabled Servers, Azure Batch, Azure DevOps, and GitHub. For details on the latter, please see https://www.githubstatus.com. Current status: We have determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We are actively working on mitigation, including updating configuration to restore relevant access permissions. Our next update will be provided by 22:30 UTC, approximately 60 minutes from now.

Impact statement: As early as 19:46 UTC on 2 February 2026, we became aware of an issue causing customers to receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for Virtual Machines (VMs) affecting multiple regions. These issues are also impacting services with dependencies on these service management operations - including Azure Arc Enabled Servers, Azure Batch, Azure Cache for Redis, Azure Container Apps, Azure DevOps (ADO), Azure Kubernetes Service (AKS), Azure Backup, Azure Load Testing, Azure Firewall, Azure Search, Azure Virtual Machine Scale Sets (VMSS), GitHub (see https://www.githubstatus.com)..Current status: We determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We have applied our mitigation across all impacted regions and have performed validation checks to ensure that all affected resources have had their configurations updated. At this stage, customers should see signs of recovery across regions. We are currently monitoring downstream services for any further impact. Our next update will be provided by 08:00 UTC, approximately 2 hours from now, or sooner if we have progress to share.

We have identified an issue in Network Infrastructure in North Central US for a subset of customers. More information will be provided by communications on Service Health section of the Azure Portal under the tracking ID FMGC-N_G.