Prerequisites
- Licensing. Makers need Copilot Studio capacity / environment access; end users need Microsoft Copilot (or the channel licences your tenant requires). Agent Store setup docs assume a Microsoft Copilot licence footprint for the organisation.2
- Environment. Build in an environment where you can publish and where Data Loss Prevention (DLP) and connector policies allow the agent’s tools.
- Publish at least once. Users cannot interact in Teams / Microsoft 365 until the agent has been published.1
- Teams and Microsoft Copilot channel. Add the channel; keep Make agent available in Microsoft Copilot selected if you want Copilot (not Teams-only).1
- Authentication. Configure end-user authentication appropriate for internal agents; insecure or broken auth is a common reason admins reject or users fail after install.
- Tenant policy. Power Platform apps may need to be allowed in Teams; catalogue apps are managed separately after approval.1
- Admin partner. Someone with Microsoft 365 admin (and often Teams admin) rights must approve the request.
Step-by-step flow (maker → admin → catalogue)
-
Publish the agent
In Copilot Studio, publish so the latest content is live. Channel configuration requires a published agent.
-
Connect Teams and Microsoft Copilot
Open Channels → Teams and Microsoft Copilot. Confirm Make agent available in Microsoft Copilot if Copilot discovery is required. Add the channel.1
-
Edit store details
Set icon, colour, short/long descriptions, developer name, privacy statement, and terms of use. Incomplete About data slows or blocks approval. Note: users who already installed via link may need to reinstall to see detail changes; admin-approved agents need a new approval for icon/description updates.1
-
Share for pilot (optional but wise)
Share with a security group for collaborative testing. Optionally show to shared users under the Teams store’s Built with Power Platform section. This is not org catalogue listing.1
-
Open Availability options
In the channel panel, open Availability options.
-
Clear the teammates-only store listing before org submit
If the agent shows Added to Teams for teammates/shared users, remove it from that section first so it does not appear in two places after approval.1
-
Show to everyone in my org → submit
Select Show to everyone in my org, review requirements, then Submit for admin approval. Coordinate with other makers — only one pending submission at a time per agent path.1
-
Admin reviews in Microsoft 365 admin center
Admin opens Agents → All agents → Requests (labels may vary; see Learn), reviews capabilities and data access, then Publish / approve or reject.2
-
Appears in catalogue
After approval, the agent is managed under Built by your org in the Microsoft 365 Agent Store and Built for your org in the Teams app store (when Teams is in scope). Only admins remove it from those sections.12
-
Optional: pin / auto-install
Ask Teams admins to use app setup policies so target users get the agent without hunting the store.1
Who does what
| Step | Maker | Admin |
|---|---|---|
| Author, test, publish, channel details | Does | Advises on standards |
| Share to pilot users / groups | Does | May restrict sharing policy |
| Submit for admin approval | Does | Receives request |
| Approve / reject; assign users | Informed | Does |
| App setup policies / pin | Requests | Does |
| Remove from Built for/by your org | Cannot alone | Does |
| Content republish (topics/knowledge) | Does (often no re-approval) | Monitors |
| Icon / description change after approval | Resubmits | Re-approves |
Common gotchas
- Not published — channel and availability options expect a published agent.
- Channel not added — or Copilot checkbox cleared, so it never reaches Microsoft 365 Copilot.
- Approval pending / rejected — makers wait; only one open submission; rejected makers fix and resubmit.
- Still only in Built with Power Platform — that section is for shared users, not org-wide catalogue.
- DLP / environment policies — blocked connectors make the agent fail review or fail at runtime.
- Authentication — agent works for the maker’s identity but not for others (especially external connections).
- User cannot see it — caching in Teams; missing licence; admin assigned a subset; agent blocked in Agents inventory; user looking in the wrong store section.
- Update re-approval — content publishes freely; changing store details / team-add options on an approved agent requires a new approval request.1
- Access narrowed after submit — do not reduce access below “everyone in the organisation” after submission or installers may fail to chat.1
Troubleshooting checklist
- Agent published successfully in Copilot Studio
- Teams and Microsoft Copilot channel connected
- “Make agent available in Microsoft Copilot” on (if Copilot is required)
- Icon, descriptions, privacy, and terms completed
- Pilot share works for a security group
- Removed from Built with Power Platform before org submit
- Submitted via “Show to everyone in my org”
- Admin sees request under Agents → Requests
- After approve: appears under Built by your org
- User has Copilot / required licence and is in assigned group
- Teams desktop: sign out/in; web: hard refresh (store cache)
- Check agent not Blocked in M365 admin Agents inventory
- DLP allows required connectors; auth prompts succeed for a second user
FAQ
I shared the agent with “everyone in the organisation”. Why is it not in Agent Store?
Sharing grants permission to use the agent. Catalogue discovery for Copilot Studio agents requires submitting for admin approval through the Teams and Microsoft Copilot availability options, then admin publish/approve.12
Do I need to resubmit after every content publish?
No. Learn documents that content updates can publish without a new approval; changing listing details (icon, descriptions) or certain channel options on an already-approved agent requires a new approval.1
Where does the admin click?
Microsoft 365 admin center → Agents → All agents → Requests (wording may change — confirm on Learn’s Agent Store article).2 Teams admin center remains relevant for app setup policies and some Teams app management.
Can SharePoint declarative agents use this same catalogue path?
No. Microsoft’s agents admin guide notes declarative agents built with SharePoint cannot be published to an organisation catalogue the same way; they rely on SharePoint/.agent sharing and site Approved placement.3
UI labels in our tenant differ from this page
Expected. Microsoft iterates Agent Store and admin “Agents” pages. Treat this page as a map of concepts; verify labels on Connect and configure an agent for Teams and Microsoft 365 and Set up Agent Store.
Approved but users still cannot find it
Check assignment scope, licence, Teams cache, whether they are browsing Built by your org vs Built with Power Platform, and whether a block policy applies. Admins can also pin via setup policies.
Next: Agent Lifecycle overview · Effective Measurements · Our Goal