Copilot Agent Builder Add to Org Catalog

Key insights

• Submit Your Agent to the Org Catalog: Microsoft now lets makers send agents from Agent Builder directly to the organization's Org Catalog, making approved agents visible and reusable across the tenant.
  
• Roles and control: makers build and iterate on a shared agent for testing while admins review submissions, publish approved agents, and manage the enterprise store listing for broad use.
  
• Submission flow: From All agents select the agent and choose Edit, then submit to the org catalog; admins review in the Microsoft 365 admin center and, if approved, publish to Built by your org in the Agent Store.
  
• Versioning and governance: The shared version (maker-managed) and the Agent Store version (admin-managed) are separate, and the approval flow tracks submissions so admins keep control over what becomes widely available.
  
• Why it matters: Centralized governance helps scale Copilot agents safely, improves discoverability for employees, and balances fast maker innovation with enterprise scalability and oversight.
  
• Practical tips: Populate the About this agent fields before you submit to reduce re-entry, coordinate with admins on approval criteria, and prioritize catalog publication to make trusted agents easy to find.
  

Keywords

Copilot Agent Builder, submit agent to org catalog, Microsoft Copilot agent submission, publish Copilot agent to organization, Copilot agents enterprise catalog, Copilot agent deployment guide, Copilot for Microsoft 365 agents, manage organizational Copilot agents