Update to agents in SharePoint: Simpler launch experience and new site AI settings
SharePoint updates simplify agent management with new Site AI settings, letting site owners control highlighted agents. Approved agents won’t appear in the Agent Picker and should be placed on pages. Rollout starts mid-November 2024, completing by June 2026, affecting all SharePoint Online tenants. Introduction We’re updating how agents in SharePoint work to provide a simpler experience for agents selected on a site. As a refresher, Get started with agents in SharePoint – Microsoft Support, there are two types of agents in SharePoint: Ready-made agent – Every SharePoint site comes with a “ready-made agent”, automatically scoped to the content on that site. These agents, scoped to the SharePoint site, require no building from site admins or site owners. Custom-built agent – With site editing permissions, you can create custom agents with a specific content scope, identity, and behavior. With this update, we’re introducing a new Site AI settings to give site owners more control over which agents are highlighted on their sites. Approved agents will no longer appear in the Agent Picker, so these agents should be placed directly on the site page for better discoverability. When this will happen General Availability (Worldwide): We began rolling out in mid-November 2024 and expect rollout to complete by early June 2026. How this affects your organization Who is affected All Microsoft 365 tenants using SharePoint Online Site owners and content authors managing how custom agents are discovered on their site What will happen Site owners will manage the site’s “Default” agent through the main agent setting in the new Site AI settings panel in SharePoint site settings. For existing sites, the current “Default” agent will automatically become the site’s main agent. For new sites, the main agent will be the ready-made agent Users no longer access approved agents through the agent picker and overflow menu in the chat pane. All approved agents remain in the Site Assets\Copilots\Approved folder. To help users discover agents, site owners and builders should surface agents directly on pages using supported web parts or shared agent links. This feature is on by default and does not require tenant-level configuration changes. […]
The post Update to agents in SharePoint: Simpler launch experience and new site AI settings appeared first on M365 Admin.
Published on:
Learn moreRelated posts
Microsoft 365 Copilot in Word: Improved support for complex edits
Microsoft 365 Copilot in Word will support complex edits like tracked changes, comments, and document structure while preserving formatting an...
Copilot Notebooks available in Microsoft 365 Copilot Chat for Basic users
Copilot Notebooks will be available in Microsoft 365 Copilot Chat for Basic users starting mid-June 2026, providing a persistent AI-powered wo...
Rolling out a simplified, consistent design and navigation experience in Viva Engage
Viva Engage is updating to a simplified, consistent design and navigation across web and Teams, improving usability and reducing clutter. The ...
Microsoft 365 Copilot: Retirement of Sora video generation experience (Frontier)
The Sora video generation experience in the Frontier program will retire between mid and late June 2026. Users will lose access to create new ...
Microsoft 365 & Power Platform Call (Microsoft Speakers) – June 9th, 2026 – Screenshot Summary
Call Highlights SharePoint Quicklinks: Primary PnP Website: https://aka.ms/m365pnp Documentation & Guidance SharePoint Dev Videos Issues...
Microsoft Teams: Improved app and agent access request flows for admin‑blocked apps
Microsoft Teams will introduce a clearer, guided request flow for access to admin-blocked apps and agents, improving user notifications and ad...
Microsoft 365 Archive: File-level archiving General Availability
Microsoft 365 Archive now supports file-level archiving for SharePoint files, enabling cold storage with discoverability. Rolling out worldwid...
Converting Get-MailboxFolderStatistics ids for use with the Graph API
In this article, we discuss how to convert Exchange folderIds (as returned by the Get-MailboxFolderStatistics cmdlet) to the RestId identifier...