Rumors City

Search this site

GitHub Copilot in Microsoft Teams: Turn a Bug Report into a Pull Request

Posted byJustin SooPublished 3 minutes read

A bug report lands in Microsoft Teams. You can now ask GitHub Copilot to investigate it without leaving the conversation.

On October 23, 2026, GitHub highlighted an updated Teams app that combines repository notifications with its Copilot cloud agent. The idea is simple: turn a discussion about a problem into a proposed code change, then review it on GitHub. See GitHub’s announcement.

What can it actually do?

  • Read the context: work from an issue notification or a conversation thread.
  • Investigate: ask the agent to look into a reported bug or plan a fix.
  • Prepare a change: have it write code and open a pull request for human review.
  • Keep collaborating: teammates can clarify the request or correct the agent in the same thread.

It works in Teams chats, channels and threads. It does not mean the agent automatically merges code into production.

How to try it

  1. Ask your Teams administrator to install the current GitHub integration for Microsoft Teams.
  2. In a Teams conversation, mention @GitHub and follow the prompts to link your GitHub account and select a repository.
  3. Open a thread about a real bug or issue, then give the agent a specific request.
  4. Review the proposed pull request, run tests and decide whether to merge it.

For example, try this in a Teams thread about a bug:

@GitHub Investigate the login error described above. Explain the likely cause, propose a minimal fix, add a regression test, and open a pull request for review. Do not merge it.

This is an example prompt, not a guarantee that the agent will resolve every bug correctly.

Three catches before you start

  • Not free for everyone: GitHub says the Copilot cloud agent integration is available with paid Copilot plans. AI usage may consume your plan’s credits.
  • Still in preview: GitHub’s docs list Microsoft Teams Public Developer Preview as a prerequisite, along with enabled cloud sandboxes for Copilot. Organization policies may also need an admin to enable the agent.
  • Thread privacy matters: GitHub says the agent captures the entire Teams thread as context. Check for secrets or sensitive customer information before invoking it.

One more deadline: GitHub says its older, separate Teams app will be retired on November 16, 2026. Existing GitHub Notifications users should update to the consolidated app; users of the legacy app should switch.

Is it worth trying?

If your team already discusses GitHub issues in Teams, this can remove a lot of context switching. Start with a small, well-defined issue and treat the generated pull request like any other contribution: read the diff, run the tests and verify the result.

Bottom line: Teams becomes a place to start a code fix, not a substitute for code review.

Sources