Microsoft Roadmap, messagecenter and blogs updates from 03-06-2026

Updated June 2, 2026: We have decided not to move forward with this change at this time. We apologize for any inconvenience.

Microsoft Purview is launching a new Personalization page that will help users personalize their individual experience on Purview.

This message is associated with Microsoft 365 Roadmap ID 483884.

[When this will happen:]

Public Preview (Worldwide): We have decided not to move forward with this change at this time.

General Availability (Worldwide): We have decided not to move forward with this change at this time.

[How this will affect your organization:]

The following features will be included in this initial rollout:

• Ability to pin or unpin solutions to the left navigation bar
• A new Personalization page where users can:
• Toggle visibility of the solution bar
• Choose to show solution walk-through on next sign in
• Export personalization data stored for the signed-in user
• Delete preferences one by one or all at once

The new Personalization page will be at Microsoft Purview > Settings (in top right corner) > Personalization:

On the new Personalization page, users will be able to hide or remove solution tiles and choose to show solution walk-throughs:

These changes will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation.

Updated June 2, 2026: We have updated the content and timeline. Thank you for your patience. 

Starting June 2026, we will resume the automatic installation of the Microsoft 365 Copilot app to eligible devices with the Microsoft 365 desktop apps. This change simplifies access to Copilot and ensures users can easily discover and engage with productivity-enhancing features

When this will happen

Rollout begins in early June 2026 and completes by end of June 2026. 

How this affects your organization

• The Microsoft 365 Copilot app will be automatically installed on Windows devices that have Microsoft 365 desktop apps, unless administrators opt out.
• On devices where the app is already installed, no visible change will occur.
• The app installation is enabled by default and does not require user interaction.
• This change does not apply to customers in the European Economic Area (EEA).

What you can do to prepare

• Before deploying, inform users about the upcoming change to avoid surprises and improve adoption.
• No compliance considerations identified, review as appropriate for your organization.

Updated June 2, 2026: We have updated the timeline. Thank you for your patience. 

We’re introducing the ability for organizations to customize Microsoft 365 profile cards by adding up to 10 custom properties sourced from external systems such as HR platforms. This enhancement helps enrich user profiles with relevant organizational details, improving discoverability and context for collaboration.

This message is associated with Microsoft 365 Roadmap ID 529851.

General Availability (Worldwide): We will begin rolling out in July 2026 (previously June) and expect to complete in July 2026 (previously June).

Who is affected: Microsoft 365 tenant admins managing user profile cards

What will happen:

• You can add up to 10 custom properties to profile cards using Microsoft Graph People connectors.
• Properties can be sourced from external systems (such as HR platforms).
• This feature is OFF by default and requires admin configuration to enable.
• Admins can configure visibility, display name, and icon for each property in Microsoft 365 admin center under: Settings > Org settings > People settings > Profile > Person info on profile cards 

  

• Once enabled, properties appear in the Contact Information section of profile cards in Outlook Web:



• Changes may take up to 24 hours to propagate across profile cards.
• Future updates will include direct ingestion from SAP SuccessFactors and Workday connectors.

• Review external systems for properties you want displayed on profile cards.
• Ingest these properties using a Microsoft Graph People connector.
• Configure visibility and enable properties in the Microsoft 365 admin center.
• Communicate this change to helpdesk staff and update internal documentation if needed.

Learn more: Microsoft 365 Copilot connectors for people data | Microsoft Learn

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.

Updated June 2, 2026: We are updating this post as a reminder. Featured Links on SharePoint web and the SharePoint mobile app are scheduled to be retired soon. We expect them to be 100% retired by the end of July. Thank you for your patience. 

[Introduction]

We’re retiring the Featured Links capability on the SharePoint Start Page due to low adoption. This change helps streamline SharePoint experiences and reduce complexity for admins and end users. Alternative options, such as global navigation links or Resources in Viva Connections, provide more consistent ways to highlight important content.

Screenshot: The Featured Links option set for retirement appears at the bottom left in this image.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): Retirement begins early March 2026 and will complete by late June 2026.

[How this affects your organization:]

Who is affected: All organizations using Featured Links on the SharePoint Start Page or SharePoint mobile app.

What will happen:

• Admins will no longer be able to create, edit, update, or access Featured Links.
• Existing Featured Links will be removed from the SharePoint Start Page and SharePoint mobile app.
• No impact to other SharePoint navigation features or Viva Connections resources.

[What you can do to prepare:]

• Review any existing Featured Links and plan alternative navigation options.
• Consider using global navigation links or Resources in Viva Connections to highlight important sites and content.
• Communicate this change to helpdesk and SharePoint site owners.
• Update internal documentation if it references Featured Links.

Learn more: Add featured links to the SharePoint start page

[Compliance considerations:]

No compliance considerations identified; review as appropriate for your organization.

Updated June 2, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

As part of our ongoing mission to deliver a modern, secure, and scalable one-stop management portal for admins, we are transitioning Teams Android device management from the Teams admin center (TAC) to the Teams Rooms Pro Management portal (PMP).

This move consolidates management of all Teams devices, including Teams Rooms on Windows, Teams Rooms on Android, Teams phones, and Teams panels, into a single unified portal, providing IT admins a consistent and seamless experience for managing devices at scale.

This message is associated with Roadmap ID 555235.

[When this will happen:]

• Public Preview: We will begin rollout in early April 2026 and expect to complete by mid-April 2026. 
• General Availability (Worldwide, GCC): We will begin rollout in late June 2026 (previously early June) and expect to complete by mid-July 2026 (previously mid-June).
• General Availability (GCC High): We will begin rollout in early August 2026 and expect to complete by mid-August 2026.
• General Availability (DoD): We will begin rollout in early September 2026 and expect to complete by mid-September 2026.

[How this affects your organization:]

Who is affected:

Admins who manage Teams Rooms on Android, Teams phones, and Teams panels.

What will happen:

• Starting June 2026, Android device management capabilities, including inventory, updates, health monitoring, and settings will transition from TAC to PMP for the device types, Teams Rooms on Android, Teams phones, Teams panels
• The following capabilities will be available and enhanced in PMP:
• Device inventories for Android-based Teams Rooms, phones, and panels, including metadata and app information
• Remote device actions (restart, log collection, sign-in/out, provisioning, and more)
• Update management
• Device settings management
• Device health monitoring
• SIP device management
• PMP will become the primary portal for all Teams device management. By July 2026, overlapping TAC capabilities (updates, settings, restart, sign-in/out, log collection, provisioning) will begin redirecting to PMP.
• This article serves as the main information source for this transition. We’ll continue updating it with timelines, milestones, migration guidance, and readiness steps as the rollout progresses.

[What you need to do to prepare:]

• No action is required until Android device management reaches General Availability.
• When Android device management reaches General Availability:
• Your existing Android-based Teams devices will automatically appear in PMP.
• Teams Rooms on Android and Teams panels are already visible in PMP.
• If your organization hasn’t used PMP before:
• Admins with Global, Teams, or Teams Device Administrator roles can access PMP at https://portal.rooms.microsoft.com.
• Ensure required URLs are allowlisted per guidance: Enrolling a device into the Pro Management Portal | Microsoft Learn.
• Learn more about Pro Management portal features with these Teams Rooms Pro Management short YouTube videos.
• Update internal helpdesk and IT documentation to reference PMP as the new management portal.
• Additional migration guidance, timelines, and FAQs will be published closer to the transition date.

[Compliance considerations]

No compliance considerations identified, review as appropriate for your organization.

Updated June 2, 2026: We are in the process of correcting an issue with setting the policy. We expect to complete in mid-June. Thank you for your patience.  

[Introduction]

We’re adding a new Exchange Online admin policy that gives admins more control over the default Mail Compose and Reply setting that determines whether commas are used as recipient separators.

This message is associated with Microsoft 365 Roadmap ID 557676.

[When this will happen]

• General availability (Worldwide): Rollout will begin in early April 2026 and complete by mid-June 2026 (previously mid-May).

[How this will affect your organization]

Who is affected

• Exchange Online administrators in New Outlook for Windows and Outlook for Web
• All users composing or replying to email in Outlook where no per‑user override is configured

What will happen

• A new admin policy will be available to set the tenant‑wide default for “Use commas as recipient separators.”
• Admins can choose whether the default is on or off for all users.
• Users may still change this setting in their Outlook client unless an admin enforces a policy that locks it: 

  

• This update is especially useful for organizations whose contacts commonly use “Last name, First name” formats.
• No changes will occur automatically—tenants will retain existing behavior unless an admin modifies the policy.

[What you can do to prepare]

No action is required. If desired, you may configure the new admin policy after rollout if you want to establish a consistent default. You can set this value via Powershell with the command “Set-Organization Config -RecipientDelimeters <Boolean>.”

You may also consider the following actions: 

• Review your organization’s preferred recipient formatting conventions.
• Update internal documentation if your helpdesk or user‑training materials reference this setting.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Updated June 1, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We are introducing a new handoff experience that allows users to take content created in Copilot Pages and seamlessly continue authoring as a SharePoint news post. This update helps users move from ideation to publishing more efficiently.

[When this will happen:]

General Availability (Worldwide, GCC): We will begin rolling out in September 2026 (previously late May) and expect to complete by end of September 2026 (previously mid-June).

[How this affects your organization]

Who is affected:

• Users who create content in Copilot Pages and publish SharePoint News
• Organizations using Microsoft 365 Copilot with SharePoint Online

What will happen:

• Users can move content from Copilot Pages directly into a SharePoint News post.
• A new SharePoint option will appear under the Create button in Copilot Pages:

  

• Selecting SharePoint opens the content in SharePoint News for continued editing and publishing.
• The feature is enabled by default.
• Existing SharePoint permissions, policies, and governance controls are respected.
• There is no disruption to existing SharePoint News workflows.

[What you can do to prepare]

Updated June 2, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re adding new building‑level insights to the recommended actions page in the Teams Rooms Pro Management portal. This update helps IT admins identify buildings with high Microsoft Teams Rooms (MTR) utilization that still have bring-your-own-device (BYOD) rooms in them, creating an inconsistent user experience from room to room. These insights support more consistent meeting experiences across buildings and help organizations optimize room‑technology investments. Available with a Teams Rooms Pro or Shared Space license.

This message is associated with Microsoft 365 Roadmap ID 553591.

[When this will happen]

• General availability (Worldwide): We will begin rolling out mid-June 2026 (previously early June) and expect to complete by late June 2026 (previously mid-June).

[How this affects your organization]

Who is affected

• Organizations using the Teams Rooms Pro Management portal with Teams Rooms Pro or Shared Device licenses

What will happen

• A new building‑level insights view will appear on the portal’s Recommended actions page:

   

• Insights will highlight buildings with high MTR usage and remaining BYOD meeting rooms: 

  

• These insights are designed to help IT create more consistent room to room experiences for users within a building.
• No changes will occur to existing configurations, policies, or settings.
• The feature will be enabled by default for tenants with eligible licenses.

[What you can do to prepare]

No action is required.

If relevant to your organization’s deployment planning, you may:

• Review your current MTR and BYOD room distribution in the Teams Rooms Pro Management portal.
• Update internal documentation or planning guidance as needed.
• Share this update with teams responsible for meeting room technology decisions.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Updated June 1, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing custom skills for AI in SharePoint, which let users teach AI in SharePoint how to perform common business tasks in a consistent, repeatable way. With skills, organizations can tailor AI behavior to their own documents, standards, and processes—such as reviewing compliance documents or offer letters—without writing code or using external tools. This update helps reduce manual effort and makes AI results more reliable for everyday SharePoint work.

This message is associated with Roadmap ID 559800.

[When this will happen:]

• Public Preview (Worldwide): We will begin rolling out in mid-April 2026 and expect to complete by early May 2026.
• General Availability (Worldwide): We will begin rolling out in mid-June 2026 (previously late May) and expect to complete by early July 2026.

[How this affects your organization:]

Who is affected:

• Users of AI in SharePoint
• SharePoint site owners and admins
• Users with edit permissions on SharePoint sites

What will happen:

• Users with edit permissions can create custom skills using natural language within AI in SharePoint.
• Skills allow users to define reusable, multi‑step AI instructions for common business tasks (for example, reviewing compliance documents or offer letters).
• AI in SharePoint can automatically select relevant skills from the current site based on a user’s query, or users can invoke a skill by name.
• Skills are saved as Markdown (.md) files in the site’s Agent Assets library (/Agent Assets/Skills/<skill-name>/SKILLmd) and are governed by existing SharePoint permissions and compliance policies.
• Skills reuse native AI in SharePoint capabilities (content understanding, list manipulation, folder organization, and other supported SharePoint actions).
• Skills cannot connect to external systems or execute custom code.
• The feature is enabled by default and has no separate tenant‑level on/off toggle.
• Existing SharePoint permissions are respected; users cannot perform actions they do not already have permission to do.

[What you can do to prepare:]

No action is required to enable this feature.

Recommended actions for admins:

• Review how SharePoint site permissions are managed, as any user with edit permissions can create skills.
• If needed, customize who can create or use skills by breaking permission inheritance on the Agent Assets library.
• Update internal governance or usage guidance to include skills as part of AI in SharePoint.
• Inform helpdesk or power users that skills are stored as files and governed by existing SharePoint controls.

We will update this post with new documentation soon.

[Compliance considerations:]

Updated May 1, 2026: We have paused rollout of this feature at this time. We will communicate via Message center when we are ready to proceed. We apologize for any inconvenience. 

[Introduction]

We are updating the Chat-only Copilot experience in Excel to better align with the editing experience. As part of this update, users who want to access additional Copilot agents (such as Researcher or Analyst) can do so by selecting the “…” menu in the header and choosing M365 Copilot.

[When this will happen]

• General Availability (Worldwide): We will communicate via Message center when we are ready to proceed.

[How this affects your organization]

Who is affected

All Excel users with Microsoft 365 Copilot licenses

What will happen

• Users can continue to use the chat‑only Copilot experience in Excel to ask questions, analyze data, and receive insights without modifying workbook content.
• However, users who want to access additional Copilot agents (such as Researcher or Analyst) can do so by selecting the “…” menu in the Excel header and choosing M365 Copilot:

  

• Existing Microsoft 365 Copilot licensing and policy controls are respected.
• There is no change to workbook editing behavior or data permissions.

[What you can do to prepare]

No admin action is required.

• Inform helpdesk and support teams about the new access path to Microsoft 365 Copilot from Excel.
• Update internal documentation or training materials that describe Copilot experiences in Excel.
• Review Microsoft 365 Copilot documentation if you want to understand available agents and licensing requirements.

Learn more: Edit with Copilot in Excel | Microsoft Support

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Updated June 2, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We are introducing the File Quarantine action in Microsoft Purview Data Loss Prevention (DLP) for SharePoint and OneDrive to help organizations better protect sensitive data. When a file violates a Purview DLP policy, it can be automatically isolated to prevent further access or sharing, allowing administrators to review and take appropriate action. This capability adds an additional layer of protection against accidental data exposure while supporting everyday collaboration.

This message is associated with Microsoft 365 Roadmap ID 557190.

[When this will happen:]

• Public Preview: Rolling out in mid‑April 2026 and expected to complete by early May 2026
• General Availability (Worldwide): Rolling out in early July 2026 (previously early June) and expected to complete by mid-July 2026 (previously mid‑June)

[How this affects your organization:]

Who is affected:

• Admins managing Microsoft Purview DLP policies for:
• SharePoint Online
• OneDrive for Business
• Compliance and security administrators responsible for data protection and investigation workflows

What will happen:

• A new Quarantine action will be available when creating or editing DLP policies for SharePoint and OneDrive.
• When a file violates a DLP policy configured with the Quarantine action:
• The file is automatically isolated in an admin‑controlled quarantine location.
• Access to the original file is prevented to stop further sharing or exposure.
• A tombstone file replaces the original file at its source location:
• Contains admin‑defined messaging
• Informs users the file has been quarantined
• Preserves collaboration context
• Administrators retain visibility through:
• Audit logs
• DLP alerts
• Activity Explorer
• Files must be restored manually by an administrator.
• Original sharing permissions are not automatically reinstated upon restore.
• This feature is not enabled by default and requires configuration within a DLP policy.

[What you can do to prepare:]

• Create an admin‑owned SharePoint site to serve as the quarantine location.
• Configure quarantine settings in Purview DLP settings:
• Destination folder
• Tombstone message
• Review and restrict access permissions for the quarantine site.
• Validate behavior using DLP policies in simulation mode before broad enforcement.
• Update internal operational processes for quarantine reviews and restore requests.
• Communicate this change to your helpdesk and compliance teams.

Learn more:

• Get started with DLP file quarantine for SharePoint and OneDrive | Microsoft Learn
• Create a DLP policy to quarantine files in SharePoint and OneDrive | Microsoft Learn 

[Compliance considerations:]

Updated June 2, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Meeting organizers in Microsoft Teams can now delete meeting‑generated content—including recordings, transcripts, AI summaries, and notes—directly from the meeting recap. This capability helps organizers manage meeting artifacts after the meeting. Shared files from the meeting are not deleted.

This message is associated with Microsoft 365 Roadmap ID 557170.

[When this will happen:]

• Targeted Release: We will begin rolling out in early May 2026 and expect to complete by early May 2026.
• General Availability (Worldwide): We will begin rolling out in late May 2026 and expect to complete by early June 2026.
• General Availability (GCC): We will begin rolling out in mid-June 2026 and expect to complete by mid-June 2026.
• General Availability (GCCH): We will begin rolling out in early September 2026 (previously late June) and expect to complete by late September 2026 (previously late June).

[How this affects your organization:]

Who is affected:

• Microsoft Teams meeting organizers
• Tenants using meeting recap features

What will happen:

• A new Delete recap content option will appear in the More (…) menu on the meeting recap page.

Screenshot 1: Delete recap content option found under the More (…) menu:

>

Screenshot 2: Delete recap content confirmation:



• Meeting organizers can permanently delete:
  • Recordings
  • Transcripts
  • AI summary
  • Notes
• Shared files are not deleted and remain accessible in their original storage locations.
• Custom summary and Audio recap will not be deleted with Delete recap content in this release.
• Deleted meeting content cannot be restored.
• The feature is enabled by default and does not require admin configuration.

[What you can do to prepare:]

• Inform users about this new capability.
• Update internal documentation and helpdesk guidance.
• Review meeting governance and retention guidance.
• Monitor usage through Teams and SharePoint analytics.

[Compliance considerations:]

Meeting organizers can now permanently delete meeting-generated content, impacting how users manage and delete their data. Review as appropriate for your organization.

Updated June 2, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing an update to how front-of-room (FoR) displays behave in Microsoft Teams Rooms on Android during webinars and structured meetings. This change ensures that when a Teams Room joins as a presenter, the in-room display defaults to the attendee view—creating a clearer and more professional experience for in-room participants, especially in hybrid scenarios where presenters and attendees are co-located.

This message is associated with Roadmap ID 559602.

[When this will happen:]

• General Availability (Worldwide): We will begin rolling out in mid-June 2026 (previously early June) and expect to complete by late June 2026.
• General Availability (GCC, GCC High, DoD): We will begin rolling out in mid-June 2026 and expect to complete by late June 2026.

[How this affects your organization:]

Who is affected:

• Organizations using Microsoft Teams Rooms on Android
• Meeting organizers and presenters running webinars or structured meetings
• In-room participants viewing front-of-room displays
• A Teams Rooms Pro license is needed to use this feature

What will happen:

• The front-of-room display will default to attendee view when joining webinars or structured meetings.
• In-room audiences will not see presenter tools such as Green Room or backstage controls.
• Presenters will retain full control from the Teams Rooms console, including:
  • Managing Green Room and off-stage participants.
  • Switching display modes (e.g., to presenter view when needed).
• The feature is enabled by default and requires no configuration.
• There is no impact to remote attendees or their experience.
• Existing Teams Rooms functionality and policies remain unchanged.

Screenshot 1: Front-of-room webinar experience with Manage screen mode on and the user in presenter view:

Screenshot 2: Console view in presenter view:

Screenshot 3: Front-of-room webinar experience with the user in attendee view:

Screenshot 4: Console view with the user in attendee view:

[What you can do to prepare:]

• No action is required to enable this feature.
• Verify device readiness: Ensure Teams Rooms on Android devices are updated.
• Validate meeting room setup: Confirm displays and consoles function as expected.
• Educate organizers and presenters on the updated experience.
• Update internal documentation.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Updated June 1, 2026: We have updated the content in ‘what you can do to prepare’. Thank you for your patience. 

[Introduction]

Microsoft Teams town halls and live events will soon support Secure Reliable Transport (SRT), a secure and resilient video streaming protocol designed to deliver high‑quality, low‑latency video over the public internet. SRT will be available alongside Real‑Time Messaging Protocol (RTMP), the existing inbound streaming protocol commonly used with external encoders. Adding SRT provides event organizers with improved reliability and flexibility, including support for backup streams with automatic failover, to help ensure smoother delivery for high‑visibility broadcast events without increasing setup complexity.

This message applies to Teams for Windows desktop and Teams for Mac desktop and is associated with Roadmap ID 554931.

[When this will happen:]

• Targeted Release: Rollout begins in early June 2026 and is expected to complete by mid-June 2026
• General Availability (Worldwide, GCC): Rollout begins in mid-June 2026 and is expected to complete by late June 2026

[How this affects your organization:]

Who is affected:

• Organizations that host Microsoft Teams town halls or live events using external encoders
• Event producers and administrators responsible for configuring broadcast streams

What will happen:

• Organizers can use SRT as an alternative to RTMP for inbound streaming
• Events can be configured with a primary and backup SRT stream with automatic failover
• Existing RTMP workflows remain supported and unchanged
• The feature is available by default; no admin policy changes are required
• No impact to users attending events

[What you can do to prepare:].

• Review encoder capabilities to confirm SRT support
• Ensure you have access to port 49891 and the domain *.rtmpingest.mcr.teams.cloud.microsoft.
• Update internal event‑production documentation to include SRT as a supported option
• Inform event production teams that a backup stream with automatic failover is now available for Teams town halls

We’ve introduced an additional policy control for SRT-In in Teams Events. To enable users to access and use SRT-In, IT admins must explicitly allow the “SRT” setting in the AllowedStreamingMediaInput parameter within CsTeamsMeetingPolicy.

Learn more: Manage RTMP-In for Teams meetings, webinars, and town halls – Microsoft Teams | Microsoft Learn (will be updated before Targeted Release begins)

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Updated June 1, 2026: We have updated the content. Thank you for your patience. 

[What and Why:]

We’re enhancing the existing AI-powered SharePoint Page and News Post creation experience by expanding Copilot in SharePoint (previously AI in SharePoint) with a new entry point and a more integrated authoring flow.

This update helps authors move more quickly from idea to publish-ready content by making AI-assisted creation available earlier and more consistently across SharePoint, while maintaining full editing control and customization flexibility.

[Rollout Schedule:]

• Public Preview (Worldwide): We began rolling out in early March 2026 and expect to complete by early June 2026.
• Targeted Release (Worldwide): We will begin rolling out in early June 2026 and expect to complete by late July 2026.

[Impact on Your Organization:]

Who is affected:

• Users who create SharePoint pages or news posts
• A Microsoft 365 Copilot (Premium) license is required to use this feature
• Tenants opted in to Copilot in SharePoint (previously AI in SharePoint) public preview

Platforms/Services:

• SharePoint Online (Web)
• Microsoft 365 Copilot
• SharePoint Pages and News Posts

What will happen:

Authors can start creating AI-assisted SharePoint pages and news posts from a new entry point in SharePoint:

>

• Authors can quickly create a SharePoint page using AI by entering a prompt.

2. Start from the Site Template Gallery

• A new prompt box will appear at the top of the SharePoint Site Template Gallery.



• From this experience, authors can:
  • Enter a prompt to describe the content they want to create
  • Select grounding files to provide additional context
  • Choose whether to create a Page or a News Post using the pivot control
• Copilot will generate a visually engaging draft that authors can continue refining directly within the page editor using the Copilot panel.
• The experience is enabled by default for eligible users, respects existing SharePoint permissions, and maintains full editing and customization flexibility.

[Action Required / Recommendations:]

No admin action is required. Consider notifying SharePoint authors and updating internal documentation as appropriate.

Learn more: Authoring with AI in SharePoint: An overview | Microsoft Support (will be updated before rollout)

[Compliance considerations:]

This notice applies to customers in the European Economic Area (EEA) who purchase through Microsoft’s commercial licensing programs with a billing account located in the EEA.

These customers have the right to purchase suites without Microsoft Teams (“no Teams” Suites). Customers in multi-year agreements may switch to “no Teams” Suites at their next annual order. The price of the “no Teams” Suites is lower than the price of the corresponding Covered Suites.

Covered Suites include Microsoft 365 Business Basic, Microsoft 365 Business Standard, Microsoft 365 Business Premium, Office 365 E1, Office 365 E3, Office 365 E5, Microsoft 365 E3, Microsoft 365 E5, and any successor or substantially equivalent versions of these suites targeted at knowledge workers in business, enterprise, and public sector organizations.

Customers are also eligible to receive the same percentage discount on the “no Teams” Suites that applies to the corresponding Covered Suites. This includes discounts that are negotiated or offered as promotions, whether applied as a price reduction or a rebate.

Customers may use the “no Teams” Suites with competing collaboration solutions if they choose to purchase and use a competitor to Microsoft Teams.

[What and Why]

Academies in Viva Learning are now available in Microsoft Teams mobile, allowing learners to access organization‑curated learning journeys directly from their mobile devices. This update extends Academy visibility and navigation to mobile, providing a consistent learning experience across desktop, web, and mobile while preserving existing admin controls and permissions.

Rollout Schedule

• Public Preview (Worldwide): We will begin rolling out in early June 2026 and expect to complete by mid-June 2026.
• General Availability (Worldwide): We will begin rolling out in early July 2026 and expect to complete by mid-July 2026.

[Impact on Your Organization]

Who is affected

• Users accessing Viva Learning in Microsoft Teams mobile

Platforms / Services

• Microsoft Teams (mobile)
• Viva Learning

What will happen

• Learners will see all Academies they have permission to access under the Academy tab in Teams mobile.

Screenshot 1: Academies visible in Viva Learning on Microsoft Teams mobile:



Screenshot 2: Learners can open an Academy to navigate Sections, Sub-sections, and Learning Paths:



• Learners can:
  • View Academies they are authorized to access.
  • Navigate Sections and Sub‑sections configured by admins.
  • Open Learning Paths and the courses within them.
  • Land directly on the Academy view when opening a shared Academy link.
  • Access the Microsoft Copilot Academy on mobile through notifications.
• Academies on mobile are view‑only.
• All Academy creation, permissions, and curation continue to be managed on Viva Learning web and desktop.
• Updates made by admins on web or desktop automatically appear on mobile.
• This feature is enabled by default and respects existing permissions.
• No policy or configuration changes are required.

[Action Required / Recommendations]

• No action is required.
• Consider notifying helpdesk staff and learners about mobile availability.

[Compliance Considerations]

No compliance considerations identified, review as appropriate for your organization.

[What and Why]

We are introducing Copilot‑generated suggested edits in Copilot Pages to help users improve the clarity and quality of their content without leaving their workflow. This enhancement brings AI‑powered writing feedback directly into the page experience, enabling users to review and apply actionable suggestions in context. This aligns with our goal to improve personal and team productivity by helping users create higher‑quality content more efficiently.

This message is associated with Microsoft 365 Roadmap ID 562351.

[Rollout Schedule]

• Frontier: We will begin rolling out to Frontier Private and Public in early June 2026.
• General Availability (Worldwide): We will begin rolling out in late June 2026 and expect to complete by mid-July 2026.

[Impact on Your Organization]

Who is affected

Users with access to Microsoft 365 Copilot and Copilot Pages

Platforms/Services

• Copilot Pages (web)
• Microsoft 365 Copilot

What will happen

• Users can request writing feedback directly within Copilot Pages using Copilot Shortcuts or Copilot Chat.
• A new Suggest edits option will be available: 

  

• Copilot analyzes page content and generates suggestions to improve clarity and writing quality.
• Suggestions appear as comment-like cards in a right-hand sidebar aligned to relevant content.
• Each suggestion can be applied with a single click using an Apply button.
• The feature is available by default to eligible users; no additional configuration is required.
• Existing Copilot policies and permissions are respected.

[Action Required / Recommendations]

No action is required.

Admins may consider the following:

• Inform users about the availability of suggested edits in Copilot Pages.
• Share guidance on accessing suggestions via Copilot Shortcuts or Copilot Chat.
• Set expectations that Frontier releases are early experiences intended for feedback and validation.
• Monitor usage and feedback as users adopt this capability.
• Review Copilot access and ensure Copilot Pages and OneDrive for Business remain enabled.

Learn more: 

• Admin policies for Copilot Pages and Copilot Notebooks | Microsoft 365 | Microsoft Learn
• Disable OneDrive creation for some users – Manage user profiles in the SharePoint admin center | SharePoint in Microsoft 365 | SharePoint | Microsoft Learn
• Frontier program – Microsoft Adoption

[Compliance considerations]

[What and Why]

We are introducing an enhanced bookable desk experience for Microsoft Teams panel based desk devices, such as Logi Dock Flex and the upcoming Yealink Linkhub. This update enables users to view at-a-glance desk availability and for visitors to reserve desks directly from the device, improving flexibility and productivity in hybrid work environments. Each device requires a Teams Shared Space license.

This message is associated with Microsoft 365 Roadmap ID 561031.

[Rollout Schedule]

General Availability (Worldwide): Rollout will begin in early July 2026 and is expected to complete by mid-July 2026.

[Impact on Your Organization]

Who is affected

• Organizations using Microsoft Teams panel based desk devices (for example, Logi Dock Flex).

Platforms/Services

• Microsoft Teams
• Teams panels based desk devices
• Android (Teams panel devices)
• Requires Teams Shared Space license

What will happen

After the Teams app update, device’s user experience will directly reference desk booking and ask users to connect their laptop with the Teams app running to make a desk reservation.

• Users will be able to:
  • View desk availability directly on supported devices.
  • Reserve desks directly from the device interface when they are visitors that do not have an account on the tenant.
• Devices will prompt users to connect their laptop running the Teams app to do desk reservations or to check-in to a reservation.
• The updated experience will be available automatically after the Teams app update on supported Android-based devices.
• Existing licensing requirements apply (Teams Shared Space license required per device).
• No new admin configuration is introduced for this change.

[Action Required / Recommendations]

No action is required.

We recommend that you:

• Identify Teams panel-based desk devices in your organization (for example, Logi Dock Flex).
• After rollout, test one or more devices to validate the updated booking experience.
• Inform users about the updated booking flow (connecting their laptop to confirm reservations).
• Update internal documentation or workspace booking guidance if applicable.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

[Introduction]

To improve endpoint performance and focus on higher-value network telemetry, Microsoft is removing SMB signature inspection events from Advanced Hunting in Microsoft Defender for Endpoint. This change reflects observed low customer value for SMB signature data on endpoints and our continued investment in more advanced SMB visibility through Zeek-based network capabilities. 

[When this will happen:]

The rollout to Worldwide, GCC, GCC High, and DoD will begin on July 1, 2026, and will complete shortly thereafter across all tenants.

[How this affects your organization:]

Who is affected:

• Security administrators and analysts using Microsoft Defender for Endpoint Advanced Hunting
• Organizations with custom detection rules, hunting queries, scheduled queries, or automated workflows that reference SMB signature inspection events

What will happen:

• Events with ActionType = “NetworkSignatureInspected” and SignatureName = “SMB_Client” will no longer be generated.
• Queries, detections, or workflows that rely on these events will stop returning results after the rollout.
• Other network signature inspection events remain unchanged.
• The change is on by default and does not require tenant configuration.

[What you can do to prepare:]

To continue identifying SMB traffic in Advanced Hunting, we recommend filtering on port 445, the standard port used by SMB, in the DeviceNetworkEvents table, which remains fully supported.

• Review custom detection rules, saved hunting queries, scheduled queries, and automated workflows for references to SMB_Client.
• Update affected queries to identify SMB traffic using port-based filtering.
• Validate updated queries return the expected results before July 1, 2026.

Query update example

Replace:

DeviceNetworkEvents
| where ActionType == "NetworkSignatureInspected"
| extend SignatureName = tostring(parse_json(AdditionalFields).SignatureName)
| where SignatureName == "SMB_Client"

With:

DeviceNetworkEvents
| where RemotePort == 445 or LocalPort == 445

For questions or feedback regarding this change, contact Microsoft Support or your Microsoft account representative.

[Compliance considerations:]

• Admin monitoring and reporting: The removal of SMB signature inspection events changes available Advanced Hunting telemetry and may affect how administrators monitor or investigate SMB activity.

[Introduction]

We’re excited to announce dynamic tool discovery, a new capability for declarative agents and federated Copilot connectors in Microsoft 365 Copilot that are built on the Model Context Protocol (MCP).

Today, when an MCP server is used by a declarative agent action or a federated Copilot connector, the tools it exposes are imported and packaged into the consuming agent or connector at publish time. Any change to that tool surface, such as adding a new tool, removing a deprecated one, or updating a tool’s schema or description, requires the agent or connector to be repackaged, re-validated, and republished before users see the change.

With dynamic tool discovery, the agent or connector resolves its available tools at runtime, directly from the MCP server. This lets users access the latest capabilities of an MCP server in near real time, without waiting on a republish cycle.

Dynamic tool discovery is starting with declarative agents (DAs) that use MCP server-based actions, and will soon be available for federated Copilot connectors (FCCs), including both Microsoft-published and custom connectors.

[When this will happen]

Rollout will happen in two waves:

– **Declarative agents (MCP server-based actions):** rollout is expected to complete by end of June 2026.

– **Federated Copilot connectors (Microsoft-published and custom):** rollout is expected in July 2026.

Public documentation will be updated around the same time.

[How this will affect your organization]

Who is affected?

Organizations with Microsoft 365 Copilot licenses where Microsoft-published declarative agents that use MCP server-based actions, or federated Copilot connectors, are enabled.

What will happen?

Microsoft-published declarative agents (and, in the next wave, federated Copilot connectors) that use MCP servers will begin resolving their tool list from the MCP server at runtime, instead of from the tool list captured at publish time. End users will see new tool capabilities surfaced shortly after the MCP server publishes them, and deprecated tools will be retired without waiting for a republish.

Admins will have the following transparency, governance, and audit capabilities through the Microsoft 365 admin center (MAC) and Microsoft Purview:

– **Identify agents and connectors that use dynamic tool discovery.** The agent or connector details view in MAC indicates whether dynamic tool discovery is in use. For agents and connectors that use dynamic discovery, the details view shows a placeholder explaining that the tool list is resolved at runtime, instead of enumerating a fixed tool list. *[Placeholder: confirm exact label and screenshot from the admin experience team.]*

– **Disable or scope an agent or connector.** There is no separate switch for the dynamic tool discovery capability itself. Admins use the existing per-agent or per-connector controls to disable a specific agent or connector, or to assign it to specific users or groups for staged availability. Enablement, scoping, and disablement work the same way regardless of whether dynamic or static tool discovery is in use.

– **Audit interactions in Microsoft Purview.** Interactions with agents and connectors that use dynamic tool discovery are recorded in the Microsoft Purview audit log under the `Copilot` workload, alongside interactions with any other declarative agent or federated Copilot connector. Admins can locate these records by filtering on `Workload = Copilot` in Purview audit search, and can identify the specific agent or connector using the `TargetAgentName` field in `CopilotEventData`.

Screenshot 1 – Identify agents and connectors with dynamic tool discovery in MAC:

[What you need to do to prepare]

– Review which Microsoft-published declarative agents and federated Copilot connectors in your tenant use MCP servers and will pick up dynamic tool discovery as part of this rollout.

– Use the agent or connector details view in the Microsoft 365 admin center to identify which ones use dynamic tool discovery.

– If a specific agent or connector does not align with your organizational policies, disable or scope it using existing per-agent or per-connector controls.

– Familiarize your compliance and security teams with locating relevant Purview audit records by filtering on `Workload = Copilot` and the `TargetAgentName` field.

– Review the public documentation for dynamic tool discovery when it is published.

[Compliance considerations]

This change does not introduce new customer data storage or modify existing Microsoft 365 compliance controls:

– No new customer data is stored by Microsoft.

– No changes to how existing customer data is processed or accessed.

– No new AI/ML interaction patterns with stored customer data.

– No impact to:

  – Data Loss Prevention (DLP)

  – Sensitivity labels

  – Conditional Access

  – Audit logging

  – eDiscovery or Content Search

  – Encryption or key management

  – Retention or deletion workflows

– No changes to GDPR Data Subject Rights handling.

Newly discovered or modified tools are screened at runtime in accordance with Microsoft enterprise security and responsible AI standards before they are activated for end users. Tool changes that fail validation are blocked.

For Microsoft-published agents and connectors, the existing publisher attestation and Microsoft 365 certification model continues to apply at publish time, in addition to the runtime validation described above.

[Introduction]

Microsoft Teams is expanding breakout room capacity to support larger meetings. With this update, breakout rooms can be used in meetings with up to 1,000 attendees, allowing organizers to run large meetings while still enabling smaller group collaboration. This change removes the need to limit meeting size in order to use breakout rooms.

This message is associated with Microsoft 365 Roadmap ID 560320.

[When this will happen]

• Targeted Release: Rollout begins in early July 2026 and is expected to complete by late July 2026.
• General Availability (Worldwide, GCC, GCCH, and DoD): Rollout begins in July 2026 and is expected to complete by late July 2026.

[How this affects your organization]

Who is affected

• Meeting organizers and participants using Microsoft Teams
• Microsoft 365 tenants

What will happen

• Breakout rooms will be supported in meetings with up to 1,000 attendees.
• Organizers can create up to 200 breakout rooms per meeting.
• Organizers no longer need to limit meeting size to enable breakout rooms.
• The feature is enabled by default and respects existing Teams meeting policies.
• There is no change to the breakout room experience for meetings under the previous 300‑attendee limit.

[What you can do to prepare]

• No action is required.
• Consider informing meeting organizers and training owners about the expanded breakout room capacity.
• Update any internal guidance or training materials that reference breakout room attendee limits.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Expected with Intune’s June (2606) service release, we are making an update to the Microsoft Intune admin center to streamline where admins configure Microsoft 365 Apps policy settings. Currently, the same policy configuration experience is available in both the Microsoft Intune admin center (Apps > Policies for Microsoft 365 apps) and the Microsoft 365 Apps admin center (Customization > Policy management). To provide a more consistent and centralized management experience, we will remove the ability to configure these policies in the Intune admin center. Instead, the page will be updated to provide a direct link to the Microsoft 365 Apps admin center where this functionality will continue to be available.

[How this will affect your organization:]

If you are accustomed to creating or editing Microsoft 365 Apps policies directly within the Intune admin center, you will need to use the Microsoft 365 Apps admin center to perform these tasks.

Important: There is no change to configured policies, functionality, or the configuration experience, the user interface is identical to the existing experience in the Intune admin center. Additionally, there is no change to the required roles or permissions needed to create or manage policies.

[What you need to do to prepare:]

Update your IT admin guidance and documentation as needed. No additional action is required to retain existing policy functionality.

[Introduction]

To help organizations manage SharePoint storage more flexibly and avoid over-provisioning, Microsoft is introducing a pay-as-you-go, consumption-based billing model for SharePoint storage overages. This option allows you to pay only for the additional storage you actually use, rather than pre-purchasing extra capacity. The experience integrates with Microsoft 365 Archive and helps align storage costs with real usage.

This change is associated with Microsoft 365 Roadmap ID 506743.

[When this will happen:]

• Public Preview (Worldwide): We will begin rolling out in early June 2026 and expect to complete by mid-June 2026.
• We will update this message with General Availability (GA) details as they become available.

[How this affects your organization:]

Who is affected:

• Microsoft 365 administrators managing SharePoint Online storage
• Note: This feature isn’t currently available to education tenants. Let us know if you’d like it to be supported in the future.

What will happen:

• Admins can enable pay-as-you-go SharePoint storage billing in the Microsoft 365 admin center.
• Storage used above the included tenant quota will be automatically billed based on consumption.
• There is no impact to users.
• The existing Office 365 Extra File Storage add‑on remains available if you prefer to manually increase your storage quota instead.
• The feature is opt-in and off by default.

[What you can do to prepare:]

• No immediate action is required. However, we recommend the following:
• Review your tenant’s current SharePoint storage usage in the SharePoint admin center > Active sites.
• Evaluate whether a consumption‑based model or manually purchased storage best fits your organization’s cost and governance preferences.
• If you plan to enable pay‑as‑you‑go billing:
  • Ensure the appropriate Azure subscription and billing permissions are in place.
  • Update internal documentation or cost‑management processes as needed.
• Share this information with finance or procurement teams if they track usage‑based charges.

Learn more: Add more SharePoint storage to your subscription | Microsoft Learn

[Compliance considerations]

• See and prioritize work, including workload details, top cases, and what needs attention.
• Retrieve case and customer interaction summaries to quickly understand service history and current context.
• Discover answers from support knowledge across Dynamics 365 and connected sources such as SharePoint.
• Draft customer communications and prepare next steps with Microsoft 365 context when relevant.
• Take action on cases through natural language, such as adding notes, updating status, and creating child cases.

• Identify resources that may be impacted by data loss prevention (DLP) policies or advanced connector policies (now Generally Available)
• Understand which connectors dominate adoption across the tenant.
• Plan for connector deprecations or licensing tier changes.
• And more!

[What and Why:]

Work IQ API is reaching general availability (GA) on June 16, delivering production-ready, enterprise-grade intelligence built for agentic workloads. It provides the data, context, and tools agents need to operate with greater awareness and effectiveness across applications and workflows. At GA, the Work IQ API will be available through consumption-based billing using Copilot Credits, see licensing details here.

Alongside this milestone, we’re introducing new cost management controls in the Microsoft Admin Center, giving IT a single place to turn on credit-based billing for services that consume Copilot Credits, set policy-based limits, and monitor consumption across users, groups, and agents.

This message is associated with Microsoft 365 Roadmap ID 559020.

[Rollout Schedule:]

• General Availability is on June 16, 2026.

[Impact on Your Organization:]

Who is affected:

• Organizations using the Work IQ API through third‑party agents or applications during public preview.
• Organizations planning to use Work IQ API with third‑party solutions after GA.

Who is not affected:

• Organizations using Work IQ only through Microsoft-built apps and agents.

Platforms/Services:

• Microsoft 365
• Work IQ API
• Microsoft admin center
• Third-party agents and applications

What will happen:

• The Work IQ API transitions from public preview to general availability.
• Consumption‑based billing using Copilot Credits is introduced for Work IQ API usage via third‑party agents and applications.
• New cost management controls become available in the Microsoft admin center.
• Existing and new usage through third-party agents or applications will require billing configuration after GA to continue service access.

[Action Required / Recommendations:]

Action is required if you use Work IQ API with third‑party agents or applications.

Starting on June 16, administrators should:

• Configure consumption‑based billing for Work IQ API in the Microsoft admin center.
• Create spend policies for users, groups, and departments.
• Set usage limits and alerts to manage spend.
• Review the Cost Management dashboard to monitor Copilot Credit usage and runway.
• Communicate this change to IT operations and finance teams supporting Copilot or agentic workloads.

Learn more:

• Work IQ API public preview: Build Copilot powered agents with A2A
• Copilot Studio licensing | Microsoft Learn
• Billing rates and management | Microsoft Learn

Compliance considerations: