From browser access to Azure DevOps: New Microsoft 365 Copilot controls and connectors

Microsoft 365 Copilot continues to expand beyond working with information already available in Microsoft 365. Recent updates add new ways for Copilot to work with the browser, connected third-party services, and Azure DevOps data, alongside controls that let administrators decide how these capabilities are made available in their organization.

In this post, we’ll look at three updates covering browser use in Copilot Cowork, write actions for federated Copilot connectors, and the new Azure DevOps MCP Connector for Copilot Deep Work.

Browser use controls for Copilot Cowork

Copilot Cowork browser use can now be enabled for specific users and security groups, giving administrators more control over who can use Cowork to perform tasks through Microsoft Edge. The capability is disabled by default, and administrators can make it available to all users or limit access to a smaller group.

Administrators can configure browser access from Copilot > Settings > View All > Cowork settings in the Microsoft 365 admin center. From there, they can enable “Allow Cowork to use the Microsoft Edge browser to perform tasks on behalf of users” and configure which users or security groups have access.

According to the Message center, the feature rolled out globally between mid- and late September 2026.

More information:

Federated Copilot connectors can now take action

Federated Copilot connectors can now use supported tools to create, update, or delete content in connected third-party services, in addition to retrieving information. Actions use the signed-in user’s identity and permissions in the connected service, while external data continues to be accessed in real time and is not indexed into Microsoft 365.

Users must approve actions that create, update, or delete data before they are performed. Administrators can manage which federated connectors are available and who can use them, and review the tools exposed by each connector. Microsoft recommends reviewing enabled connectors against security, compliance, and acceptable-use requirements, including licensing, privacy, and data residency requirements for third-party services. Connectors that do not meet organizational requirements can be disabled. Researcher remains read-only.

According to the Message center, the worldwide rollout began in early October 2026 and is expected to complete later this month.

More information:

Azure DevOps MCP Connector brings project data into Copilot Deep Work

The Azure DevOps MCP Connector connects Azure DevOps with Microsoft 365 Copilot Deep Work. Users can ask natural-language questions about Azure DevOps work items, bugs, and project data, and the connector supports multi-step, agent-driven workflows.

Administrators can control access through the Azure DevOps data in Microsoft 365 Copilot setting in the Microsoft 365 admin center, with access configured for all users, specific users and groups, or no users. User queries and relevant Copilot context may be shared with Azure DevOps to complete requests, and Azure DevOps data may be returned to Copilot. Write actions are supported and require user confirmation and configuration support.

Administrators should review the access scope and data-sharing notice, check the applicable Azure DevOps and Microsoft product terms, and update internal guidance for affected users and support teams.

According to the Message center, the worldwide rollout began in mid-October 2026 and is expected to complete later this month.

These updates expand where Microsoft 365 Copilot can retrieve information and perform actions, while adding or retaining administrator controls over access. Browser access in Copilot Cowork can be scoped to selected users, federated connectors can now modify data in third-party services, and access to Azure DevOps data can be controlled through the Microsoft 365 admin center.

For administrators, this makes it worth reviewing existing connector configurations, access scopes, and the data-sharing implications of the capabilities being enabled.

If you'd like to stay up to date with Microsoft 365, Copilot, Teams, security, compliance, and AI-related announcements, you can follow me on LinkedIn.

Comments