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

Updated September 3, 2025:  the rollout has been postponed for GCC, GCCHigh, and DoD environments to a later date. We apologize for any inconvenience.

In Microsoft Purview | Insider Risk Management (IRM), policy tuning analysis provides admins with a real-time prediction of the number of users in a tenant that could potentially match a given set of policy conditions. After this rollout, policy tuning analysis will support insider risk policies that are scoped for priority content.

This message is associated with Microsoft 365 Roadmap ID 378409.

This message is associated with MC786326 (about the preview for this feature that started in May 2024).

[When this will happen:]

General Availability (Worldwide): We will begin rolling out late June 2025 (previously mid-June) and expect to complete by late August 2025 (previously late July).

General Availability (GCC, GCCHigh, DoD): We will communicate via Message center when we are ready to proceed.

[How this will affect your organization:]

After this rollout, admins can use real-time analytics for policies scoped for priority content to help predict the number of users that could potentially match a given set of policy conditions. This feature enables admins to quickly adjust the selection of indicators and thresholds of activity occurrence so they can efficiently translate their insider risk strategies into pragmatic controls and keep from having too few or too many alerts.

1. In IRM, Navigate to Settings > Insider Risk Management > Analytics, turn on Analytics, and then select Save.

2. Create/edit a policy scoped to all users in the organization.

3. When you get to Content to prioritize in the policy wizard, select the priority content types you want to prioritize:

4. Select the items for each priority content type as applicable.

5. On the scoring page, select Get alerts only for activity that includes priority content:

6. Configure the rest of the policy as applicable and save it.

7. 1-2 days after the policy is saved, edit the policy again and navigate to the indicator thresholds page where insights on user activity containing the scoped priority content for each indicator will be visible under Choose your own thresholds:

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

This change will be available by default for admins to configure. To use this feature, admins will need to enable Analytics in Insider risk management > Settings. After Analytics is enabled and insights are populated, admins will be able to see real-time predictions in policies scoped to all users/groups and scored only for priority content.

Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy.

You can access the Insider Risk Management solution in the Microsoft Purview compliance portal.

Learn more: Configure policy indicators in insider risk management | Microsoft Learn

Updated May 18, 2026: We have updated the timeline for the legacy PDF viewer retirement. Thank you for your patience. 

The Adobe-powered PDF viewer in Microsoft Edge for Business is now available in beta for organizations to test. Organizations can now experience the viewer by default in Edge Beta (starting in version 136) and validate how it works within their PDF workflows. This early testing period helps identify and address any issues before the viewer becomes the default in Edge Stable release in October 2025. We will retire the legacy PDF viewer in September 2026.

This message is associated with Microsoft 365 Roadmap ID 489231.

[When this will happen:]

• The Adobe-powered PDF viewer is now available in beta to test.
• General Availability (Worldwide): We will begin rolling out mid-October 2025 and expect to complete by late October 2025.

[How this will affect your organization:]

Before this rollout, organizations have to manually configure a policy to test the new PDF viewer.

After this rollout:

• No policy configuration is needed. The new PDF viewer is enabled by default in Edge Beta (starting in version 136).
• We recommend organizations proactively validate their workflows with the new viewer before October’s Edge Stable release.
• Organizations that already adopted the new PDF viewer using the NewPDFReaderEnabled policy do not need to take additional action and will continue using the updated viewer with ongoing improvements.

Key enhancements include:

• Performance: Faster document load and smoother scrolling
• Accessibility: Improved support for screen readers and form accessibility
• Compatibility: Enhanced color profile support, more precise text selection, and fonts for Chinese, Japanese, and Korean languages

Exclusive features for organizations:

• View XFA PDFs using IE (Internet Explorer) mode
• Extended support for viewing Microsoft Information Protection (MIP) Protected PDF Files to different sovereignties
• View sensitivity labels for MIP-protected PDFs
• Enhanced digital signature verification in Edge PDF Viewer

In October, the new Adobe-powered PDF viewer will be on by default.

The Adobe-powered PDF viewer in Edge, with the enhanced toolbar at the top of the page:

[What you need to do to prepare:]

• Organizations that have not yet moved to the new PDF viewer should test it in Edge Beta in preparation for the default enablement in October.
• Test all your internal PDF workflows and critical documents in the new PDF viewer.
• Report feedback and issues through the standard Microsoft support channels.
• For organizations ready to fully migrate sooner, the NewPDFReaderEnabledcan be used to enable the new PDF viewer in Edge Stable release today with these settings:
  • True: New PDF viewer enabled
  • False: Legacy viewer retained
  • Default: Current default behavior
  • No action is required if your organization is already using the new PDF viewer through policy configuration.

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

Learn more about the PDF reader change:Microsoft Edge and Adobe partner to improve the PDF experience

Updated May 18, 2026: We have updated the opt-out timeline. Thank you for your patience. 

[Introduction]

Starting in October 2025, Microsoft Edge version 141 will introduce the Adobe-powered PDF viewer as the default experience for enterprise users on Windows. This change enhances performance, accessibility, and compatibility, and introduces exclusive enterprise features. It follows our earlier public announcement and aligns with Roadmap ID 489231 and MC post MC1072406.

General Availability: Migration will occur on a phased rollout. Rollout will begin October 2025 and will complete March 2026. 

Who is affected:

• All enterprise users on Windows using Microsoft Edge.

What will happen:

• The Adobe-powered PDF viewer will replace the legacy viewer as the default experience.
• User interface and controls will remain unchanged.
• The new viewer offers improved performance, accessibility, compatibility, and exclusive enterprise features.

Admins can manage the experience using two policies:

NewPDFReaderEnabled: Controls the default viewer in Edge for Windows. 

NewPDFReaderWebView2List: Controls viewer behavior in WebView2 apps. 

Policy behavior:

No action is required if your organization is ready to adopt the new viewer.

If you wish to manage the experience:

• Enable the new viewer early using the NewPDFReaderEnabled policy.
• Opt-out by disabling the same policy. Opt-out will be supported until September 2026, at which time the policy will be deprecated and any remaining organizations will be moved to the new viewer. 
• Review and update internal documentation if needed.
• Communicate this change to helpdesk or support teams.

Learn more: Microsoft Edge and Adobe partner to improve the PDF experience.

For support, contact your Microsoft CSAM or CSS representative.

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

[Introduction]

To improve collaboration and streamline meeting workflows, Microsoft Teams is introducing the ability to consult and merge Public Switched Telephone Network (PSTN) callers into active meetings—even when those callers are behind auto-attendants or Interactive Voice Response (IVR) systems that require Dual-Tone Multi-Frequency (DTMF) navigation. This enhancement allows users to reach subject matter experts via dial-in and seamlessly bring them into the broader conversation.

This message is associated with Microsoft 365 Roadmap ID 518218.

• Targeted Release: Rolling out early April 2026 (previously early March), expected to complete by mid-April 2026 (previously mid-March).
• General Availability:  Rolling out mid-April 2026 (previously late March), expected to complete by mid-June 2026 (previously late April).

[How this affects your organization:]

• Who is affected: All Microsoft Teams users who initiate or manage meetings with PSTN participants. Administrators overseeing Teams meeting policies and call configurations.
• What will happen:
  • Users can consult with PSTN or Voice over Internet Protocol (VoIP) participants via the Participants panel.
  • A new interface will allow users to access a dialpad to navigate IVR systems and auto-attendants using DTMF tones.
  • Once the external party is reached, users can merge them into the ongoing meeting.
  • No changes to existing administrator policies; feature is enabled by default.

[What you can do to prepare:]

• No administrator action is required for this rollout.
• If your organization uses custom training or helpdesk documentation, consider updating it to reflect this new capability.
• Before rollout, we will update this post with new documentation.

[Compliance considerations:]

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

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

[Introduction]

We’re introducing the Restart Event feature in Microsoft Teams Events to improve resiliency for live events. This feature lets organizers restart a live event that encounters an unrecoverable failure, minimizing disruption and ensuring continuity for Town Halls and other large meetings.  

This message is associated with Microsoft 365 Roadmap ID 523214.  

[When this will happen]

• General Availability (Worldwide): We will begin rolling out in early January 2026 and expect to complete by mid-April 2026 (previously end of March).
• General Availability (GCC and GCCH): We will begin rolling out in late January 2026 and expect to complete by mid-April 2026 (previously end of March).
• General Availability (DoD): We will begin rolling out in early February 2026 and expect to complete by early June 2026 (previously mid-April).

[How this affects your organization]

Who is affected: Organizers and admins managing Microsoft Teams live events.  

What will happen:  

• Organizers will see a new Restart Event button in the Teams UI for live events.  
• The feature is enabled by default; no admin configuration is required.  
• Attendees may experience a brief interruption while the event restarts but can rejoin seamlessly.  
• No impact on existing policies or tenant-level settings.  

[What you can do to prepare]

• Communicate this new capability to event organizers and support teams.  
• Update internal training and documentation for large event management.  
• No policy or tenant-level changes are needed.

[Compliance considerations]

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

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

Introduction

Connectivity changes between cmdlets and Microsoft 365 services like SharePoint and Exchange now require a new parameter for improved security and modern authentication. Starting April 30, 2026, Admins must use Exchange Online PowerShell v3.9.0 or later and include the -EnableSearchOnlySession parameter when running Connect-IPPSession to execute Data Lifecycle Management cmdlets.

When this will happen:

Enforcement begins April 30, 2026.

How this affects your organization:

• Who is affected: Admins using Data Lifecycle Management cmdlets in Security & Compliance PowerShell.
• What will happen:
  • You must use Exchange Online PowerShell v3.9.0 or later.
  • You must include the -EnableSearchOnlySession parameter when running Connect-IPPSession.
  • This applies to the following cmdlets:
    • New-RetentionCompliancePolicy
    • Set-RetentionCompliancePolicy
    • New-RetentionComplianceRule
    • Set-RetentionComplianceRule
    • New-ComplianceTag
    • Set-ComplianceTag
    • Remove-ComplianceTag
    • New-ComplianceRetentionEvent
    • Set- ComplianceRetentionEvent
    • Remove- ComplianceRetentionEvent
    • New-ComplianceRetentionEventType
    • Set-ComplianceRetentionEventType
    • Remove- ComplianceRetentionEventType
  • No impact for users accessing Data Lifecycle Management through the Purview portal.

What you can do to prepare:

• Update scripts and workflows to include the -EnableSearchOnlySession parameter.
• Ensure your organization is using Exchange Online PowerShell version 3.9.0 or later.
• For more information, visit: Learn about Data Lifecycle Management solutions in Microsoft Purview.

Compliance considerations:

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

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

[Introduction]

Microsoft Teams will soon automatically remove hidden metadata (EXIF) from images shared in chats and channels. This helps protect sensitive details such as photo location and device information from being shared without user awareness, improving privacy and security.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web and is associated with Microsoft 365 Roadmap ID 542795.

[When this will happen:]

• Targeted Release: Rollout begins in late January 2026 and completes by early February 2026.
• Worldwide and GCC: Rollout begins in mid-February 2026 and completes by mid-June 2026 (previously mid-April).
• GCC High: Rollout begins in late February 2026 and completes by mid-June 2026 (previously mid-April).
• DoD: Rollout begins in early March 2026 and completes by mid-June 2026 (previously mid-April).

[How this affects your organization:]

• Who is affected: All users sharing images in Microsoft Teams chats and channels.
• What will happen:
  • EXIF metadata (e.g., GPS location, camera model, manufacturer info) will be automatically removed from images shared in Teams conversations.
  • The visible image content remains unchanged.
  • No admin action is required; this feature is enabled by default.
  • If users need to retain EXIF data, they can upload images to OneDrive and share a link via Teams.

[What you can do to prepare:]

• Inform end users, security, and compliance stakeholders that EXIF data will no longer be available in Teams-shared images.
• Update internal documentation or training that references sharing metadata via images.
• Review workflows, diagnostics, or integrations that rely on EXIF data and plan alternatives.

[Compliance considerations:]

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

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

[Introduction]

We are introducing structured document generation with Microsoft Forms in SharePoint. This capability will help organizations generate standardized, compliant documents through simple form-driven experiences. It will reduce manual effort, improve template consistency, and support governance across high-volume document workflows. Creating and configuring structured document forms will require a Microsoft 365 Copilot license.

This message is associated with Microsoft Roadmap ID 545896.

[When this will happen]

Public Preview: We began rolling out opt-in in mid-February 2026 and completed by end of March 2026. Starting June 15, the public preview will be on by default.

General availability (Worldwide): We will begin rolling out July 2026 and expect to complete by end of July 2026.

[How this affects your organization]

Who is affected:

• All Microsoft 365 tenants using SharePoint Online
• Users with a Microsoft 365 Copilot license who will create structured document forms

What will happen:

• Users with a Microsoft 365 Copilot license will be able to create structured document forms linked to approved SharePoint templates.
• Business teams will be able to maintain and enforce template governance while enabling document generation across the organization.
• Users will be able to generate consistent, compliant documents by completing a form.
• Existing SharePoint permissions, governance policies, and information management controls will continue to apply.
• Document generation through published forms will be available based on standard SharePoint permissions.
• The feature will be on by default; no admin action will be required.

Screenshot 1 – Review and refine AI-suggested fields before publishing:

Screenshot 2 – Edit content and apply advanced template customizations, including conditional sections in Word:

[What you can do to prepare]

No admin action is required. You may choose to:

• Inform business stakeholders who manage templates and document workflows.
• Review opportunities to streamline document processes with form-driven generation.
• Update internal documentation or training materials if needed.

Watch the video: Generate documents by filling in the form (18 seconds)

[Compliance considerations]

No compliance considerations identified. Review as appropriate

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

[Introduction]

We’re introducing ad-hoc room reservation directly from the Microsoft Teams Rooms on Windows console. This update enables users to reserve an available room on the spot without relying on a personal device or hallway panel, supporting quick, spontaneous meetings and helping reduce scheduling conflicts. This feature requires a Teams Rooms Pro license. 

This message is associated with Microsoft 365 Roadmap ID 548648.

[When this will happen]

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

[How this will affect your organization]

Who is affected

• Users and admins of Teams Rooms on Windows with Teams Rooms Pro licenses.

What will happen

• After this feature becomes available on room devices, users can reserve an available room directly from the Teams Rooms calendar by choosing Reserve and selecting an end time: 

  

• End times appear in 15-minute increments for up to the end of the day or until the next scheduled meeting, whichever comes sooner:

   

• The feature is enabled by default.
• Admin controls will be available on the Teams Rooms Pro Management portal: Rooms > Settings > Meetings > Allow ad-hoc room reservation.

[What you can do to prepare]

• No action is required before rollout.
• Notify users of the new reservation workflow.
• Update internal training or documentation.
• Use Teams Rooms Pro Management portal or device settings if you want to restrict ad-hoc reservations.

[Compliance considerations]

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

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

[Introduction]

We’re improving how Outlook respects the x‑ms‑reactions: disallow header in Classic Outlook for Windows. This update ensures that when reactions are disallowed, the Reactions button is correctly disabled and any failed reaction attempts are fully reverted. This provides a more consistent and trustworthy user experience across Outlook clients and prevents user confusion.

This message is associated with Roadmap ID 558442.

[When this will happen:]

• Current Channel: This change has rolled out as part of version 2904 (build 19929).
• Monthly Enterprise Channel: This change has rolled out as part of version 2904 (build 19929).
• Semi-Annual Enterprise Channel: This change will be rolled out as part of version 2904 (build 19929).

[How this affects your organization:]

Who is affected:

• Users running Classic Outlook for Windows
• Organizations that disallow email reactions using the x‑ms‑reactions: disallow header

What will happen:

• The Reactions button will appear grayed out when reactions are disallowed.



• Failed reaction attempts will be automatically undone in the UI.
• Users will no longer see misleading reaction states.
• Behavior will be consistent across all Outlook clients.
• The change is enabled by default and respects existing configurations.

[What you can do to prepare:]

No action is required.

You may optionally:

• Inform helpdesk staff about the improved reaction behavior to reduce potential user questions.
• Review internal documentation if you reference reaction controls or messaging headers.
• Continue using the x‑ms‑reactions: disallow header as you do today; existing configurations are fully supported.

Learn more: Disallow reactions in Outlook | Microsoft Learn

[Compliance considerations:]

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

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

[Introduction]

To improve reliability for large-scale live events, Microsoft Teams town halls will soon support a backup Real-Time Messaging Protocol (RTMP) stream. RTMP is a standard live‑streaming protocol used by event organizers to send live video and audio to a streaming service, such as Microsoft Teams. This enhancement helps ensure uninterrupted broadcasts by automatically failing over to a secondary RTMP stream if the primary stream experiences an interruption. This change increases resiliency for high-visibility events without adding complexity for organizers.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. It is associated with Roadmap ID 554932.

[When this will happen:]

General Availability (Worldwide, GCC): Rollout begins late April 2026 and completes by mid-June 2026 (previously late April)

[How this affects your organization:]

Who is affected:

• Organizers and producers hosting Microsoft Teams town halls using RTMP-based production workflows

What will happen:

• Organizers can configure a backup RTMP stream during event setup using Teams Meeting options in Production tools.
• If the primary RTMP stream fails, Teams will automatically fail over to the backup stream with no manual intervention.
• There’s no change to the attendee experience.
• The feature is available by default; no admin configuration is required.

[What you can do to prepare:]

• No action is required.
• Optionally, update internal event-production documentation and notify event producers of this new resiliency option.

Learn more: Use RTMP-In in Microsoft Teams | Microsoft Support (will be updated before rollout)

[Compliance considerations:]

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

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

[Introduction]

We’re updating AI Interpreter in Microsoft Teams to deliver more accurate and consistent real-time interpretation. These improvements enhance recognition of people’s names and common industry terminology, and Interpreter will now use your organization’s Custom Dictionary from the Microsoft 365 admin center to reflect preferred terms across meetings. This update also expands language availability with the addition of Traditional Chinese.

This message is associated with Microsoft 365 Roadmap ID 558434.

[When this will happen]

• Targeted Release: Rolling out in late April 2026 (previously early April) and expected to complete in late April 2026 (previously mid-April).
• General Availability (Worldwide): Rolling out in late April 2026 (previously mid-April) and expected to complete in early June 2026 (previously late April).

[How this affects your organization]

Who is affected

• Organizations using Microsoft Teams multilingual meetings with Interpreter, live captions, or transcripts, and users licensed for Microsoft 365 Copilot

What will happen

• AI Interpreter accuracy will improve for real-time interpretation.
• Recognition of people’s names and industry-specific terminology will be more consistent.
• Interpreter will use your tenant’s Custom Dictionary from the Microsoft 365 admin center to improve translation consistency.
• Traditional Chinese will be added as a supported language: 

  

• This update applies to all currently supported languages:
  • English
  • Simplified Chinese
  • Traditional Chinese
  • French
  • German
  • Italian
  • Japanese
  • Korean
  • Portuguese
  • Spanish
• The AI Interpreter experience requires a Microsoft 365 Copilot license for users.
• Existing admin policies and configurations are unchanged.
• The feature will be enabled by default for eligible, licensed users.

[What you can do to prepare]

No admin action is required before rollout.

To ensure users can take advantage of this update, you may want to:

• Confirm that users who need AI Interpreter are assigned a Microsoft 365 Copilot license.
• Review and maintain Custom Dictionary entries in the Microsoft 365 admin center.
• Update internal documentation or helpdesk materials if needed.
• Communicate this update to Teams meeting organizers and interpreters who rely on multilingual capabilities.

[Compliance considerations]

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

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

[Introduction]

We are introducing separate admin controls for Viva Engage Communities and Storylines in Microsoft Teams. These controls provide more granular management by allowing administrators to independently enable or disable each experience within Teams, while existing controls in the Viva Engage admin center remain unchanged. By default, both Communities and Storylines will be enabled in Teams unless configured otherwise.

[When this will happen:]

• General Availability (Worldwide): Individual controls will be available by May 26, 2026

[How this affects your organization:]

Who is affected:

• All users licensed for Microsoft Teams and Viva Engage
• Administrators managing Teams messaging policies

What will happen:

• Two new independent controls will be available in the Teams admin center:
  • Communities
  • Storylines

Screenshot: Viva Engage Controls in Teams Admin Center:



• Admins can configure these controls through Teams messaging policies.
• Default state:
  • Communities in Teams: On
  • Storylines in Teams: On
• If Communities is turned off in Teams, it is hidden in Teams but remains available in Viva Engage.
• If Storylines is turned off in Teams, it is hidden in Teams but remains available in Viva Engage.
• If Storylines is disabled in Viva Engage, it is disabled in both Viva Engage and Teams.
• If Viva Engage experiences in Teams was previously turned off, Storylines will remain off and Communities will be enabled by default after this update.
• Changes may take up to 24 hours to propagate.

[What you can do to prepare:]

Action required:

• Review and configure your preferred settings before Communities reach General Availability in June. If no action is taken, Communities and Storylines will remain enabled by default in Teams.

Recommended steps:

• Review current Teams messaging policies
• Decide whether Communities and Storylines should be enabled or disabled
• Update settings as needed

To disable Communities in Teams:

1. Go to Teams admin center
2. Select Settings & policies
3. Choose Global (Org-wide default) or custom policy
4. Open Messaging settings
5. Set Communities to Off
6. Save changes

To disable Storylines in Teams:

1. Go to Teams admin center
2. Select Settings & policies
3. Choose Global (Org-wide default) or custom policy
4. Open Messaging settings
5. Set Storylines to Off
6. Save changes

Learn more: Manage Viva Engage experiences in Microsoft Teams – Microsoft Teams | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

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

[Introduction]

To support more effective in-person collaboration, Microsoft Teams is expanding AI-powered meeting notes with the Facilitator agent to Teams Rooms on Android. This enhancement allows teams meeting in a physical room to capture real-time notes, decisions, and action items—without requiring a scheduled or hybrid meeting. The experience is designed to ensure notes are securely stored in your tenant while no data remains on the room device after the meeting ends.

This message is associated with Microsoft 365 Roadmap ID 56700.

[When this will happen]

General Availability

• Worldwide and GCC: We will begin rolling out in early July 2026 (previously late June) and expect to complete by mid-July 2026.
• GCC-H: We will begin rolling out in mid-July 2026 and expect to complete by mid-August 2026.

[How this affects your organization]

Who is affected

• Organizations using Teams Rooms on Android
• Rooms licensed with Teams Rooms Pro

What will happen

• During an in-person meeting, users can start AI-powered notes by selecting the Take notes button on the Teams Rooms console.
• Notes appear on the front-of-room display or touch board during the meeting: 

  

• Notes are stored in tenant-owned SharePoint embedded storage.
• Access to notes requires adding your work account using the Access notes button on the Teams Rooms console.

  

• After the meeting, notes can be viewed and edited by participants with access via the meeting recap in the meeting chat on the Teams desktop client.

• If no participant was added during the note-taking session via Access notes, notes are deleted automatically.

Default state:

• The feature is available automatically once licensing and prerequisite configurations are met.
• No additional admin enablement is required beyond existing settings.

[What you can do to prepare]

No immediate action is required if your organization already meets the prerequisites.

To prepare:

• Confirm Teams Rooms Pro licenses are assigned to applicable rooms.
• Ensure Facilitator is enabled in your tenant.

• Verify Loop components are enabled:
  • IsLoopEnabled
  • IsCollabMeetingNotesFluidEnabled
• Ensure meeting transcription is enabled in Teams meeting policies.
• Consider notifying helpdesk staff and users about:
  • How to start notes in an in-person meeting
  • Where notes are stored and accessed after the meeting

Learn more:

• Allow Facilitator in the Teams admin center – Set up Facilitator in Microsoft Teams | Microsoft Teams | Microsoft Learn
• Meetings – Admins- Manage transcription and captions for Teams meetings | Microsoft Teams | Microsoft Learn
• Settings management for Loop functionality in Teams – Admin policies for Loop components and Loop workspaces | Microsoft 365 | Microsoft Learn

[Compliance considerations]

Updated May 18, 2026: We have paused rollout of this feature at this time. We will communicate via Message center when we are ready to proceed. Thank you for your patience. 

[Introduction]

We’re making it easier for users to manage tasks where they already work. The Microsoft Planner experience is now available directly in Outlook (web and the new Outlook for Windows) and in the Microsoft 365 Copilot app. This change reduces context switching by allowing users to view and manage tasks and plans alongside email, calendar, and Copilot experiences.

This update is based on customer feedback requesting tighter integration between task management and daily productivity workflows.

This message is associated with Microsoft 365 Roadmap ID 513278.

[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 Microsoft 365 tenants
• Users who access Outlook on the web, the new Outlook for Windows, or the Microsoft 365 Copilot app

What will happen

• The Planner experience will be available directly within Outlook (web and new Outlook for Windows).
• Users can view and manage:
  • Personal tasks
  • Shared plans
• Tasks and plans can be accessed alongside email and calendar workflows.
• Where licensed and enabled, users can access Planner through Microsoft 365 Copilot experiences.
• This feature is enabled by default.
• Existing Microsoft 365 permissions, Planner settings, and Copilot policies are respected.
•  A Microsoft 365 Copilot (Premium) license is not required to use the Planner app in Outlook.
• There is no change to where Planner data is stored.

[What you can do to prepare]

No admin action is required.

You may consider:

• Informing users that Planner is now accessible within Outlook and the Microsoft 365 Copilot app.
• Updating internal documentation or helpdesk guidance to reflect this new access point.
• Encouraging users to explore Planner for managing tasks and plans.
• Monitoring adoption and feedback using existing usage and feedback channels.

Learn more: Microsoft Planner | Microsoft Support

[Compliance considerations]

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

• The security score and its qualitative rating will no longer appear on the Security > Overview page.
• Recommendations generated from the security score calculation will no longer be displayed.
• The Security > Overview page will remain available but will no longer include the score or recommendation sections.
• All other Security Hub capabilities, including Data Protection & Privacy, Identity & Access Management, Compliance, and proactive policy management, are not affected and continue to be available.

• Microsoft Secure Score in the Microsoft 365 Defender portal, which provides a comprehensive security posture assessment across your Microsoft 365 environment.
• Environment-level security settings in the Power Platform admin center, where you can continue to configure and monitor individual security features such as IP firewall, tenant isolation, data policies, and environment security groups.
• Managed Environment governance controls, which provide policy enforcement including solution checkers, sharing limits, and access controls.

• Security overview – Power Platform admin center
• Important changes (deprecations) coming in Power Platform
• Managed Environments overview

[Introduction]

To help organizations access more up-to-date Microsoft 365 Copilot insights, we are introducing a new Power BI report and query named Microsoft 365 Copilot latest usage snapshot for analyst users in Viva Insights Advanced Insights.

This report provides Copilot usage data updated daily and includes three months of activity, typically available within two to three days prior to the current date. This capability helps analysts monitor recent adoption trends and better understand short term usage patterns across their organization.

This message is associated with Microsoft 365 Roadmap ID 561325.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Viva Insights users with the Insights Analyst role
• Users who work in the Viva Insights web app and use Power BI for advanced analysis

What will happen

• A new Power BI report and query named Microsoft 365 Copilot latest usage snapshot will be available to eligible analysts.
• Daily Copilot usage data will be available with up to three months of activity history.
• Activity data typically reflects usage up to two to three days before the current date, actual timing may vary.
• The Adoption overview page provides an organization-wide view of Copilot usage, including:
  • adoption trends
  • group-level adoption
  • usage by app and feature

    

• Data can be filtered and segmented using organizational attributes and time ranges to identify patterns and areas of strong or low adoption.
• Custom analysis is supported through the included query based on daily data, with export options through CSV download, the Power BI connector, or Microsoft Fabric.
• Microsoft 365 Copilot licenses and Viva Insights licenses must be assigned to users included in the analysis.
• Availability requires at least 50 Microsoft 365 Copilot licenses in the organization.
• The report is available by default to eligible users, and no additional admin configuration is required.
• Existing Copilot Analytics reports and queries are not changed.

The following metrics are not supported in this report or query at this time:

• Meeting hours recapped by Copilot
• Meeting hours summarized by Copilot in Teams
• Meetings recapped by Copilot
• Total meeting hours summarized or recapped by Copilot
• Total meetings summarized or recapped by Copilot
• Copilot assisted hours or dollar value
• All Copilot for Sales metrics 
• Any metrics related to power users

[What you can do to prepare]

No admin action is required if your organization already meets the prerequisites.

You can prepare by taking the following steps:

• Confirm that appropriate users are assigned the Insights Analyst role in Viva Insights.
• Ensure users have the latest version of Power BI Desktop installed. If users have an older version installed, they should uninstall it and install the latest version before using the report.
  • Getting started with Power BI
• Verify that users included in the analysis have the required licenses assigned.
• Communicate this new capability to analyst users in your organization so they know what to expect.

Learn more: 

• Advanced analysis introduction | Viva Insights | Microsoft Viva | Microsoft Learn
• Getting started with Power BI | Microsoft
• Export query data to Power BI | Viva Insights | Microsoft Viva | Microsoft Learn
• Export query data to Microsoft Fabric | Viva Insights | Microsoft Viva | Microsoft Learn
• Power BI report templates | Viva Insights | Microsoft Viva | Microsoft Learn

[Compliance considerations]

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

• Database storage is lower by the amount previously attributed to this content.
• File storage is proportionally higher.
• Total tenant storage is unchanged. Content moved tiers; it did not grow.

• If you were near your database limit, you likely have more headroom.
• If you were near your file limit, confirm you have sufficient file capacity; additional capacity is available via add-on.

• Dataverse capacity-based storage overview
• Dataverse capacity-based storage details
• Add more Microsoft Dataverse capacity to your tenant
• Power Platform Licensing Guide

• Notification type control: CSRs can configure secondary device sound settings at the notification type level, including incoming conversation alerts and new message alerts.
• Channel-specific settings: Settings can be applied at the individual digital messaging channel level, giving each representative control over their audio notification experience.
• User-level personalization: Each CSR manages their own secondary device preferences with no impact on other representatives or existing channel configurations.

[Introduction]

We are retiring the ability to create classic style agents from the Microsoft Copilot Studio app in Microsoft Teams.

Classic agent creation is now available in the Microsoft Copilot Studio web app to provide a more consistent and scalable authoring experience. Going forward, the web app will be the primary location for creating and managing these agents.

[When this will happen]

• Web app experience available: Beginning early April 2026 (already available)
• Retirement effective date: June 30, 2026

[How this affects your organization]

Who is affected

• Admins and users creating classic style agents using Microsoft Copilot Studio
• Organizations with Microsoft 365 enterprise licenses (E1, E3, E5, F1) that include the Power Virtual Agents for Office 365 entitlement
• Users of the Microsoft Copilot Studio app within Microsoft Teams

What will happen

• Previously, classic style agents could only be created within the Microsoft Copilot Studio app in Microsoft Teams.
• Users create and manage classic style agents in the Copilot Studio web app.
• Starting June 30, 2026, users will no longer be able to create classic style agents within the Microsoft Teams app.
• Users attempting to create agents in Teams will be automatically redirected to the Copilot Studio web experience via a link in the Teams app.
• Existing agents will continue to function with no interruption.
• This change is on by default and cannot be disabled or opted out after the retirement date.
• There are no changes to compliance, security, or data handling.
• Agents will continue to:
  • Be created in Dataverse for Teams environments
  • Use access permissions managed by Microsoft Teams
• Agents created under this entitlement will not include generative AI capabilities.

[What you can do to prepare]

No immediate action is required. However, we recommend that you:

• Communicate this change to users who create or manage classic style agents in Teams.
• Transition users to the Microsoft Copilot Studio web app before June 30, 2026.
• Update internal documentation and training materials to reflect the new agent creation experience.
• Review any governance policies or processes that reference agent creation in the Teams app.
• If needed, manage user access by updating license assignments for the Power Virtual Agents for Office 365 app.
• If users report that they can no longer create agents in Teams, direct them to the Copilot Studio web app.

[Compliance considerations]

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

[Introduction]

We are adding Heading 1 (H1) as a selectable heading level in SharePoint Pages web part title areas to support improved semantic structure and accessibility. This update helps authors create pages that follow accessibility best practices and consistent document structure.

[When this will happen:]

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

[How this affects your organization:]

Who is affected: All users who create or edit pages in SharePoint Online.

What will happen:

• Authors can select H1 from the heading level options in supported web part title areas.

Screenshot: Style selector including Heading 1:



• Selecting H1 is optional and must be explicitly chosen.
• Existing pages are not changed.
• All existing heading level options (H2–H6) remain unchanged in behavior and availability.
• The page banner continues to default to H1.
• Custom fonts are preserved regardless of heading level.
• The feature is enabled by default.

[What you can do to prepare:]

• No admin action is required.
• Optionally notify SharePoint page authors about the new H1 option.
• Update internal authoring or accessibility guidance if applicable.
• Prepare help desk staff for questions about heading levels.

[Compliance considerations:]

Authors can choose whether or not to select H1 when editing a web part title.

[Introduction]

We’re updating how agents in SharePoint work to provide a simpler experience for agents selected on a site.

As a refresher, Get started with agents in SharePoint – Microsoft Support, there are two types of agents in SharePoint:

• Ready-made agent – Every SharePoint site comes with a “ready-made agent”, automatically scoped to the content on that site. These agents, scoped to the SharePoint site, require no building from site admins or site owners. 
• Custom-built agent – With site editing permissions, you can create custom agents with a specific content scope, identity, and behavior.

With this update, we’re introducing a new Site AI settings to give site owners more control over which agents are highlighted on their sites. Approved agents will no longer appear in the Agent Picker, so these agents should be placed directly on the site page for better discoverability.

[When this will happen]

General Availability (Worldwide): We began rolling out in mid-November 2024 and expect rollout to complete by early June 2026.

[How this affects your organization]

Who is affected

• All Microsoft 365 tenants using SharePoint Online
• Site owners and content authors managing how custom agents are discovered on their site

What will happen

• Site owners will manage the site’s “Default” agent through the main agent setting in the new Site AI settings panel in SharePoint site settings.
• For existing sites, the current “Default” agent will automatically become the site’s main agent.
• For new sites, the main agent will be the ready-made agent
• Users no longer access approved agents through the agent picker and overflow menu in the chat pane. All approved agents remain in the Site Assets\Copilots\Approved folder.
• To help users discover agents, site owners and builders should surface agents directly on pages using supported web parts or shared agent links.

This feature is on by default and does not require tenant-level configuration changes.

[What you can do to prepare]

No immediate admin action is required. We recommend the following preparation steps:

• Ask site owners and builders to review the approved agents on their sites in the Site Assets\Copilots\Approved folder.
• Encourage site owners to add or update agent links on pages using supported web parts, such as: Agent Link web part, Editorial Card web part, and adding shared .agent file links in Text web part
• Inform users that agents they recently used can be found in:
• • Build “Owned by me” section by choosing the Agents filter,
  • OneDrive web Home > Recent view (filterable by agent), or
  • Microsoft 365 Copilot agents list

Learn more:

• Use the Agent Link web part | Microsoft Support
• Use the Editorial Card web part | Microsoft Support
• Add text, tables, and images to your page with the Text web part | Microsoft Support 

[Compliance considerations] 

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

Introduction

We are introducing a new organization-level setting that allows admins to migrate Outlook on the web (OWA) from Exchange-based Data Loss Prevention (DLP) policy evaluation to Data Classification Services (DCS)-based DLP policy evaluation. This change brings OWA in line with the new Outlook experience, enabling enhanced capabilities such as the new oversharing policy tips experience and “Wait to send.” This update helps provide a more consistent, modern, and scalable DLP experience across Outlook clients.

When this will happen:

• General Availability (Worldwide): Rollout will begin mid-May 2026 and complete by late May 2026.
• General Availability (GCC): Rollout will begin mid-May 2026 and complete by mid-June 2026.

How this affects your organization:

Who is affected:

• Admins managing Exchange Online and Microsoft Purview DLP policies
• Organizations using DLP policies in Outlook on the web

What will happen:

• A new organization-level setting (DlpViaDcsEnabled) will be available to control DLP evaluation mode in OWA.
• By default, the setting is False, meaning Exchange-based DLP remains in use.
• Admins can manually enable DCS-based DLP evaluation for OWA using PowerShell.
• Once enabled, OWA will use DCS-based DLP policy evaluation instead of Exchange-based evaluation.
• Users may experience enhanced DLP features, including:
  • Improved oversharing policy tips
  • “Wait to send” functionality
  • Alignment with new Outlook DLP behavior
• Some legacy Exchange-based DLP predicates will no longer be supported after migration. Refer to Data loss prevention policy tip reference for Outlook for Microsoft 365 | Microsoft Learn for details about supported features.

What you can do to prepare:

• If you plan to continue using Exchange-based DLP evaluation, no action is required.
• If you plan to migrate to DCS-based DLP evaluation by enabling the DlpViaDcsEnabled setting:
• Important: Review existing DLP policies before enabling this setting. Some Exchange-based predicates are not supported with DCS-based DLP and policies using them may no longer work as expected after migration.
• Test DCS-based DLP evaluation in a controlled environment
• Enable the setting using Exchange Online PowerShell:

Get-OrganizationConfig | Select DlpViaDcsEnabled
Set-OrganizationConfig -DlpViaDcsEnabled $true

• Communicate changes to compliance teams.
• Update internal documentation.

Learn more: Set-OrganizationConfig (ExchangePowerShell) | Microsoft Learn

Compliance considerations: