Microsoft is expanding enterprise administration capabilities for Copilot Cowork by bringing Power Platform connector management under the Microsoft 365 admin center. Announced on November 6, 2026, the update allows administrators to control which supported third-party connectors Cowork can use, creating a more centralized approach to managing integrations across organizational workflows.
The worldwide rollout is scheduled for completion by mid-November 2026. While the change gives IT teams greater visibility and control over connector availability, it also introduces an important governance consideration: existing Data Loss Prevention (DLP) policies configured through the Power Platform admin center do not apply to Copilot Cowork.
For organizations exploring AI-powered workflows and third-party integrations, the distinction matters. Administrators will need to review their connector settings and ensure their governance requirements are addressed before enabling additional integrations.
What Is Changing in Microsoft Copilot Cowork?
Copilot Cowork is gaining support for Power Platform connectors published as plugins. These connectors allow the AI experience to interact with supported third-party applications and services, extending the range of tasks organizations can carry out through Cowork.
Under the new arrangement, connector availability is managed through the Microsoft 365 admin center rather than relying solely on individual connection decisions.
Administrators can allow or block supported Power Platform connectors, giving organizations a centralized way to determine which integrations are available to users.
Microsoft says Cowork will respect these administrative settings when users create connections and when the system executes actions. Importantly, this enforcement also applies to connections established before a particular connector was blocked.
This means administrators are not limited to controlling new connections. They can also change the availability of previously configured integrations.
Why Microsoft Is Bringing Connector Management Into the Microsoft 365 Admin Center
Third-party integrations are becoming an increasingly important part of enterprise AI adoption. Organizations want AI assistants to work with business applications, access relevant information, and support processes that extend beyond the boundaries of a single productivity platform.
However, every additional integration introduces questions about access, oversight, and organizational policy.
For IT administrators, allowing users to connect AI tools to external services without a centralized management approach can make it harder to maintain consistent governance.
By bringing supported Power Platform connector controls into the Microsoft 365 admin center, Microsoft is giving administrators a more unified place to manage connector availability within the Cowork environment.
The change is particularly relevant for organizations that want to expand AI-assisted workflows while retaining administrative oversight over which external services users can access.
It also reflects a broader direction in enterprise AI management: organizations need to consider not only what an AI assistant can do, but also which applications it can interact with and under what conditions.
How the New Power Platform Connector Controls Work
The updated management approach introduces several important capabilities for Microsoft 365 administrators.
1. Administrators Can Allow or Block Supported Connectors
IT teams can review supported Power Platform connectors in the Microsoft 365 admin center and configure their availability according to organizational requirements.
This gives organizations more control over which third-party applications and services can be accessed through Copilot Cowork.
For example, an organization may decide that certain integrations are appropriate for its employees while others should remain unavailable until they have passed internal security and compliance reviews.
2. Previously Established Connections Are Also Affected
One of the most significant details is that Cowork respects connector availability settings even when a connection was established before the connector was blocked.
This is important because changing a connector’s availability is not simply a restriction on future connections.
Organizations can use the administrative control to address existing connections as well, reducing the risk of assuming that previously configured integrations will remain available after a policy change.
3. Cowork Automations Follow the Same Connector Policies
The new controls also extend to Copilot Cowork Automations.
This matters because automated workflows may interact with external applications without requiring users to initiate every individual action manually.
Applying connector availability policies to Automations helps ensure that these workflows operate within the same approved connector boundaries as other Cowork activities.
4. Additional Connectors Will Become Available Over Time
Microsoft is continuing to add Power Platform connectors to the Microsoft 365 admin center.
As additional supported connectors are introduced, they will become available for use in Cowork.
Organizations should therefore treat connector governance as an ongoing administrative responsibility rather than a one-time configuration exercise.
New integrations may require additional reviews before administrators decide whether to make them available to employees.
The Important Security Consideration: Power Platform DLP Policies Do Not Apply
Although the update strengthens centralized connector management, Microsoft has highlighted an important limitation that administrators should not overlook.
Power Platform admin center Data Loss Prevention (DLP) policies do not apply to Copilot Cowork.
DLP policies are commonly used in Power Platform environments to help organizations govern how business and non-business data can be used across connectors and applications.
However, administrators should not assume that existing Power Platform DLP configurations automatically provide the same protections for connector activity within Cowork.
The distinction is important for organizations with established compliance frameworks, particularly those handling confidential business information, customer records, financial data, or other sensitive organizational content.
Connector availability controls and DLP enforcement serve different governance purposes. Being able to block a connector does not mean that all existing data protection requirements are automatically enforced within the Cowork experience.
Organizations should therefore evaluate the security implications of each integration before enabling it.
Practical considerations include:
- Reviewing what information an approved third-party connector can access.
- Assessing whether the connected application is suitable for the intended business workflow.
- Checking authentication and permission requirements.
- Evaluating how the integration aligns with internal data-handling policies.
- Determining whether additional governance or monitoring measures are necessary.
- Reviewing compliance requirements before allowing employees to use new connectors.
The key takeaway is that centralized connector management improves administrative oversight, but it should not be mistaken for a complete replacement for an organization’s wider security and compliance controls.
What Happens to Existing Microsoft 365 Capabilities?
Organizations already using Copilot Cowork do not need to interpret this change as a disruption to their existing Microsoft 365 productivity integrations.
Microsoft confirms that existing capabilities involving email, calendars, Teams, and files are unaffected by the update.
The announcement specifically concerns Power Platform connectors and their availability through the Microsoft 365 admin center.
This distinction should help IT teams understand the scope of the change and focus their review on the relevant third-party integrations rather than assuming that all Cowork functionality is being reconfigured.
Rollout Timeline: When Will the Update Be Available?
Microsoft announced the change on November 6, 2026, with worldwide general availability expected to complete by mid-November 2026.
The rollout introduces connector management capabilities progressively, alongside the addition of further Power Platform connectors to the Microsoft 365 admin center.
Organizations should not assume that every supported connector will appear simultaneously. Availability will depend on Microsoft’s ongoing connector additions.
For IT departments, the rollout period provides an opportunity to review existing integration requirements and prepare an appropriate approval process.
What IT Administrators Should Do Now
Microsoft recommends that administrators review available connectors and configure their availability according to organizational requirements.
The relevant management location is:
Microsoft 365 admin center → Agents → Tools
Administrators should consider the following steps:
- Review available connectors: Identify which supported Power Platform connectors are listed in the Microsoft 365 admin center.
- Assess business requirements: Determine which third-party applications are necessary for employees and existing business processes.
- Configure connector availability: Allow or block supported connectors based on internal approval and governance requirements.
- Review existing connections: Consider how changes to connector availability could affect previously established integrations.
- Evaluate Cowork Automations: Check whether automated workflows depend on connectors that may be restricted.
- Reassess data protection requirements: Do not assume that Power Platform admin center DLP policies cover Cowork connector activity.
- Establish an ongoing review process: Revisit connector availability as Microsoft introduces additional integrations and organizational requirements change.
These steps can help organizations approach the expanded integration capabilities with a clearer understanding of their administrative responsibilities.
What This Means for Enterprise AI Adoption
The update highlights an important challenge facing organizations adopting AI assistants: expanding functionality must go hand in hand with appropriate administrative controls.
Connecting Copilot Cowork to third-party services can make it more useful across different business functions. Employees may benefit from workflows that bring together information and actions from multiple applications rather than switching between disconnected tools.
For IT teams, however, this wider connectivity also creates a need for more deliberate integration management.
The ability to control connector availability centrally is a useful step toward addressing that requirement. It gives administrators a clearer mechanism for determining which supported integrations are permitted and ensures that those settings also apply to Cowork Automations and previously established connections.
Still, the DLP limitation means organizations must take a broader view of security. Connector approval is only one part of enterprise governance, and organizations should evaluate how Cowork integrations fit into their existing compliance and data protection strategies.
What Organizations Should Watch Next
With worldwide rollout expected to finish by mid-November 2026, the next important development will be the continued addition of Power Platform connectors to the Microsoft 365 admin center.
Organizations should monitor the available connector list and assess new integrations before making them accessible to employees.
It will also be important to watch for further Microsoft guidance on enterprise governance and data protection across Cowork integrations, particularly for organizations that depend on Power Platform DLP policies in their existing environments.
For now, the message to IT administrators is straightforward: review the new connector controls, establish clear approval requirements, and do not assume that existing Power Platform DLP policies extend to Copilot Cowork.
As enterprise AI tools become more connected to business applications, the organizations best positioned to adopt them responsibly will be those that treat integration governance as part of deployment planning—not something to address after new capabilities have already reached employees.
Discover more from Dellenny
Subscribe to get the latest posts sent to your email.
