Microsoft Roadmap, messagecenter and blogs updates from 29-05-2026

Updated May 28, 2026: We have decided not to move forward with this change. We apologize for any inconvenience.

As a follow up to MC804771, based on Admin feedback, we are updating the behavior for automated hiding of inactive channels to be opt-in (suggestions) only. With this update, Teams will offer users suggestions on channels that are inactive, and the user is prompted to review their inactive channels and hide them only if they choose. The user will also be able to view when they last visited the channel to help them decide if they would like to hide the channel. The settings support this opt-in workflow and there are no changes to the on demand hiding process.

This message is associated with Microsoft 365 Roadmap ID: 325780

[When this will happen:]

Targeted Release: Available now.

General Availability (Worldwide, GCC, GCC High, DoD): We have decided not to move forward with this change.

[How this will affect your organization:]

Before this rollout:

Users had to manually manage their relevant channels list by hiding inactive and irrelevant channels.

After this rollout:

Manage preferences for automated suggestions via Teams Settings

If users prefer to manage channels manually, they can opt out of the auto-suggestions process. Simply go to Teams settings, select General, and toggle off “Suggestions for hiding inactive channels.”

Hide inactive channels on demand when needed

Users can manually view which channels are inactive and choose to hide some or all of them whenever you need. This can be done from Settings, under General, by clicking the “Get Suggestions” button. Note that this action can be performed once every 24 hours.

Automated suggestions of inactive channels

With this, Teams will suggest channels that have been inactive for the user. Once the inactive channels are identified, the user is notified with the coach mark message, “Looks like you haven’t visited some channels lately. Hide them to help you focus.”

The user can select Review and Hide to see the details and decide which channels they would like to hide. The user can choose not hide any channels by selecting Not Now.

If a user has less than or equal to 25 shown channels, no channels will be suggested for that user. This feature is on by default and all Teams users on the affected platforms will have access to it.

[What you need to do to prepare:]

Admins need to be aware of this feature, but no additional action is needed.

Updated May 28, 2026: We have updated the timeline. Thank you for your patience. 

Introduction

We’re introducing context preservation behavior in Microsoft Teams that restores recent conversation and view state when users return after a brief period.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. It’s associated with Roadmap ID 557184.

When this will happen:

Targeted Release: Rollout begins early April 2026 and is expected to complete by mid-April 2026. 

General Availability (Worldwide): Rollout begins mid-April 2026 (previously mid-March) and is expected to complete by late June 2026 (previously late April)

How this affects your organization:

Who is affected:

• All Microsoft Teams users

What will happen:

• When users leave a chat, channel, or Quick View and return within 30 minutes,
  • Their previously selected tab is restored
  • Any opened side panel is restored
  • The layout is restored
  • In Quick View, the previously selected message is restored
• This supports short interruptions and quick context switching, allowing users to resume work without resetting their workspace
• When users return after more than 30 minutes:
  • The conversation or view opens in the default layout 
  • Prior context is not restored
• The feature is enabled by default
• There are no new admin controls or configuration options

What you can do to prepare:

No action is required

Compliance considerations:

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

Updated May 28, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We will introduce new controls that allow users to customize how quick views appear at the top of their chat and channels lists in Microsoft Teams. This update aligns with customer feedback requesting a cleaner and more focused experience. These controls will help users see only the quick views that are relevant to them and manage when those views appear.

This message is associated with Microsoft 365 Roadmap ID 555856.

[When this will happen]

• Targeted Release: We will begin rolling out in March 2026 and expect to complete in March 2026.
• General Availability (Worldwide, GCC, GCCH, and DoD): We will begin rolling out in late March 2026 and expect to complete by late June 2026 (previously mid‑April).

[How this affects your organization]

Who is affected: All Microsoft Teams users in commercial Microsoft 365 tenants.

What will happen:

• Today, within the Teams chat and Teams apps, users see a set of quick views displayed above the lists of chats and channels. These quick views are always visible for all users, regardless of whether they contain messages.
• With this update, quick views will appear only when they contain messages, and users will have new controls to manage how their quick views behave:

  

• Quick views such as Mentions, Followed threads, and Tag mentions will, by default, appear only when a user has at least one message associated with that view.
• Users will be able to adjust each of these quick views from the context menu, including the ability to show them only when unread messages exist.
• Quick views such as Saved will be configurable to show always or be hidden.
• Hidden quick views will be accessible by selecting the eye icon next to the Quick views header.
• The Quick views section will be collapsible, and the header will appear in bold when any quick view contains unread messages.
• This feature will not require admin configuration and will be enabled automatically for users.
• Platform availability: This update will be available on Microsoft Teams for Windows, Mac, and web. Support for mobile platforms will follow in a future update.

[What you can do to prepare]

No admin action will be required to enable this feature.

You may want to:

• Inform your helpdesk or support staff about the upcoming change.
• Update user training materials or documentation if you maintain them.
• Review Teams support resources once updated documentation for quick views becomes available.

[Compliance considerations]

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

Updated May 28, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re releasing an improvement to Microsoft Teams that syncs your recently used emojis and reactions across devices. With this update, users will see the same set of “recently used” emojis when using Teams on Android, iOS, Mac, Windows desktop, and Teams for the web, creating a more consistent and seamless experience when communicating across chats and channels. This enhancement aligns with customer feedback requesting a unified emoji experience across platforms.

This message is associated with Microsoft 365 Roadmap ID 554927.

[When this will happen]

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

[How this affects your organization]

Who is affected

• All Microsoft Teams users across supported clients.

What will happen

• Recently used emojis and reactions will sync across devices.
• Users will see the same “recently used” list regardless of which Teams client they use.
• The feature will be enabled by default; no configuration is required for rollout.
• Existing Teams admin settings and messaging policies will continue to apply.
• There is no impact to message flow, data storage, compliance boundaries, or customer data pathways.

[What you can do to prepare]

No action is required. This update will roll out automatically.

Admins may optionally:

• Inform helpdesk or support teams about this user experience update.
• Update internal documentation if you reference emoji behavior or Teams UI details.
• Review your Messaging settings and Messaging policies if you manage custom emoji usage.

Learn more about emoji and reaction usage in Microsoft Teams: Send an emoji, GIF, or sticker in Microsoft Teams | Microsoft Support

[Compliance considerations]

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

This feature does not introduce new data storage, processing changes, AI/ML capabilities, communication pathways, admin reporting changes, or modifications to Purview‑governed workflows. 

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

[Introduction]

We are adding new Copilot metrics across Microsoft 365 apps to help you better understand how users engage with Copilot. These metrics include actions taken in the Microsoft 365 Copilot app, Microsoft Edge, and OneNote, and intent-based usage across Outlook, Word, Excel, and PowerPoint. This update expands visibility into how users adopt Copilot and supports improved insights in the Copilot Dashboard and Advanced Analysis in Copilot Analytics. 

In parallel, Microsoft 365 Copilot Chat will unify Work and Web tabs into a single, streamlined Copilot Chat experience. As part of this change, Copilot Analytics will consolidate Copilot Chat (Work) and Copilot Chat (Web) reporting into one unified Copilot Chat metric.

This message is associated with Microsoft 365 Roadmap ID 557981.

[When this will happen]

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

[How this affects your organization]

Who is affected

• This capability is available to users who are licensed for Microsoft 365 Copilot.
• All Microsoft 365 tenants with access to Copilot Dashboard or Copilot Analytics in Viva Insights

What will happen

• New metrics will appear in the Copilot Dashboard and Advanced Analysis.
• Copilot Chat (Work) will be renamed as Copilot Chat, and Copilot Chat (web) will be renamed as Copilot Chat (legacy web).
• You will be able to track Copilot usage in the Microsoft 365 Copilot app, Microsoft Edge, and OneNote:

   

  

• Additional intent-based scenarios will be measured in Outlook, Word, Excel, and PowerPoint. These scenarios include suggested replies, translation, coaching, and clean data.
• The feature will be enabled automatically for all tenants.
• No configuration changes or policy updates are required.

[What you can do to prepare]

• No action is required before rollout.
• You may choose to notify relevant teams about the new metrics.
• Update internal documentation if your organization tracks Copilot usage analytics.
• Review updated online documentation when it becomes available in early May.

[Compliance considerations]

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

Updated May 28, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We’re improving the Frontier Admin Control by adding support for Entra ID groups when managing Frontier enrollment. This update helps administrators scale Frontier pilots more efficiently by aligning enrollment with existing access management practices and reducing the need to manage individual users.

Nested groups are not supported.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Microsoft 365 administrators who manage Frontier access using the Frontier Admin Control.

What will happen:

• Admins will continue to manage Frontier access from the Frontier Admin Control in the Microsoft 365 admin center.
• Admins can assign Frontier access using Entra ID groups in addition to individual users.

Screenshot: Frontier admin control showing the option to assign access to specific users and groups:

>

• Group-based enrollment supports managing pilot audiences without enabling Frontier for the entire tenant.
• A maximum of 10,000 enrolled users applies when using specific users and/or groups.
  • Admins will see a warning if adding a group causes the total enrolled user count to exceed this limit.
  • Admins must remove users or groups until the total enrollment is within the limit.
• Tenants enrolling All Users are not subject to the 10,000-user limit.
• There is no change for tenants already enrolling the entire organization.

[What you can do to prepare:]

• No immediate action is required.
• If you plan to use group-based enrollment:
• Create or identify a dedicated Entra ID group for Frontier participants.
• Add the group to the Frontier Admin Control instead of managing individual users.
• Review group membership regularly to ensure the total enrolled users remain within the 10,000-user limit (if not using All Users).
• Update internal admin documentation or pilot guidance, if applicable.

[Compliance considerations:]

This change introduces an admin control that can be managed through Entra ID group membership. No other compliance impacts were identified.

Updated May 28, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

To help organizations respond more quickly to external security threats, Microsoft Teams will allow users to report suspicious external users directly from Teams. These reports will surface in the Teams admin center, giving admins greater visibility into potentially risky interactions and enabling faster investigation and response. This enhancement will build on existing reporting capabilities and will use user signals as an additional layer of protection against phishing, impersonation, and social engineering attacks.

This message is associated with Microsoft 365 Roadmap ID 560547.

[When this will happen]

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

[How this affects your organization]

Who is affected

• All Microsoft 365 tenants using Microsoft Teams
• Users who interact with external users in Teams
• Admins managing Teams security and reporting in the Teams admin center

What will happen

• Users will be able to report suspicious external users directly in Teams, in addition to blocking them: 

  

• Reporting will be available during first time external chat requests and from an external user profile card.
• Reporting will be supported across Teams experiences including chats, meetings, channels, and search results.
• When a user is reported, the submission will appear in the Teams admin center under Protection reports > User reported security submission report

  

• Admins will be able to review reported users and investigate potential phishing, impersonation, or other suspicious activity.
• Additional metadata will be available through report export to support investigation and response workflows.
• This feature will be enabled by default and will respect existing Teams messaging policies.

[What you can do to prepare]

No action will be required if you want to keep user reporting enabled.

Admins may choose to take the following actions:

• Review current Teams messaging policies and confirm that the Report a security concern setting remains enabled.
• Familiarize security and helpdesk teams with the User reported security submission report in the Teams admin center.
• Update internal security guidance or user education materials, if applicable.
• If a malicious external user is identified through these reports, block that user at the tenant level using External access settings to prevent further communication attempts.

[Compliance considerations]

Updated May 28, 2026: We have updated the content. Thank you for your patience. 

[Introduction]

We’re updating the way SharePoint Online enforces user storage quotas to ensure they are consistently aligned with license entitlements. This change fixes an issue where user-specific storage limits could be incorrectly applied during quota refreshes, which could result in inaccurate storage enforcement. These updates help ensure predictable storage behavior and improve reliability for admins managing storage at scale.

[When this will happen]

General Availability (Worldwide, GCC, GCCH, and DoD): We will begin rolling out in late May 2026 and expect to complete in June 2026.

[How this affects your organization]

Who is affected

• Microsoft 365 tenants using SharePoint Online
• Users who are currently over the OneDrive for Business storage quota allowed by their assigned license
• Admins who have set user-specific storage limits above licensed entitlements

What will happen

• User storage quotas will be re-evaluated against license limits during the refresh process.
• Users whose OneDrive for Business storage usage exceeds their licensed quota will be placed into a read-only state, which temporarily restricts write access to existing SharePoint content until storage usage is remediated.
• This includes scenarios where:
  • An admin-set user quota exceeds the license allowance, or
  • A user with an EDU license exceeds their licensed storage limit.
• No changes are made for users who are within their licensed storage limits.

[What you can do to prepare]

• Identify users exceeding licensed storage limits
  • Review OneDrive storage usage across your organization to identify users whose usage exceeds their licensed quota.
  • Use Identify OneDrive Users Over License-Based Storage Quota | PnP Samples 
  • Review this article: OneDrive site is read-only because storage quota was exceeded – SharePoint | Microsoft Learn
• Take corrective action for affected users. For users exceeding their licensed storage limits:
  • Upgrade the user’s license to increase available storage, or
  • Work with the user to reduce storage usage to within licensed limits.
• Inform your helpdesk and SharePoint admins about this change so they can support users who may be placed into a read-only state.
• If all users are within their licensed storage quotas, no action is required.

[Compliance considerations]

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

Updated May 28, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

A new Security Detection Report in the Teams admin center provides a unified view of messaging security detections across signals such as impersonation, malicious URLs, and weaponizable file types. This centralized reporting experience improves visibility into threats in Teams and helps admins investigate and respond to suspicious activity more efficiently.

This message is associated with Microsoft 365 Roadmap ID 560702.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Admins who manage Microsoft Teams environments and security operations
• Security and helpdesk teams responsible for investigating messaging threats

What will happen:

• A new Security Detection Report will be available in the Teams admin center under Analytics & reports > Protection reports > Security detections report.

Screenshot: Example of a Security Detection Report:



• The report provides centralized visibility into messaging security detections across Teams, including impersonation attempts, malicious links, and unsafe file types.
• Admins can review detection details such as:
• Sender
• Recipient context
• Detection type
• Available user actions
• Admins can export report data for further investigation, including additional metadata such as sender identifier and thread ID.
• The following messaging security protections are enabled by default:
• Impersonation detection does not require configuration.
• Malicious link scanning can be managed through Messaging safety settings in the Teams admin center.
• Unsafe file type scanning can be managed through Messaging safety settings in the Teams admin center.
• Admins can block malicious external users identified in the report through External access settings to prevent further communication attempts.

[What you can do to prepare:]

• Review current Messaging safety settings to confirm malicious link and file scanning configurations.
• Familiarize security and helpdesk teams with the new report and export capabilities.
• Update investigation and response workflows to incorporate Teams detection signals.
• Use Teams admin center navigation path to locate the report:
  • Analytics & reports > Protection reports > Security detections report
• Update internal documentation or runbooks if you document security investigation processes.

Before rollout, we will update this post with new documentation.

[Compliance considerations:]

Introduces enhanced admin reporting for monitoring and investigating messaging security detections.

Updated May 28, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why]

Users are currently blocked from sending messages in Microsoft Teams while a file upload is in progress, which can disrupt real-time collaboration. With this update, file uploads will occur asynchronously in the background, allowing users to continue sending messages without interruption.

This message is associated with Microsoft 365 Roadmap ID 560813.

[Rollout Schedule]

• Targeted Release: Rollout will begin in early July 2026 (previously mid-June) and is expected to complete by mid-July 2026 (previously late June).
• General Availability (Worldwide): Rollout will begin in mid-July 2026 (previously late June) and is expected to complete by late July 2026 (previously late June).

[Impact on Your Organization]

Who is affected

All Microsoft Teams users who send files in chats or channels

Platforms/Services

• Microsoft Teams
• Desktop (Windows, Mac)
• Web
• Mobile (iOS, Android)

What will happen

• Users will be able to send chat messages while files are uploading.
• File uploads will occur asynchronously in the background.
• The message input box will no longer be blocked during uploads.
• There are no changes to how files are stored or shared.
• Existing compliance, retention, and security policies remain unchanged.
• This feature will be enabled by default for all tenants.

[Action Required / Recommendations]

• No action is required.
• Consider informing your users about improved file upload behavior in Teams chats.
• Update internal training or support documentation if you reference file-sharing workflows.

[Compliance considerations]

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

Updated May 27, 2026: We have updated the content. Thank you for your patience. 

[What and Why]

We are introducing the Prepare for Questions skill in Copilot in PowerPoint for Web to help users become more productive and confident presenters. This feature analyzes presentations to identify potential weak points and anticipate audience questions, helping users improve storytelling and deliver presentations more effectively.

This skill requires Anthropic model. GPT5.5 support coming soon.

[Rollout Schedule]

General Availability (Worldwide): We will begin rolling out in late May 2026 and expect to complete by late May 2026.

[Impact on Your Organization]

Who is affected

• Users in Microsoft 365 tenants with access to Copilot in PowerPoint for Web

Platforms/Services

• PowerPoint for Web
• Microsoft Copilot Chat

What will happen:

• Users will have access to the new ‘Prepare for Questions’ Copilot skill within PowerPoint for Web: 

  

• The feature provides insights to help users anticipate and prepare for audience questions.
• This feature is enabled by default for eligible users.
• IT admins cannot control the availability of individual skills.
• Skills that depend on the Anthropic model will respect existing admin configuration; if the Anthropic model is disabled, those skills will not be available.

[Action Required/Recommendations]

No action is required.

• Inform your users about this new capability and how it can help improve presentation quality and confidence.
• Review your current Copilot and model configuration settings, if applicable.
• (Optional) Update internal documentation or training materials to reflect this new feature.

Learn more: Anthropic as a subprocessor for Microsoft Online Services | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

[Compliance considerations]

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

Updated May 27, 2026: We have updated the content. Thank you for your patience. 

[What and Why]

We are introducing the Prepare for Questions skill in Copilot in PowerPoint for Windows Desktop to help users become more productive and confident presenters. This feature analyzes presentations to identify potential weak points and anticipate audience questions, helping users improve storytelling and deliver presentations more effectively.

This skill requires Anthropic model. GPT5.5 support coming soon.

[Rollout Schedule]

General Availability (Worldwide): We will begin rolling out in late May 2026 and expect to complete by late May 2026.

[Impact on Your Organization]

Who is affected

• Users in Microsoft 365 tenants with access to Copilot in PowerPoint for Windows Desktop

Platforms/Services

• PowerPoint for Windows Desktop
• Microsoft Copilot

What will happen:

• Users will have access to the new ‘Prepare for Questions’ Copilot skill within PowerPoint for Windows Desktop: 

  

• The feature provides insights to help users anticipate and prepare for audience questions.
• This feature is enabled by default for eligible users.
• IT admins cannot control the availability of individual skills.
• Skills that depend on the Anthropic model will respect existing admin configuration; if the Anthropic model is disabled, those skills will not be available.

[Action Required/Recommendations]

No action is required.

• Inform your users about this new capability and how it can help improve presentation quality and confidence.
• Review your current Copilot and model configuration settings, if applicable.
• (Optional) Update internal documentation or training materials to reflect this new feature.

Learn more: Anthropic as a subprocessor for Microsoft Online Services | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

[Compliance considerations]

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

Updated May 27, 2026: We have updated the content. Thank you for your patience. 

[What and Why]

We are introducing the Prepare for Questions skill in Copilot in PowerPoint for Mac to help users become more productive and confident presenters. This feature analyzes presentations to identify potential weak points and anticipate audience questions, helping users improve storytelling and deliver presentations more effectively.

This skill requires Anthropic model. GPT5.5 support coming soon.

[Rollout Schedule]

General Availability (Worldwide): We will begin rolling out in late May 2026 and expect to complete by late May 2026.

[Impact on Your Organization]

Who is affected

• Users in Microsoft 365 tenants with access to Copilot in PowerPoint for Mac

Platforms/Services

• PowerPoint for Mac
• Microsoft Copilot

What will happen:

• Users will have access to the new ‘Prepare for Questions’ Copilot skill within PowerPoint for Mac: 

  

• The feature provides insights to help users anticipate and prepare for audience questions.
• This feature is enabled by default for eligible users.
• IT admins cannot control the availability of individual skills.
• Skills that depend on the Anthropic model will respect existing admin configuration; if the Anthropic model is disabled, those skills will not be available.

[Action Required/Recommendations]

No action is required.

• Inform your users about this new capability and how it can help improve presentation quality and confidence.
• Review your current Copilot and model configuration settings, if applicable.
• (Optional) Update internal documentation or training materials to reflect this new feature.

Learn more: Anthropic as a subprocessor for Microsoft Online Services | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

[Compliance considerations]

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

[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

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.

[What and Why:]

Microsoft Teams events will support custom user templates, allowing organizers to save an event configuration and reuse it when creating future events. This reduces repeated setup and helps ensure consistent event configuration and branding across events created in your organization.

This message is associated with Microsoft 365 Roadmap ID 561915.

[Rollout Schedule:]

• Targeted Release (Worldwide): We will begin rolling out in early June 2026 and expect to complete by late 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 who organize and schedule Microsoft Teams events

Platforms/Services: Microsoft Teams (events scheduling experience) 

What will happen:

• Organizers can save an existing Teams event as a reusable template.
• Templates can include event details, participants, branding, and configuration settings.
• Saved templates can be reused and edited for future events.
• New events can be created from a predefined configuration.
• No admin configuration is required.

[Action Required / Recommendations:]

• No action is required.
• Consider informing Teams event organizers about this capability.

[Compliance considerations:]

Event templates store copies of existing event configuration data for reuse within the tenant.

[What and Why:]

Assign open shifts is a new Microsoft Teams Shifts capability that helps managers build schedules more efficiently. Managers can enter shifts that need coverage as open shifts, then use Assign open shifts to automatically assign those shifts within a schedule group based on employee availability, approved time off, historical scheduling patterns, and configured scheduling rules. Managers can review and adjust assignments before publishing the schedule.

This message is associated with Microsoft 365 Roadmap ID 562535.

[Rollout Schedule:]

• General Availability (Worldwide): Rollout begins in mid-June 2026 and is expected to complete by late June 2026.

[Impact on Your Organization:]

• Who is affected: Frontline managers who create or manage schedules using Microsoft Teams Shifts.
• Platforms/Services: Microsoft Teams (Shifts) on web and desktop.
• What will happen:
  • A new “Assign open shifts” button appears for users with scheduling permissions.
  • Open shifts can be automatically assigned based on availability, time off, historical patterns, and scheduling rules.
  • Managers can review and edit assignments before publishing.
  • Using the feature is optional.

  Screenshot 1: Select a schedule group and review constraints from the Assign Open Shifts dialog:

  

  Screenshot 2: A schedule has been successfully generated:

  

[Action Required / Recommendations:]

• No action is required.
• Admins may choose to share documentation and update internal guidance for scheduling managers.

Learn more: Auto-assign open shifts – Microsoft 365 for frontline workers | Microsoft Learn

[Compliance considerations:]

[What and Why:]

PowerPoint Live presenters will soon be able to refresh their presentation during a live meeting to load the latest version of the deck without restarting the presentation. This improvement helps presenters stay aligned with last-minute updates and reduces meeting disruption, supporting personal and team productivity by keeping everyone in sync in real time.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected:

• Users who present content using PowerPoint Live in Microsoft Teams meetings.

Platforms/Services:

• Microsoft Teams (PowerPoint Live)

What will happen:

• Presenters will see a new one‑click option during a PowerPoint Live session to reload the latest saved version of the presentation.
• Selecting the button reloads the latest saved version of the presentation.

Screenshot: Select the refresh button to reload your PowerPoint deck and present the latest updates:



• The presentation continues without needing to stop and restart sharing.
• The feature is available by default; no admin configuration is required.

[Action Required / Recommendations:]

• No action is required.
• Consider notifying presenters and helpdesk staff about this enhancement.

[Compliance Considerations:]

The feature reloads the most recent version of an existing PowerPoint file during a live presentation but does not introduce new storage locations or retention behaviors.

[What and Why]

To address customer feedback, Microsoft is introducing a new user-level setting in Microsoft Teams that allows individuals to disable file previews in their messaging experience. This gives users more control over how files are displayed while preserving the existing experience by default.

This message is associated with Roadmap ID 561321.

[Rollout Schedule]

• Targeted Release: Rollout will begin in early June 2026 and is and is expected to complete by mid-June 2026.
• General Availability (Worldwide): Rollout will begin mid-June 2026 and is expected to complete by late June 2026.

[Impact on Your Organization]

Who is affected:

All users in Microsoft 365 tenants who use Microsoft Teams.

Platforms / Services:

• Microsoft Teams for Windows desktop, Teams for Mac desktop, Teams for the web

What will happen:

• A new setting called “Enable file previews” will appear under Settings > Files and links.
• The setting is ON by default, so there is no change to existing behavior.
• Users can turn the setting OFF to disable file previews for themselves.
• This setting applies per user; other users will still see file previews if enabled.
• The setting applies only for the current client and needs to be set for each client (for example, desktop and web).

[Action Required / Recommendations]

• No admin action is required.
• Notify helpdesk staff about this change.
• Optionally inform users that they can manage file previews in Teams settings.

[Compliance considerations]

Updated May 28, 2026: We have updated the timeline. 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 new entry points 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 two entry points in SharePoint:

1. Start from Publish

• A new prompt box will appear at the top of the Publish landing page.

>

• 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:]

[What and Why]

Microsoft Defender XDR is adding two new account action buttons, Disable account and Reset password, to the Password protection experience. This update allows administrators to take direct remediation actions on accounts identified as risky from the Password protection page.

[Rollout Schedule]

• Public Preview: Late May 2026 through mid-June 2026
• General Availability (Worldwide): Late Jun 2026 through late June 2026

[Impact on Your Organization]

Who is affected

• Administrators using Microsoft Defender XDR
• Applies to Active Directory human user accounts

Platforms/Services

• Microsoft Defender XDR (web portal)
• Password protection experience

What will happen

• The Password protection page will include two new action buttons:
  • Disable account
  • Reset password
• These actions can be performed directly from the Password protection page: 

  

• These actions apply only to Active Directory human user accounts.
• These actions are not available for the krbtgt (Kerberos Ticket Granting Ticket) accounts.
• The feature is enabled by default.
• No configuration changes are required.

[Action Required/Recommendations]

• No action is required.
• Inform security administrators about the new actions available in the Password protection page.
• Review internal processes for responding to risky accounts.
• Update internal documentation if applicable.

Learn more: Investigate identity password protection (Preview) | Microsoft Learn

[Compliance considerations]

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

[What and Why]

We are updating the default setting for the profanity filter in Microsoft Teams live captions from On to Off. This change ensures captions more accurately reflect spoken content, supporting accessibility needs and aligning with regional regulatory requirements (including the EU). Users retain full control and can enable or disable the filter at any time.

This message is associated with Microsoft 365 Roadmap ID 560323.

[Rollout Schedule]

• Targeted Release: Early June 2026 – Mid-June 2026
• General Availability (Worldwide): Mid-June 2026
• General Availability (GCC, GCCH, and DoD): Mid-June 2026 – Late June 2026

[Impact on Your Organization]

Who is affected

• Users who have never configured their live captions profanity filter setting in Teams
• Applies to all Microsoft 365 tenants using Microsoft Teams

Platforms/Services

• Microsoft Teams
• Meetings, calls, and events
• Microsoft Teams Rooms (MTR) devices
• Desktop, web, and mobile clients

What will happen

• The profanity filter for live captions will be Off by default for newly initialized users.
• Users who have already configured this setting will not be affected.
• Live captions may display unfiltered language by default after rollout.
• Users can update their preference at any time in Teams settings:

  

• No changes are made to admin policies or configurations.

[Action Required / Recommendations]

No admin action is required.

Admins may consider the following:

• Inform helpdesk and support teams about this change.
• Communicate to users that:
  • Live captions may display unfiltered language by default.
  • Users can re-enable profanity filtering in Teams settings.
• Update internal documentation or training materials if applicable.

Learn more: Use live captions in Microsoft Teams meetings | Microsoft Support

[Compliance considerations]

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

[What and Why]

We are introducing the Teams Rooms Builder in the Teams Rooms Pro Management portal, a visual planning tool that helps IT admins design and standardize meeting spaces. Builder simplifies the process of selecting compatible devices, licenses, and room configurations, helping organizations plan deployments more efficiently and consistently. This feature supports faster decision-making and improved standardization across Teams Rooms environments.

This message is associated with Microsoft 365 Roadmap ID 561549.

[Rollout Schedule]

• General Availability (Worldwide): Early June 2026 through mid-June 2026

[Impact on Your Organization]

Who is affected

IT admins managing Teams Rooms Pro environments

Platforms/Services

• Teams Rooms Pro Management portal (web)
• Microsoft Teams Rooms ecosystem
• Requires a Teams Rooms Pro license

What will happen

• A new Teams Rooms Builder experience will be available in the Pro Management portal: 

  

• Builder provides a visual and guided interface to design meeting rooms (traditional, signature, and flexible spaces).
• Admins can:
  • Explore room configurations and layout options.
  • Select compatible devices and licenses: 

    

  • Generate and download a Bill of Materials (BOM).
• The feature is enabled by default for tenants with Teams Rooms Pro.
• Admins can control visibility and role-based access through existing Pro Management Portal settings, including the option to hide Builder for their tenant.
• No changes will be made to existing rooms or device configurations.
• Purchasing capabilities are not included (no shopping cart or transaction functionality).

[Action Required / Recommendations]

No action is required.

Admins may consider the following:

• Review Builder availability and settings in the Teams Rooms Pro Management portal.
• Adjust visibility and role-based access as needed to align with your organization’s governance model.
• Share guidance with relevant IT teams responsible for meeting room planning and deployment.

[Compliance considerations]

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

[Introduction]

We will retire the Microsoft 365 Usage Analytics Power BI template app to streamline reporting experiences and align with modern, supported Microsoft 365 reporting solutions. Starting June 1, 2026, new downloads will no longer be available, and the app will reach end of support on August 1, 2026.

Customers will continue to have access to core usage insights through the Microsoft 365 admin center and Microsoft Graph APIs.

[When this will happen]

• June 1, 2026: New downloads of the template app will no longer be available.
• August 1, 2026: The app and associated data pipelines will reach end of support and stop functioning.
• August 2026: This change will be effective worldwide.

[How this affects your organization]

Who is affected

• Admins and analysts using the Microsoft 365 Usage Analytics Power BI template app
• Organizations relying on the app for Microsoft 365 usage, adoption, or activity reporting

What will happen

• New downloads of the template app will stop after June 1, 2026.
• Existing installations will stop receiving data after August 1, 2026.
• Reports and dashboards based on the template app will no longer refresh.
• Historical reports will remain accessible, but data will not be current.
• Data that has already been exported from the template app will remain usable outside the app.
• There will be no replacement of the template app as a single packaged solution.
• Equivalent usage metrics will continue to be available through supported Microsoft tools.
• There will be no admin control or option to extend use of the retiring app after end of support.

[What you can do to prepare]

Action is required.

• Identify whether your organization is currently using the Microsoft 365 Usage Analytics Power BI template app.
• Plan your transition to supported reporting solutions before August 1, 2026.
• Review alternative reporting options available today. All core usage metrics currently available in the template app as of May 2026 will continue to be accessible through:
  
  • Microsoft 365 admin center usage reports, available at https://admin.microsoft.com
  • Microsoft Graph APIs for programmatic access to usage metrics and custom integrations
• If you plan to rebuild a custom reporting solution, review Microsoft documentation for available usage metrics, including adoption, usage, communication, collaboration, storage, mobility, and service-level activity across Microsoft 365 services such as Exchange, Teams, OneDrive, and SharePoint.
• Update internal documentation and reporting processes as needed.
• Communicate this change to relevant stakeholders and reporting owners.

Learn more:

• Microsoft 365 usage analytics overview | Microsoft 365 admin center | Microsoft 365 | Microsoft Learn
  
• Working with Microsoft 365 usage reports in Microsoft Graph | Microsoft Graph | Microsoft Learn
  

[Compliance considerations]

• Faster load times through optimized scripting, ensuring quicker display of the chat button even on slower network connections.
• Modernized look and feel with expanded customization options to better align with your brand and website design.
• Quality-of-life improvements, including enhanced media support for smoother customer interactions.

• Create sites end-to-end: Generate complete Power Pages sites from initial site creation through production-ready release.
• Leverage platform-aware code generation: The generative AI code generation tools with skills to understand Power Pages-specific constructs including web roles, table permissions, web APIs, and site settings.
• Generate accurate security configurations: Produce correctly structured table permissions and web role assignments that follow Power Pages best practices.
• Build with modern frameworks: Create React and TypeScript-based single-page applications optimized for Power Pages hosting.

• Makers can assign security roles to individual summaries, giving them fine-grained control over who can view specific insights. This improvement aims to ease past challenges surfaced through support cases where incorrect or missing privileges prevented summaries from appearing as expected, reinforcing the importance of precise access control.
• Row summary support is extended to include US Government clouds, making the feature available to regulated customers working within stricter compliance and data boundary requirements. With this expansion, users in government environments can access the same at-a-glance understanding of records that commercial users enjoy.
• First-party summaries shipped by Dynamics 365 product teams, like Customer Service and Sales, are currently not accessible from view pages. The improvements in this wave allow users to see relevant Microsoft-provided insights immediately when browsing records in the grid, without needing to open each record individually.

• Improves evaluation accuracy by validating agent quality across full conversational flows, not isolated responses.
• Reduces production risk by detecting context loss, instruction drift, and breakdowns that only appear over multiple turns.
• Enables more realistic testing that mirrors real customer interactions..Accelerates issue identification in complex workflows, reducing costly post-release fixes..
• Strengthens release confidence for enterprise agents operating in multi-step scenarios..

• Access process mining semantic models in Power BI for reporting and dashboard creation.
• Preserve object-centric relationships between process entities in Fabric.
• Combine process intelligence data with other Fabric data sources.
• Configure data refresh synchronization for updated process insights.
• Use existing Fabric governance, security, and data management controls.

• Access to Microsoft Fabric.
• Appropriate permissions to publish and manage semantic models in Fabric.
• Existing object-centric process mining data in Power Automate.

• Selecting Dataverse knowledge sources in Copilot Studio.
• Viewing labeled information in citations within responses.

• Access extended customer information unified by Customer Insights – Data from external sources not available to Dataverse.
• Understand processed insights, such as calculated measures of a user’s purchase activity over time, or rewards points.
• Quickly discover what key segments the customer is a member of.
• If a customer has duplicate contacts or leads, determine which contact or lead is considered authoritative for that customer.
• See predictive insights for the customer, such as Customer Lifetime Value (CLV) and Churn risk, giving you greater insights into the customer’s current relationships with your company.

• Time-off requests: Evaluated against configurable constraints such as available leave balance, maximum consecutive days, allowed time‑off windows, shift coverage thresholds (over‑ or understaffed percentages), first‑come, first‑served rules, and seniority or tenure.
• Shift bidding: Governed by constraints including shift capacity, skill or proficiency matching, bid order or first‑come, first‑served logic, bidding windows, seniority, and schedule conflict checks such as overlaps or locked schedules.
• Shift swapping: Validated using constraints that assess coverage impact before and after the swap, detect schedule conflicts, and enforce swap eligibility rules such as allowed swap types and limits per period.

[What and Why]

This update introduces a simplified profile assignment and channel management experience for cloud update. Admins can now use groups to assign profiles and combine profile assignment with channel selection in a single step. This streamlines onboarding, makes it easier to move devices between update channels, and helps maintain consistent update management across the organization.

This message is associated with Microsoft 365 Roadmap ID 558250.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected: Admins managing Microsoft 365 Apps updates using Cloud Update in the Microsoft 365 Apps admin center.

Platforms / Services:

• Microsoft 365 Apps
• Microsoft 365 Apps admin center (Cloud Update)

What will happen:

• Admins can assign Cloud Update profiles using Microsoft Entra ID groups or built-in update channel groups.

Screenshot 1: Microsoft 365 Apps admin center home page showing available update profiles and access to profile management:



Screenshot 2: Profile details view showing device selection criteria using Microsoft Entra groups and built-in update channel groups:



• Profile assignment and update channel selection are combined into a single workflow.
• The Switch device update channel control in inventory is replaced by profile-based channel assignment.
• Existing Cloud Update profiles are automatically migrated with their associated built-in channel groups.
• Existing exclusions, rollout waves, pause controls, and rollback settings continue to apply.
• There is no impact to users.

[Action Required / Recommendations]

• No action is required to receive this public preview.
• Existing Cloud Update customers: profiles remain active and devices continue to be managed.
• New Cloud Update customers: profiles remain inactive until one or more groups are assigned.
• If you currently use the Switch device update channel control: add your group to the appropriate profile.
• Review and update any internal documentation related to Cloud Update.

Learn more:

New changes coming to cloud update – Microsoft 365 Apps | Microsoft Learn

[Compliance considerations]

[What and Why]

Microsoft Copilot Studio is introducing support for Mistral Medium 3.5. This update will provide customers with more flexibility to select models that best meet their business needs for agent orchestration and generative AI scenarios. External models such as Mistral remain disabled by default and require admin opt-in, ensuring administrators maintain control over model usage, data access, and compliance.

[Rollout Schedule]

• Public Preview: Rollout begins at the end of May 2026.

[Impact on Your Organization]

Who is affected

• Admins managing Microsoft Copilot Studio
• Organizations building or managing agents in Microsoft Copilot Studio

Platforms/Services

• Microsoft Copilot Studio
• Microsoft admin center
• Power Platform admin center

What will happen

• Mistral Medium 3.5 will be available as a selectable model in Copilot Studio for supported environments.
• The model will be included in the multi-model selection experience for agent orchestration.
• External models, including Mistral, will be disabled by default.
• Admins will need to enable external models at the tenant level before use.
• Makers will be able to select Mistral Medium 3.5 after admin enablement.
• Existing policies and governance controls will continue to apply.
• There will be no impact to users or workflows unless admins enable external models.

[Action Required / Recommendations]

No action is required unless you plan to enable this feature.

If you choose to enable Mistral Medium 3.5:

• Review external model configuration in your tenant
• Enable external models in the Microsoft admin center. Review: Connect to xAI’s models | Microsoft Learn
• Configure permissions and governance in the Power Platform admin center. Review: Allow external language models for generative responses | Microsoft Learn
• Communicate this change to makers using Copilot Studio.
• Update internal governance or AI usage policies if applicable.

Learn more: 

• Connect to xAI’s models | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn
  
• Allow external language models for generative responses | Microsoft Learn
  
• Mistral Medium 3.5 joins Copilot Studio model lineup for agents | Microsoft Copilot Blog
  
• Select a primary AI model for your agent | Microsoft Copilot Studio | Microsoft Learn
  

[Compliance considerations]

[What and Why]

You’re receiving this message because your organization uses Microsoft Entra ID Self-Service Password Reset (SSPR).

Currently, SSPR may allow users to verify their identity using contact information stored in directory attributes such as mobile phone, business phone, and alternate email, even if those values were never explicitly registered as authentication methods.

To strengthen identity security, SSPR will require explicitly registered authentication methods for verification. This change is part of Microsoft’s Secure Future Initiative and ensures password reset verification is based on trusted, user-validated methods rather than directory-sourced attributes.

[Rollout Schedule]

• July 6, 2026: SSPR registration campaign begins prompting users and administrators to register authentication methods.
• September 7, 2026: Enforcement begins. SSPR will no longer accept directory-sourced contact information for verification.
• General Availability (Worldwide, GCC, GCC High): Early September 2026 through mid-September 2026

[Impact on Your Organization]

Who is affected

• All users (including administrators) in tenants with SSPR enabled
• Applies to Public cloud and US Government clouds (GCC, GCC High, DoD)

Platforms/Services

• Microsoft Entra ID
• Self-Service Password Reset (SSPR)
• Web and admin portal experiences

What will happen

• Only explicitly registered authentication methods will be accepted for SSPR verification.
• Directory attributes (such as mobilePhone, businessPhone, otherMails) will no longer be valid unless registered.
• Approximately 86% of SSPR verifications already use registered methods today.
• Users without registered methods at enforcement will be:
  • Unable to complete password resets
  • Prompted to register methods or contact an administrator
• The registration campaign will proactively prompt affected users starting July 6, 2026.

[Action Required / Recommendations]

Action is required before September 7, 2026.

• Review authentication method registration coverage:
  • Go to Microsoft Entra admin center → Authentication methods → User registration details
• Ensure all users (including admins) have at least one registered authentication method that satisfies your SSPR policy.
• Allow or enable the SSPR registration campaign to prompt users automatically.
• Plan fallback processes:
  • Helpdesk-assisted registration
  • Alternative onboarding scenarios for users unable to self-register
• Communicate this change to:
  • IT admins and helpdesk teams
  • Users (encourage registration via My Security Info)

Learn more:

• Manage user authentication methods | Entra admin center
• Microsoft Q&A for Entra ID | Microsoft Security | Microsoft Entra | Microsoft Entra ID | Microsoft Learn
• Password policies and account restrictions in Microsoft Entra ID | Authentication | Microsoft Entra ID | Microsoft Entra | Microsoft Learn
• Prepopulate user authentication contact information for Microsoft Entra self-service password reset (SSPR) | Authentication | Microsoft Entra ID | Microsoft Entra | Microsoft Learn
• Register security information (My Security Info)
• Secure Future Initiative | Microsoft 

[Compliance Considerations]

[What and Why]

We are updating how Microsoft Teams sends guest invitation emails to improve clarity and trust in cross-tenant collaboration. Instead of being sent from a Microsoft no-reply address, guest invitation emails will soon appear to come directly from the inviter’s email address.

This change helps recipients easily recognize who invited them, enables direct replies, and reduces confusion, improving the overall collaboration experience.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected

• All Microsoft Teams users who invite external guests
• External recipients of guest invitations
• Microsoft 365 administrators managing guest access and collaboration policies

Platforms/Services

• Microsoft Teams
• Exchange Online (email delivery behavior)

What will happen

• Guest invitation emails will appear to come from the inviting user’s email address instead of a Microsoft no‑reply address: 

  

• Invitees can reply directly to the inviter via email or can redeem the invitation and use Teams.
• There are no changes to guest access permissions or policies.
• No admin configuration required.
• The feature will be enabled by default across all tenants.

[Action Required / Recommendations]

No action is required.

However, we recommend that you:

• Inform users that invitation emails will now appear to come from their own email address.
• Prepare helpdesk/support teams for potential questions about unexpected replies from external guests.
• Review your guest access policies to ensure they align with your organization’s collaboration practices.
• Update internal documentation or training materials if they reference invitation email behavior.

Learn more: 

• Add guests to a team in Microsoft Teams | Microsoft Support
• Guest experience in Teams | Microsoft Teams | Microsoft Learn

[Compliance considerations]

[What and Why]

We are updating the licensing SKU and service plan names for Microsoft Clipchamp to improve clarity and consistency across purchasing, billing, and subscription management experiences. This update aligns Clipchamp naming with Microsoft 365 standards, helping administrators and procurement teams more easily identify and manage licenses. There are no changes to Clipchamp functionality, features, or user experience.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected

• Administrators and procurement teams managing Microsoft 365 licensing

Platforms/Services

• Microsoft 365 admin center
• Microsoft commerce and billing systems
• Reporting, exports, and APIs that surface license and service plan names

What will happen

• Clipchamp license (SKU) names and associated service plan names will be updated across:
  • Microsoft 365 admin center
  • Billing and purchase experiences
  • Reporting and license exports



• Existing Clipchamp subscriptions will automatically reflect the new names.
• There are no changes to:
  • Clipchamp features or capabilities
  • User workflows or access
  • Service availability
• The change is applied automatically and enabled by default.

[Action Required / Recommendations]

No action is required.

We recommend that you:

• Review and update any internal documentation, scripts, or processes that reference Clipchamp SKU or service plan names after June 10, 2026.
• Notify helpdesk, licensing, and procurement teams about the updated naming to avoid confusion when reviewing licenses and service plans.

[Compliance considerations]

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

[Introduction] 

Microsoft 365 Copilot licensed users will soon be able to share their desktop screen or mobile camera and ask Copilot questions about what they’re seeing. Copilot analyzes the visual content in real time and provides insights, explanations, or guidance grounded in both the on-screen content and the user’s work data. Vision in Microsoft 365 Copilot will be enabled by default and can be accessed through voice in Copilot. 

This message is associated with Microsoft 365 Roadmap ID 561037.

[When this will happen] 

General Availability (Worldwide): We will begin rolling out vision in late June 2026 and it will be generally available by late July 2026. 

[How this will affect your organization] 

• Vision is on by default, and admins can disable it. 
• Users will start seeing the option to use vision during a voice conversation from the following locations:
  • Microsoft 365 Copilot Chat input box  
  • Copilot key or Win+C shortcut on Windows 
  • Mobile camera sharing button in Microsoft 365 Copilot mobile app 
• To start using vision on desktop screens, the user selects the “Start Screen Share” button.
  • A “Sharing your screen” message appears while sharing is active.
  • To stop sharing, users select the “Stop sharing” button.
  • On mobile, users tap the camera icon to start sharing and tap it again to stop.
• Visual input is user-initiated and session-bound. Copilot processes only the content shared during the active session. 
• Audio and video data is deleted after 48 hours. If feedback is enabled, data is temporarily stored for users to provide feedback to Microsoft. 
• Vision in Microsoft 365 Copilot adheres to Microsoft’s enterprise grade commitments to data security and privacy. 
• No action is required to enable the feature.
•  If you want to disable vision, you can do so in the Microsoft 365 admin center under Copilot > Settings > Copilot Actions > Screen and camera sharing
• You can disable vision in Microsoft 365 Copilot without affecting voice availability.  

[What you need to do to prepare]   

• Review how privacy and security of organizational data is protected when using this feature.
• Communicate the availability and benefits of this feature to your users.  
• Remind users to ensure that their microphone permissions and device settings are compatible with voice activation.

Learn more: 

• Data, Privacy, and Security for Microsoft 365 Copilot | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn
• Enterprise data protection in Microsoft 365 Copilot and Microsoft 365 Copilot Chat | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn
• Providing feedback about Microsoft Copilot with Microsoft 365 apps | Microsoft Support

[Compliance considerations]

[Introduction]

We are introducing updates to the Microsoft 365 Copilot app that deliver a more streamlined, chat-centered experience. These updates simplify the chat and response layout, improve navigation, and introduce new ways for users to organize work—helping them stay focused, maintain context, and move work forward efficiently.

[When this will happen]

• Frontier: Late May 2026 
• Generally available behind opt-in toggle: June 2026 
• Generally available, default on: July 2026 

[How this affects your organization]

Who is affected

• All users accessing the Microsoft 365 Copilot app on the web or desktop
• Applies to Microsoft 365 Copilot (Premium) and Copilot Chat (Basic) tenants

What will happen

Throughout the Copilot app, experiences have a new, cleaner look with simplified headers and text input components. In addition, users will see the following updates:

Streamlined navigation

• The navigation pane has a new pinned section where users can pin frequently used agents, apps, and Copilot experiences (like Notebooks, Microsoft 365 apps, chat conversations, etc.) directly in the navigation pane for easy access. 
• The app launcher moves to the waffle menu in the top right of the expanded navigation pane where users can access apps and experiences like Create, Notebooks, Outlook, Teams, Word, Excel, PowerPoint, and custom apps. Some users in an early test group may have already seen this change roll out a few weeks prior. 
• The agents section in the navigation pane is simplified to a flyout menu, where users can hover over to see their pinned and recently used agents, as well as access agent store and agent builder. Users can also select the agents label to open the agent store directly.
• The new Tasks tab in the navigation pane opens a consolidated view of the user’s long-running Copilot activity, including scheduled chats and agent activity, so they can easily track autonomous Copilot tasks and take action when needed. 
• Users can collapse the Copilot app navigation pane by selecting the icon in the top left corner of the pane (“collapse navigation” text string appears when the user hovers over the icon).

Chat update

• Work and web grounding controls are consolidated into a single “Work IQ” toggle in the upper-left corner of the chat screen. Work IQ is enabled by default and combines enterprise data with web grounding to provide more complete responses. Users can turn off Work IQ to disable enterprise data tools and switch to web-only grounding. When Work IQ is turned off, prompt suggestions and the CIQ menu are limited to web-based suggestions, and the Sources menu is disabled. Agents continue to function as usual.
• The Copilot Chat layout has been simplified with a rich prompting canvas that preserves formatting when pasting content, refreshed prompt suggestions and header text, and a streamlined menu for adding content, agents, and images.
• Copilot Chat response’s structure is clearer for more scannable information, citations, and more relevant suggested actions. 

Agent update

• When a user opens an agent from the agent flyout menu in the navigation pane or from the Agent Store and lands on the agent home screen, they will see details about where the agent came from, including a profile card of the agent maker and tooltips alongside the organization name. The ghost text in the agent chat input includes the agent’s name to clearly show that the interaction is with the agent. 

These updates will roll out to all Microsoft 365 users with access to the Copilot app. 

Default behavior

• When these updates roll out to Frontier users, the new experience will be their default experience. This allows Microsoft to generate sufficient feedback to inform decisions impacting full GA deployment. 
• When these updates roll out to worldwide users in June, the new experience will be available via an opt-in toggle. The experience will be disabled by default. 
• In July, these features will become available by default for all users. The opt-in toggle will be removed at this time. 

Screenshot 1 – Microsoft 365 Copilot app home screen view:

Screenshot 2 – Microsoft 365 Copilot app home screen with expanded navigation view:

Screenshot 3 – Chat response in Copilot app view:

[What you can do to prepare]

No action is required to enable this change.

To prepare for these changes, we recommend that administrators:

• Inform users about the updated Copilot app experience 
• Share updated Microsoft support documentation (https://support.microsoft.com/Microsoft-365-Copilot/what-is-the-microsoft-365-copilot-app) with users when it has been updated with the new experience in June (aligned to when the updates roll out to general audiences). 
• If applicable, update internal guidance and training materials to reflect changes to navigation, chat experience, and where users access key capabilities. 
• If participating in preview programs (e.g., Frontier), validate the experience in your environment and provide feedback to help shape final GA 

Learn more:

• Announcement – Microsoft 365 Blog

[Compliance considerations]

Updated May 28, 2026: We have decided not to move forward with this change. We apologize for any inconvenience.

Note: Hiding inactive channels

Based on Admin feedback, we are updating the behavior for automated hiding of inactive channels to be opt-in (suggestions) only. With this update, Teams will offer users suggestions on channels that are inactive, and the user is prompted to review their inactive channels and hide them only if they choose. The user will also be able to view when they last visited the channel to help them decide if they would like to hide the channel. The settings support this opt-in workflow and there are no changes to the on-demand hiding process.

This feature is enabled for targeted release.

This message is associated with Microsoft 365 Roadmap ID 325780.

[When this will happen:]

The feature is in public preview.

Targeted Release: Available now.

General Availability (Worldwide) and all clouds: We have decided not to move forward with this change.

[How this will affect your organization:]

Before this rollout: Users had to manually manage their relevant channels list by hiding inactive and irrelevant channels.

After this rollout:

Manage preferences for automated suggestions via Teams Settings

If users prefer to manage channels manually, they can opt out of the auto-suggestions process. Simply go to Teams settings, select General, and toggle off “Suggestions for hiding inactive channels.”

Hide inactive channels on demand when needed

Users can manually view which channels are inactive and choose to hide some or all of them whenever you need. This can be done from Settings, under General, by clicking the “Get Suggestions” button. Note that this action can be performed once every 24 hours.

Automated suggestions of inactive channels

With this, Teams will suggest channels that have been inactive for the user. Once the inactive channels are identified, the user is notified with the coach mark message, “Looks like you haven’t visited some channels lately. Hide them to help you focus.”

The user can select Review and Hide to see the details and decide which channels they would like to hide. The user can choose not hide any channels by selecting Not Now

If a user has less than or equal to 25 shown channels, no channels will be suggested for that user. This feature is on by default and all Teams users on the affected platforms will have access to it.

[What you need to do to prepare:]

Admins need to be aware of this feature, but no additional action is needed.