Disabling CoPilot Plug-Ins

2026-11-16T19:59:42.5866667+00:00

We currently have users who are getting familiar with creating agents in our environment and we are running into an issue with publishing the agents because of plug ins that require admin rights. We would like to disable all plug ins and work on enabling the ones that are needed. (1) is this the correct approach?, (2) where can we be disable these plug ins, Power Platform admin or Tenant admin console? (3) if there's a better way, can you share?

Microsoft 365 and Office | Install, redeem, activate | For business | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. AI answer

    2026-11-17T13:07:11.48+00:00

    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.

    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.

    1. Open Power Platform admin center.
    2. Go to Security → Data and privacy → Data policy.
    3. Create a policy, or edit your existing Copilot Studio policy.
    4. Add the development or training environments to the policy.
    5. On Assign connectors, place approved connectors in the appropriate Business or Non-business group.
    6. Put unapproved, blockable connectors in Blocked.
    7. Save and publish the policy.
    8. 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:

    1. In Power Platform admin center, go to Security → Data and privacy → Data policy.
    2. Edit the policy.
    3. Under Prebuilt connectors, find a blockable connector.
    4. Select More actions → Configure connectors → Connector actions.
    5. Allow or deny individual actions.
    6. 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:

    1. Go to Microsoft 365 admin center → Agents → All agents.
    2. Select the agent.
    3. Select Block.
    4. 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^

    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

    1. Make plugins and agents available and govern access
    2. Configure data policies for agents
    3. Connector action control
    4. Governance and lifecycle actions for agents available in Microsoft 365 admin center
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Ana Le 2,980 Reputation points Independent Advisor
    2026-11-17T08:32:30.39+00:00

    Hello,

    For the primary control of Copilot plug-ins, I would recommend using the Microsoft 365 admin center rather than the Power Platform admin center. You can navigate to:

    Microsoft 365 admin center, extend Agents and click on Settings. Then, choose Agent and plugin access

    Under the installation settings, administrators can control plug-in availability based on the following publisher categories: Microsoft, your organization, all external publishers or only certified external publishers. It will be the same as the screenshot below:

    enter image description here

    This allows your organization to establish which types of plug-ins users are permitted to access and provides greater control while users become familiar with creating and publishing agents. I hope this information helps. Please feel free to let me know if you have any further questions or concerns.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.