GitHub Copilot Cloud Agent in Microsoft Teams

GitHub is expanding its Copilot suite into Microsoft Teams with a new cloud agent feature. This integration aims to bridge the gap between meeting discussions and code execution, allowing teams to turn chat into actionable development work.

Collaborative Agent Sessions

The core functionality allows users to initiate a GitHub Copilot cloud agent session directly within Microsoft Teams. By mentioning @GitHub in a channel, thread, or direct message, the system starts a session visible to all participants.

Anyone in the conversation can ask questions, add context, and steer the work. Participants with write access to the repository can trigger Copilot to make changes based on the discussion.

Workflow: From Meeting to Ready Work

GitHub highlights a specific workflow called “Turn meeting decisions into ready work.” During a team standup or discussion, users can hand action items to Copilot. For example, a team can discuss a problem and ask Copilot to investigate while the meeting is ongoing. The agent’s investigation is visible to everyone, allowing the team to direct it further before the meeting ends.

Async Work in Secure Sandboxes

Tasks started in Teams can be handed off to a secure cloud sandbox where Copilot works asynchronously. Users can follow progress in the channel thread and then continue working with the agent-generated artifacts from their terminal, the GitHub Copilot app, or their preferred IDE.

Availability and Billing

As of the release, the public preview is available only to users on paid GitHub Copilot plans. GitHub Copilot cloud agent sessions started in Teams consume AI credits. For organizations, this usage is governed by usage-based billing budgets. Cloud sandbox usage is billed separately and can be controlled via product-level or SKU-level budgets.

Compliance and Governance

Security and compliance are addressed through an additional approval step for pull requests. Repository administrators can now require an extra approval for any pull request attributed to the Microsoft Teams Copilot integration identity before it can merge. If a repository already requires two approvals, enabling this feature means Copilot-created pull requests will require three approvals, effectively keeping a human in the loop.