GitHub has combined repository notifications and Copilot coding tasks in one Microsoft Teams app, with its separate legacy app scheduled to retire November 16, 2026, according to the company's October 23 announcement. The immediate question for existing users is which installation they have.
Azeem Hassni's October 24 report covers the migration and setup, while LUMACTA's October 24 explainer examines the separation between requesting work and approving changes. Both draw on company material; LUMACTA explicitly describes its coverage as analysis without a firsthand product test.
Consolidation Builds On An Earlier Integration
This is an app consolidation, rather than Copilot's first appearance in Teams. GitHub's September 25 update already described using conversation context for coding work and administrator enablement for the Teams integration.
Combining entry points can simplify the route from an update to a coding request, but a shorter route does not itself establish better code or faster delivery. The practical change for existing users begins with choosing the correct migration path.
Two Installations Need Different Actions
For users of the app previously called GitHub notifications, GitHub's instruction is to update the existing installation. The company says its notification capabilities will continue working. That route differs from replacing the separate legacy GitHub app.
The legacy app will be renamed "GitHub (deprecated)." Its users should install the consolidated app to continue using Copilot in Teams before the November 16 retirement. Identify the installed application before deciding whether an update completes the job.
An October 19 Microsoft notice reproduced in a third-party archive makes the steps more specific: manually update GitHub Notifications, or remove the legacy app from Teams conversations and add the consolidated app to those conversations.
A Notification Becomes A Proposed Change
After choosing the installation path, connect the coding workflow. Setup involves mentioning @GitHub, connecting a GitHub account when prompted, and selecting a repository, according to GitHub. Make the intended destination explicit before delegating a task.
GitHub describes notifications arriving in channels, group chats, or private chats. In its example, a bug report prompts an @GitHub request; the agent investigates, makes a proposed fix, and opens a pull request. The team then reviews, tests, and merges.
A pull request is a proposal to incorporate code changes. The useful shift is where that proposal begins: a conversation containing an incoming report can become the starting point for engineering work. The team's acceptance decision remains a separate step.

Check The Workflow Before The Deadline
The archived Microsoft notice recommends checking that notifications for intended repositories and event types reach the intended conversations. It also advises reviewing Teams app access policies and allowing required chat-context permissions where resource-specific consent is restricted.
Treat the migration as an inventory exercise. Record which app each working conversation uses and assign someone to handle the change. For an initial trial, choose a small defect with an observable expected result, then compare the proposed changes with that acceptance condition. Assign a reviewer before starting the task and agree on who handles missed notifications or a wrong repository choice. This makes the trial answer an operational question: can colleagues reliably finish the work they initiated?
Keep a short record of the trial: the original report, the requested outcome, the resulting proposal, and the review decision. Counting generated pull requests alone would say little about whether the integration improved the work. A useful acceptance check follows the whole sequence through normal review.
The practical deadline is an opportunity to clarify ownership alongside installation. This report, part of our technology news coverage, attributes product behavior to GitHub and distinguishes the outside reports' interpretations under our source and correction standards.
Images: AI-generated images.
Discussion
Join the discussion
Useful notes, corrections, and field experience belong here. Keep replies specific and constructive.