Azure Devops Outage History

Azure DevOps users experienced intermittent 500 failures for Maven packaging operations in Azure Artifacts when feeds were configured to upstream to Maven Central, affecting multiple regions globally. The issue was caused by traffic volume and limit problems with the Maven Central upstream provider. The incident lasted 1.7 hours and was resolved through engagement between the Azure Artifacts engineering team and the public package provider to address the traffic constraints.

Azure DevOps experienced an availability degradation incident affecting other services in the United States region for 36 minutes. Engineers investigated and triaged the event during the outage period. The incident was classified as minor and has been resolved.

Azure DevOps experienced availability degradation affecting other services in the United States region for 1 hour. Engineers investigated and triaged the incident during this period. The service has since been restored to normal operation.

Azure DevOps experienced availability degradation affecting core services in the Canada region for 44 minutes. The incident impacted service availability while engineers investigated and triaged the event. The service was restored after the 44-minute outage period.

Azure DevOps Managed DevOps Pools stopped acquiring VMs for 9.8 hours, causing pipeline failures across multiple regions including the US, Canada, Europe, and Asia Pacific. The issue specifically affected pools using Ubuntu images with custom networking, initially triggered by a Canonical outage that impacted customers with network allowlisting configurations. Microsoft resolved the incident by advising affected customers to allowlist access to azure.archive.ubuntu.com and switch from subnet delegation to isolated VNets as a temporary workaround.

Azure DevOps experienced an availability degradation incident affecting other services in the United States region for 52 minutes. Engineers investigated and triaged the event during the outage period. The incident was classified as minor severity and has been resolved.

Azure DevOps experienced a 3.1-hour availability degradation in the East US region that caused intermittent issues with users fetching and updating profile information. The incident affected the User service and other related services across the United States. Engineers investigated and resolved the issue, with the User service returning to normal state.

Azure DevOps experienced availability degradation affecting the Artifacts component in the Europe region for 52 minutes. Engineers investigated and triaged the incident during this period. The service has since been restored to normal operation.

Azure DevOps experienced delays in build job execution across multiple regions including Europe, Asia Pacific, and India, affecting the Pipelines component for 1.7 hours. Engineers identified and mitigated the root cause, with significant improvement observed. The system was restored to normal operation with continued monitoring.

Azure DevOps customers experienced VsTest failures in distributed test flows due to a System.IO.FileNotFoundException related to the System.Collections.Immutable assembly when using Microsoft.TestPlatform version 18.5.0. The issue affected testing services globally across all regions for 44 minutes. The problem was resolved through coordination with the publishing team, with customers advised to either switch to single agent VsTest flow or revert to earlier Microsoft.TestPlatform versions as workarounds.