GitHub Copilot in Microsoft Teams: turn bug reports into pull requests

GitHub Copilot in Microsoft Teams can now turn a notification into code. Since 23 October 2026, the consolidated GitHub app for Teams lets you mention @GitHub in a channel or chat so Copilot investigates an issue, makes a fix and opens a pull request.

Your team still reviews, tests and merges the change. The older GitHub app will be renamed "GitHub (deprecated)" and retired on 16 November.

Sources checked on 26 October 2026. Features, prices and availability can change; confirm the linked primary sources before acting.

How the workflow runs

A bug report becomes a pull request without leaving the conversation. The review still happens on GitHub.

1. A GitHub notification or bug report arrives in a Teams channel, group chat or private chat.
2. Someone mentions @GitHub and asks Copilot to investigate and fix it.
3. Copilot works on the change and opens a pull request.
4. The team reviews it, CI runs and a person merges it.

Set up GitHub Copilot in Microsoft Teams

Install or update the consolidated GitHub app, then connect your account on first use. Existing notification features keep working after the update.

1. Install the consolidated GitHub app in Teams, or update it if you already use GitHub notifications.
2. If you use the legacy app, install the consolidated one to keep using Copilot in Teams.
3. Mention @GitHub and follow the prompts to connect your GitHub account and choose a repository.

GitHub's changelog does not list plan requirements. Confirm that your organisation's Copilot policy allows Copilot to create pull requests before rolling this out.

Review gates you should keep

Treat a Copilot pull request like any contributor's. Protect the branch before anyone can trigger one from chat.

Ask for a failing test that reproduces the bug as part of the fix. Treat chat text as untrusted input too: a pasted report can contain instructions that should not shape the code.

Migrate from the legacy app before 16 November

List the channels that use the legacy app first. Then install the consolidated app, confirm notifications still arrive and remove the old app.

Do this per team, not all at once, so a missed subscription is noticed early.

Our verdict: useful for small, well-described bugs in repositories with good tests, and only with branch protection in place. Our code review checklist for small teams applies to agent pull requests too, and our Cursor vs GitHub Copilot comparison covers plans. For help wiring GitHub into your workflow, see our workflow automation service.

Sources and further reading

• Turn notifications into code with GitHub Copilot in Teams — GitHub

Image credits

Explanatory diagrams: Cloudsoft Zone, CC BY-SA 4.0. Featured photograph: Microsoft, CC0, via Wikimedia Commons. GitHub Codespaces side by side terminal: Wikideas1, CC0, via Wikimedia Commons.