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
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