Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Control who can use your plugin over time. Start with the plugin's controls in the Microsoft 365 admin center; use separate capability controls only when the package setting doesn't cover the access you need.
Use the Manage plugins with Microsoft Agent 365 administration map to find the page for a task and identify when a capability has controls outside the package.
Apply plugin controls
| Goal | Where | Procedure | Verify |
|---|---|---|---|
| Change who can use the plugin | Agents > Tools > Plugins > Users | Manage plugin availability for users | The intended audience can use it; users outside the scope can't. |
| Set allowed publisher categories | Agents > Settings > Agent and plugin access | Manage plugin availability at the organization level | The selected category matches organizational policy. |
| Respond to access requests | Agents > Tools > Requests | Review plugin access requests | The request is approved or rejected; verify the requester's resulting access. |
| Stop use across the organization | Agents > Tools > Plugins | Block a tool | The plugin is blocked; test access in a new conversation. |
| Restore use | Agents > Tools > Plugins | Follow the supported plugin controls for the affected package. | Its status and availability match the intended audience. |
| Change an administrator installation | Agents > Tools > Plugins | Install or uninstall as needed. | The installation state matches the plan. |
Restricted plugins can remain discoverable and users can request access. Blocking is a separate package control. In Cowork, blocking takes effect for new conversations; conversations already using the plugin continue until they end.
Apply a component control when required
Use a separate control only when the plugin-level setting doesn't cover the access or behavior you need to manage.
- If an agent included in your plugin has applicable Agent Registry controls, use those controls for agent-specific availability, deployment, ownership, requests, or lifecycle actions. See Governance and lifecycle actions for agents.
- If your plugin requires a separately managed connector connection, use the connector's product experience for connection, authentication, data-source, indexing, synchronization, or policy settings. For Power Platform connector visibility, see Overview of the Tools page.
- If your plugin references a remote MCP server, use its hosting and administration environment for credentials, authorization, security, availability, logging, and runtime controls.
- If you need to block a separately managed MCP server, follow Block or allow an MCP server. Review linked plugins and other users before applying a server-wide control.
- If your plugin uses an app registration, permission, account, or external service, use the product that owns that setting.
Blocking or uninstalling a plugin doesn't necessarily stop a remote service, revoke consent, remove indexed connector data, or prevent another plugin from using the same MCP server or connector. Check the documented effect of each action.
Verify the governance outcome
- Confirm that the plugin has the intended status and user scope.
- Test an allowed user and, when access is restricted, a user outside the scope in a new conversation.
- Verify that required agent, connection, permission, and remote-service controls enforce the intended access.
- Review access requests and assign an owner and next action to any that remain.
- Record the applied controls, exceptions, remaining dependencies, and owner.
Note
This article governs plugin packages and their included capabilities. For an existing standalone (unpackaged) item, use its product-specific administration guidance, such as Agent Registry or Manage plugins, skills, and MCP servers.