The News, Explained
On November 17, GitHub released a public preview of Azure DevOps integration in the Copilot app. Teams that keep their code in Azure DevOps can clone a repository, make changes in a separate branch, and open a pull request to ask teammates to review those changes. They can see automated checks and review comments in the app. The Copilot app doesn’t support cloud work sessions for Azure DevOps repositories. Source Source
The integration is off by default. It requires a Microsoft account that already has access to the Azure DevOps organization, project and repository. On Copilot Business and Enterprise, an administrator must allow the Copilot app. Connecting the account adds no repository permissions. The existing Azure DevOps permissions and checks still govern approvals and merges, and Azure DevOps records actions under the signed-in user’s name. Source
Where the work session runs and what data reaches the AI model are separate questions. GitHub says private code, diffs, review comments and excerpts from build logs returned by tools can enter the selected model’s input. Anything shown in chat or tool results stays in local session history, and existing model restrictions and organizational data policies still apply. Source
OYOPICK’s Take
For a team that already reviews code in Azure DevOps, keeping checks and colleagues’ comments in the app can save some switching between tools. A small documentation edit is a sensible first task because a person can readily compare the change with the test results. The app has no separate setting to limit the integration to selected repositories, so a team that wants a narrow trial should first limit what the test account itself can access. Source