What shipped
The GitHub Copilot app is a standalone desktop application that lets developers delegate coding tasks to AI agents. The new integration connects it to Azure Repos. Agents can create branches, change and commit code, and open pull requests. Several agent sessions can run in parallel. The app also gives you a place to review code, add comments and manage pull requests.
The headline extra is Agent Merge. Microsoft's Azure DevOps Blog, in a post by product manager Dan Hellem, says agents can watch a pull request, address review comments, resolve CI issues and merge automatically when the PR is ready.
The repositories stay in Azure Repos. Nothing here requires a migration to GitHub.
Timeline
GitHub's changelog and the Azure DevOps Blog covered this in the same week:
- November 17: GitHub's changelog said Azure DevOps integration was in public preview as part of its Microsoft Ignite releases. A separate Azure DevOps Blog post the same day described the Copilot app working with Azure Repos through an Azure DevOps extension.
- November 19: Hellem's post gave the setup walkthrough and the roadmap.
These are the same feature, announced in stages.
How to turn it on
Microsoft's post and GitHub's documentation together give this path:
- Open the app's Settings and go to Experimental. Enable Azure DevOps integration. GitHub's documentation says the integration is disabled by default.
- Sign in with your Microsoft account. Go to Accounts > Add account and sign in with the Microsoft account you use for Azure DevOps.
- Add a repository. GitHub's documentation says to click the plus control next to Sessions, choose Add Azure DevOps repository, type your organization name, pick a repository and follow the prompts to clone it. Microsoft's post describes the same step as creating a session and selecting Add from Azure DevOps.
- Describe a coding task in an agent session. The agent can branch, edit, commit and open a PR. Track the PR in the sidebar and click View PR to review it in the app.
- To respond to feedback, click Fix on a review comment. When you are ready, use Approve, then Complete to merge.
Microsoft also recommends enabling the Azure DevOps Remote MCP Server. Go to Customize > Installed, choose Add server, and pick Azure DevOps. Entering your organization name is optional. A November 17 Microsoft post says that server has been generally available since August 2026. It also says it uses Microsoft Entra ID for authentication.
Prerequisites
- The Copilot app, installed and signed in.
- A Microsoft account with access to the Azure DevOps organization, project and repository.
- A plan that qualifies. GitHub's documentation lists Copilot Business, Enterprise or Individual.
- For Business and Enterprise users, an administrator who has left the Copilot app policy enabled.
Limits to know before you start
- No cloud sessions. Cloud sessions aren't available for Azure DevOps repositories. Work runs locally.
- Preview status. GitHub's documentation says the integration is subject to change.
- Not everything is built yet. Microsoft lists viewing and opening work items, starting coding sessions from work items and Projects support as planned improvements. They are not part of this initial repository integration. A separate Azure DevOps Copilot Plugin, labelled preview and not supported for production workloads, covers work-item and PR browsing. It is a different thing.
Security and governance
GitHub's documentation spells out several points that admins should read:
- Permissions don't expand. Azure DevOps permissions apply to every action, and connecting an account grants no extra access.
- No repository allow-list. The integration has no setting to restrict it to selected repositories.
- No separate audit log. Actions appear in Azure DevOps under the signed-in user's name. An agent's commits and PR actions will look like the person's own.
- Data goes to the model. Private code, PR descriptions and diffs, review comments and build-log excerpts can enter the selected model's context. Content shown in chat or tool results stays in local session history. Existing model restrictions, training settings and enterprise policies still apply. For third-party models, check that provider's terms.
- Sign-out isn't revocation. Signing out removes locally stored tokens but does not revoke access with Microsoft. Use Microsoft Entra account controls for that.
- Agent Merge needs care. Once you enable it on a PR, the agent can complete it without a separate confirmation, provided Azure DevOps checks and policies pass. Some actions, such as creating PRs or resolving review threads, may also run without another approval prompt, depending on your tool-permission settings.
Practical advice (my analysis, not from the documentation)
Your branch policies are the real safety net. If a repo has loose policies, such as no required reviewers or weak CI gates, Agent Merge will test them. Before piloting, I'd suggest:
- Require human reviewers on protected branches.
- Make sure build validation actually catches regressions.
- Try the integration on a low-risk repository first.
- Remember that agent activity is attributed to the user, so make sure your team knows that.
Licensing and context
Microsoft's November 17 post links this to licensing. It says GitHub Enterprise Cloud now includes Copilot access at no additional seat charge, including use of the Copilot app with Azure DevOps. It adds that AI usage is billed separately through AI credits. Without Enterprise Cloud, you can buy a standalone Copilot license. Microsoft also says to ask your account team about availability, so confirm before you budget.
The same post says GitHub remains the home of the most complete agentic development experience. It also offers migration paths for teams that want to move. A reader comment under it asked whether Azure DevOps is being deprecated. The post doesn't answer that. Azure DevOps shops can read the messaging as "start now, migrate later." Skeptics will note that the best experience is still on GitHub.
Bottom line
Teams on Azure Repos can now hand branch-and-PR work to Copilot agents from a desktop app without leaving Azure DevOps. The preview is local-only and still missing work-item features. Its governance story relies on existing Azure DevOps permissions and policies rather than dedicated controls. Pilot it where your review gates are strong, and treat Agent Merge as something to switch on deliberately.
References
- Azure DevOps integration with the GitHub Copilot app (public preview) Azure DevOps Blog · 2026-11-19T17:39:09+00:00
- Managing Azure DevOps work with the GitHub Copilot app - GitHub Docs docs.github.com
- README.md github.com