Turn a Teams GitHub Issue Notification Into a Fix PR With Copilot

TLDR

The consolidated GitHub app connects Teams notifications to Copilot tasks.
Code changes require a paid Copilot plan, enabled cloud sandboxes and repository write access.
A generated PR still needs your team's review, testing and merge decision.

Ask for a fix where the issue arrives

A bug notification in Teams can now be the starting point for a code change. GitHub's October 23 update combines notifications and Copilot in one app: mention @GitHub to request investigation, a fix and a pull request.

The notification itself is not an instruction to merge code. GitHub describes a handoff in which the team reviews, tests and merges the proposed fix after the agent's work.

Check access before handing over the issue

The integration remains in public preview. You need paid GitHub Copilot access, a Teams account and enabled cloud sandboxes. Organization policy may require an administrator's help. Starting changes also requires write access to the repository.

Mention @GitHub and complete account linking and repository selection. Existing GitHub notifications users should update the app. The separate Teams app migration guide identifies the legacy installation that needs replacing.

Name the repository and the base branch

A request can identify both its destination and an existing branch to use as the PR base. For example:

@GitHub Fix the empty-input bug in this issue and add a regression test. Open a pull request. repo=OWNER/REPO branch=main

Replace the repository and branch placeholders. Follow-up mentions in the same thread can add requirements, such as treating whitespace-only input as empty input too.

The full thread becomes task context. Use a focused conversation or a direct message when the surrounding discussion should not travel with the request.

Make the next human action visible

The Teams integration groups channel notifications by issue or PR and updates their status. PRs created in shared conversations use the app's identity. Where a repository ruleset already requires approval, an extra approval for these PRs is enabled by default.

Review and workflow notifications are disabled by default, even though issue and PR notifications are enabled. Add them if the channel should carry the handoff through CI and review:

@GitHub subscribe OWNER/REPO reviews workflows

Check the proposed change against the reported bug and its regression test before merging. Moving the request into Teams gives the team another place to initiate work; the PR remains the place to decide whether that work should ship.