Publish agents for Microsoft 365 Copilot

This article describes the current state of Microsoft 365 distribution options and procedures for Copilot extensibility. Depending on its intended purpose as a line-of-business or marketable software solution, agents, plugins, and Microsoft Graph connectors can be published to your organization or to the Microsoft Commercial Marketplace through Microsoft Partner Center.

The following table summarizes the distribution support for Copilot extensibility scenarios, according to single tenant (line-of-business) or multitenant (independent software vendor, or ISV) channels.

The remainder of this article outlines the distribution processes for each Copilot extensibility type.

Microsoft 365 and Copilot program

As an independent software publisher, you can distribute your Copilot app package through the Microsoft 365 and Copilot program of Microsoft Partner Center.

Submission of your app package to the program requires compliance with the following certification policies for acceptance to in-product stores.

For agents, message extension plugins, and Microsoft Graph connectors:

• Microsoft Commercial Marketplace certification policies:
  • 100 General
  • 1140 Teams (including 1140.9 Agents for Microsoft 365 Copilot)
• Validation guidelines for agents
• Publisher verification

For Copilot Studio actions (Power Platform connectors) as plugins:

• Microsoft Commercial Marketplace certification policies:
  • 100 General
  • 5000 Power Platform Connectors (including 5000.4 Connectors with AI Plugin)
• Prepare Power Platform connector and plugin files for certification

To submit your app package to the Microsoft 365 and Copilot program in Partner Center, see the Store step-by-step submission guide.

Agents

Agents are packaged, distributed, and managed using the same Microsoft 365 app package as Teams apps that are integrated to run across the Microsoft 365 ecosystem.

When built with Copilot Studio, agents for Microsoft 365 Copilot can also be published to the organization from Copilot Studio. Distribution through Partner Center is not yet supported for agents created from Copilot Studio.

Distribute an agent to your organization

If you use Copilot Studio to create a declarative agent for Microsoft 365 Copilot, you can use Copilot Studio to publish your agent for sharing and/or submit it for publish to your organization's catalog by an admin.

If you use Teams Toolkit to build an agent for Microsoft 365 Copilot, build your app package with Teams Toolkit and upload it as a custom app package to the Integrated Apps section of Microsoft Admin Center (admin.microsoft.com). From there, admins can manage access, configure default settings, and review and consent to requested data and permissions.

Distribute your agent through Microsoft Partner Center

Before submitting your agent to Partner Center, ensure it meets all applicable:

• Microsoft Commercial Marketplace certification policies
• Store validation guidelines for Copilot extensibility

Once ready, submit your app package to Microsoft Partner Center through the Microsoft 365 and Copilot program as a Teams app.

Once validated and approved by Microsoft, your agent is an active offer in the Microsoft Commercial Marketplace and ready for IT enablement. Once enabled by an IT administrator, it appears in the Agents* category of the store within Microsoft Teams. Once deployed by an admin or acquired by a user, it will then appear as an installed agent for Microsoft 365 Copilot.

Teams message extension plugins for Copilot

Teams message extension apps used as plugins for Copilot are packaged and distributed in the same way as Teams apps that are integrated to run across the Microsoft 365 ecosystem. As such, they're available to end-users both as plugins and message extensions apps that work directly in Microsoft Teams chat and Microsoft Outlook email compose windows.

Distribute a message extension plugin to your organization

Follow these instructions to upload your custom app package to the Integrated Apps section of Microsoft Admin Center (admin.microsoft.com). From there, admins can manage access, configure default settings, and review and consent to the requested data and permissions for both your app experience and plugin experience.

Distribute a message extension plugin through Microsoft Partner Center

Before you submit your message extension app to Partner Center, make sure that it meets all applicable Microsoft Commercial Marketplace certification policies and also the guidelines for high-quality message extension plugins.

When ready, submit your app package to Microsoft Partner Center through the Microsoft 365 and Copilot program as a Teams app.

After your submission is validated and approved by Microsoft, your plugin is an active offer in the Microsoft Commercial Marketplace and ready for IT enablement. When enabled by an IT administrator, it appears in the Agents category of the store within Microsoft Teams. When it's deployed by an admin or acquired by a user, it appears as an installed plugin for Microsoft 365 Copilot.

Copilot Studio actions as plugins for Copilot

Power Platform connector actions as Copilot plugins can be shared across an organization or published broadly via Microsoft Partner Center. Once an action is published, your administrator has to review and enable the plugin for use.

Distribute a Copilot Studio action to your organization

By default, Copilot Studio actions are only visible and usable in Copilot Studio by the person who created them. They can be authorized for sharing at the Power Platform object level. Follow these instructions to publish a connector action from Copilot Studio.

Once published, an administrator must enable your connector action it before it can be used within Microsoft 365 Copilot or a custom agent, in addition to meeting the end-user prerequisites for using actions in Microsoft 365 Copilot.

Distribute a Copilot Studio action through Microsoft Partner Center (preview)

Ensure your app meets Power Platform certification criteria and Microsoft Commercial Marketplace policies for Power Platform Connectors, then submit your app package to Microsoft Partner Center through the Microsoft 365 and Copilot program as a Power Platform Connector.

Once certified and published by Microsoft, your action is available for IT enablement in the Microsoft Admin Center, with Copilot listed as one of its Host Products. Once deployed, your action will appear as an installed plugin for Copilot.

For more info, see Get your Power Platform connector and plugin certified.

Microsoft Graph connectors for Copilot

Microsoft Graph connector publishing options depend on whether you have a standalone connector or a connector that's part of a Microsoft Teams app. While both scenarios are supported for single-tenant distribution, submission to the Microsoft Partner Center Microsoft 365 and Copilot program is currently limited to Microsoft Graph connectors packaged within Teams apps.

Distribute a Microsoft Graph connector for Copilot to your organization

You can distribute standalone Microsoft Graph connectors through the Microsoft Admin Center (admin.microsoft.com). For details, see Set up and manage Microsoft Graph connectors.

You can distribute Microsoft Graph connectors within Teams apps via the Teams admin center. For details, see Enable the simplified admin experience for your Microsoft Graph connector.

Distribute a Microsoft Graph connector for Copilot through Microsoft Partner Center

For Microsoft Graph connectors within Teams apps, make sure that your app meets all applicable Microsoft Commercial Marketplace certification policies, then submit your app package to Microsoft Partner Center through the Microsoft 365 and Copilot program as a Teams app. For more information, see Make your Microsoft Graph connector available for other organizations.

After your app package is validated and approved by Microsoft, your app is an active offer in the Microsoft Commercial Marketplace and ready for IT enablement. When enabled by an IT administrator, it appears in the Agents category of the store within Microsoft Teams.