Plans for GitHub Coding Agent for Azure DevOps (ADO) repos / work items?

[InDieTasten]

Select Topic Area

Question

Copilot Feature Area

Copilot Coding Agent

Body

I am really impressed with GitHub Coding Agent and would like to utilize it in our projects that are hosted in Azure DevOps.

Are there any plans to support Coding Agent on repos in ADO, and then possibly be able to assign Work Items from ADO Boards to the agent?

Or do I have to think about syncing repos between the two and integrating ADO WorkItems possibly via MCP to the coding agent?

I don't want to build an entirely new process and way of working in my ADO organization just for Microsoft to also enable a more native solution for ADO in a couple of months, similar to how GitHub Advanced Security is now featured in ADO as well.

[Akash1134]

Hello @InDieTasten,

Thank you for your question about GitHub Copilot Coding Agent for Azure DevOps repositories and work items.

Currently, the full Copilot Coding Agent experience (assigning issues and having the agent create PRs) is designed specifically for GitHub repositories. However, we're actively bridging this gap through:

1. Azure DevOps MCP Server (now in public preview): Enables GitHub Copilot to access and interact with Azure DevOps resources including work items, PRs, test plans, and more. Learn more here.

2. Repository migration tools: We've enhanced GitHub Enterprise Importer to simplify migration from Azure DevOps to GitHub while preserving history, branches, and metadata.

3. Azure DevOps + GitHub integration: Azure DevOps Basic usage rights are now included with GitHub Enterprise licenses, allowing seamless use of Azure Boards/Pipelines with GitHub repositories.

Your approach of exploring MCP integration is a valid interim solution. While we don't have a specific timeline for native Coding Agent support in Azure DevOps repositories, our direction is clear: enabling AI-powered development across our product ecosystem.

Is there a specific aspect of the Coding Agent functionality you're most interested in for your Azure DevOps workflow?

[InDieTasten]

Thank you for validating my approach, as well as hinting that a GitHub Coding Agent for ADO is in line with the current direction of development at GitHub/Microsoft.

The most interesting aspect of Coding Agent to me is by far its autonomy and natural interface. Assigning issues and reviewing PRs is a very natural and well-known workflow and doesn't require any additional training or adaption in the team and their tools (apart from perhaps stating requirements and expectations in a more explicit way in issues / work items, but I think that's a good direction even without leveraging AI).

We are not ready to move from ADO to GitHub. The ADO eco system is quite extensive, the Boards and Test Plans features, as well as all the market place extensions (many of which not available for GitHub) is locking us to ADO.

[rkalasky]

@Akash1134 could you expand on "allowing seamless use of Azure Boards/Pipelines with GitHub repositories." Is there a link to any docs on that? Wondering how deep that integration is. We're in a similar boat as @InDieTasten. Our code is hosted on ADO and we have significant pipeline investments over there but we're interested in taking further advantage of the agent capabilities.

[amer-5]

Hello @InDieTasten

At the moment, GitHub Copilot Coding Agent is primarily designed to work within GitHub repositories and workflows. Native support for Azure DevOps (both repos and Boards) hasn’t been announced yet, so today the options would be along the lines of syncing repos between GitHub and ADO, or connecting ADO Work Items through a custom integration (for example, using MCP or APIs).

That said, Microsoft has a history of bringing GitHub features into Azure DevOps over time—GitHub Advanced Security is a good example—so it’s very possible that deeper ADO integration for Copilot agents will come in the future. If your team’s process is tightly tied to ADO, it may be worth waiting to see what’s announced, rather than reinventing your workflows.

In short:

Today: Use GitHub repos directly, or sync/integrate ADO manually.

Future: Native ADO support may be added, but nothing official has been shared yet.

[Coops9]

But you are (somewhat) bringing this to Azure DevOps? well for DevOps work items - against Github repo code (I believe)

See post here: https://learn.microsoft.com/en-us/azure/devops/release-notes/roadmap/2025/boards/work-item-integration-with-github-coding-agent