GitHub Copilot Coding Agent Arrives in Microsoft Teams: Legacy App Retires November 16

According to Microsoft's Teams blog, GitHub notifications and GitHub Copilot now live in a single app in Teams called GitHub. Microsoft's pitch is that the app helps people build with your team around the shared context from your chats, channels, and meeting chats using your GitHub Copilot license. It gives two examples of how it's being used: customer support teams are using GitHub to turn customer feedback from Teams channels into filed issues, and engineering teams are asking GitHub to investigate, reproduce, and fix bugs without leaving Teams.

Admins should pay attention to the deadline that comes with this release. The old app is being retired, and the cutoff is close.

What changes for admins: the deprecation deadline​

Microsoft has also published a Message Center notice, MC1515929, about the consolidation. The notice says Microsoft is consolidating GitHub Notifications and GitHub Copilot capabilities into a single GitHub app in Microsoft Teams. The date to remember: the legacy app will be deprecated on November 16, 2026.

The names have changed several times, so here is which app is which:

• September 2025: GitHub launched a public preview of a Copilot-powered Teams app called "GitHub." At the same time, the older notifications app was renamed. In the preview announcement, Microsoft's 365 Developer Blog said the previous GitHub for Teams app is now GitHub Notifications.
• October 2026: GitHub's October 23 changelog describes the new consolidated app as the one "previously called GitHub notifications." If you already run GitHub Notifications, GitHub says to update it to the latest version, and your existing notification features will keep working.
• The app being retired is the legacy GitHub app, the Copilot preview app. Per the Message Center notice, users of the legacy GitHub app will see it appear as GitHub (deprecated). GitHub's changelog tells those users to install the consolidated app if they want to keep using Copilot in Teams.

Microsoft lists these actions for admins:

1. Notify affected users to remove the legacy GitHub app from Teams conversations and add the new GitHub app before November 16, 2026.
2. Review your organization's Teams app access policies to ensure the new GitHub app is available to users who need it.

The notice also confirms who gets the AI features: the app is being renamed GitHub, with GitHub Copilot capabilities available to users with an eligible GitHub Copilot license. Anyone without a license still gets notifications.

Section summary: If your tenant uses GitHub Notifications, update it. If people use the legacy Copilot preview app, move them to the consolidated app before November 16.

How it works: from bug report to pull request​

GitHub's October changelog lays out three steps. A bug report shows up in Teams. Someone mentions @GitHub, and Copilot investigates, writes a fix and opens a pull request. Then the team reviews, tests and merges it. Humans still own the last step. Nothing is merged automatically.

GitHub's documentation fills in the details. You can reply to a GitHub notification in a channel, a group chat or a private chat and @mention GitHub to hand off a task. Copilot reads the linked issue or pull request plus the thread to work out what you want. It can investigate the issue, reproduce the bug, run tests, make changes and prepare a pull request for review. The work runs asynchronously in a cloud sandbox. You can keep steering it from Teams, or continue on the results in GitHub, a terminal or your editor.

According to Redmondmag's coverage, the release adds four main features:

• GitHub Canvas. A new GitHub Canvas interface displays proposed changes, implementation plans and pull requests without requiring users to leave Teams. GitHub's docs say the canvas is read-only. It shows only content you can already see on GitHub through your linked account, so it doesn't open a path around repository permissions.
• Multi-repository sessions. One session can cover up to 11 repositories, as long as they all belong to the same organization or personal account. You need write access to every one of them.
• Model choice. Redmondmag reports guided account setup, natural-language repository selection and options for choosing the AI model used for individual tasks. Per GitHub's docs, the model you pick applies for the rest of that conversation only. Which models you can choose depends on your plan and your organization's policies.
• Guided onboarding. Microsoft says the new guided web onboarding experience helps you sign in through your default browser using saved passwords or passkeys and grant Teams access to the right organizations and repositories.

GitHub's docs show an example prompt for pointing Copilot at a specific repository and branch:

@GitHub Create a pull request to YOUR-PROMPT repo=OWNER/REPO branch=BRANCH-NAME

The repo parameter sets the repository. The branch parameter names an existing branch to use as the base for the pull request.

Setup checklist: Microsoft 365 and GitHub​

The Teams side has two admin requirements. Microsoft lists them like this:

• Microsoft 365 admins: ensure resource-specific consent is enabled so users can let the GitHub app use conversation context.
• TAC admins: ensure the GitHub app is allowed for users in the Teams admin center.

On the GitHub side, users need a paid Copilot plan. If Copilot comes from an organization or enterprise, GitHub's docs say the cloud agent policy is on by default, but an owner can turn it off. Microsoft and GitHub describe one requirement differently. Microsoft's announcement lists enabling cloud sandboxes for each organization as a prerequisite. GitHub's current docs say Teams sessions run in a cloud sandbox that "doesn't need a separate setting." If sessions won't start, check this first.

For end users, GitHub's documentation gives this sequence:

1. Add the GitHub app from the Teams app store. It only has to be installed once per team, and then each member connects their own GitHub account.
2. In a chat or channel, type @GitHub and follow the prompts to connect your account. Microsoft's blog also points to a "Get started" button in the welcome message.
3. Type @GitHub help to see the available commands.
4. Use @GitHub subscribe OWNER/REPO to get repository events in the channel.
5. Use @GitHub settings to set default repositories for a channel. All the defaults have to share the same owner.
6. Start a task by mentioning @GitHub and describing the work. Direct messages can't have a default repository, so name the repository in your prompt.

Common snags, based on GitHub's docs:

• "Why can't I start a session?" You need write access to every repository in the session. Guests and outside collaborators can't start or steer a session at all.
• "I changed the channel defaults and nothing happened." Default repository changes only apply to new conversations, not ones already running.
• "The session won't start and MCP is involved." A repository MCP configuration that is invalid or too large can stop a session from starting. A repository admin has to fix it.
• "My subscriptions vanished." They shouldn't have. GitHub says updating GitHub Notifications to the combined app keeps existing subscriptions and scheduled reminders.

Section summary: Get resource-specific consent, Teams admin center approval, Copilot licensing and repository write access in place before you roll this out widely.

Security and governance: what security teams should know​

Redmondmag says MCP support lets you configure which tools and connected services GitHub can leverage in Teams, but GitHub's documentation gives more detail on how that's controlled. MCP servers are set up per repository, and a repository admin decides which servers, tools and credentials are allowed. Personal MCP servers only apply when you own the session. Teams has no single switch that unlocks every tool. Control stays with each repository.

The biggest privacy issue is thread context. GitHub's docs warn that when you mention @GitHub, Copilot takes the whole thread as context, and that context ends up in the artifacts it creates. If a channel has spent three weeks discussing an incident, including customer names and someone's frustrated comments about a vendor, all of it can become context for an issue or pull request. GitHub suggests sending the app a direct message, or starting a new thread, when you want to limit the context.

Identity matters too:

• Direct messages: Copilot acts with the permissions of your linked GitHub account.
• Channels and group chats: Copilot creates pull requests and other artifacts under its app identity, not as you.

That second point affects branch protection. GitHub notes that pull requests created this way aren't attributed to a person. If a repository ruleset already requires at least one approval, these pull requests need one more approval before merging, and that behavior is on by default. That's a sensible safeguard, but warn reviewers before the extra approvals catch them off guard.

Analysis: useful, with caveats​

The following is the author's analysis based on general industry experience, not vendor claims.

The strongest argument for this app is that bugs and requirements are usually discussed in chat, while the fixes happen somewhere else. Reports surface in a channel, get discussed for a while, and then someone has to rewrite everything as a ticket. Letting the agent read the thread removes that rewriting step. Microsoft's own example, support staff turning customer feedback into issues, may matter more than the coding features. It lets people who aren't developers feed the backlog without learning GitHub.

There are caveats:

• Context can include too much. The same thread history that makes the agent useful can bring in sensitive or misleading discussion. A thread that ruled out an approach halfway through can still steer the agent toward it.
• Review load moves. Agent-written pull requests still need careful human review. Teams that measure success by pull requests opened instead of pull requests merged will get the wrong idea.
• Licensing splits the room. People without Copilot licenses get notifications but no AI features. That's predictable, but it can cause confusion in channels where only some people can steer the agent.
• Vendor framing. Microsoft and GitHub are presenting this as a productivity win, which is what vendors do. Neither has published independent data on how well agent-written fixes hold up.

The bottom line​

The consolidated GitHub app puts notifications, Copilot's cloud agent, a read-only review canvas, multi-repository sessions and repository-controlled MCP tools into one Teams app. For most admins, the urgent task is the November 16, 2026 retirement of the legacy app. Update GitHub Notifications, move anyone still on the preview app, and check Teams app access policies before the old app shuts off. The longer-term work is governance: decide which channels should be able to send their full history to an AI agent, and make sure reviewers understand the app-identity approval rule.

Related WindowsForum topics: Teams admin center app policies, GitHub Copilot licensing for enterprises, resource-specific consent in Microsoft 365, and MCP server governance for development teams.