GitHub Copilot in Teams: New App and November Migration Deadline

GitHub announced a consolidated Microsoft Teams app on October 23, bringing repository notifications and Copilot into the same app. Teams can receive an issue update, ask Copilot to work on it, and review the resulting pull request. Existing users also have a migration deadline to check.

The important distinction is that Copilot already worked in Teams. This release joins the notification and agent workflows rather than introducing coding from chat for the first time. For teams that already discuss repository updates in Teams, the useful change is a shorter path from noticing a problem to asking for a proposed fix.

Which GitHub Teams app should you update?

If you have GitHub notifications installed, update it to the latest version. That app is becoming the consolidated GitHub app, and GitHub says its existing notification capabilities will continue to work.

If you use the legacy GitHub app, install the consolidated app instead. The older app will be renamed GitHub (deprecated) and retired on November 16, 2026. After installation, mention @GitHub and follow the connection and repository-selection prompts.

The similar names make this worth checking before an organization sends out migration instructions. An instruction to simply update GitHub could send people down the wrong path if they have the legacy installation.

From an issue notification to a proposed change

The linked GitHub Community announcement describes a workflow starting with a notification in a channel, group chat or private chat. Ask @GitHub to investigate the issue, implement the change and open a pull request. The team still reviews, tests and decides whether to merge it.

GitHub's Copilot integration documentation explains that tasks run asynchronously in cloud sandboxes. You can continue steering the work from Teams or work with the resulting artifacts in GitHub or an editor. Repository write access is required to trigger code changes.

That makes the integration useful for a bounded task with clear acceptance criteria. A discussion about a reproducible bug can become a request for a fix and regression test. A vague complaint still needs someone to define what correct behavior looks like before delegating implementation.

Plans, preview status and conversation context

Copilot in Teams remains a public preview. It requires a paid GitHub Copilot plan and enabled cloud sandboxes; organization or enterprise administrators may need to enable the relevant policies. GitHub's Teams setup guide also lists app-installation permission and Microsoft Public Developer Preview for the Teams client as prerequisites.

There is a context boundary to understand before using it. GitHub says Copilot captures the entire thread, and that context is stored in generated artifacts. A direct message to the app can narrow the context. Treating a long, mixed-purpose conversation as a ready-made implementation brief would therefore be a poor default.

The practical test for this consolidation is whether teams can turn a well-defined discussion into a reviewable change with less copying and lost context. Keeping the request precise and the review independent matters more than how quickly the agent opens the pull request.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help developer-tool teams turn technical releases and workflow changes into clear stories that developers and founders can use and share.

Book a 30-minute call.