Make your plugin available and govern access

After you publish or share a plugin, complete the setup and access actions its method requires. A Microsoft 365 administrator handles actions that require administrator permissions. The plugin owner and intended users complete the rest.

If you built the plugin, give the responsible administrator or owner:

• The plugin identity and exact version.
• The published listing or package.
• The intended users or groups and supported Microsoft 365 experiences.
• Required licenses, permissions, consent, connections, and external services.
• Setup instructions and a support contact.

Publishing or sharing distributes the plugin. It doesn't ensure that every intended user can use it in every Microsoft 365 experience. Users might need to sign in, grant consent, or connect an account. Some direct-sharing methods require no administrator action.

Manage plugins with Microsoft Agent 365

Microsoft Agent 365 is the administrative control plane for observing, governing, and securing agents and the tools they use. Use its controls in the Microsoft 365 admin center to manage plugin packages, access, and requests.

Use the page that matches the object and task you're managing:

The inventories are related but not interchangeable:

• Tools Registry inventories plugin packages, skills, MCP servers, and connectors. For an overview, see Overview of the Tools page.
• Agent Registry inventories agents and provides agent-specific ownership, availability, deployment, and lifecycle controls. For the supported actions, see Governance and lifecycle actions for agents.

For authoritative procedures, see Manage plugins, skills, and MCP servers, Agent Registry, Agent Requests, and agent details.

Manage the plugin package to control its installation and availability. Also check separate controls when a packaged agent has an Agent Registry record, a connector requires separate connection or policy controls, a remote MCP server has separate hosting or runtime controls, or an app registration, permission, or external service is managed by another product. A control on the plugin doesn't automatically govern every dependency.

Choose the next task

Follow the instructions for your publishing or sharing method. Complete only the review, approval, acquisition, installation, assignment, enablement, and connection actions that apply.

When a capability has its own controls

Manage the plugin as the product. Start with its availability and access settings, and use the administration map in Manage plugins with Microsoft Agent 365 to find the right administration surface.

Plugin availability doesn't grant access to external services or data. Complete the authentication, consent, permissions, and connection steps required by the plugin's capabilities.

An included agent, connector connection, or remote MCP server can also have separate controls. Follow the owning product's guidance when those controls are necessary to manage the plugin. Don't assume that changing the plugin's settings changes every component, connection, or external service.

Check that users can use the plugin

Before finishing setup, confirm that:

• Intended users can find or receive the expected plugin version.
• They can access each Microsoft 365 experience you intend to support.
• They can complete any required sign-in, consent, and connections.
• They can successfully perform the intended task.
• The plugin's access settings meet your organization's requirements.

Record the verified audience, experiences, plugin version, completed setup actions, and support owner.

If something prevents users from using the plugin, record the issue, its effect on the intended users, and the person responsible for resolving it.

Related content

• Publish or share your plugin
• Manage plugins with Microsoft Agent 365
• Make your plugin available
• Govern plugin access and connections
• Monitor your plugin
• Improve and update your plugin
• Retire your plugin