A white lock cottage beside a canal, with the lock in the distance and still water in the foreground

Microsoft announced a public preview of Azure DevOps integration in the GitHub Copilot app

On November 19, the Azure DevOps blog announced the public preview of Azure DevOps integration in the Copilot app. Dan Hellem, a product manager for Azure DevOps, writes that you can start agent sessions that work directly with your Azure DevOps repositories to create branches, make code changes, commit changes, and open pull requests. The on-page date is November 19th, 2026, and the published timestamp is 2026-11-19T17:39:09+00:00, which is 10:39 a.m. America/Phoenix.

I haven’t installed the GitHub Copilot app, and I haven’t connected an Azure Repos repository. This is what the announcement and the current official GitHub docs say.

Cream-paper schematic: a desktop-app pane with an agent node, an arrow into a repo pane with a folder, a branch fork, and a pull-request document, then a diamond merge gate with a token shape underneath
The Azure DevOps blog and the official GitHub docs describe Copilot app agents working in Azure Repos, then opening pull requests that Agent Merge can complete when checks and policies pass. Original schematic by Tech & AI Pulse.

What Microsoft says shipped in the preview

The post describes the GitHub Copilot app as a standalone desktop application that lets developers delegate coding tasks to AI agents: exploring a codebase, implementing changes, fixing bugs, and creating pull requests. With the Azure DevOps integration, Hellem writes, you can now use those capabilities with repositories hosted in Azure Repos. Agents can create branches, make code changes, commit changes, and open pull requests. Multiple agent sessions can also run in parallel, the post says, so different tasks can progress at the same time.

The app also provides a place to review code, add comments, and manage pull requests. With Agent Merge, the post says, agents can monitor pull requests, address review comments, resolve CI issues, and automatically merge changes when they’re ready.

To turn the integration on, the post says you go to Settings, then Experimental, and enable Azure DevOps integration. It also recommends enabling the Azure DevOps Remote MCP Server: from Customize, then Installed, you add a server, choose Azure DevOps, and you can optionally enter your Azure DevOps organization name. That’s the blog’s recommendation, not a setup I ran, and it’s optional in the announcement.

Getting started, the post says: create a new session, select Add from Azure DevOps, and choose the repository you want to work with. Once it’s connected, you can ask Copilot questions about the repository or give an agent a coding task, then review the changes and manage the pull request in the app.

What’s next is explicitly planned, not part of this preview. Hellem lists the ability to view and open work items, start coding sessions directly from work items, and Projects support. Throughout the public preview, the post says, Microsoft will keep addressing existing gaps and expanding support. If you hit issues, the post points you to the Copilot app’s GitHub issue tracker.

What the official GitHub docs add

GitHub’s how-to, Managing Azure DevOps work with the GitHub Copilot app, repeats that the integration is in public preview and subject to change. It says Copilot Business, Copilot Enterprise, or Copilot Individual users can use the feature.

The docs list the prerequisites: the Copilot app, installed and signed in, and a Microsoft account with access to the Azure DevOps organization, project, and repository you want to work with. Cloud sessions aren’t available for Azure DevOps repositories. For Copilot Business and Copilot Enterprise users, the organization or enterprise administrator must keep the GitHub Copilot app policy enabled. And, the docs say, “Azure DevOps permissions apply to every action you take through the integration. Connecting your account does not grant additional access to repositories or pull requests.”

The integration is disabled by default. You enable it under Experimental in the app settings, then add a Microsoft account if it isn’t there already. To add a repository, the docs say you choose Add Azure DevOps repository in the sidebar, type your organization name, select a repository, and follow the prompts to clone it. From there you can start an agent session. The agent can create a branch, make code changes, commit them, and open a pull request. You review those changes in the app. The docs also say the agent’s tools follow your session’s tool permissions, and depending on your settings, actions such as creating a pull request or replying to and resolving review threads can run without another prompt.

For finishing a pull request, the docs describe a manual path — review the changes, then Complete, then confirm the merge — and an Agent Merge path. If you enable Agent Merge for a pull request, GitHub says the agent can address review feedback, fix CI failures, resolve conflicts, and complete that pull request when Azure DevOps checks and policies pass. After you enable it for the pull request, “the agent can complete it without a separate confirmation.” Your Azure DevOps permissions and the repository’s configured checks and policies still determine whether that pull request can be completed.

Security caveats the docs actually spell out

This is write access to real repositories, in a public preview, and the docs are blunt about the limits.

The integration does not provide a setting to restrict it to selected repositories. Access to individual repositories and actions continues to be governed by Azure DevOps permissions. The GitHub Copilot app does not provide a separate audit log for the integration. Actions appear in Azure DevOps under the signed-in user’s name.

Azure DevOps content returned to the agent can enter the selected model’s context, the docs say. That can include private code, pull request descriptions and diffs, review comments, and excerpts from build logs. Content that appears in chat or tool results is retained in local session history. Signing out of your Microsoft account in the app removes the locally stored authentication tokens, but does not revoke access with Microsoft. To revoke access, GitHub says to use your Microsoft Entra account controls.

I’d treat the Microsoft account, organization name, repository permissions, and Agent Merge as things you turn on deliberately. Agent Merge can complete a pull request without a separate confirmation once you’ve enabled it for that pull request and the checks and policies pass. The Azure DevOps blog’s optional Remote MCP Server is another connection that will need the same care with tokens and organization access. I haven’t tried any of this, and a public preview that’s subject to change is not a finished security story.

Hero photo: Duke’s Lock, Oxford Canal 01 by Mertbiol, via Wikimedia Commons; CC0 1.0; cropped and resized.