Azure Devops Outage History

Azure DevOps experienced a 4.8-hour availability degradation affecting Azure Pipelines running on VMSS (Virtual Machine Scale Set) pools in the United States, where customers encountered problems with scaling pools in and out. Engineers identified the issue with VMSS Elastic Pool scaling and applied mitigations and fixes to restore service. Full recovery was achieved after the fixes were implemented, with some customers seeing recovery before complete resolution.

Azure DevOps experienced availability degradation in the Central US region for 3.2 hours, affecting Boards, Repos, Pipelines, and Test Plans services. Users encountered intermittent slowness, failed requests, slow page loads, and failed API calls across all affected components. Engineers investigated and resolved the incident, which was suspected to be related to a networking dependency in the region.

Azure DevOps experienced performance degradation affecting users in Sweden, Denmark, and Finland on April 8th, 2026 between 10:00 and 14:00 CET. The incident impacted all major components including Pipelines, Repos, Boards, Test Plans, Artifacts, and Core services across European regions. The degradation lasted 5.3 hours and was related to ongoing work to improve Azure DevOps failover capabilities.

Azure DevOps experienced access issues for customers using Microsoft Defender for Cloud, affecting core services across multiple regions including Europe, United States, Asia Pacific, Australia, India, Brazil, Canada, and United Kingdom. The incident lasted 3.1 hours and was resolved after Microsoft identified and incrementally rolled out a mitigation.

Azure DevOps pipelines failed to trigger from GitHub events for 3.2 hours, affecting customers globally across all major regions. The issue was caused by disrupted messaging between GitHub and Azure DevOps services. Engineers restored the messaging connection and processed the backlog of events, returning pipeline triggering to normal operation.

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

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

Azure DevOps experienced a degradation in the User Extension (UserExt) service in the UK South region for 2.4 hours. Users encountered intermittent delays and failures in user-related operations including identity resolution, loading user information in the UI, and performing actions requiring user access checks. The incident was resolved after engineers completed their investigation and mitigation efforts.

Azure DevOps experienced availability degradation in Central US affecting Boards, Repos, Pipelines, and Test Plans for 1.2 hours. Engineers identified the root cause and executed mitigation to resolve the impact on customers. The service was restored with continued monitoring to ensure system stability.

Azure DevOps experienced availability degradation in Central India affecting a small portion of users for 2.1 hours. The incident impacted Boards, Repos, Pipelines, and Test Plans services in the India region. Engineers identified the root cause and implemented a mitigation that required approximately 60 minutes to complete.