Microsoft Adds Azure DevOps Plugin to the GitHub Copilot App

Azure DevOps work moves into the GitHub Copilot app

Microsoft announced on August 27, 2026 that an Azure DevOps plugin is now available for the GitHub Copilot app. This is an initial released integration rather than a future roadmap item, although Microsoft describes the extension as being in its early stages and says its functionality is currently limited.

The first version lets users view assigned work items and pull requests from My Work, open those records, edit work items, and edit or complete pull requests without leaving the Copilot app. Microsoft says the plugin can be installed from the app's Customize area under Editor's picks, after which users sign in and provide their Azure DevOps organization and project information.

Why the integration matters

The release links two workflows that have often been split across products: conversational or agentic work in GitHub Copilot and planning/repository activity in Azure DevOps. For teams that still use Azure Boards or Azure Repos, the plugin provides a direct path to manage day-to-day work from the Copilot app rather than requiring a repository migration before basic Azure DevOps records can be handled there.

GitHub's current Copilot app documentation also supports connecting projects hosted outside GitHub by repository URL, including Azure DevOps repositories. That broader app capability is separate from this new plugin: the plugin specifically adds an Azure DevOps work surface for pull requests and work items.

Released now, but still an early integration

The key status distinction is important. Microsoft says the plugin is available now, but it also explicitly calls the Azure DevOps app extension early-stage and limited. The announcement does not claim full Azure DevOps feature parity, autonomous end-to-end project management, or broad support for every Azure Boards, Repos and Pipelines workflow.

For engineering organizations evaluating the integration, the practical test is therefore narrow: whether the current pull-request and work-item actions reduce context switching enough to be useful today. Teams should also review their existing Azure DevOps permissions and organizational policies before enabling connected AI workflows.

Microsoft says it plans to add more capabilities over time, but it did not commit to a specific timetable in the announcement.