Work & Productivity

GitHub Brings AI Coding Tasks Into Microsoft Teams

By Marcus Delgado / October 27, 2026 / Updated November 8, 2026

Laptop displaying programming code beside a notebook and an orange mug

Quick answer: GitHub’s Teams app now lets you reply to an issue notification, @mention GitHub and ask Copilot to investigate, change the code and open a pull request. Your team still reviews and merges it. As of November 8, 2026 it is no longer labeled a preview: GitHub’s November 6 changelog calls @GitHub in Slack and Teams generally available. The Copilot side needs a paid Copilot plan and the right admin policies. If your team is still on the old Teams app, you have until November 16, 2026 to switch.

Key takeaways

GitHub folded its notifications app and its Copilot features into one Teams app on October 23, 2026.
Notifications alone do not need a Copilot license. Asking Copilot to do work does: a paid plan, with cloud sandboxes enabled.
The legacy Teams app is being renamed “GitHub (deprecated)” and retired on November 16, 2026.
Only people with write access can trigger changes. Guests and outside collaborators cannot.
A pull request is a proposal, not a finished fix. Humans still review, test and merge.

What changed, in date order

This story has moved a few times since the first headlines, so here is the timeline from GitHub’s own changelog pages.

August 21, 2026: GitHub launched Copilot cloud agent sessions in Microsoft Teams as a public preview for paid plans. Sessions used AI credits, and cloud sandbox use was billed separately.
October 23, 2026: The notifications app and the Copilot features became one GitHub app for Teams. Existing notification features keep working, and people who already had “GitHub notifications” should update it.
October 28, 2026: GitHub said the connected Copilot cloud experience and cloud sandboxes are generally available on paid plans, with Slack and Teams among the places you can use them. Billing for cloud sandbox usage begins in November 2026.
November 6, 2026: GitHub announced that @GitHub in Slack and Teams is generally available. The post also mentions a Canvas view in Teams, repository detection from your message, a fix for follow-up replies, and a note in created issues and pull requests saying which chat they came from.

One wrinkle: the October 23 post never says “preview” or “generally available” and does not list plans. Those details live in the August post and the documentation. This article is a read-through of GitHub’s published pages, not a hands-on test.

How it works in practice

Picture a bug report landing in a Teams channel as a GitHub notification. Instead of copying it into a ticket and pinging a developer, someone replies and mentions @GitHub with the task. Here is the flow as the documentation describes it.

Someone installs the GitHub app for the team. After that, each person connects their own GitHub account.
In a channel, group chat or personal chat, a user mentions @GitHub and describes the task, naming the repository or picking it when asked. Typing “@GitHub help” lists the commands.
Copilot works in a cloud sandbox, using the conversation as context. It can reproduce a bug, run tests and make changes, then posts back when it has something.
Anyone in the thread can mention @GitHub again to add context or ask for changes. Copilot takes into account the messages since the previous mention.
An “Open canvas” button shows the plan, file changes and pull request overview. GitHub describes it as read-only.
People review, test and merge the pull request on GitHub, like any other proposed change.

Garbage in, garbage out still applies. “Login is broken” gives an agent very little to work with. A message that says what you did, what happened and what you expected gives it a fair shot.

What you need before it works

Most of the friction is admin setup, not Teams itself. This table sums up what GitHub’s documentation and changelog say as of November 8, 2026.

Item	What GitHub says
Plan	A GitHub account with Copilot access through a paid plan. Notifications alone need no Copilot license, per GitHub’s community post.
Admin policies	For org and enterprise users, the Copilot cloud agent policy is on by default, but an owner can switch it off. The August post said admins must enable the cloud agent and cloud sandboxes.
Teams app	Install once per team; each member connects their own GitHub account. Teams on GitHub Notifications update that app, and subscriptions and scheduled reminders carry over.
Repository access	Only users with write access to every repository chosen for the session can start or steer it.
Who is excluded	Guest members and outside collaborators cannot start or steer sessions in Teams.
Repositories per session	Up to 11, all owned by the same organization or personal account.

Cost, limits and security notes

Cost

I could not find a per-session price on any page I read. In August, GitHub said Teams sessions used AI credits, organization usage fell under usage-based billing budgets, and sandbox usage was billed separately and could be capped. On October 28 it said sandbox billing starts in November 2026 and draws from the included Actions entitlement first, then follows your existing rates and budgets. These rules change, so check your own billing page rather than trusting a blog post, including this one.

Who owns the pull request

In a direct message, Copilot uses your linked account’s permissions. In a channel or group chat, it creates things under the app’s own identity. The docs say that when a repository already requires approvals through rulesets, pull requests made in a shared context need one extra approval. The August post called this an optional setting for repository admins, while the docs describe it as on by default, so check your repository settings instead of assuming.

What the thread exposes

Copilot captures the whole thread as context, and the docs say that context is stored in the artifacts it generates. If a thread holds customer data or credentials, start a fresh thread or message the app directly before asking for work.

A rollout checklist for your team

Check which Teams app you have. If it is the old one, install the consolidated app before November 16, 2026.
Ask your admin whether the Copilot cloud agent policy and cloud sandboxes are enabled.
Confirm who has write access, and who is a guest or outside collaborator and will be locked out.
Check the billing page and set a budget before people start experimenting.
Pick one low-risk repository for the first few sessions.
Keep your normal review and test requirements. The pull request is a draft of an answer, not the answer.

Frequently asked questions

Do I need a Copilot license just to get notifications in Teams?

No. GitHub’s community post says notifications do not need a Copilot license, and that using Copilot requires a paid plan with cloud sandboxes enabled.

Is it still in preview?

GitHub’s August post called the Teams integration a public preview. Its November 6 post says @GitHub in Slack and Teams is generally available. The documentation page I read does not mark the Teams integration as preview, though it does mark Copilot Memory that way.

What happens to the old GitHub app in Teams?

GitHub says it will be renamed “GitHub (deprecated)” and retired on November 16, 2026. Install the consolidated app to keep using Copilot in Teams.

Can Copilot merge its own fix?

Nothing I read says it can. GitHub’s announcement ends with the team reviewing, testing and merging, and repository rules such as required approvals still apply. It does not claim the fix will always be correct.

Before you decide

This is worth a trial if your team already lives in Teams and your bug reports already arrive there. It saves a hop, and the review step stays where it belongs. It is less compelling if your issues are vague, your repositories sprawl, or your admins have not enabled the policies, because then the agent mostly produces questions.

The unglamorous parts matter most: who has write access, who pays for sandbox time, and what sits in a thread before you invoke an agent. Sort those first, then try something low-stakes. A wrong pull request costs a few minutes; a thread full of secrets is a worse day.