Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The November 17 announcement introduces Azure DevOps integration in public preview. Enable it under Settings > Experimental, then add your Microsoft account through Accounts.
- Connecting an account grants no additional repository or PR access. Business and Enterprise users also need administrators to keep the GitHub Copilot app policy enabled.
- Manual completion includes a Complete confirmation. Once Agent Merge is enabled for a PR, the agent can complete it after Azure DevOps checks and policies pass, without another confirmation.
- The app has no separate audit log for this integration. Actions appear in Azure DevOps under the signed-in user, and private code, comments and build-log excerpts can enter model context.
Who can use the preview, and what does it do?
On November 17, 2026, GitHub announced Azure DevOps integration in Copilot app as a public preview, meaning its behavior may change. It brings repository cloning, agent coding, pull request creation, checks, review feedback and completion into the app. A pull request, or PR, is a request to merge code changes.
The guide lists Copilot Business, Copilot Enterprise or Copilot Individual. You need the app installed and signed in, plus a Microsoft account with access to the target Azure DevOps organization, project and repository. For Business and Enterprise users, administrators must keep the GitHub Copilot app policy enabled. The guide does not enumerate individual plan tiers, countries or a minimum app version, so it does not establish access for every account.
Cloud sessions are not available for Azure DevOps repositories. Connecting a Microsoft account or successfully cloning a repository does not remove that restriction.
Enable the integration and add a repository
Open Settings in the app, select Experimental, and enable Azure DevOps integration. It is disabled by default. Then go to Accounts > Add account and follow the prompts to sign in with the Microsoft account you use for Azure DevOps. You do not need to add it again if the relevant account is already connected.
Use the add control beside Sessions in the sidebar and choose Add Azure DevOps repository. Enter your organization name, select a repository, and follow the cloning prompts. You can then select that connected repository under Start session in to begin an agent session.
If a repository is missing, check the selected Microsoft account and its organization, project and repository access. Connecting the account grants no additional permissions. Changing a network or proxy exit does not create access rights.
Check the changes as a task becomes a PR
Describe the specific code change in a session for the repository. The agent can create a branch, edit code, commit and open a PR. Review the actual diff and respond to approval requests. Once the PR exists, click View PR to inspect changes, checks and review feedback.
To have an agent address a review comment, click Fix on that comment, then inspect its changes and reply. A task completion message, a comment reply or the start of CI does not establish that the target PR has passed its checks.
Agent tools follow the session’s tool permissions. Depending on those settings, creating a PR or replying to and resolving review threads can run without another approval prompt. Do not assume every write action will ask for confirmation again.
Choose manual completion or Agent Merge
For manual completion, inspect the changes and comments in the PR view and click Approve when you are ready to approve. To merge, click Complete, review the confirmation and confirm. Azure DevOps permissions and the repository’s configured checks and policies determine whether you can approve or complete the PR.
You can instead enable Agent Merge for an individual PR. The agent can address review feedback, fix CI failures, resolve conflicts and complete that PR when Azure DevOps checks and policies pass. Once enabled, it can complete the PR without a separate confirmation, so check the target PR and scope before turning it on.
Agent Merge does not guarantee that every conflict can be resolved or remove repository rules. Check the actual code, reviews and check results; enabling the option does not mean a merge has happened.
Understand repository controls and activity records
The app policy is an access requirement for Business and Enterprise users. Azure DevOps permissions continue to govern individual repositories and actions. The integration does not offer a separate setting to restrict it to selected repositories; adding one repository does not establish an allowlist that isolates all others.
Copilot app does not provide a separate audit log for the integration. Actions appear in Azure DevOps under the signed-in user’s name. For a team review, correlate the account, PR, checks and review records rather than expecting a separate, complete integration audit ledger in the app.
Check data handling and revoke access when needed
Azure DevOps content returned to the agent can enter the selected model’s context. That may include private code, PR descriptions and diffs, review comments and build-log excerpts. Content shown in chat or tool results is retained in local session history.
Existing model restrictions, training settings and enterprise policies continue to apply. GitHub-provided models follow the Copilot terms for your plan; models from another provider require review of that provider’s data handling terms as well. Before connecting work, establish which repositories and content the task may use.
Signing out of the Microsoft account in the app removes locally stored authentication tokens, but does not revoke access with Microsoft. Use Microsoft Entra account controls to revoke access. This guide describes public documentation; it did not perform a real sign-in, clone, paid request or PR merge.
Sources
Frequently Asked Questions
Do I have to migrate an Azure DevOps repository to GitHub first?
The reviewed guide has you select and clone a repository from your Azure DevOps organization, then start a session in that repository. It does not require a migration to GitHub first. Check any repository-use or migration rules set by your own organization separately.
Is app version 1.2.0 also the minimum for Azure DevOps?
The sources do not establish that. The same announcement names version 1.2.0 and later in its GHES section. Neither its Azure DevOps section nor the reviewed Azure DevOps guide specifies a minimum app version. Check the actual client entry point rather than applying another integration’s version requirement.
Does public preview mean the integration or model requests are free?
The two reviewed sources do not provide a separate integration price table or promise free or unlimited model requests. Confirm subscription eligibility, model costs and your account’s available allowance under the applicable plan. Public preview alone does not establish free access.