Mitigated: Failures and slowness across multiple Azure Devops experiences and geographies

Our engineering team has applied a mitigation to the impacted database that is improving availability for customers. We are continuing to monitor our services to ensure the issue is fully mitigated.

We continue to investigate failures and slowness across multiple Azure DevOps experiences impacting multiple geographies. The primary impacts seem to be failures and slowness with Personal Access Token (PAT) usage and Azure Pipelines jobs failing to start or run jobs. Unfortunately there are no known workarounds. Database performance in a service responsible for generating and authenticating tokens, including Personal Access Tokens and Pipeline session tokens, is the underlying problem. We are investigating multiple mitigation paths and will continue to post updates as we learn more.

Our engineers are currently investigating an issue with failures and slowness across multiple Azure DevOps experiences and all geographies. The impact is failures and slowness in Azure Pipelines jobs starting or running jobs, as well REST usage with Personal Access Tokens (PATs). We will continue to investigate and post additional updates as we learn more.

Customers might experience failures or slowness across multiple Azure DevOps experiences, in particular when using PATs. Our engineers are currently investigating the issue.