Skip to main content
🦉
Message CenterMicrosoft 365 Updates
HomePermissionsTenant FinderM365 ReportPortfolio
🦉
M365 Message Centerby Cengiz YILMAZ

Track the latest updates, features, and announcements for Microsoft 365 services. Comprehensive archive of service updates and important changes.

Quick Links

HomePermissionsTenant FinderM365 ReportPortfolio

Connect

© 2026 M365 Message Center. Created with ❤ by Cengiz YILMAZ

Data sourced from Microsoft 365 Message Center • Not affiliated with Microsoft

  1. Home
  2. /
  3. MC1280557

Submit agent to the Agent Store from Agent Builder

Plan for Change
Major Change

Message ID

MC1280557
View in Admin Center

Roadmap ID

557173
View in Roadmap

Services

Microsoft 365 suite

Affected Platforms

DesktopWeb

Summary

Starting mid-May 2026, Agent Builder users can submit agents for admin review before publishing to the organization's Agent Store catalog. Admins control approval, access, and deployment. Approved agents appear in the store for users to discover and install, with updates requiring reapproval. No pre-rollout action needed.

Details

Introduction

We're introducing the ability to submit agents built with Agent Builder for administrator review and approval before publishing to the organization's catalog in the Agent Store—making it easier to scale distribution of high-quality internal agents while maintaining IT admin control. Once approved, agents appear in the Built by your org section of the Agent Store, where users across the org can discover and install them.

This message is associated with Microsoft 365 Roadmap ID 557173.

When this will happen:

General Availability (Worldwide): Rollout will begin in mid‑May 2026 and is expected to complete by late May 2026.

How this affects your organization:

Who is affected:

  • Users of Agent Builder.
  • Microsoft 365 administrators responsible for reviewing and publishing agents.
  • Users who discover and install organization‑approved agents from the Agent Store.

What will happen:

There is no impact to users unless an agent is submitted, approved, and published by an administrator. Here is how it works:

  • Submission: Agent Builder users can request org publishing of their agents by selecting Submit to your org catalog, including in tenants with sharing controls.
  • Screenshot 1: Agent Builder menu showing the Submit to your org catalog option for requesting administrator review and approval:

    user settings>

  • Review: Submitted agents create a review request in the Microsoft 365 admin center. Using the existing publishing and approval workflow, admins have full control over which agents are published, who can access them, and how they are deployed (for example, scoping access to specific users or security groups, preinstalling, or pinning agents).
  • Screenshot 2: Microsoft 365 admin center showing the agent publishing workflow, where administrators can review submissions and control deployment settings such as user access and installation options.

    user settings

  • Distribution: Users can discover and install approved agents directly from the Agent Store.

Management and Updates:

Once published, the agent appears as a separate entry in the Agent Registry under Agents > All agents. Agent updates require a new admin submission, and each one triggers a new review cycle before the updated version becomes available in the Agent Store.

What you can do to prepare:

  • No action is required before rollout.
  • Admins can familiarize themselves with the agent review experience in the Microsoft 365 admin center under Agents > All agents > Requests.
  • Consider communicating this capability to internal agent makers so they understand the submission and approval process.
  • Review internal guidance or documentation related to agent governance, if applicable.

Learn more: Publish agents | Microsoft Learn

Compliance considerations:

Area Explanation
Admin controls and access management Admins can approve or reject agent submissions and control availability, scope, and deployment through existing Microsoft 365 admin center workflows. Access can be limited to specific users or security groups.

Timeline

Published
Apr 15, 2026
Message published to Message Center
Updated
Apr 15, 2026
Message content updated
End Date
Jun 30, 2026
Message timeline ends

Tags

#New feature#User impact#Admin impact

Category

Plan for Change

Related Messages

Similar updates

MC1279072

Microsoft 365 Copilot Chat: Use prepaid Copilot Credits without Pay‑As‑You‑Go billing

Apr 13, 2026
MC1279068

Microsoft Purview | Information Protection: Sensitivity label inheritance for Teams meeting artifacts

Apr 13, 2026
MC1278920â—Ź

Support for Office LTSC 2021, and additional apps will end on October 13, 2026

Apr 13, 2026
MC1163760â—Ź

New support for HR and employee profile data in Microsoft 365 Copilot connectors

Oct 1, 2025
MC981462â—Ź

Multiple account access to Copilot in Microsoft 365 desktop and mobile apps

Jan 16, 2025