GitHub Teams app consolidation sets a November 16 deadline for the legacy integration

GitHub is consolidating Teams notifications and Copilot into one app, with different next steps depending on which integration a team already uses. Its October 23 announcement says the legacy GitHub app will be renamed `GitHub (deprecated)` and retired on November 16. Teams that use it need to install the consolidated GitHub app to continue using Copilot in Teams. [GitHub gives the migration instructions here](https://github.blog/changelog/2026‑10‑23‑turn‑notifications‑into‑code‑with‑github‑copilot‑in‑teams). The new consolidated app was previously called GitHub notifications. If that is the app already installed, GitHub directs users to update it to the latest version and says existing notification capabilities will continue to work. The practical first step is therefore to identify the installed app before assuming that every team needs the same replacement procedure.

The [consolidated GitHub app in Microsoft Teams](https://teams.microsoft.com/l/app/ca9e26b7‑dce5‑44a0‑b2b7‑a70a3d65ce25) is the destination linked by the release. For existing GitHub notifications users, the announced path is an update to that app. For users of the legacy GitHub app, the announced path is installing the consolidated app before the November 16 retirement. The [release notice](https://github.blog/changelog/2026‑10‑23‑turn‑notifications‑into‑code‑with‑github‑copilot‑in‑teams) does not specify a retirement hour or timezone. After installation, users can mention `@GitHub` and follow the prompts to connect a GitHub account and select a repository. Those connection steps matter: installing a Teams app and choosing the GitHub identity and repository for a task are separate parts of getting the workflow ready. The announcement does not establish a team’s effective repository permissions or demonstrate that its connection has survived a migration.

GitHub describes a workflow in which a bug report arrives in Teams, a user invokes `@GitHub`, and Copilot investigates the issue, changes code and opens a pull request. Notifications can appear in channels, group chats or private chats. The final step remains the team’s review, testing and merge; [the release presents human review as part of the workflow](https://github.blog/changelog/2026‑10‑23‑turn‑notifications‑into‑code‑with‑github‑copilot‑in‑teams). This consolidation is distinct from the [multi‑repository Slack and Teams update covered earlier by OpenTools](https://opentools.ai/news/github‑copilot‑multi‑repo‑slack‑teams‑context‑permissions). That earlier change broadened the repositories a conversation could work across. The October 23 notice gives teams a current app‑upgrade and replacement decision, with a retirement date for the old integration. It should not be read as the first availability of Copilot actions in Teams.

For a team following these instructions, a useful acceptance check is to confirm the intended GitHub account and repository in the consolidated app, then check the notification and pull‑request workflow it actually relies on. That is a practical consequence of the account‑connection and repository‑selection prompts in the [official instructions](https://github.blog/changelog/2026‑10‑23‑turn‑notifications‑into‑code‑with‑github‑copilot‑in‑teams), not a test OpenTools has performed. A pull request produced through Teams still needs the team’s normal code review and testing. The consolidation announcement does not announce broader repository access, a plan entitlement change or unattended merging. Its immediate consequence is narrower and actionable: update the app formerly called GitHub notifications, or replace the legacy GitHub app before its announced retirement, then verify the resulting connection and workflow.