Microsoft Teams: Channel agent orchestration with GitHub, Asana, and Jira via Model Context Protocol (MCP)

Updated August 20, 2026: We have paused rollout of this feature at this time. We will communicate via Message center when we are ready to proceed. We apologize for any inconvenience. Microsoft is introducing a new capability in Teams that enables Channel Agent to orchestrate tasks with select third-party Model Context Protocol (MCP) servers, including GitHub, Asana, and Atlassian (JIRA). This integration supports collaborative workflows that reflect real human teamwork, allowing agents to transparently reason through tasks and gather information across tools. This change helps reduce manual switching between apps and improves task completion efficiency—all within the familiar Teams environment. A Microsoft 365 Copilot license is required to use this feature. This message is associated with Microsoft 365 Roadmap ID 515466. When this will happenTargeted Release (Worldwide): Begins in mid-November 2025 and is expected to complete by end of July 2026 (previously late January). General Availability: We will communicate via Message center when we are ready to proceed.  How this affects your organization Who is affected: Microsoft 365 tenants using Teams and Channel Agent integrations. What will happen: Channel Agent will be able to collaborate with Model Context Protocol (MCP) servers like GitHub, Asana, and Jira. Users can ask Channel Agent questions and receive coordinated responses across tools:           Screenshot 1 Screenshot 2 The feature will be available in preview and requires admin enablement. A Microsoft 365 Copilot license is required. There is no impact unless enabled by tenant admins. What you can do to prepare Enable Channel Agent usage in Teams for your tenant. Allow apps that integrate with Model Context Protocol (MCP) servers such as GitHub, Asana, or Jira. Ensure users who need access have a Microsoft 365 Copilot license. Review internal documentation and update helpdesk guidance as needed. Compliance considerations No compliance considerations identified, review as appropriate for your organization.