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

Updated May 27, 2026: We have updated the timeline. This feature will now be included as part of another update referenced in MC796790. Administrators will gain the ability to manage Microsoft 365 certified SaaS applications through org-wide settings for third-party apps. No changes will be applied to tenant-wide settings unless initiated by an administrator. Thank you for your patience.

This feature will empower administrators to manage the availability of trusted Microsoft Teams apps based on rules, for enhanced security. Admins will be able to manage Microsoft 365 certified apps in the Teams admin center through a new control in Org-wide settings. You can further customize the availability of these apps based on permissions accessed and publisher names. The system automatically checks the Microsoft 365 certified apps that meet all the conditions you specify and makes those apps available.  

This message is associated with Microsoft 365 Roadmap ID 485712.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out mid-April 2026 (previously early April) and expect to complete by end of July 2026 (previously late April).

[How this will affect your organization:]

Before this rollout, you cannot manage at bulk the availability of Microsoft 365 certified apps. They are only controlled by third-party app tenant settings.

After this rollout, you can manage Microsoft 365 certified apps availability from org-wide settings in the Teams admin center at Manage apps > Actions > Org-wide app settings > Third-party apps. 

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before or after 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. This new control will be disabled by default.

Learn more: Manage org-wide app settings in Manage your apps in the Microsoft Teams admin center – Microsoft Teams | Microsoft Learn (will be updated before rollout)

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

[Introduction]

As part of our ongoing protection investments in Microsoft Teams, we will continue expanding the ways users can report suspicious or incorrect activity. Users can already report security concerns and incorrect detections in chats and channels (MC1037768, MC1147984), and more recently in calls (MC1223828). These user‑submitted reports help identify potential malicious activity and strengthen your organization’s security posture.

Building on this foundation, we will introduce new capabilities that allow Teams administrators to review and export user‑reported security submissions directly in the Teams admin center. A new Protection reports section will be added under Analytics and reports, giving admins unified visibility into user‑reported calls, chats, and channels.

This message relates to Microsoft 365 Roadmap ID 536571.

[When this will happen]

Phase 1 – User‑reported call data

• Targeted Release: Rollout will begin in mid-April 2026 (previously mid‑March) and complete in late April 2026 (previously late March).
• General Availability (Worldwide): Rollout will begin in late April 2026 (previously mid‑April) and complete in mid-June 2026 (previously early May).

Phase 2 – User‑reported chats and channels

• This phase will add message‑level reporting for security concerns and incorrect detections.
• The timeline will be communicated in a future update to this Message center post.

[How this affects your organization]

Who is affected: Teams administrators who have access to Analytics and reports in the Teams admin center.

What will happen:

• A new Protection reports section will appear under Teams admin center > Analytics & reports:

  

• Admins will be able to view and export data about user‑submitted security reports for calls (Phase 1) and later chats and channels (Phase 2).
• Reported interactions will begin populating once users submit reports.
• Admins will be able to review reported calls or messages and take appropriate action.
• Admins will be able to view 1‑day, 7‑day, and 30‑day reporting windows.
• This feature will require that user reporting settings be enabled in the Teams admin center.

[What you can do to prepare]

To ensure reporting data is available when rollout begins, verify that end‑user reporting features are enabled:

• Enable Report a call: Teams admin center > Calling settings
• Enable Report a security concern and Report incorrect detection: Teams admin center > Messaging settings
• Once enabled and users begin submitting reports, access data at: Teams admin center > Analytics & reports > Protection reports > User‑reported security submission
• Update internal documentation if your helpdesk relies on reporting workflows.
• If you maintain training or onboarding materials about Teams security practices, consider adding guidance on how users can report suspicious interactions.

[Compliance considerations]

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

[Introduction]

We’re enhancing AI analysis in Data Security Investigations (DSI) to help analysts evaluate risky content more efficiently. These updates streamline the workflow by automatically preparing items for AI analysis as they’re added to an investigation and by introducing a new standard categorization option. Standard categorization can reduce time and cost, while advanced categorization—including AI‑generated topics—remains available.

This message is associated with Microsoft 365 Roadmap ID 557556.

[When this will happen]

• Public Preview: Rolling out mid‑March 2026 through mid‑April 2026.
• General Availability (Worldwide): Rolling out mid‑April 2026 through mid-June 2026 (previously mid‑May).

[How this will affect your organization]

Who is affected

• Microsoft Purview administrators and analysts using Data Security Investigations.
• All Microsoft 365 tenants with access to DSI capabilities.

What will happen

• Items added to an investigation will be automatically prepared for AI analysis, reducing manual steps.
• A new standard categorization option will be available.
• Advanced categorization (including AI‑generated topics) remains available.
• No changes to existing admin settings—feature is enabled by default as part of the DSI workflow.
• Users may notice:
  • Faster categorization and analysis readiness.
  • An updated categorization selection interface.

Screenshot – Data Security Investigations standard vs. advanced categorization:

[What you can do to prepare]

No admin action is required before rollout.

To prepare:

• Inform analysts and relevant security operations staff about the new categorization options.
• Update internal documentation if you describe DSI workflows or categorization processes.

Learn:

• Learn about Data Security Investigations | Microsoft Purview | Microsoft Learn
• Use AI analysis in Data Security Investigations | Microsoft Purview | Microsoft Learn

[Compliance considerations]

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

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

[Introduction]

The new Outlook for Windows now allows users to store S/MIME encryption certificates directly within Contacts. This capability enables users to save recipients’ public certificates and use them to send S/MIME encrypted emails, improving secure communication and continuity when transitioning from classic Outlook for Windows (Win32). Certificates previously stored in Contacts in classic Outlook will automatically be available in new Outlook.

This message is associated with Microsoft 365 Roadmap ID 518288.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Users of new Outlook for Windows
• Organizations that use S/MIME encryption

What will happen:

• Users can store recipients’ S/MIME public certificates directly in Contacts.

Screenshot: To add a S/MIME certificate, go to Your contacts > Certificates > Add certificate:



• Stored certificates can be used to encrypt outgoing email to those recipients.
• Certificates saved in Contacts in classic Outlook (Win32) will automatically carry over.
• Feature is available by default; no admin configuration required.
• No impact to users who are not using new Outlook for Windows.

[What you can do to prepare:]

• No admin action is required to enable this feature.
• If your organization uses S/MIME:
  • Instruct users to add or import S/MIME public certificates into Contacts.
  • Communicate how to select S/MIME encryption when composing emails. Learn more: Send S/MIME or Microsoft Purview encrypted emails in Outlook | Microsoft Support.
• Update internal documentation for users transitioning from classic Outlook.
• Inform helpdesk teams of this improved certificate handling experience.

[Compliance considerations:]

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

[Introduction]

To help organizations deliver more polished and branded town hall events, Microsoft Teams is introducing the ability for organizers and presenters to upload custom background images in the Manage what attendees see experience. This enhancement allows teams to replace default backgrounds with branded visuals—such as company logos or event-specific designs—so presenters and shared content appear consistently on brand for attendees. This capability is available with a Teams Premium license. This update applies to Teams for Windows desktop and Mac desktop.

This message is associated with Microsoft 365 Roadmap ID 561493.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Organizers and presenters of Teams town hall events
• Users assigned a Teams Premium license
• Tenants using Manage what attendees see in town halls

What will happen

• Organizers and presenters can upload custom background images directly within the Manage what attendees see experience.
• Uploaded backgrounds appear behind presenters and shared content in supported town hall layouts.
• JPEG and PNG image formats are supported, with recommended resolution guidance shown during upload.
• Custom backgrounds appear alongside existing default background options in the background picker.
• The feature is enabled by default for eligible users and applies only to town hall events where Manage what attendees see is enabled.
• There is no change to standard Teams meetings or webinars.

[What you can do to prepare]

• No admin action is required before rollout.
• Consider notifying users who organize or present town halls about this new capability.
• Prepare branded background images that align with your organization’s visual identity guidelines.
• Update internal documentation or event playbooks if you provide guidance on hosting town halls.
• Optionally, run a test town hall event to familiarize presenters with the upload flow and attendee experience.

Learn more: Customize the event screen – Manage what attendees see in Microsoft Teams | Microsoft Support

[Compliance considerations]

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

[Introduction]

We’re introducing the Visualize this slide skill in Copilot in PowerPoint for Windows desktop. In Copilot, a skill is a user‑initiated action that performs a specific task on existing content. This new capability helps users quickly transform both simple text into a visually stunning image and text-heavy slides into polished, professional visuals. 

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

[When this will happen:]

General Availability (Worldwide): Rollout begins in mid-May 2026 and completes by mid-May 2026.

[How this affects your organization:]

Who is affected:

• Users with access to Copilot in PowerPoint for the web

What will happen:

• A new Visualize this slide skill option appears in Copilot in PowerPoint for the web.

Screenshot: Copilot in PowerPoint with the Visualize this slide skill selected:



• Text-based slides can be transformed into visually rich layouts.
• The feature is enabled by default for eligible users.
• Existing Copilot and compliance policies are respected.

[What you can do to prepare:]

• No admin action is required.
• Consider informing users about this new Copilot capability.
• Update internal documentation if needed.
• IT admins cannot control the availability of individual skills. However, skills that depend on the Anthropic model adhere to existing admin configurations—if the Anthropic model is disabled for a tenant by the IT admins, those associated skills will not be available to users in that tenant.

Learn more: Edit with Copilot in PowerPoint – Microsoft Support (will be updated soon)

[Compliance considerations:]

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

[Introduction]

We’re introducing the Visualize this slide skill in Copilot in PowerPoint for Mac. In Copilot, a skill is a user‑initiated action that performs a specific task on existing content. This new capability helps users quickly transform both simple text into a visually stunning image and text-heavy slides into polished, professional visuals.

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

[When this will happen:]

General Availability (Worldwide): Rollout begins in mid-May 2026 and completes by mid-May 2026.

[How this affects your organization:]

Who is affected:

• Users with access to Copilot in PowerPoint on Mac desktop

What will happen:

• A new Visualize this slide skill option appears in Copilot in PowerPoint.

Screenshot: Copilot in PowerPoint with the Visualize this slide skill selected:



• Text-based slides can be transformed into visually rich layouts.
• The feature is enabled by default for eligible users.
• Existing Copilot and compliance policies are respected.

[What you can do to prepare:]

• No admin action is required.
• Consider informing users about this new Copilot capability.
• Update internal documentation if needed.
• IT admins cannot control the availability of individual skills. However, skills that depend on the Anthropic model adhere to existing admin configurations—if the Anthropic model is disabled for a tenant by the IT admins, those associated skills will not be available to users in that tenant.

Learn more: Edit with Copilot in PowerPoint – Microsoft Support (will be updated soon)

[Compliance considerations:]

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

[Introduction]

We’re introducing the Visualize this slide skill in Copilot in PowerPoint for the web. In Copilot, a skill is a user‑initiated action that performs a specific task on existing content. This new capability helps users quickly transform both simple text into a visually stunning image and text-heavy slides into polished, professional visuals. 

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

[When this will happen:]

General Availability (Worldwide): Rollout begins in mid-May 2026 and completes by mid-May 2026.

[How this affects your organization:]

Who is affected:

• Users with access to Copilot in PowerPoint for the web

What will happen:

• A new Visualize this slide skill option appears in Copilot in PowerPoint for the web.

Screenshot: Copilot in PowerPoint with the Visualize this slide skill selected:



• Text-based slides can be transformed into visually rich layouts.
• The feature is enabled by default for eligible users.
• Existing Copilot and compliance policies are respected.

[What you can do to prepare:]

• No admin action is required.
• Consider informing users about this new Copilot capability.
• Update internal documentation if needed.
• IT admins cannot control the availability of individual skills. However, skills that depend on the Anthropic model adhere to existing admin configurations—if the Anthropic model is disabled for a tenant by the IT admins, those associated skills will not be available to users in that tenant.

Learn more: Edit with Copilot in PowerPoint – Microsoft Support (will be updated soon)

[Compliance considerations:]

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

[Introduction]

The Review this presentation skill is rolling out as part of Copilot in PowerPoint for Windows desktop. In Copilot, a “skill” is a user‑initiated action that performs a specific task on existing content. This capability reviews existing slides and provides detailed recommendations to improve structure, clarity, and storytelling, helping users refine presentations more efficiently.

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

[When this will happen:]

General Availability (Worldwide): Available now

[How this affects your organization:]

Who is affected:

Users with access to PowerPoint Copilot on Windows desktop.

What will happen:

• The Review this presentation option becomes available within PowerPoint Copilot.

Screenshot: Copilot in PowerPoint with the Review this presentation skill selected:

• Copilot will analyze the current presentation and generate suggestions to improve narrative flow, organization, and slide clarity.
• Suggestions are provided for review only; no changes are applied automatically.
• The feature is available by default for eligible users and respects existing Copilot access controls.

[What you can do to prepare:]

• No admin configuration is required.
• Optionally, you might notify users with access to PowerPoint Copilot about the new Review this presentation option.
• IT admins cannot control the availability of individual skills. However, skills that depend on the Anthropic model adhere to existing admin configurations—if the Anthropic model is disabled for a tenant by the IT admins, those associated skills will not be available to users in that tenant.

Learn more: Edit with Copilot in PowerPoint – Microsoft Support (will be updated soon)

[Compliance considerations:]

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

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

[Introduction]

The Review this presentation skill is rolling out as part of Copilot in PowerPoint for Mac. In Copilot, a “skill” is a user‑initiated action that performs a specific task on existing content. This capability reviews existing slides and provides detailed recommendations to improve structure, clarity, and storytelling, helping users refine presentations more efficiently.

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

[When this will happen:]

General Availability (Worldwide): Available now

[How this affects your organization:]

Who is affected:

Users with access to PowerPoint Copilot on Mac desktop.

What will happen:

• The Review this presentation option becomes available within PowerPoint Copilot.

Screenshot: Copilot in PowerPoint with the Review this presentation skill selected:

• Copilot will analyze the current presentation and generate suggestions to improve narrative flow, organization, and slide clarity.
• Suggestions are provided for review only; no changes are applied automatically.
• The feature is available by default for eligible users and respects existing Copilot access controls.

[What you can do to prepare:]

• No admin configuration is required.
• Optionally, you might notify users with access to PowerPoint Copilot about the new Review this presentation option.
• IT admins cannot control the availability of individual skills. However, skills that depend on the Anthropic model adhere to existing admin configurations—if the Anthropic model is disabled for a tenant by the IT admins, those associated skills will not be available to users in that tenant.

Learn more: Edit with Copilot in PowerPoint – Microsoft Support (will be updated soon)

[Compliance considerations:]

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

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

[Introduction]

The Review this presentation skill is rolling out as part of Copilot in PowerPoint for the web. In Copilot, a “skill” is a user‑initiated action that performs a specific task on existing content. This capability reviews existing slides and provides detailed recommendations to improve structure, clarity, and storytelling, helping users refine presentations more efficiently.

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

[When this will happen:]

General Availability (Worldwide): Available now

[How this affects your organization:]

Who is affected:

Users with access to PowerPoint Copilot on the web.

What will happen:

• The Review this presentation option becomes available within PowerPoint Copilot.

Screenshot: Copilot in PowerPoint with the Review this presentation skill selected:

• Copilot will analyze the current presentation and generate suggestions to improve narrative flow, organization, and slide clarity.
• Suggestions are provided for review only; no changes are applied automatically.
• The feature is available by default for eligible users and respects existing Copilot access controls.

[What you can do to prepare:]

• No admin configuration is required.
• Optionally, you might notify users with access to PowerPoint Copilot about the new Review this presentation option.
• IT admins cannot control the availability of individual skills. However, skills that depend on the Anthropic model adhere to existing admin configurations—if the Anthropic model is disabled for a tenant by the IT admins, those associated skills will not be available to users in that tenant.

Learn more: Edit with Copilot in PowerPoint – Microsoft Support (will be updated soon)

[Compliance considerations:]

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

Updated May 27, 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-July 2026 (previously early June) and expect to complete by late July 2026 (previously early June).
• General Availability (Worldwide): We will begin rolling out in early August 2026 (previously mid-June) and expect to complete by late August 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]

• The top apps by user activity
• The top flows by run volume
• The top agents by session count

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

[Introduction]

New Outlook for Windows now supports Lightweight Directory Access Protocol (LDAP) directories for S/MIME certificate lookup. This enables tenants to configure LDAP directories for their organization as well as enabling users to configure LDAP directories themselves. Once configured, users can find recipients’ public encryption certificates from the directories when sending encrypted email, improving secure collaboration with external partners. This is especially valuable for tenants who collaborate with external partners and rely on public/partner LDAP directories to store public S/MIME certificates of users. 

This message is associated with Microsoft 365 Roadmap ID 518287.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

•  Organizations that use S/MIME encryption with external recipients whose public certificates are hosted in third-party LDAP directories 
•  Admins managing Exchange Online

What will happen:

• Admins can configure LDAP directories using Exchange Online PowerShell.
• Users can add LDAP directories in Settings > Mail > S/MIME in new Outlook.
• When composing an S/MIME encrypted email, users can select recipients from the LDAP directory via the To field. This will directly enable Outlook to retrieve the certificate from the selected LDAP directory. If users add a recipient directly to the ‘To list’, Outlook will scan all available certificate sources, including the configured LDAP directories.
• LDAP endpoints must not require authentication, as authentication is not currently supported.

Screenshot: “Add LDAP directory” option in Settings > Mail > S/MIME and LDAP recipient picker in the To field during message composition:



• Feature is enabled by default once available.
• No impact to:
  • Classic Outlook for Windows users
  • Organizations not using LDAP for S/MIME certificate discovery

[What you can do to prepare:]

• No action is required to enable this feature
• If your organization uses LDAP for S/MIME certificates:
  • Identify LDAP directory endpoints used by your organization
  • Run the Add-LdapDirectory cmdlet to register a new directory:

  Add-LdapDirectory -Organization "contoso.com" -Id "corp-ldap" -Host "ldap.corp.com" -Port 636 -UseSsl

  • Configure directories using Exchange Online PowerShell (Add-LdapDirectory).
  • Ensure LDAP endpoints do not require authentication.
  • Communicate guidance to users transitioning to new Outlook: Set up Outlook to use S/MIME encryption | Microsoft Support.

Learn more: Configure S/MIME in Exchange Online | Microsoft Learn (will be updated before we complete rollout)

[Compliance considerations:]

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

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

[Introduction]

Microsoft Teams is introducing slash (/) commands for apps in the compose box across chats and channels. This change provides a standardized way for users to invoke app functionality directly from the compose box and receive responses inline.

This message is associated with Microsoft 365 Roadmap ID 495002.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• All Microsoft Teams users
• App developers publishing apps in the Teams Store

• Users can type “/” in the compose box to discover and invoke supported app commands.
• Apps can return responses as Targeted Messages (visible only to the user who invoked the command).
• The feature is available by default when apps support slash commands
• No changes to existing admin policies or permissions.
• Apps will only appear in slash commands if their developers update the app manifest to define supported commands.

[What you can do to prepare:]

• No action is required.
• Review internal app inventory and confirm continued availability of apps that adopt slash commands.
• Update internal guidance if you provide documentation on Teams app usage.

[Compliance considerations:]

Introduces a new targeted messaging pattern (user-only visibility) within chats and channels.

What and Why

The June 2026 Windows security update will be released as a hotpatch baseline update rather than a standard hotpatch update. This baseline refresh is required periodically to maintain the trusted foundation that enables future hotpatch updates to install without requiring device restarts.

Rollout Schedule

This change applies to the June 2026 Windows security update.

Impact on Your Organization

Who is affected:

• Organizations with Windows devices enrolled in hotpatch updates

Platforms / Services:

• Windows
• Windows Update
• Hotpatch-enabled devices

What will happen:

• Hotpatch-enabled devices will receive the June 2026 security update through the standard Windows Update servicing process.
• A device restart will be required to complete installation.
• After installation and restart, the update will appear in update history and compliance reporting as usual.
• Devices remain enrolled in hotpatch, and the next restart-free hotpatch update is expected in August 2026.

Devices not enrolled in hotpatch and devices using standard Windows updates are not affected.

Action Required / Recommendations

• Ensure update deployment policies remain in place.
• Plan for and communicate the one-time restart requirement.
• No additional configuration changes are required.

Additional information

Hotpatch updates overview

Compliance considerations

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

[What and Why:]

To improve clarity, precision, and performance of transport rule reporting, Microsoft is updating the behavior of two Exchange Online reporting cmdlets. Starting July 30, 2026, Get-MailDetailTransportRuleReport and Get-MailTrafficPolicyReport will return transport rule data only when the request explicitly specifies the relevant EventType. This change helps ensure that reporting queries are intentional, predictable, and aligned with how transport rule events are generated and logged.

This update supports enterprise‑ready manageability by reducing ambiguous results and helping administrators build more reliable automation and compliance reporting.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected:

• Exchange Online administrators
• Security, compliance, or messaging teams
• Any organization using PowerShell scripts, automation, or reporting that relies on transport rule data from these cmdlets

Platforms/Services:

• Exchange Online
• Exchange Online PowerShell

What will happen:

• Get-MailDetailTransportRuleReport and Get-MailTrafficPolicyReport will no longer return transport rule results by default.
• Transport rule data will be returned only when one of the following parameters is explicitly included:
  • -EventType TransportRuleHits
  • -EventType TransportRuleActionHits
• Scripts or reports that do not include one of these parameters may return empty or incomplete results.
• This change applies only to these two cmdlets. No other Exchange Online cmdlets are affected. 

[Action Required / Recommendations:]

If your organization uses these cmdlets for transport rule reporting, action is required before July 30, 2026.

Recommended actions:

• Review all scripts, scheduled jobs, and automation that use:
  • Get-MailDetailTransportRuleReport
    
  • Get-MailTrafficPolicyReport
    
• Update queries that require transport rule results to explicitly include:
  • -EventType TransportRuleHits or
    
  • -EventType TransportRuleActionHits
    
• Validate updated scripts in a non‑production or test context.
• Update internal documentation and operational runbooks.
  
• Notify messaging and security operations teams of this change.

[Compliance considerations:]

This change alters how admins retrieve and report on transport rule data for compliance and auditing purposes.

[What and Why]

Microsoft 365 includes modern collaboration tools — such as Microsoft Loop and Copilot Pages — that allow people to co-author content in real time. These tools store content in cloud-native file formats (.loop and .page files) that are designed for live collaboration but cannot be opened or read outside of their respective applications.

In eDiscovery, when investigators export search results or add items to a review set, Loop and Copilot Pages content arrives in these cloud-native formats. The files cannot be opened in a standard document viewer and are difficult to produce for legal review or regulatory proceedings.

To address this challenge, we are adding an HTML conversion option in Microsoft Purview eDiscovery (Premium). When enabled, this setting automatically converts Loop and Copilot Pages files into HTML during export from search or when adding items to a review set.

This message is associated with Microsoft 365 Roadmap ID 561492.

[Rollout timeline]

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

[Impact on your organization]

Who is affected:

Organizations using Microsoft Purview eDiscovery (Premium) to manage investigations involving Microsoft Loop or Copilot Pages content.

Platform:

Web (Microsoft Purview portal)

Licensing requirements:

This feature requires a Microsoft 365 E5 or equivalent license that includes Microsoft Purview eDiscovery (Premium). Organizations without this license will not see this setting.

What will happen:

• What HTML conversion does:
  • When enabled, this setting converts Loop and Copilot Pages files into HTML (HTML | Living Standard) during export from search or when adding items to a review set.
  • HTML files can be opened in any web browser without special software, making the content accessible for production.
  • The converted HTML output preserves all text content and images from the original Loop or Copilot Pages file.
  • The visual appearance may differ from how the content looks inside the Loop or Copilot Pages application.
  • The converted content is fully indexed, which means you can use keyword searches to find specific terms within Loop and Copilot Pages content in your review sets.
• How to enable it:
  • This capability is controlled by a new setting on the process submission page in the Microsoft Purview portal.
  • When submitting an export or add‑to‑review‑set process, eDiscovery managers or administrators can choose to enable HTML conversion for Loop and Copilot Pages content.
  • The setting is off by default. If you take no action, Loop and Copilot Pages files will continue to export in their original format.

  Screenshot: Use this setting to convert .loop and .page files to HTML for improved review and searchability:

  

[Action Required / Recommendations:]

• Enable the HTML conversion setting when submitting export or add-to-review-set processes in the Microsoft Purview portal.
• Inform your eDiscovery team and update internal documentation to reflect the new HTML conversion option.

Learn more: Microsoft Purview eDiscovery documentation

[Compliance considerations]

[What and Why:]

We are extending Zero-hour Auto Purge (ZAP) in Microsoft Defender for Office 365 to scan and remediate malicious messages located in users’ Deleted Items folders. This enhancement strengthens post-delivery protection by ensuring phishing, spam, and malware messages are removed even after a user deletes or reports them, improving overall tenant security without introducing new policies or configuration.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected:

• All tenants using Exchange Online Protection or Microsoft Defender for Office 365 Plan 1 or Plan 2 with ZAP enabled

Platforms/Services:

• Exchange Online
• Microsoft Defender for Office 365
• Outlook (desktop, web, mobile)

What will happen:

• ZAP will retroactively scan and take action on malicious messages found in the Deleted Items folder within the ZAP detection window.
• This includes messages that were:
  • Reported by users as phishing
  • Automatically moved after accepting calendar invitations
  • Manually deleted by users
• Messages identified as malicious will follow existing policy actions (for example, move to Junk, quarantine).
• No new policies, actions, or configuration settings are introduced.
• Admins will see additional ZAP activity in existing reports and alerts.
• A new SourceLocation column will be added to the EmailPostDeliveryEvents table in Advanced Hunting to indicate the originating folder (for example, DeletedItems).
• User experience remains unchanged.

[Action Required / Recommendations:]

No action is required.

This change is enabled by default and respects your existing anti‑spam, anti‑phishing, and anti‑malware policies.

Recommended actions for admins:

• Review existing ZAP-related reporting in Mail flow status and Threat Explorer to help your Security Operations Center (SOC) become familiar with the additional activity.
• Update internal security documentation or helpdesk guidance to note that Deleted Items are now included in ZAP remediation.

Learn more: Zero-hour auto purge (ZAP) in Microsoft Defender for Office 365 | Microsoft Learn

[Compliance Considerations:]

[What and Why]

Planner agent in Microsoft 365 Copilot is generally available. This capability brings Planner work management into Copilot and enables users to create, update, and manage personal tasks and shared basic plans without switching context. Planner agent provides insights into priorities, deadlines, and at-risk work, and uses interactive task cards that require users to review and confirm updates before changes are applied.

This message is associated with Microsoft 365 Roadmap ID 516576.

[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

• Users with an active Microsoft 365 Copilot license

Platforms/Services

• Microsoft 365 Copilot experiences across web and supported endpoints

What will happen

• Planner agent will be available across Microsoft 365 Copilot experiences.
• Users can find and add Planner agent from the Copilot agent store.
• Users can create, view, and update personal tasks and shared basic plans

  : 

• Users can generate structured plans that include goals, buckets, task hierarchies, and improved plan organization.
• A plan selection experience is available when working with multiple plans.
• Additional task fields are supported as part of plan and task management.
• Interactive task cards are used to present suggested updates and require users to review and confirm changes before they are applied.
• Planner agent provides insights such as priorities, deadlines, and at-risk work.
• Updates since the initial Frontier release include improvements to reliability, system behavior, and overall quality.

[Action Required/Recommendations]

No immediate action is required.

Important: Planner agent is preinstalled for users based on license eligibility. The ability to restrict the agent to specific user groups is no longer available, as it is the case for all preinstalled agents today. Admins can still block the agent for the entire tenant through the Microsoft 365 admin center. For more information, review Agent installation in Microsoft 365 Copilot | Microsoft Learn.

Recommended actions:

• Confirm that users have active Microsoft 365 Copilot licenses.
• Review agent availability and settings in the admin center if needed.
• Update internal documentation if your organization tracked preview functionality.
• Inform helpdesk and users about the new Planner agent capability.

Learn more: 

• Agent installation in Microsoft 365 Copilot | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn
• Manage agents in the Microsoft 365 admin center | Microsoft 365 admin center | Microsoft 365 | Microsoft Learn

[Compliance considerations]

[What and Why:]

Beginning in June 2026, Microsoft 365 Copilot will be able to answer user questions using Power BI reports and semantic models for customers enrolled in Frontier. Copilot will ground responses in Power BI data, including scenarios where users share a specific report and scenarios where Copilot finds the right report automatically. The experience is built to work within existing security and permission models.

[Rollout Schedule:]

Starting early June 2026, data answering capabilities grounded in Power BI content will be available in Frontier tenants.

[Impact on Your Organization:]

• Who is affected: Organizations using Microsoft 365 Copilot and Power BI that are enrolled in Frontier
• Platforms/Services: Microsoft 365 Copilot, Power BI, Microsoft Fabric
• Licensing requirements:
  •  Microsoft 365 Copilot (Premium) license is required to use this feature.
  • Use of Fabric content, including Power BI reports, will be subject to the usual Power BI licensing to view content in the service.
  • Users are not required to have access to Fabric Copilot. 
• What will happen:
  • Users can ask Copilot questions grounded in Power BI reports and semantic models.
  • Responses respect existing Power BI and Microsoft 365 permissions.
  • The feature is enabled by default. Admins can disable the feature through the Microsoft 365 admin center.
  • To generate responses, Microsoft 365 Copilot will search and retrieve data stored in Fabric, which means user query data from Microsoft 365 Copilot will be shared with Fabric. Fabric operates separately from Microsoft 365 Copilot and is subject to different commitments. Data processed in Fabric is subject to Fabric’s Product Terms. 

Screenshot: Before and after improvement in Copilot responses with Power BI data grounding:

• No action is required.
• Admins can disable the feature in the Microsoft 365 admin center. At the time of release, this control will be available on the Copilot settings page under the setting Fabric data in Microsoft 365 Copilot.  

[Compliance considerations:]

[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.com.
• 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.

We've released updates to the following update channel for Microsoft 365 Apps:

• Current Channel

[When this will happen:]

We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting May 26th, 2026 (PST).

[How this will affect your organization:]

If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.

If you manage updates directly you can now download this latest update and begin deployment.

[What you need to do to prepare:]

To get more details about this update view the following release notes:

• Current Channel

• Uses the original project estimate for PoC calculations to deliver stable, predictable revenue without EAC-driven fluctuations.
• Anchors revenue recognition to a fixed baseline to improve transparency and boosts confidence in reported project financials.
• Reduces reliance on changing forecasts to minimize rework and exceptions during month-end close.
• Provides clear traceability from estimate to recognition to strengthen audit readiness and compliance.
• Aligns revenue with initial project expectations to enhance visibility into true project performance and profitability.
• Creates smoother revenue trends across reporting periods to enable better executive decision-making and financial planning.
• Standardizes how teams evaluate project progress to support consistent financial processes across the organization.

• Match subcontractor vendor invoices to recorded actuals.
• Validate invoice amounts using receipt and actual cost data.
• Reduce manual reconciliation and invoicing errors.
• Streamline subcontracting procure-to-pay.

1. AgentReject — The representative manually rejected the notification for an assigned conversation.
2. MaximumSessionsReached — The representative had 10 conversation sessions open in a single browser tab.
3. VoiceConnectivityProblem — A network issue prevented connection to the voice SDK during a voice call.
4. FailedToAssignDueToSystemError — An internal system error triggered the rejection automatically.
5. CallTimedOut — Connectivity or browser-related issues caused the incoming conversation to automatically rejected.