Microsoft Teams: GitHub app consolidation and legacy GitHub app deprecation
What the notice says
Microsoft's text, with its sections, lists and tables; source markup removedWhat and Why
We are consolidating GitHub Notifications and GitHub Copilot capabilities into a single GitHub app in Microsoft Teams. The new app brings repository updates and GitHub Copilot coding capabilities together, so users can follow GitHub activity and act on it within Teams.
As part of this consolidation, the legacy GitHub app will be deprecated by November 16, 2026 and displayed as GitHub (deprecated) until it is retired. Users of the legacy app should remove it from their Teams conversations and add the new app, named GitHub, to those conversations before this date.
Users of the existing GitHub Notifications app need to update the app to the latest version. This app is being renamed GitHub and brings GitHub Copilot capabilities to users with an eligible GitHub Copilot license.
Rollout Schedule
General Availability (Worldwide): We will begin rolling out in mid-October 2026 and expect to complete by mid-November 2026.
Legacy GitHub app deprecation: The legacy app will be deprecated on November 16, 2026.
Impact on Your Organization
- Users of the legacy GitHub app: The app will appear as GitHub (deprecated). Users should remove it from their Teams conversations and add the new GitHub app to those conversations before November 16, 2026.
- Users of GitHub Notifications: The app must be manually updated to the latest version. The app is being renamed GitHub, with GitHub Copilot capabilities available to users with an eligible GitHub Copilot license.
Action Required/Recommendations
- Notify affected users to remove the legacy GitHub app from Teams conversations and add the new GitHub app before November 16, 2026.
- Review your organization's Teams app access policies to ensure the new GitHub app is available to users who need it.
- Ask existing users of the GitHub Notifications app to update the app to the latest version.
- Ask users to confirm that the new GitHub app delivers notifications for the repositories and event types they follow to the intended Teams conversations.
- If your organization restricts resource-specific consent (RSC), configure the applicable team and chat consent policies to allow the GitHub app’s required RSC permissions so GitHub Copilot can use chat and thread history as context. Learn how to configure RSC permissions here.
- Update internal guidance to identify the updated app and distinguish it from GitHub (deprecated).
Compliance considerations
| Question | Answer |
|---|---|
| Does the change include an admin control and can it be controlled through Entra ID group membership? | Yes. Admins can use Teams app access policies and app management controls to manage app availability for users. Review your organization's Teams app governance policies as appropriate. |
| Does the change provide a new way of communicating between users, tenants, or subscriptions? | No. The change consolidates existing GitHub app capabilities into a single Teams app and deprecates the legacy app. |
What changed
Between the versions this installation saw, newest firstThis installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.
Linked documentation
Microsoft pages the notice links to- https://learn.microsoft.com/en-us/microsoftteams/platform/graph-api/rsc/grant-resource-specific-consent Checked 19 Oct 2026
This site links to Microsoft's pages instead of copying them. Installations inside an organization can keep a copy for comparison.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.