We are excited to announce that OpenHands Enterprise now supports Azure DevOps. Any user within an Organization in OpenHands Enterprise can sign in with their Microsoft Entra ID credentials, open Azure Repos directly in OpenHands, and trigger AI-powered development workflows from Azure Boards work items or pull request comments.

This integration brings three core capabilities to your Azure DevOps environment: seamless single sign-on via Microsoft Entra ID, direct access to Azure Repos with branch and pull request creation, and AI-powered workflows triggered from work items and PR comments.

Why we built this

Teams using Azure DevOps often work across multiple Microsoft tools and need seamless authentication without managing additional passwords. By integrating with Microsoft Entra ID, OpenHands leverages your existing identity infrastructure for secure, compliant access.

Previously, developers had to switch between tools—authenticating separately, finding repositories, manually cloning code, and re-explaining context to yet another tool. Now, everything happens directly where your team already works, with Azure Boards and Azure Repos as the starting point for developing with OpenHands.

Sign in with Microsoft Entra ID

OpenHands Enterprise supports signing in with your Microsoft Entra ID credentials through Azure DevOps authentication. Once an administrator configures the integration, users simply click "Sign in with Azure DevOps" on the login page.

This leverages your existing Microsoft identity infrastructure—no additional passwords to manage, and access is automatically enforced based on each user's Entra ID and Azure DevOps permissions. OpenHands uses OAuth 2.0 to authenticate, ensuring secure, token-based access without sharing credentials.

Access Azure Repos and Create Pull Requests

After signing in, users can select Azure DevOps repositories directly from the OpenHands repository picker. OpenHands can list Azure DevOps projects and repositories available to the signed-in user, clone repositories using their OAuth token, and read branch and pull request context.

Most importantly, OpenHands can create branches and pull requests directly in your Azure Repos. This means developers can delegate implementation work to OpenHands and have changes automatically submitted back for review—no manual Git operations required.

Repository references use the format organization/project/repository, making it easy to identify and access the right repos across your Azure DevOps organization.

Trigger OpenHands from Azure DevOps

OpenHands can be triggered from Azure DevOps through Azure Boards work item comments or Azure Repos pull request comments. This brings AI-powered development directly into your existing Azure DevOps workflow.

Use cases include asking OpenHands to create an implementation pull request from a work item, review a pull request directly in Azure Repos, generate tests or validation evidence, or inspect pipeline logs and propose a fix for incidents.

OpenHands reads the work item or pull request context—including descriptions, comments, and code changes—and responds back to Azure DevOps when the job starts and completes. Developers stay in their familiar Azure DevOps environment while benefiting from AI-assisted development.

Getting Started

Organization administrators can configure the Azure DevOps integration in the OpenHands Enterprise Admin Console. Once configured, the integration is immediately available to all users in the organization.

For setup instructions, visit the Azure DevOps integration guide in our documentation.