|
| 1 | +--- |
| 2 | +title: Agent Store in Microsoft 365 Copilot |
| 3 | +f1.keywords: |
| 4 | +ms.author: erikre |
| 5 | +author: ErikRe |
| 6 | +manager: dansimp |
| 7 | +ms.date: 03/26/2026 |
| 8 | +ms.update-cycle: 180-days |
| 9 | +audience: Admin |
| 10 | +ms.topic: concept-article |
| 11 | +ms.service: microsoft-365-copilot |
| 12 | +ms.localizationpriority: medium |
| 13 | +ms.collection: |
| 14 | +description: Learn about Agent Store in Microsoft 365 Copilot. |
| 15 | +--- |
| 16 | + |
| 17 | +# Set up Agent Store in Microsoft 365 Copilot |
| 18 | + |
| 19 | +Agent Store is the central hub in Microsoft 365 Copilot where you can easily discover and install agents. By bringing together agents from Microsoft, trusted partners, and your own organization, Agent Store connects your team to a curated ecosystem of agents. |
| 20 | + |
| 21 | +:::image type="content" source="media/copilot-agent-store/copilot-agent-store-01.png" alt-text="Screenshot the Agent Store in Microsoft 365 Copilot." lightbox="media/copilot-agent-store/copilot-agent-store-01.png"::: |
| 22 | + |
| 23 | +There are three ways to include agents in your Agent Store environment: |
| 24 | + |
| 25 | +1. Deploy prebuilt agents to Agent Store |
| 26 | +2. Create agents with Copilot Studio publish to Agent Store |
| 27 | +3. Bring agents from external platforms to Agent Store |
| 28 | + |
| 29 | +## Prerequisites |
| 30 | + |
| 31 | +Before you begin, make sure you have the following: |
| 32 | + |
| 33 | +- A Microsoft 365 Copilot license assigned to your organization |
| 34 | +- Access to the [Microsoft 365 admin center](https://admin.microsoft.com/) with Global Admin or Teams Admin permissions |
| 35 | +- Access to Copilot Studio (if you plan to create and publish agents to Agent Store using Copilot Studio) |
| 36 | +- An Azure subscription and developer access (if you plan to publish agents built by your organization to Agent Store) |
| 37 | + |
| 38 | +## Overview |
| 39 | + |
| 40 | +The following table summarizes the three common agent deployment methods. |
| 41 | + |
| 42 | +| Method | Use case | Performed by | |
| 43 | +|---|---|---| |
| 44 | +| [Deploy prebuilt agents](#deploy-prebuilt-agents) | Deploy agents from Microsoft and trusted partners. | Admin | |
| 45 | +| [Create and publish with Copilot Studio](#create-and-publish-copilot-studio-agents-built-by-your-organization) | Create custom agents using a natural language authoring tool. | Maker/Admin | |
| 46 | +| [Bring agents from external platforms](#bring-agents-from-external-platforms) | Connect agents built on external platforms or custom code. | Developer/Admin | |
| 47 | + |
| 48 | +> [!NOTE] |
| 49 | +> Agents built using Agent Store. |
| 50 | +
|
| 51 | + |
| 52 | +## Deploy prebuilt agents |
| 53 | + |
| 54 | +Prebuilt agents are available from Microsoft and trusted partners. Use this method to browse and enable agents in [Microsoft 365 admin center](https://admin.microsoft.com/) that are already built and verified. No development work is required. |
| 55 | + |
| 56 | +### Step 1: Browse the agent catalog (Admin) |
| 57 | + |
| 58 | +1. Go to the [Microsoft 365 admin center](https://admin.microsoft.com/). |
| 59 | +2. Select **Agents** > **All agents** to open the agent catalog. |
| 60 | +3. Review the available agents from Microsoft, verified third-party providers, and your organization. |
| 61 | + |
| 62 | +### Step 2: Review agent details and configure access (Admin) |
| 63 | + |
| 64 | +1. In the agent table, select an agent to open its details pane. |
| 65 | +2. Review the agent’s information based on availability and capability: |
| 66 | +- Select **Overview** to view details, such as **Publisher**, **Channel**, and **Last updated**. |
| 67 | +- Choose **Users** to assign and deploy to users or to allow users to install. |
| 68 | +- Select **Data & tools** to view **Capabilities**, **Knowledge**, and **Actions**. |
| 69 | +- Select **Security & compliance** to view agent risks and protections. |
| 70 | +- Choose **Certification** to view the certification or publisher attestation information available for the agent. |
| 71 | +- Select **Activity** when you’ve previously deployed the agent and want to confirm usage data. |
| 72 | + |
| 73 | +### Step 3: Configure agent assignment and availability (Admin) |
| 74 | + |
| 75 | +1. After choosing an agent, select **Users** > **Deployed to**. Choose who the agent is assigned to by selecting **Just me**, **Entire organization**, or **Specific users/groups**. |
| 76 | +2. To restrict access to an agent, select **Block** or **Remove** from the agent details page. |
| 77 | + |
| 78 | +### Step 4: Make the agent available in Agent Store (Admin) |
| 79 | +1. After you’ve made an agent available from the [Microsoft 365 admin center](https://admin.microsoft.com/), it becomes available in Agent Store inside Microsoft 365 Copilot. |
| 80 | +2. Users can find and install the agent from Agent Store, which is accessible across Microsoft 365 apps including Teams, Outlook Word, Excel, and PowerPoint. |
| 81 | + |
| 82 | +## Create and publish Copilot Studio agents built by your organization |
| 83 | + |
| 84 | +Use this method to create a custom agent using Copilot Studio, the native agent development platform for Microsoft 365 Copilot. Makers at your organization build and submit agents for review in Microsoft 365 admin center. Admins review and approve these agents in [Microsoft 365 admin center](https://admin.microsoft.com/) before they become available to users in Microsoft 365 Copilot. |
| 85 | + |
| 86 | +> [!NOTE] |
| 87 | +> In addition to building agents with Microsoft Azure AI Foundry, custom code, or third-party AI platforms, agents can also be built and shared using Agent Builder within Microsoft 365 Copilot. |
| 88 | +
|
| 89 | +### Step 1: Build the agent in Copilot Studio (Maker) |
| 90 | + |
| 91 | +1. In Copilot Studio, select **Agents** from the menu on the left. Select **Create blank agent** in Copilot Studio and follow the prompts to define your agent using natural language instructions, articles, and actions. |
| 92 | +2. Add and configure instructions, knowledge, search, tools, articles, and any required integrations. |
| 93 | +3. Test the agent in the built-in test panel before publishing. Publishing makes the agent available to the Admin within [Microsoft 365 admin center](https://admin.microsoft.com/). |
| 94 | + |
| 95 | +### Step 2: Submit the agent for admin approval (Maker) |
| 96 | +1. In Copilot Studio, select the **Channels** tab for your agent. |
| 97 | +2. Select **Microsoft 365 Copilot and Microsoft Teams** as the publishing channel. The related pane will show channel specific settings. |
| 98 | +3. Confirm that **Make agent available in Microsoft 365 Copilot** has been selected. |
| 99 | +4. Select **Edit details** to configure how your agent will be displayed. Once complete, select **Save** to return to the channel specific settings. |
| 100 | +5. Select **Save** to send the agent for admin review. Once the agent is reviewed and published in the [Microsoft 365 admin center](https://admin.microsoft.com/), you're able to view your agent in Agent Store. |
| 101 | + |
| 102 | +> [!NOTE] |
| 103 | +> The agent isn't visible to users until an Admin approves the request. After approval, the agent appears under **Agents** > **All agents** > **Built by your org** in Agent Store. |
| 104 | +
|
| 105 | +### Step 3: Review and approve the agent request (Admin) |
| 106 | +1. In the [Microsoft 365 admin center](https://admin.microsoft.com/), select **Agents** > **All agents** > **Requests**. |
| 107 | +2. Select the pending requested agent to review agent details, including capabilities, data access, and maker information. |
| 108 | +3. Select **Publish** to make the agent available in the **Built by your org** collection in Agent Store, or **Reject** to decline the request. |
| 109 | + |
| 110 | +If the request is rejected, Copilot Studio notifies the maker so they can make changes and resubmit. |
| 111 | + |
| 112 | +## Bring agents from external platforms |
| 113 | + |
| 114 | +Use this method to bring agents built outside of Copilot Studio into Microsoft 365 Copilot and Agent Store, including those on Microsoft Azure AI Foundry, custom code, or third-party AI platforms. |
| 115 | + |
| 116 | +### Step 1: Package the agent using the Microsoft 365 Agent Toolkit (Developer) |
| 117 | +1. Install the [Microsoft 365 Agents Toolkit](https://aka.ms/M365AgentsToolkit) and [Microsoft 365 Agents SDK](/microsoft-365/copilot/extensibility/m365-agents-sdk). |
| 118 | +2. Create and configure a bot service resource in Azure. |
| 119 | +3. Configure the agent event listeners to handle Microsoft 365 Copilot interactions. |
| 120 | +4. Prepare the agent manifest package according to the toolkit requirements. |
| 121 | + |
| 122 | +> [!TIP] |
| 123 | +> For full setup instructions, see [Bring your agents into Microsoft 365 Copilot](/microsoft-365/copilot/extensibility/bring-agents-to-copilot). |
| 124 | +
|
| 125 | +### Step 2: Submit the packaged agent to the organizational catalog (Developer) |
| 126 | +1. Once the agent is packaged using the Microsoft 365 Agent Toolkit, submit it to your organization’s agent catalog directly from the toolkit. |
| 127 | +2. Verify that the agent appears as a pending request in the [Microsoft 365 admin center](https://admin.microsoft.com/). |
| 128 | + |
| 129 | +### Step 3: Review and approve the agent request (Admin) |
| 130 | +1. In the [Microsoft 365 admin center](https://admin.microsoft.com/), select **Agents** > **All agents** > **Requests**. |
| 131 | +2. Select the agent with the pending request to review the agent details. |
| 132 | +3. Select **Approve** to publish the agent to Agent Store, or **Reject** to decline the request. |
| 133 | + |
| 134 | +After approval, the agent is available to users in Agent Store within Microsoft 365 Copilot. |
| 135 | + |
| 136 | +## Related content |
| 137 | + |
| 138 | +- [Learn about Copilot Studio](/microsoft-copilot-studio/) |
| 139 | +- [Manage agents in the Microsoft 365 Admin Center](/microsoft-365/admin/) |
0 commit comments