AI news · 2 min read
GitHub brings Teams notifications and Copilot into one app
GitHub combines Teams notifications and Copilot. Legacy-app users need to migrate before November 16; preview access and repository policies still apply.
Announcement date:
Affiliate disclosure: Some links may earn CreatorStack a commission at no extra cost to you.
At a glance
GitHub’s October 23 update combines Teams notifications and Copilot in one app. Update the notifications app, or replace the legacy GitHub app before its November 16 retirement. Copilot remains a public preview with setup and policy requirements. Review and test any resulting pull request before merging.
A bug report arrives in a team chat, followed by a discussion that explains how to reproduce it. GitHub’s October 23 update brings notifications and Copilot into the same Teams app, so that conversation can become a request to investigate and prepare a pull request. Consolidation announcement.
The immediate task for existing users is identifying which app is installed. GitHub says users of GitHub notifications should update it; existing notification functions continue. Users of the legacy GitHub app should install the consolidated app before the old one, renamed GitHub (deprecated), retires on November 16.
Check access before planning the workflow
The setup documentation still describes a public preview. It requires permission to install Teams apps, Microsoft Public Developer Preview enabled in the Teams client, and cloud sandboxes enabled for the Copilot plan. An organization or enterprise owner may need to enable the relevant policies.
That means an updated app alone does not establish that every teammate can delegate work. Connect the intended GitHub account, confirm repository access and check those prerequisites before promising a chat-based handoff.
Turn the discussion into a checkable request
For an illustrative first task, use a small interface bug: a signup button stays disabled after correcting an invalid email. Give the agent the repository, reproduction steps, expected behaviour and an acceptance check. Ask for a pull request that explains the change and reports which checks ran. This example has not been executed.
Keep the useful parts of the conversation attached to the task. “Fix this” leaves the agent to infer whether the problem is validation, loading state or an expected access restriction. A short reproduction narrows the work and gives the reviewer a way to decide whether the fix is complete.
The usage guide says work can continue outside Teams in GitHub, a terminal or an editor. Open the resulting diff, reproduce the original bug and examine test results before merging. The chat is a convenient starting point; it does not replace that review.
First check your installed app and the migration deadline. For the next step, our coding-agent workflow guide explains how to keep a delegated task small enough to inspect.
Common questions
Questions people ask.
- Do all existing Teams users need a new installation?
- GitHub says users of the notifications app should update it. Users of the legacy GitHub app should install the consolidated app before the legacy app retires on November 16.
- Does a Teams mention bypass Copilot policies?
- No. The current documentation requires cloud sandboxes enabled for the Copilot plan, and organization or enterprise policies may require owner action.
Sources & freshness
This article was refreshed on 24 Oct 2026 using the sources below. A source check verifies published information, not output quality or checkout availability in every region.
- github.blog/changelog/2026-10-23-turn-notifications-into-code-with-github-copilot-in-teams/
- docs.github.com/en/integrations/how-tos/teams/integrate-github-with-teams
- docs.github.com/en/integrations/how-tos/teams/use-github-in-teams
What changed: Original coverage of the consolidated Teams app, legacy migration deadline, access prerequisites and a reviewable bug-report workflow.
Found a correction? Let us know.