Feature Request: Native Azure DevOps (Azure Repos) Integration for Codex
What variant of Codex are you using?
Web
What feature would you like to see?
Summary
Please add native support for Azure DevOps Git repositories (Azure Repos) in Codex, comparable to the existing first-class GitHub integration.
Problem Statement
Codex currently provides native, seamless integration with GitHub repositories, enabling workflows such as repository access, branch analysis, pull request creation, and code review automation.
However, many enterprise and public-sector organizations rely on Azure DevOps (Azure Repos) as their primary source control system. The lack of native Azure Repos support prevents these teams from adopting Codex in their standard development workflows.
Today, users must rely on manual workarounds (local clones, scripts, or intermediate mirrors to GitHub), which:
• Break enterprise security and compliance models
• Increase operational complexity
• Reduce the effectiveness of Codex in CI/CD and PR-based workflows
• Limit adoption in Microsoft-centric environments
Requested Capability
Enable Codex to operate natively on Azure DevOps Git repositories, with parity to GitHub integration features, including (but not limited to):
• Secure authentication via Microsoft Entra ID (Azure AD) and/or Azure DevOps PAT
• Read/write access to Azure Repos
• Branch creation and management
• Pull Request creation, updates, and reviews
• Access to PR comments, discussions, and diffs
• Repository-scoped permissions aligned with Azure DevOps security models
• Compatibility with Azure DevOps projects, organizations, and multi-repo setups
Expected Benefits
• Enables Codex adoption in enterprise and regulated environments
• Aligns Codex with Microsoft-centric development stacks (Azure, DevOps, Entra ID)
• Eliminates the need for insecure or inefficient workarounds
• Improves developer productivity in organizations already standardized on Azure DevOps
• Expands Codex’s reach beyond GitHub-only ecosystems
Target Users
• Enterprise engineering teams
• Public sector and government organizations
• Companies using Azure DevOps for CI/CD, Boards, and Repos
• Teams with compliance requirements preventing GitHub usage
Additional Notes
Azure OpenAI and Microsoft Foundry already provide enterprise-grade hosting for Codex models. Native Azure Repos integration would be a natural and strategic extension, completing the end-to-end Azure developer experience.
Priority
High — this feature is a key blocker for Codex adoption in many enterprise environments.
Additional information
_No response_
26 Comments
Plus one to this request, I need this like yesterday.
Plus one this would be really useful
Plus one
Yes please!
Plus one here.
plus one
Very much agree with this post. We are looking to incorporate AI into the SDLC and create workflows but the lack of integration with Azure DevOps reduces how impactful codex can be in the org.
plus 1000!
plus 1001! :)
plus 1002!
It's really surprising how much money OpenAI is leaving on the table by not having first class Azure DevOps (at least Repos) integration.
There are more private enterprises using ADO with private repos, than even have a GitHub account. GH only got "popular" for private repos in the last few years after Microsoft started really pushing new advanced features on that side of things. Yes ADO has lagged behind on that, but as far as I am aware, ADO adoption has not declined. ADO has a reputation as a very stable and reliable platform and that is why companies trust it.
They don't even need Microsoft's permission to do this. The level of enrichment you could deliver for ADO with PR review automations, etc, is quite unprecedented. There are very few other tools on the market for ADO that could do what OpenAI could do in a very short space of time.
Plus one
+1
Plus one
+1
+1
+1
+1
+1
+1
+1
+1
A native integration with Azure Repos is dearly needed. This is even more important taking recent GitHub issues into account.
+1
+1
+1