ADO MCP in Copilot

The Azure DevOps MCP Connector integrates Azure DevOps with Microsoft 365 Copilot Deep Work, enabling natural-language queries on work items and project data. Rolling out worldwide in October 2026, it supports multi-step workflows, admin controls, and user-confirmed write actions, enhancing project analysis and automation.

[What and Why:]

The Azure DevOps (ADO) MCP Connector introduces a protocol-based integration between Azure DevOps and Microsoft 365 Copilot Deep Work. This enables agents to access and analyze work items, bugs, and project data through natural language, reducing the need for manual navigation and query writing when analyzing development work.

Built on Model Context Protocol (MCP), this connector supports multi-step, agent-driven workflows and lays the foundation for write actions. Write actions are gated by user confirmation and configuration support. This supports business process automation by helping organizations bring project context into Copilot experiences while preserving admin controls.

[Rollout Schedule:]

• General Availability (Worldwide): Rollout will begin in mid-October 2026 and is expected to complete by late October 2026.

[Impact on Your Organization:]

Who is affected:

• Users who use Microsoft 365 Copilot Deep Work to analyze Azure DevOps work items, bugs, and project data.
• Admins who manage Microsoft 365 Copilot data access and Azure DevOps integration settings.
• Organizations that use Azure DevOps for project planning, engineering workflows, or issue tracking.

Platforms/Services:

• Microsoft 365 Copilot Deep Work
• Azure DevOps
• Azure DevOps MCP Connector
• Microsoft 365 admin center

What will happen:

• Users will be able to ask Microsoft 365 Copilot natural-language questions about Azure DevOps work items, bugs, and project data.
• Copilot agents will be able to access and analyze Azure DevOps data through the ADO MCP Connector when allowed by admin configuration.
• User queries and relevant Copilot context may be shared with Azure DevOps to complete requests.
• Azure DevOps data may be returned to Copilot for responses and supported actions.
• The connector supports multi-step, agent-driven workflows.
• Write actions are supported as a foundation capability and are gated by user confirmation and configuration support.
• Admins can configure the Azure DevOps data in Microsoft 365 Copilot setting in the Microsoft 365 admin center.

[Action Required/Recommendations:]

Before rollout, admins should:

• Review the Azure DevOps data in Microsoft 365 Copilot setting in the Microsoft 365 admin center.
• Choose the appropriate access scope: All users, Specific users and groups, or No user.
• Review the data-sharing notice and applicable Azure DevOps and Microsoft product terms before allowing access.
• Notify affected users and support teams before rollout.
• Update internal guidance for using Azure DevOps data with Microsoft 365 Copilot Deep Work.

[Compliance considerations:]

Does the change alter how existing customer data is processed, stored, or accessed?	User queries and relevant Copilot context may be shared with Azure DevOps to complete requests, and Azure DevOps work items, bugs, and project data may be returned to Copilot for responses and supported actions.
Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data?	The ADO MCP Connector enables Copilot agents to access and analyze Azure DevOps work items, bugs, and project data through natural language and multi-step agent workflows.
Does the change provide end users any new way of interacting with generative AI?	Users can ask Microsoft 365 Copilot natural-language questions about Azure DevOps project data and receive responses grounded in Azure DevOps content.
Does the change include an admin control and can it be controlled through Entra ID group membership?	Admins can configure the Azure DevOps data in Microsoft 365 Copilot setting in the Microsoft 365 admin center and choose All users, Specific users and groups, or No user.
Does the change allow a user to enable and disable the feature themselves?	Write actions are gated by user confirmation, and user access depends on admin configuration. The user can choose whether to initiate Copilot interactions with Azure DevOps data.