AI - GitHub Copilot in Microsoft Teams, from notifications to pull requests

02 Nov, 2026

I really like the idea of this, especially if you are using GitHub.com 😉 Turning a Teams conversation about a bug into a proposed fix makes a lot more sense than just adding another notification to the pile.

My sticking point is self-hosted GitHub Enterprise Server. This new Copilot workflow is not documented for GHES, so for organisations keeping their repositories there, the announcement is less useful. If that support arrives, I can see a lot more value in this 😊

GitHub Copilot in Microsoft Teams

GitHub notifications and GitHub Copilot now live in one Teams app, called GitHub. Reply to an issue or pull request notification, mention @GitHub, and ask it to investigate or make a change using the linked work and the conversation as context.

Official announcement

Vlad Catrinescu shared the walkthrough:

View post by @vladcatrinescu on X

From a notification to a proposed fix

The workflow is quite straightforward:

An issue or pull request update arrives in a Teams channel, group chat or private chat.
Reply to the notification with @GitHub and describe the task.
Copilot works asynchronously in a cloud sandbox. It can investigate the issue, reproduce a bug, run tests, implement changes and prepare a pull request.
Use Open canvas to view the plan, file changes and pull request beside the conversation. The canvas is read-only; steer the agent through the thread, then review and test the proposed changes before deciding whether to merge.

The same approach works for features, extra test coverage and documentation updates. The useful part is keeping the discussion and the resulting work together, rather than rebuilding all that context in another tool.

What the GA release adds

Microsoft announced general availability on 30 October 2026, which Rod Trent highlighted:

View post by @rodtrent on X

The GitHub app in Microsoft Teams is now generally available!

Alongside the canvas, the release adds:

Multi-repository work: the current documentation supports up to 11 repositories with the same owner in one session, provided you have the required access.
Model choice and repository selection: choose a model for the conversation and configure default repositories for channels.
MCP support: use configured tools and connected services, with repository administrators controlling repository MCP configuration.
Guided sign-in and attribution: connect through your browser, grant repository access, and trace issues and pull requests back to the Teams discussion that started them.

What about self-hosted GitHub Enterprise?

There is an important distinction here: GitHub Enterprise Cloud and GitHub Enterprise Server are not the same thing.

NOTE

GitHub already documents a separate Teams integration for GHES, available from GHES 3.8. It uses a private app and supports repository notifications and actions such as commenting on issues. So it would be wrong to say that self-hosted GitHub has no Teams integration at all.

However, that is not the new Copilot notification-to-pull-request experience. As of 2 November 2026, the announcements and current Teams documentation do not describe that workflow for GHES. GitHub’s Copilot guidance for GHES describes options such as local clients working with checked-out code instead.

That is the gap I would like to see closed. Notifications are useful, but delegating the work from the conversation is the part that makes this interesting.

Getting started and things to check

NOTE

For the Copilot functionality, you need a paid GitHub Copilot plan, the relevant organisation or enterprise policies to allow cloud agent work, and write access to every selected repository to start or steer changes. Teams administrators must allow the GitHub app, and resource-specific consent must be enabled so it can use conversation context.

Add the app through teams.github.com, connect your GitHub account and use @GitHub help. To receive repository notifications in a channel, use @GitHub subscribe OWNER/REPO. Notification subscriptions and Copilot’s default repository settings are separate.

One thing worth remembering: Copilot uses the whole thread as context, and that context can be included in the issues or pull requests it creates. A focused thread or direct message is a better starting point than a sprawling conversation containing unrelated information.

If you already use GitHub Notifications, update it to the combined app; existing subscriptions and scheduled reminders are preserved. Microsoft also says the separate legacy app, renamed GitHub (deprecated), will retire on 16 November 2026.

Useful links

<< Previous Post

~~Next Post >>~~

#Blog #AI #GitHub #GitHub Copilot #Microsoft #Microsoft Teams #GitHub Enterprise Server