Azure DevOps & GitHub Connectivity Incident: Pipelines Service Connection Failures
Summary
A widespread incident is impacting the connection between GitHub and Azure DevOps Pipelines. Numerous users are reporting error messages such as “connection service is…”, preventing the execution of CI/CD pipelines.
What happened?
Since the morning of June 1, 2026, reports have been accumulating in the Microsoft Developer Community regarding authentication and connectivity issues between GitHub and Azure DevOps. Affected teams are unable to run pipelines that access GitHub repositories.
Why it matters
CI/CD pipelines are the backbone of modern software development. A failure of these connections leads to immediate halts in the delivery pipeline, prevents deployments, and significantly impacts the productivity of global development teams.
Evidence
The Microsoft Developer Community lists several threads on this topic. Users consistently report errors when creating work items and running pipelines. Legacy projects under .visualstudio.com seem particularly affected, but modern setups are also involved.
Analysis
The error descriptions suggest a problem in the underlying infrastructure of service connections or an unannounced API change. As official status updates from Microsoft are still pending, it is likely a deep technical issue in the communication layer.
Practical Takeaways
- Monitor official Azure and GitHub status pages.
- Check existing service connections for validity.
- Consider using Personal Access Tokens (PAT) as a temporary workaround if OAuth-based connections fail.
Open Questions
- Is a specific regional update the cause?
- When will an official fix be provided by Microsoft?
- Are other integrations (e.g., Jira or Bitbucket) also affected?