Understand Agents in Microsoft Copilot

In Microsoft Copilot, agents appear in the Plugins page. To open it, select Plugins in the left pane. Plugins brings together agents from Microsoft, trusted partners, and your own organization, and connects your team to a curated ecosystem of AI resources.

Note

Agent Store used to appear as Agents & Skills or Agent Store in the left pane of Microsoft Copilot. It now appears as Plugins, and agents are listed with other plugins, such as skills and connectors. Agents that you added before this change are listed under Added on the Plugins page. You can also open them from Agents in the left pane.

Agents are a type of plugin. On the Plugins page, agents appear alongside skills and connectors. The Plugins page has two tabs:

  • Chat: Agents and plugins that you use in Copilot Chat. This article describes the Chat tab.
  • Cowork: Plugins, connectors, and skills that you use in Copilot Cowork.

Note

For information about plugins that you can use with Copilot Cowork, see Manage plugins for Copilot Cowork.

Screenshot of the Plugins page in Microsoft Copilot, with the Added section and the Discover section.

The Plugins page has two main sections. Added lists the agents and plugins that you already have. Discover lists the agents and plugins that you can add, grouped into categories. To show only certain categories, select Filter categories next to Discover. To find a specific agent, use the Search for a plugin box.

The following table describes each section and category.

Section or category Description
Added The agents, skills, and connectors that you added, plus any that Microsoft or your admin installed for you. For example, Microsoft preinstalls and pins some agents in Microsoft Copilot for all licensed users. To see all of your added items, select Manage all. On the Manage all page, you can filter by Agents, Connectors, or Skills. You can also choose whether Copilot can use certain plugins automatically for relevant tasks.
Built by Microsoft Agents that Microsoft builds and maintains. With your Microsoft Copilot subscription, you have access to several Microsoft agents. Some agents, such as Researcher and Analyst, are built in to Copilot. You can add others. If an agent doesn't appear, you might not have a Microsoft Copilot license, or your admin might not have turned on the agent.
Built by your org Custom agents that makers and developers in your organization created for internal use. Makers build agents and submit them for review. Admins review and approve these agents in the Microsoft 365 admin center before users can see them. Makers can build agents with Agent Builder or Copilot Studio. Developers can also bring agents from external platforms, including Microsoft Foundry, custom code, or third-party AI platforms.
Agents for your team Agents built with or extended by the Microsoft Agent 365 SDK. These agents work alongside your team like a teammate. The SDK gives these agents an identity backed by Microsoft Entra, governed access to Microsoft 365 data through managed MCP servers, and full observability. These agents can also receive and respond to notifications in Teams, Outlook, and Word, just like a person. Each agent inherits the compliance, governance, and security policies that your organization defines.
Featured A curated selection of agents. It highlights new or useful agents from Microsoft, trusted partners, and your own organization. What appears here can change over time.
More plugins All other agents and plugins available to you, including agents from Microsoft partners.

To learn more about an agent, select it to open its details pane. The details pane shows what the agent includes, where it works, its pricing, its skills, its permissions, and its reviews. To use an agent, select Add. If you already added the agent, select Open instead. With a work or school account, some agents need approval from your IT admin. For these agents, you see Request approval instead of Add.

Prerequisites

Before you begin, make sure you have the following:

  • A Microsoft Copilot license assigned to your organization
  • Access to the Microsoft 365 admin center with Global Admin or Teams Admin permissions
  • Access to Copilot Studio, if you plan to use Copilot Studio to create agents and publish them to Copilot
  • An Azure subscription and developer access, if you plan to publish agents that your organization builds on external platforms

Important

Microsoft recommends that you use roles with the fewest permissions. Using roles with the fewest permissions helps improve security for your organization. Global Administrator is a highly privileged role that should be limited to emergency scenarios when you can't use an existing role. For more information, see About administrator roles in the Microsoft 365 admin center.

Overview

An agent is a specialized AI assistant that extends Copilot for a specific area of work. It uses your organization's knowledge and automation to find information, summarize data, or take actions such as sending emails or updating records. A declarative agent gives users a goal-directed conversational experience. You define its purpose, instructions, knowledge, and supported actions.

You can deploy agents in different ways, depending on where you built the agent.

Method Use case Performed by
Deploy prebuilt agents Deploy agents from Microsoft and trusted partners. Admin
Create and publish Agent Builder agents Create and publish a declarative agent with Agent Builder, the built-in agent authoring tool in Microsoft Copilot. Maker/Admin
Create and publish agents with Copilot Studio Create custom agents with a natural language authoring tool. Maker/Admin
Bring agents from external platforms Connect agents that you built on external platforms or with custom code. Developer/Admin
Integrate agents with the Agent 365 SDK Integrate your agent with the Agent 365 SDK. Developer/Admin

Deploy prebuilt agents

Microsoft and trusted partners provide prebuilt agents. Admins can use this method to browse and turn on agents that are already built and verified. You do this in the Microsoft 365 admin center, and no development work is needed.

Step 1: Browse the agent catalog (Admin)

  1. Go to the Microsoft 365 admin center.
  2. Select Agents > All agents to open the agent catalog.
  3. Review the available agents from Microsoft, verified third-party providers, and your organization.

Step 2: Review agent details and configure access (Admin)

  1. In the agent table, select an agent to open its details pane.
  2. Review the agent's availability and capabilities:
    • Select Details to view details such as Publisher, Channel, and Last updated.
    • Select Users to assign and deploy the agent to users, or to let users install it.
    • Select Data & tools to view the agent's Capabilities, Knowledge, and Actions.
    • Select Security to view agent policies and protections.
    • Select Certification to view certification or publisher attestation information for the agent.
    • Select Activity to view usage data for an agent that you already deployed.

Note

The tabs in the details pane can differ from agent to agent, depending on what each agent can do.

Step 3: Preinstall an agent for users (Admin)

  1. In the agent table, select an agent to open its details pane.
  2. Select Install to start the preinstall process.
  3. Choose who gets the agent: Just me, All users, or Specific users/groups.
  4. Select Next, and then review the permissions.
  5. Select Next, and then review the preinstall details.
  6. Select Finish installation.

Step 4: Make the agent available in Copilot (Admin)

  1. In the agent table, select an agent, and then select Users > Available to.
  2. Choose who can use the agent: All users, No users, or Specific users/groups.

After you make an agent available in the Microsoft 365 admin center, users can find it on the Plugins page in Microsoft Copilot and add it. Agents are available across Microsoft 365 apps, including Teams, Outlook, Word, Excel, and PowerPoint.

Note

To restrict access to an agent, select Block or Remove on the agent details page in the Microsoft 365 admin center.

For more information about managing agents, see Manage agents in the Microsoft 365 admin center.

Create and publish Agent Builder agents

Use this method to create a declarative agent with Agent Builder, the built-in agent authoring tool in Microsoft Copilot. Makers in your organization select New agent on the Plugins page to build an agent. Then they submit the agent to the organization's catalog directly from Agent Builder. Admins review and approve these agents in the Microsoft 365 admin center. After approval, the agents appear in the Built by your org category the Plugin section.

Note

Agent Builder doesn't support authoring actions that integrate external services. To add low-code actions, connectors, or workflows, copy the agent to Copilot Studio, and then follow the Copilot Studio publishing steps.

Tip

Makers can also share an Agent Builder agent directly with specific people or groups. Sharing doesn't need admin review, and the agent appears in the Shared with you category for those people. Sharing works best when you're iterating, piloting, or distributing to a known audience. Submitting to the org catalog works best when you want to make a production-ready agent broadly available in your organization.

Step 1: Build the agent in Agent Builder (Maker)

  1. In Microsoft Copilot, select Plugins in the left pane, and then select Chat > New agent.
  2. Choose how to build your agent:
    • Describe: Describe the agent in natural language. Agent Builder generates the name, description, instructions, knowledge sources, and suggested prompts for you. We recommend this approach.
    • Skip to configure: Configure the agent yourself on the Configure tab.
    • Start with a template: Choose a template that already has a description, instructions, and prompts for a specific use case.
  3. On the Configure tab, review and refine the agent's name, icon, description, instructions, knowledge sources, and starter prompts. Turn on capabilities such as Create documents, charts, and code and Create images as needed.
  4. Test the agent on the Preview tab.
  5. Select Create. The agent doesn't exist until you select Create. You can't submit the agent to your org catalog until you publish it at least once.

For more information about Agent Builder, see the following resources:

Step 2: Submit the agent to your org catalog (Maker)

  1. In Microsoft Copilot, select Plugins in the left pane, and then select Chat. In the Added category, select Manage all.

  2. Find the agent that you want to submit. Select More options (...) next to the agent, and then select Edit. The agent opens in Agent Builder.

  3. If your agent has unpublished changes, select Update to publish them. The submission uses the latest published version of your agent.

  4. In the Agent Builder header, select More (...), and then select Submit to your org catalog. You can also select the Submit to your catalog link in the share dialog or in the dialog that appears after you publish.

  5. In the submission dialog, complete the following required fields:

    Field Maximum length Description
    Display name 30 characters The name that appears in Copilot.
    Short description 80 characters A short summary of what the agent does.
    Developer name 32 characters Your name or your team's name.
    Creator website 2,048 characters A valid HTTPS link to more information about you or your team.
    Privacy statement 2,048 characters A valid HTTPS link to your organization's privacy statement.
    Terms of use 2,048 characters A valid HTTPS link to your organization's terms of use.

    Replace any default placeholder links with your own URLs. Short description, Creator website, Privacy statement, and Terms of use are prefilled from the agent's About this agent settings.

  6. Select Continue. Agent Builder saves your changes, publishes the updated version, and submits the agent for admin review. The dialog shows Submitted for admin approval.

  7. Select Done.

Note

The agent doesn't appear in Copilot until an admin approves the request. To check the status, open the agent in Agent Builder, and then select More (...) > Submit to your org catalog. The dialog shows Waiting for approval, Approved, or Rejected by your admin. After approval, the agent appears in the Built by your org category on the Plugins page.

Important

Changes that you publish with Update in Agent Builder don't automatically flow to Copilot. To update the Copilot version, resubmit the agent for admin approval. Until an admin approves the update, users who add the agent from Copilot get the last approved version.

For more information, see Submit agents from Agent Builder to your org catalog.

Step 3: Review and approve the agent request (Admin)

  1. In the Microsoft 365 admin center, select Agents > All agents > Requests.
  2. Select the pending request to review the agent's details. These details include the display name and short description, capabilities and knowledge sources, sensitivity label, and developer information.
  3. Select Publish to store to add the agent to the Built by your org category of the Plugin section of Copilot, or select Reject submission to decline the request. The publishing wizard lets you choose who can install the agent, apply a policy template, and review permissions.

If you reject the request, the maker sees your comment in Agent Builder. The maker can then make changes and resubmit the agent.

Create and publish Copilot Studio agents built by your organization

Use this method to create a custom agent with Copilot Studio, the native agent development platform for Microsoft Copilot. Makers in your organization build agents and submit them for review. Admins review and approve these agents in the Microsoft 365 admin center before users can see them in Microsoft Copilot.

Note

You can also build agents in Microsoft Foundry, with custom code, or on third-party AI platforms. Makers can also build and share agents with Agent Builder in Microsoft Copilot.

Step 1: Build the agent in Copilot Studio (Maker)

  1. In Copilot Studio, select Agents in the left pane. Select New agent, and then follow the prompts to define your agent with natural language instructions, articles, and actions.
  2. Add and configure instructions, knowledge, search, tools, articles, and any integrations that you need.
  3. Test the agent in the built-in test panel before you publish it. Publishing makes the agent available to admins in the Microsoft 365 admin center.

For more information about Copilot Studio, see the following resources:

Step 2: Submit the agent for admin approval (Maker)

  1. In Copilot Studio, select the Channels tab for your agent.
  2. Select Microsoft Copilot and Microsoft Teams as the publishing channel. The pane shows settings for that channel.
  3. Make sure that Make agent available in Microsoft Copilot is selected.
  4. Select Edit details to set how your agent appears. When you're done, select Save to return to the channel settings.
  5. Select Save to send the agent for admin review.

Note

The agent isn't visible to users until an admin approves the request. After approval, the agent appears in the Built by your org category on the Plugins page.

Step 3: Review and approve the agent request (Admin)

  1. In the Microsoft 365 admin center, select Agents > All agents > Requests.
  2. Select the pending request to review the agent's details, including its capabilities, data access, and maker information.
  3. Select Publish to store to add the agent to the Built by your org category of the Plugin section or Copilot, or select Reject submission to decline the request.

If you reject the request, Copilot Studio notifies the maker so that they can make changes and resubmit.

Bring agents from external platforms

Use this method to bring agents that you built outside Copilot Studio into Microsoft Copilot. These include agents built in Microsoft Foundry, with custom code, or on third-party AI platforms.

Step 1: Package the agent with the Microsoft 365 Agents Toolkit (Developer)

  1. Install the Microsoft 365 Agents Toolkit and the Microsoft 365 Agents SDK.
  2. Create and configure a bot service resource in Azure.
  3. Configure the agent's event listeners to handle Microsoft Copilot interactions.
  4. Prepare the agent manifest package to meet the toolkit requirements.

Tip

For full setup instructions, see Bring your agents into Microsoft Copilot.

Step 2: Submit the packaged agent to your org catalog (Developer)

  1. After you package the agent with the Microsoft 365 Agents Toolkit, submit it to your organization's agent catalog directly from the toolkit.
  2. Make sure the agent appears as a pending request in the Microsoft 365 admin center.

Step 3: Review and approve the agent request (Admin)

  1. In the Microsoft 365 admin center, select Agents > All agents > Requests.
  2. Select the pending request to review the agent's details.
  3. Select Publish to store to add the agent to the Built by your org category of the Plugin section of Copilot, or select Reject submission to decline the request.

After approval, users can find the agent on the Plugins page in Microsoft Copilot.

Integrate your agent with the Agent 365 SDK

Some organizations already built agents with other SDKs or platforms, such as Copilot Studio, Microsoft Foundry, the OpenAI Agents SDK, or custom code. The Microsoft Agent 365 SDK can add enterprise capabilities to these agents without a full rebuild.

The Agent 365 SDK gives agents an identity backed by Microsoft Entra, governed access to Microsoft 365 data through managed MCP servers, and full observability. It also lets agents receive and respond to notifications in Teams, Outlook, and Word, just like a person. Agents run within an IT-approved blueprint system, so each agent instance inherits the compliance, governance, and security policies that your organization defines.

When you finish building these Agent 365-enabled agents, they appear in the Agents for your team category of the Plugin section of Copilot. This option works well for organizations that want to bring agents into Copilot and make sure the agents meet the same enterprise standards as every other agent in the catalog.