Here are a few upcoming updates related to Copilot agents, and the governance of them in your organization. These changes introduce new approval workflows, model lifecycle updates, and improved access management experiences. There is also an update to the Sonnet model available in Copilot Studio.
Agent builder submission and approval workflow for organization catalog
A new submission and approval capability is being introduced for agents built with Agent Builder, making it easier to scale internal distribution while maintaining administrative control. Agent makers can now submit their agents for review before they are published to the organization’s Agent Store, where approved agents will appear under a dedicated “Built by your org” section.
This change introduces a more structured governance model. Users creating agents can request publication directly from the Agent Builder interface, while administrators review submissions in the Microsoft 365 admin center. Admins retain full control over which agents are approved, who can access them, and how they are deployed, including scoping access to users or security groups, as well as options such as preinstallation or pinning. Once published, agents are managed through the Agent Registry under "Agents > All agents", and any updates require a new submission and approval cycle.
From a configuration perspective, administrators can familiarize themselves with the review workflow in the Microsoft 365 admin center under Agents > All agents > Requests. Additional guidance on publishing and managing agents can be found in the official documentation.
According to the Microsoft 365 Roadmap ID 557173 this is still in development, but according to my Message Center, it is rolling out as of "Mid May". So please monitor your Message Center to look for status for your tenant.
Request and approval experience for microsoft-built agents in the agent store
A new request and approval experience is being introduced for Microsoft-built agents in the Agent Store, providing improved visibility and control over how users gain access to these agents. Users will be able to request access directly from the Agent Store, even if the agent is not currently available due to organizational configuration.
This update enhances transparency by allowing administrators to see which agents users are interested in, while maintaining full control over approvals. Requests are centrally managed in the Microsoft 365 admin center under Copilot > Agents & connectors, where admins can approve or reject access at a granular, per-user level. This functionality applies specifically to Microsoft-built agents and does not extend to other types of agents in the store.
The feature is enabled by default and does not require any additional configuration. Administrators can simply navigate to the relevant section in the Microsoft 365 admin center to manage incoming requests as they appear.
Originally planned for rollout early March 2026, the rollout is now scheduled to begin in July 2026 and complete by the end of July 2026. Follow up the official Microsoft 365 Roadmap ID 494809. As with other roadmap items, the rollout timeline may change (again), so monitoring the Message Center remains important for up-to-date guidance.
Automatic migration from Claude sonnet 4.5 to newer models in copilot studio
Microsoft has announced an upcoming model lifecycle change in Copilot Studio where agents currently using Claude Sonnet 4.5 will be migrated to newer supported models. This update aligns the platform with modern model capabilities and ensures long-term reliability as older models are retired.
Organizations using Copilot Studio agents configured with Claude Sonnet 4.5 will be directly affected. Starting May 30, 2026, any remaining agents using this model will be automatically migrated to Claude Sonnet 4.6 as part of a phased rollout. While configurations such as flows, integrations, and governance controls remain unchanged, differences in model behavior may result in variations in tone, formatting, or response quality. Usage analytics and reporting will also reflect the new model after migration.
Administrators and makers have a limited window to prepare. Between April 30 and May 30, 2026, they can test agents with supported models such as Claude Sonnet 4.6 or alternative models and validate behavior before automatic migration begins. There is also an option to defer migration once for up to 30 days by enabling the “Continue using retired models” setting in Copilot Studio. This setting must be configured before May 30, 2026, and is documented here.
The evaluation window opened on April 30, 2026, with automatic migration beginning May 30, 2026, and a final enforced migration deadline of June 30, 2026 after any deferral period.
The evaluation window opened on April 30, 2026, with automatic migration beginning May 30, 2026, and a final enforced migration deadline of June 30, 2026 after any deferral period.
Thanks for reading. If you found this useful, feel free to follow along for more updates and practical insights. You can find the link to my LinkedIn profile in the main menu on the front page.
Comments