GitHub Copilot in Microsoft Teams: Setup & November 16 Migration Checklist

Quick answer: GitHub has combined repository notifications and Copilot cloud-agent work in a consolidated Microsoft Teams app. If your tenant uses the legacy app that Teams labels GitHub (deprecated), replace it before November 16, 2026. If you already use the app previously called GitHub notifications, update it instead; existing notification capabilities should continue.^[1]

Five-minute migration checklist

• [ ] In Teams, identify whether users have GitHub, GitHub notifications, or GitHub (deprecated) installed.
• [ ] If you have GitHub notifications, update it to the latest version.^[1]
• [ ] If you have GitHub (deprecated), install the consolidated GitHub app before November 16 and add it to the required chats or channels.^[1]
• [ ] In a Teams message, type @GitHub and complete the GitHub account connection.^[2]
• [ ] Subscribe one test channel with @GitHub subscribe OWNER/REPO.^[3]
• [ ] If you want Copilot coding tasks, confirm a paid Copilot plan and enable Copilot cloud agent/cloud sandboxes.^[1][4]
• [ ] Test on a non-critical repository and require human review before merging.

What changed

The consolidated GitHub app can post repository updates in Teams channels, group chats and private chats. From a notification thread, a user can mention @GitHub and ask Copilot to investigate an issue, run tests, implement a proposed fix and prepare a pull request for review.^[1]

GitHub says ordinary notifications do not require a Copilot license. Copilot actions require a paid GitHub Copilot plan plus cloud sandboxes; organization or enterprise administrators may also need to enable Copilot cloud agent and cloud sandboxes.^[1][4]

The Copilot integration is in public preview, so behavior and prerequisites may change.^[2][4] Microsoft also describes the preview as available in channels, group chats, meeting chats and one-to-one chats, with existing branch protections and required reviews still applying.^[5]

Which Teams app do you have?

If it says “GitHub notifications”

Update the app to the latest version. GitHub says existing notification capabilities will continue in the consolidated app.^[1]

If it says “GitHub (deprecated)”

Treat this as a migration, not an update. Install the consolidated GitHub app and move the app into every conversation that still depends on the legacy integration. GitHub says the legacy app retires on November 16, 2026.^[1]

If it says “GitHub”

Confirm it is the current consolidated listing, connect a test account and run @GitHub help. Do not assume the display name alone proves that every old channel subscription or administrator policy has carried over.

How to install and connect the consolidated GitHub app

1. Open the official GitHub integration listing in the Teams app store.
2. Select Add and approve the requested access.
3. Add the app to the intended team, channel or conversation.
4. Type @GitHub in a Teams message.
5. Follow the browser prompts to connect your GitHub account.
6. Run @GitHub help to confirm the connection and view available commands.^[2]

GitHub’s setup documentation currently lists a GitHub account, permission to install Teams apps, Microsoft Public Developer Preview in the Teams client and cloud sandboxes for Copilot work as prerequisites.^[2] Because the feature is in preview, verify these requirements in the official documentation when deploying it broadly.

Subscribe a Teams channel to a repository

Use these commands in a channel, replacing the sample owner and repository:

@GitHub subscribe OWNER/REPO
@GitHub subscribe list
@GitHub subscribe list features

To remove the subscription:

@GitHub unsubscribe OWNER/REPO

GitHub documents these commands for channel notifications. The app may prompt you to install or authorize the GitHub app for the relevant repository or organization.^[3]

Start a Copilot coding task from Teams

Mention @GitHub in a chat or thread and describe a bounded task. For example:

@GitHub Investigate the failing checkout test linked in this thread. Reproduce the failure, explain the likely cause, add or update a regression test, and prepare a pull request. Do not change production credentials, deployment files, billing settings or unrelated code.

To name a repository and base branch explicitly, GitHub documents this structure:^[4]

@GitHub Create a pull request to fix the issue described in this thread repo=OWNER/REPO branch=BRANCH_NAME

Copilot can use the linked issue or pull request and the conversation thread as context. It can continue asynchronously in a cloud sandbox and post the result back to Teams.^[1][4]

Permissions and review behavior

Only users with write access to a repository can trigger Copilot to make changes. Other conversation participants can contribute context, while guests and outside collaborators cannot start or steer a Copilot session in Teams.^[4]

In a direct message, Copilot acts with the permissions of the linked GitHub account. In a shared channel or group context, generated artifacts use the GitHub app identity instead. GitHub says an unattributed Copilot pull request requires one additional approval when repository rules already require at least one approval.^[3][4]

Keep branch protection, required status checks and human pull-request review enabled. A generated pull request is a proposal, not a verified fix.

Important privacy and security checks

GitHub states that Copilot captures the entire thread as context when it is mentioned in Teams, and that this context is stored in the artifacts the agent generates. Use a direct message or a new, tightly scoped thread when the surrounding conversation contains unrelated or sensitive material.^[4]

Before broad rollout:

• Review the GitHub app permissions requested in Teams.
• Confirm which repositories the app can access.
• Keep secrets, customer data, access tokens and incident credentials out of Teams prompts.
• Enable the app first for a pilot group and non-critical repository.
• Require code-owner review and CI checks before merge.
• Review generated issues and pull requests for sensitive thread content.
• Define who may enable cloud sandboxes and Copilot cloud agent at organization or enterprise level.

Three safer copy-paste task prompts

1. Investigate without changing code

@GitHub Investigate the issue linked in this thread. Summarize the reproduction steps, affected files, likely cause and safest fix options. Do not modify code or create a pull request yet.

2. Prepare a small reviewed fix

@GitHub Reproduce the reported bug and prepare the smallest reasonable fix with a regression test. Avoid unrelated refactoring. Run the relevant tests and list anything you could not verify. Create a pull request for human review; do not merge it.

3. Turn a decision into an issue

@GitHub Create an issue from the agreed decision in this thread. Include scope, acceptance criteria, dependencies, risks and open questions. Do not include private customer details or credentials.

Verification checklist after migration

1. The consolidated GitHub app appears in the intended Teams conversation.
2. @GitHub help responds for a connected user.
3. @GitHub subscribe list shows the expected repositories.
4. A test issue or pull-request event creates the expected Teams notification.
5. Users without a Copilot license can still receive ordinary notifications.^[1]
6. An eligible test user can start a Copilot session only in an approved repository.
7. The resulting pull request respects branch protection and required reviews.^[4][5]
8. The team has removed the legacy GitHub (deprecated) app from migrated conversations before November 16.^[1]

Troubleshooting

@GitHub does not respond

Confirm the current app is installed in that team or conversation, the user connected a GitHub account and the Teams administrator permits the app. Then run @GitHub help again.^[2]

Notifications work but Copilot tasks do not

Check for a paid Copilot plan, enabled Copilot cloud agent and enabled cloud sandboxes. Organization or enterprise policy can block access even when ordinary notifications work.^[1][4]

Copilot cannot use the requested repository

Confirm the user has write access, the app is authorized for the repository and the repository is named explicitly in the request. Outside collaborators and guests cannot start or steer these sessions.^[4]

The agent uses too much conversation context

Start a new thread or use a direct message. GitHub warns that the entire thread becomes context for the request and generated artifact.^[4]

FAQ

Is GitHub Copilot in Microsoft Teams generally available?

No. GitHub’s current documentation labels the integration a public preview that is subject to change.^[2][4]

Do Teams notifications require GitHub Copilot?

No. GitHub says notifications do not require a Copilot license. Copilot coding actions require a paid Copilot plan and cloud sandboxes.^[1][4]

When does the legacy GitHub Teams app retire?

GitHub says the app labeled GitHub (deprecated) retires on November 16, 2026.^[1]

Can Copilot merge its own pull request from Teams?

The documented workflow creates work for review. Existing repository policies, branch protections and required reviews continue to apply, and people remain responsible for deciding what gets merged.^[5]

Can Copilot read the whole Teams thread?

Yes. GitHub says the entire thread is captured as context when Copilot is invoked, so use a new thread or direct message when you need narrower context.^[4]

Sources

1. Turn notifications into code with GitHub Copilot in Teams — GitHub Changelog
2. Setting up the GitHub integration for Teams — GitHub Docs
3. Using GitHub in Teams — GitHub Docs
4. Using Copilot cloud agent in Teams — GitHub Docs
5. Turn conversations into code with GitHub Copilot in Microsoft Teams — Microsoft Community Hub