Mention @GitHub to start a shared session in a channel, group chat or meeting chat. Everyone who has access to the same repo can add context, make changes, and review the pull request together.
From conversation to pull request
GitHub Copilot for Microsoft Teams
Your AI builder, right in Teams. Bring @GitHub into any chat or channel to answer questions, investigate bugs, create issues, make code changes, and open pull requests. Turn team conversation into code without leaving Teams.
Review the plan, code changes, and PR without leaving Teams
Open canvas to review the plan, file changes, and pull requests next to your conversation.
Turn updates into reviewable code
Start work right from a GitHub notification
Get issue and pull request updates in Teams. Reply with @GitHub to investigate, fix, and draft a pull request in the same thread.
More ways to work from Microsoft Teams
Turn product feedback into fixes
Add @GitHub to your feedback channel. Turn a user report into a GitHub issue, or ask GitHub Copilot to fix it and open a pull request.
Prototype ideas as you discuss them
Ask @GitHub to build a first version of the idea your team is discussing. Review it, iterate, and take it all the way to a PR together in the same thread.
Frequently asked questions
How does multi-step work move from Microsoft Teams to GitHub?
Mention @GitHub in a chat or channel. GitHub Copilot uses your default repository (or one you name), shares a live task plan, works in a cloud environment, and can open a pull request for human review.
How does a shared Microsoft Teams session work?
Participants in the same group chat or channel thread contribute to one GitHub Copilot session and shared context instead of separate environments for each person.
Can everyone in the Teams conversation authorize code changes?
No. Participants can follow the session, add context, and steer the plan, but repository permissions and existing approval rules determine who can authorize and merge changes.
What does a Microsoft 365 administrator need to approve?
Microsoft 365 admins: Allow the GitHub app in Teams app policies, and turn on resource-specific consent (RSC) so users can let the app use conversation context.
GitHub enterprise admins: Enable Copilot cloud agent and cloud sandboxes for every organization that will use it, and assign GitHub Copilot licenses to users.
How is conversation and repository data handled?
When you mention @GitHub, GitHub Copilot uses the whole thread as context and can leverage it to create artifacts, like issues or pull requests. Read the GitHub General Privacy Statement.
How do I get started?
Add the GitHub app to Teams, then mention @GitHub to connect your account, give access to your desired organizations and repositories, and pick a default repository to start work. Type @GitHub help to see what else it can do.