Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
Use a Power Platform data policy to block unapproved connectors in the Copilot Studio environments, then allow only the connectors or connector actions your agents require; plugin deployment and tenant consent must be governed separately.
Recommended approach: controlled allow-list
Disabling everything and enabling approved capabilities incrementally is a valid starting posture, but there is no single “disable all plugins” control covering every layer. Microsoft separates these controls:
- Power Platform admin center: Copilot Studio connector usage and data policies.
- Microsoft 365 admin center: Plugin/agent inventory, availability, installation, requests, and blocking.
- Microsoft Entra admin center: Application permissions and tenant-wide consent.
- Owning product/service: Connection authentication and source permissions. ^1^
For your publishing failures, start with Power Platform data policies, because Copilot Studio evaluates connector policy when agents are published and enforces violations in real time. ^2^
1. Create the connector baseline in Power Platform
You need a tenant administrator or the Environment Admin role for the environments in scope.
- Open Power Platform admin center.
- Go to Security → Data and privacy → Data policy.
- Create a policy, or edit your existing Copilot Studio policy.
- Add the development or training environments to the policy.
- On Assign connectors, place approved connectors in the appropriate Business or Non-business group.
- Put unapproved, blockable connectors in Blocked.
- Save and publish the policy.
- Test by republishing an agent in the targeted environment.
Data policies can specifically prevent makers from:
- Using selected Power Platform connectors as tools.
- Making HTTP requests.
- Using Azure Bot Service skills.
- Publishing to selected channels.
- Adding event triggers.
- Publishing agents without authentication. ^2^
Do not indiscriminately block every Copilot Studio connector: blocking all publishing channels, for example, can leave the agent with no permitted publication target.
2. Restrict individual connector actions where possible
If an entire connector is too broad, configure allowed and denied operations:
- In Power Platform admin center, go to Security → Data and privacy → Data policy.
- Edit the policy.
- Under Prebuilt connectors, find a blockable connector.
- Select More actions → Configure connectors → Connector actions.
- Allow or deny individual actions.
- Set Default connector action settings to Block if newly introduced actions should require approval.
This creates an allow-list within a connector, rather than approving every operation it exposes. This control applies to blockable prebuilt connectors; it does not support unblockable or custom connectors. Trigger-level controls currently require PowerShell. The administrator also needs Power Apps access so the action list can be retrieved. ^3^
3. Govern plugin and agent availability in Microsoft 365
Connector policy does not determine whether a published plugin or agent is available to users. In the Microsoft 365 admin center, use:
- Agents → Settings → Agent and plugin access — control availability by publisher category.
- Agents → Tools → Plugins → [plugin] → Users — make a plugin available only to selected users or groups.
- Agents → Tools → Requests — review plugin access requests.
- Agents → All agents → Requests — review agent submissions; this is a separate queue.
- Agents → Tools — install, uninstall, block, or delete a supported plugin. ^1^
For a published agent that must be disabled tenant-wide:
- Go to Microsoft 365 admin center → Agents → All agents.
- Select the agent.
- Select Block.
- Select Block agent → Save.
Blocking a Copilot Studio or Copilot Agent Builder agent affects its availability in Microsoft Copilot and host applications such as Teams and Outlook. ^4^
4. Handle admin-consent requirements separately
If publishing reports that a capability requires administrator approval, determine whether it is:
- A blocked connector/action: change the Power Platform data policy only after approval.
- A plugin availability or installation request: process it under Microsoft 365 Agents.
- An application permission or tenant-wide consent request: review it in Microsoft Entra.
- A connection or source-permission problem: configure it in the owning service.
Publishing, approval, availability, assignment, consent, and connection are separate operations; successfully publishing an agent does not automatically grant users access to its services. ^1^
A practical rollout is to use separate development and production environments, apply a restrictive allow-list to both, and permit production plugins or agents only to approved security groups after connector, permission, data-access, and publishing tests pass.
References