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

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

[Introduction]

We’re introducing a private chat feature for organizers, co-organizers, and presenters in structured meetings and webinars in Microsoft Teams. This separate chat enhances collaboration by allowing key participants to communicate privately before, during, and after the event, without involving attendees. Additionally, we are unifying backroom chat behavior in town halls to ensure consistent functionality across all structured meetings. Currently, backroom chat behavior varies depending on whether streaming chat is enabled for town halls and whether the organizer has a Teams Premium license. This update removes that inconsistency.

This message is associated with Roadmap ID 392328 and applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, Teams for iOS/Android, MTR-W and MTR-A devices.

[When this will happen:]

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

[How this affects your organization:]

Who is affected: Admins managing Microsoft Teams meetings, webinars, and town halls.

What will happen:

• New private chat for organizers, co-organizers, and presenters: This chat is separate from attendee chat and is available before, during, and after the event.
• Unified backroom chat policy for town halls: The default setting will be ON for all town halls, regardless of streaming chat availability or license type.
• Existing town halls will adopt the new policy once meeting options are updated.
• If admins turn the backroom chat policy OFF, previously enabled town halls will lose access after update.
• Non-TPre town halls (those without a Teams Premium license) will have backroom chat ON by default after rollout and update.

Two potential impacts:

• If an admin explicitly turns the new backroom chat policy OFF, any already-scheduled town hall that previously had backroom chat ON will lose access once the meeting options are updated.
• For non-TPre town halls where backroom chat was previously OFF, it will switch to ON by default after the rollout and a meeting options update.

[What you can do to prepare:]

• Review your Teams meeting policies and decide whether to enable private chat for organizers and presenters.
• Communicate this change to helpdesk staff and event organizers.
• Update internal documentation to reflect the new backroom chat behavior.
• If you want to disable backroom chat, adjust the policy in the Teams admin center.

[Compliance considerations:]

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

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

[Introduction]

Copilot Notebooks enables users to generate Excel spreadsheets directly from the content and references collected in a notebook. Copilot creates a structured spreadsheet based on the notebook’s context, which can then be opened and edited in Excel. This capability streamlines the transition from ideas and source material into a usable spreadsheet by reducing manual setup and formatting.

[When this will happen:]

• Public Preview via Frontier: Rollout begins in late March 2026 and is expected to complete by late April 2026.
• General Availability (Worldwide): Rollout begins in early June 2026 (previously late May) and is expected to complete by early June 2026 (previously late May).

[How this affects your organization:]

Who is affected:

• Users with access to Microsoft Copilot and Copilot Notebooks
• Organizations using Excel in Microsoft 365
• A Microsoft 365 Copilot (Premium) license is required to use this feature

What will happen:

• Users will be able to generate an Excel spreadsheet from content and references stored in a Copilot Notebook.



• The generated spreadsheet opens in Excel and can be edited like any other Excel file.
• The feature is enabled by default for eligible users.
• Existing Microsoft 365 security, compliance, and Copilot policies are respected.

[What you can do to prepare:]

• No admin action is required.
• Review internal guidance or helpdesk documentation related to Copilot and Excel workflows.
• Consider notifying users that Copilot Notebooks can now generate Excel spreadsheets from notebook content.

Learn more: Get started with Microsoft 365 Copilot Notebooks | Microsoft Support (will be updated before rollout)

[Compliance considerations:]

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

[Introduction]

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

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

This message is associated with Microsoft 365 Roadmap ID 557981.

[When this will happen]

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

[How this affects your organization]

Who is affected

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

What will happen

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

   

  

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

[What you can do to prepare]

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

[Compliance considerations]

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

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

[Introduction]

Microsoft Teams is introducing Efficiency Mode, a performance-optimized experience designed for hardware-constrained devices. This change improves app responsiveness and meeting quality by adjusting resource usage based on device capabilities.

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

[When this will happen:]

General Availability (Worldwide): Rollout begins in late May 2026 (previously early May) and is expected to complete by end of May 2026 (previously mid-May).

[How this affects your organization:]

Who is affected:

• Users running Microsoft Teams on hardware‑constrained devices (for example, devices with limited CPU, memory)

What will happen:

• Efficiency Mode is enabled by default on eligible devices.
• An Efficiency Mode indicator appears in the Teams app title bar.



• When enabled:
  • Video resolution sent from the user’s camera is dynamically adjusted in meetings.
  • The app launches without a pre-selected chat and shows a static image in the message pane.
• Users can opt out via Settings > General > “Never use efficiency mode.”
• To align with the new standardized approach of how indicators are displayed in the title bar, for VDI users the “Optimized” pill is replaced with the new icon.

[What you can do to prepare:]

• No action is required if the default behavior works for your organization.
• Consider informing helpdesk teams about the new mode and opt-out option.
• Update internal documentation if applicable.

[Compliance considerations:]

Users can enable or disable the feature themselves. No other compliance considerations were identified.

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

[Introduction]

We’re introducing integration of the Microsoft Purview SDK into the Microsoft Agent Framework SDK to help organizations build secure, enterprise-ready AI agents. This integration enables developers to apply Microsoft Purview compliance and data protection capabilities directly within agent runtimes. It extends existing security and governance controls to custom-built AI agents across Microsoft 365 workloads.

This message is associated with Microsoft 365 Roadmap ID 534609.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Organizations building or planning to build AI agents using the Microsoft Agent Framework SDK
• Admins and developers responsible for security, compliance, and governance of custom AI agents
• Tenants with Microsoft Purview licenses that enable SDK usage

What will happen

• Developers can embed Microsoft Purview SDK controls directly into AI agent runtimes built with the Agent Framework SDK.
• AI agents can respect existing Microsoft Purview compliance configurations, such as data protection and policy enforcement, when accessing organizational data.
• There is no change to user experiences in Microsoft 365 services.
• The integration is not enabled automatically; it requires developer implementation within custom agents.
• Existing Microsoft Purview policies and configurations remain unchanged unless explicitly used by the agent.

[What you can do to prepare]

No immediate admin action is required if your organization is not developing AI agents.

If your organization builds AI agents:

• Share this update with your development and security teams.
• Review Microsoft Purview SDK documentation to understand supported compliance capabilities.
• Validate how existing Purview policies should be applied within agent workflows.

Learn more: Building Secure, Enterprise-Ready AI Agents with Purview SDK and Agent Framework | Microsoft Security Community Blog

[Compliance considerations]

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

[Introduction]

We are introducing optical character recognition (OCR) scanning support for Microsoft Purview Data Loss Prevention (DLP) on Windows endpoint devices. This enhancement enables DLP policies to detect sensitive information within images embedded inside Office documents and PDF files.

Previously, embedded images were skipped during endpoint DLP scanning, creating a detection blind spot. With this update, embedded images are OCR-processed, helping improve data protection coverage and reduce risk of accidental data exposure.

This message is associated with Microsoft 365 Roadmap ID 381750.

[When this will happen:]

• General Availability (Worldwide): Rollout will begin in late June 2026 (previously late May) and is expected to complete by end of June 2026 (previously end of May).

[How this affects your organization:]

Who is affected:

• Admins managing Microsoft Purview Data Loss Prevention
• Organizations using Endpoint DLP on Windows devices
• Users working with Word, Excel, PowerPoint, and PDF files on Windows endpoints

What will happen:

Once OCR is enabled for your organization, DLP policies applied to endpoint devices will be able to scan images embedded inside Office documents (Word, PowerPoint, Excel) and pdf files on Windows devices. This means:

• Sensitive data detection in embedded images: If a document contains an embedded image with sensitive information (such as credit card numbers, Social Security numbers, or financial data), DLP policies can now detect that data and enforce configured actions (audit, block, or block with override).
• Closes a detection blind spot: Previously, embedded images were entirely skipped during endpoint DLP scanning. This update ensures those images are processed using OCR and evaluated against your DLP policies.
• Cost implications: Enabling OCR incurs additional costs based on the volume of images scanned. Costs are charged per image scanned via Azure AI Services. Organizations can monitor OCR costs through:
  • The OCR cost dashboard in the Microsoft Purview compliance portal under Data loss prevention → Overview
  • Cost Management + Billing in the Azure portal, filtered by your Azure AI Services resource 

[What you can do to prepare:]

To take advantage of this feature, complete the following steps: 

1. Verify prerequisites:
   • Confirm Microsoft Sense Client version 10.8820.27904.1000 or later.
   • Run: MsSense.exe --version from C:\Program Files\Windows Defender Advanced Threat Protection.
   • Ensure Windows OS update KB5079473 is installed on endpoint devices.
2. Enable OCR in Microsoft Purview:
   1. Navigate to the Microsoft Purview compliance portal.
   2. Go to Data loss prevention → Overview → Data loss prevention settings.
   3. Under Optical Character Recognition (OCR), select Turn on OCR scanning.
   4. Select the appropriate Azure pay-as-you-go subscription and Azure AI Services resource.
   5. Select Save.
3. Review and update DLP policies:
   • Ensure policies include Devices as a location.
   • Consider testing with Test mode and policy tips before enforcing actions.
   • Verify sensitive information types are configured for detection in embedded images.
4. Set up billing and monitor costs:
   • Configure OCR billing before enabling the feature.
   • Review the OCR cost dashboard in Purview after enabling.
5. Assign appropriate roles:
   • Compliance Data Administrator
   • Compliance Administrator
   • Information Protection
   • Information Protection Admin

Learn more:

• Learn about optical character recognition in Microsoft Purview | Microsoft Learn
• Get started with Activity Explorer | Microsoft Learn
• Create and deploy a DLP policy | Microsoft Learn
• Learn about Endpoint DLP | Microsoft Learn

[Compliance considerations:]

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

[What and Why]

Data Security Posture Management (DSPM) in Microsoft Purview is now generally available. This capability helps organizations better understand, assess, and improve their data security posture across Microsoft 365 by identifying risks, surfacing insights, and guiding remediation actions. This release aligns with our continued investment in enterprise-ready security and compliance tools to help you protect sensitive data at scale.

This message is associated with Microsoft 365 Roadmap ID 542790.

[Rollout Schedule]

General Availability (Worldwide): Mid-June 2026 (previously late-May) – Late July 2026 (previously late June)

[Impact on Your Organization]

Who is affected

• Admins and security/compliance teams using Microsoft Purview in Microsoft 365 tenants

Platforms/Services

• Microsoft Purview (web experience)

What will happen

• The Data Security Posture Agent will be generally available in DSPM.
• The feature provides centralized insights into data risks and posture across your environment.
• Admins will be able to view recommendations and take actions to improve data security posture.
• The experience transitions from preview to GA with no disruption to existing configurations.
• No change to existing policies or configurations is required.
• Availability is aligned with your tenant’s Microsoft Purview deployment.

[Action Required / Recommendations]

No action is required.

As a best practice, you may want to:

• Review DSPM capabilities in Microsoft Purview and assess how they fit into your data security strategy.
• Explore configuration and usage guidance:
  • Learn how to set up the new data security posture agent.
  • Review how to use DSPM insights and recommendations.
• Notify your security and compliance teams of this availability.
• Update internal documentation if you reference Purview DSPM capabilities.

Learn more: 

• Get started with the Data Security Posture Agent | Microsoft Purview | Microsoft Learn
• Using the Data Security Posture Agent – Considerations for Microsoft Purview Data Security Posture Management | Microsoft Purview | Microsoft Learn

[Compliance Considerations]

[What and Why]

Microsoft Purview Data Lifecycle Management is introducing the ability to archive OneDrive and SharePoint files based on retention policies. This feature helps organizations reduce storage costs by moving inactive content to Microsoft 365 Archive while maintaining compliance and discoverability. By excluding archived content from Copilot indexing, organizations can also improve the relevance and quality of Copilot responses, ensuring users focus on current, active data.

This message is associated with Microsoft 365 Roadmap ID 561208.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected

• Admins managing Microsoft Purview Data Lifecycle Management
• Organizations using retention policies in SharePoint Online and OneDrive

Platforms/ServicesPlatforms/Services

• Microsoft Purview (Data Lifecycle Management)
• SharePoint Online
• OneDrive for Business
• Microsoft 365 Archive
• Microsoft Copilot

What will happen

• A new Archive option will be available within retention policy settings in Data Lifecycle Management.
• Admins can configure retention policies to move inactive files to Microsoft 365 Archive storage.
• Archived files remain available for compliance scenarios, including eDiscovery.
• Archived content will be excluded from Copilot indexing, helping improve answer relevance.
• This feature is not enabled by default and requires admin configuration.
• Existing retention policies and compliance configurations remain unchanged unless updated by admins.

  

[Action Required / Recommendations]

No immediate action is required.

To prepare and take advantage of this feature:

• Review your current retention policies in Microsoft Purview Data Lifecycle Management.
• Evaluate opportunities to reduce storage costs by archiving inactive content.
• Update retention policies to include the new Archive option where appropriate.
• Inform compliance and records management stakeholders about this new capability.
• Review internal documentation and processes related to data lifecycle and storage optimization.

[Compliance Considerations]

If your organization has Conditional Access policies scoped to Register security information, those policies will now apply when users set up Windows Hello for Business (WHfB) or register macOS Platform SSO credentials.

Today, these registration flows enforce MFA, but do not evaluate your registration-targeting Conditional Access policies — meaning requirements like authentication strength, trusted locations, or other CA conditions aren’t enforced when users enroll WHfB or macOS Platform SSO credentials. This change closes that gap.

Organizations without these policies aren’t affected.

When this will happen

• July 6, 2026: Gradual rollout begins.

• July 13, 2026: Rollout complete for all tenants.

How this affects your organization

Users registering WHfB or macOS PSSO credentials will need to satisfy your registration-targeting Conditional Access policy requirements before completing enrollment. For example, a user might need to use an existing FIDO2 security key, approve a push notification in Microsoft Authenticator, or connect from a trusted network location — depending on what your policies require. Any Grant controls you’ve configured will apply.

Users who don’t meet the requirements will be blocked from completing registration until the conditions are met.

Action recommended

1. In Entra admin center > Protection > Conditional Access, find policies targeting Register security information.
2. Review Grant controls — check what requirements users must satisfy during registration (authentication strength, trusted locations, MFA method).
3. Consider whether users setting up a new device can meet your policy requirements — for example, make sure users have a FIDO2 security key or other qualifying credential available before they start device setup.
4. Test with report-only mode before enforcement reaches your tenant.
5. Update helpdesk docs — users may see a new authentication prompt during device setup.

If you experience issues during the rollout window (July 6–July 13), contact Microsoft Support or your account team for assistance.

Learn more: Require MFA for security info registration

[Introduction]

We are introducing file-level archiving for Microsoft 365 Archive. This capability allows organizations to move individual SharePoint files or folders into low-cost archival storage while keeping them visible in their original location. This helps reduce storage costs and optimize content lifecycle management without losing metadata, permissions, or compliance coverage.

This message is associated with Microsoft 365 Roadmap ID 477371.

[When this will happen]

• Public Preview: Available now.
• General Availability (Worldwide): Rollout begins in late June 2026 and is expected to complete by late July 2026.

[How this affects your organization]

Who is affected

• SharePoint administrators
• Users in organizations that enable Microsoft 365 Archive and file-level archiving

What will happen

• File-level archiving is not enabled by default. Admins must enable Microsoft 365 Archive and then enable file-level archiving.
• Users with Edit permissions can archive individual files or entire folders in SharePoint document libraries.
• Archived files:
  • Remain in their original location with a visual indicator
  • Retain metadata, permissions, and compliance coverage
  • Cannot be opened until reactivated
• Reactivation behavior:
  • Instant reactivation within 7 days of archiving
  • After 7 days, reactivation may take up to 24 hours
• Archived files:
  • Are excluded from Copilot responses
  • Are hidden from default search results
• Storage and billing:
  • Archived content is billed using Pay-As-You-Go pricing
  • Storage costs are approximately 75% lower than active storage
  • Charges apply to storage exceeding the SharePoint tenant quota
• Admin capabilities:
  • Enable or disable file-level archiving at tenant or site level
  • Control default behavior for new sites
  • Monitor usage via PowerShell (FileArchiveStorage metrics)
• All archive and reactivation actions are logged in the Microsoft 365 audit log.

[What you can do to prepare]

• Enable Microsoft 365 Archive in the Microsoft 365 admin center (if not already enabled).
• Configure file-level archiving:
  • Verify tenant-level status:
    • Run Get-SPOTenant and confirm AllowFileArchive is set to True
  • Enable or disable file-level archive for specific sites:
    • Set-SPOSite -Identity <URL> -AllowFileArchive True/False
  • Control the default for newly created sites:
    • Set-SPOTenant -AllowFileArchiveByDefault True/False
  • Monitor usage:
  • Run Get-SPOTenant and Get-SPOSite to view FileArchiveStorage (GB)
• Review which sites should allow file-level archiving and configure accordingly
• Inform site owners and end users about:
  • How archiving works
  • Reactivation timing differences
  • Search and Copilot behavior changes

Learn more: Manage file-level archive (preview) – Manage Microsoft 365 Archive | Microsoft 365 Archive | Microsoft Learn

[Compliance considerations]

[What and Why]

Microsoft Teams is enhancing Information Barriers (IB) enforcement to provide consistent compliance protection across all communication scenarios, including external collaboration.

With this update, IB policies will be enforced between users within the same tenant even when they participate in external group chats, calls, or meetings. This improvement ensures that organizations with regulatory or compliance requirements can maintain policy enforcement regardless of how conversations are initiated or who else is included.

This feature strengthens enterprise-grade compliance and risk management while enabling safer external collaboration.

[Rollout Schedule]

General Availability (Worldwide):

• Rollout start: June 15, 2026
• Rollout completion: June 18, 2026

[Impact on Your Organization]

Who is affected

• Organizations that have Information Barriers configured
• Users in those organizations who participate in external chats, calls, or meetings

Platforms/Services

• Microsoft Teams (chat, group chat, meetings, and calls)
• Applies across desktop, web, and mobile clients

What will happen

Pre-existing external conversations are not retroactively modified at rollout.

• IB policies will be enforced between internal users in external conversations.
• This feature is enabled by default for tenants with IB policies configured.
• Existing IB configurations and policies are respected; no reconfiguration required.

New and updated behavior:

• Creating new external group chats or calls:
  • Teams will validate IB policies between internal participants.
  • Users who are not allowed to communicate will be excluded automatically.
• Adding participants to existing external conversations:
  • IB policies are validated before allowing the addition.
  • The action will be blocked if policies prevent communication.
• Existing external conversations at rollout:
  • External threads that already include non-compliant internal participants are not automatically changed at rollout.
  • Non-compliant participants will remain in those threads unless a re-evaluation occurs.
• Ongoing and conditional enforcement:
  • If IB policies or user segment membership changes, the conversation may be reprocessed.
  • At that time, users who are no longer allowed to communicate will be automatically removed.
  • Conversations will continue for compliant participants.

[Action Required/Recommendations]

No immediate action is required.

However, we recommend that administrators:

• Review your existing Information Barriers policies to understand potential impact on external collaboration scenarios.
• Inform helpdesk and support teams about:
  • Existing external chats may retain non-compliant participants initially
  • Changes in behavior when adding users to chats or meetings
  • Possible participant removal from existing conversations after rollout
• Communicate this update to users in regulated teams or roles that frequently collaborate externally.
• Update internal documentation if you describe external collaboration or IB enforcement scenarios.

Learn more: [To be updated closer to rollout.] Information Barriers in Microsoft Teams | Microsoft Purview | Microsoft Learn

[Compliance considerations]

[What and Why]

Microsoft Purview Data Security Triage Agent in Data Loss Prevention (DLP) will include a sensitive data remediation capability to help organizations identify and remediate sensitive information across SharePoint and OneDrive at scale. This capability will automate user engagement by sending remediation requests directly to the last modifier of affected files through Microsoft Teams. By enabling a closed-loop remediation process, organizations will be able to reduce compliance risk, improve remediation rates, and gain better visibility into remediation progress.

[Rollout Schedule]

• Public Preview: Rollout will begin in late June 2026 and is expected to complete by late July 2026.

[Impact on Your Organization]

Who is affected

• Microsoft Purview administrators managing Data Loss Prevention
• Users who modify files containing sensitive data in SharePoint or OneDrive

Platforms/Services

• Microsoft Purview (Data Loss Prevention, Data Security Triage Agent)
• Microsoft Teams
• SharePoint Online
• OneDrive for Business

What will happen

• This capability will be off by default and will require admin opt-in in Data Security Triage Agent settings.
• After the capability is enabled:
  • The agent will detect files associated with Data Loss Prevention alerts.
  • Only alerts triaged as Needs attention will be eligible.
  • A Microsoft Teams message will be sent to the user who last modified the file.
  • Users will receive daily reminder messages until remediation is completed or the configured reminder duration is reached.
  • Administrators will be able to configure the number of reminder days.
  • Remediation progress will be tracked in the Data Security Posture Management dashboard.
• Scope limitations:
  • Applies only to SharePoint and OneDrive workloads.
  • Does not apply to Endpoint or Teams-originated alerts.
  • Alerts marked as Less urgent or not triaged are not included.

[Action Required/Recommendations]

Action may be required if you plan to use this feature.

• Enable the Data Security Triage Agent in Data Loss Prevention settings if it is not already enabled.
  • Review: Enable the agent – Get started with the Microsoft Purview Triage Agent in Data Loss Prevention | Microsoft Learn
• Enable the sensitive data remediation capability and configure reminder duration.
  • Review: Remediation reminder (Preview) – Get started with the Microsoft Purview Triage Agent in Data Loss Prevention | Microsoft Learn
• Review your Data Loss Prevention policies and determine which policies will use remediation.
• Ensure that your Microsoft Teams environment is configured to support agent messaging.
  • Review: Configure Microsoft Teams for the Data Security Triage Agent remediation messages | Microsoft Learn
• Coordinate with your Teams administrator to deploy and manage the required app.
• Review setup and configuration guidance.
• Communicate this change to your security and compliance stakeholders.

Learn more: 

• Configure Microsoft Teams for the Data Security Triage Agent remediation messages | Microsoft Purview | Microsoft Learn
• Get started with the Microsoft Purview Triage Agent in Data Loss Prevention | Microsoft Purview | Microsoft Learn

[Compliance considerations]

[What and Why:]

We’re removing the statistics line from the Get-CsCallQueue PowerShell cmdlet output that displays the current number of calls waiting in a call queue. This change aligns call queue monitoring with enhanced real-time reporting available in the Queues app.

[Rollout Schedule:]

We will begin rolling out in late August 2026 and expect to complete by mid-September 2026.

[Impact on Your Organization:]

Who is affected: Teams Administrators who use the Get-CsCallQueue PowerShell cmdlet.

Platforms/Services: Microsoft Teams, Teams PowerShell

What will happen:

• The statistics line showing the current queue size will be removed from the cmdlet output.
• The cmdlet will continue to return call queue configuration information with no change to usage.
• Administrators will no longer be able to view real-time call waiting counts using PowerShell.
• Enhanced real-time call queue reporting is available through the Queues app.

Example of removed output:

Statistics : Current queue size = 0

[Action Required / Recommendations:]

No action is required.

If you currently rely on PowerShell to view real-time call queue size:

• Review the Queues app for enhanced real-time call queue reporting.
• Update internal documentation or scripts that reference the removed statistics line.
• Inform helpdesk or operations teams of this change to avoid confusion.

[Compliance considerations:]

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

[What and Why:]

We’re introducing shared and delegate mailbox scheduling for events, which allows executive assistants and delegates to organize events on behalf of leaders using shared or delegated mailboxes. This ensures invitations and updates are sent from recognized organizational mailboxes, improving trust, consistency, and overall event coordination.

This message is associated with Microsoft 365 Roadmap ID 561912.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected: Event organizers, executive assistants, Chiefs of Staff, delegates, and admins managing events on behalf of leaders or teams.

Platforms/Services: Microsoft Teams, Exchange Online (delegate, shared, and group mailboxes)

What will happen:

• Events can be created and managed using delegate, shared mailboxes.
• Invitations, updates, and notifications are sent from the selected mailbox identity.
• Delegates can manage scheduling and logistics on behalf of leaders or teams.
• Event communications align with trusted organizational mailboxes, improving credibility and recipient trust.
• The feature is enabled by default and respects existing Exchange permissions.

[Action Required / Recommendations:]

• No action is required.
• Review delegate and shared mailbox permissions to ensure appropriate access.
• Communicate this change to executive support staff and helpdesk teams.

[Compliance Considerations:]

[Introduction]

We are updating the page editing experience in SharePoint Online by reorganizing the content pane toolbox used when creating or editing pages and news posts. This change allows users to see all web parts on opening the toolbox and separates stock images, videos and recently used images into dedicated tabs within the toolbox. Section templates are moved to a separate tab. 

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in late May 2026 and is expected to complete by late June 2026.

[How this affects your organization:]

Who is affected:

• All users who create or edit pages and news posts in SharePoint Online.

What will happen:

• When opening the content pane toolbox, all available web parts are visible by default, with no extra navigation required.
• The content pane has additional tabs for Stock images, Videos, and Recently used.
• Section templates are moved to a separate tab.
• Tabs group content by category, so you can easily switch between content types.

Screenshot: Toolbox showing different web parts and tabs for Stock images, Videos, and Recent: 



• Existing pages are not affected.
• This update is enabled by default and does not introduce new admin controls.

[What you can do to prepare:]

• No admin action is required.
• Optionally notify page authors about the updated content pane layout.

Learn more: Using web parts on SharePoint pages | Microsoft Support

[Compliance considerations:]

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

[What and Why]

Microsoft Purview Information Protection is introducing File Labeler and File Viewer applications for macOS. These clients will bring sensitivity labeling and protected file viewing capabilities to Mac users, aligning with the experience already available on Windows.

This update will help organizations consistently apply and enforce protection policies across platforms, supporting enterprise-grade security and compliance for sensitive content across devices.

This message is associated with Microsoft 365 Roadmap ID 561327.

[Rollout Schedule]

• Public Preview: The macOS client will be made available for download on or around May 29, 2026.
• General Availability (Worldwide): The macOS client will be made available for download on or around September 30, 2026.

[Impact on Your Organization]

Who is affected

• Users on macOS who work with labeled and protected files
• Admins managing Microsoft Purview Information Protection

Platforms/Services

• macOS
• Microsoft Purview Information Protection

What will happen

• The macOS client will be made available to download via the Microsoft Purview Information Protection page.
• Users will be able to apply, change, and remove sensitivity labels on supported files, including Office documents, PDFs, images, text files, and other file types.
• Users will be able to apply labels and protection to single files, or multiple files
• Labels and protection will remain applied when files are shared or moved.
• Users will be able to open and view protected files (including .pfile-based formats) that are not supported by their originating applications.
• The macOS client will provide parity with the Windows File Labeler and File Viewer, with the following exceptions:
  • Advanced label-based protection will not be supported in this release.
  • Need to work with files, selecting a folder will not show the option.
• The client will not be pre-installed and will need to be downloaded separately.
• Existing sensitivity labeling policies will continue to apply; no changes will be required.

[Action Required/Recommendations]

No immediate action is required.

Admins may consider the following:

• Review your current sensitivity labeling policies to ensure they meet cross-platform needs.
• Inform macOS users about the availability of labeling and protected file viewing capabilities.
• Download the macOS client from the Microsoft Purview Information Protection page when it becomes available.

Learn more:

• Learn about Advanced label-based protection for all files on devices | Microsoft Purview | Microsoft Support
• Learn about sensitivity labels | Microsoft Purview | Microsoft Learn
• Label and protect files in File Explorer in Windows | Microsoft Support
• View protected files with Microsoft Purview Information Protection viewer | Microsoft Support

[Compliance considerations]

[Introduction]

Microsoft will introduce an enhanced export experience for Viva Glint Heat Map reports. This update will add a new option to export Heat Map reports as fully editable PowerPoint slides, making it easier and faster for managers to customize, share, and present survey insights outside of Viva Glint using native PowerPoint tools.

This message is associated with Microsoft 365 Roadmap ID 560821.

[When this will happen]

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

[How this affects your organization]

Who is affected

Managers and users with access to Heat Map reports in Microsoft Viva Glint across Microsoft 365 tenants (Worldwide and GCC).

What will happen:

• A new export option, Export report to PowerPoint, will be added for Heat Map reports.
• Heat Map reports can be exported as native, editable PowerPoint slides, allowing direct editing of text, layout, and visuals using built‑in PowerPoint tools.
• The existing Export screenshots to PowerPoint option will continue to be available.
• Both export options will appear in the same export dropdown.
• The editable PowerPoint format will improve layout consistency and reduce unnecessary whitespace.
• Export performance will improve, reducing timeouts and increasing reliability.
• The feature will be enabled by default and will respect existing Viva Glint role‑based permissions.
• No admin configuration or policy changes will be required.

[What you can do to prepare]

No action is required before rollout.

Optionally:

• Consider notifying managers that a new editable PowerPoint export option will be available for Heat Map reports.
• Update any internal documentation or training materials that reference Viva Glint Heat Map report exports.
• Prepare helpdesk staff for questions about the two available export options.

Learn more [to be updated closer to GA rollout]: How to Export Report to PowerPoint – Export to PowerPoint | Viva Glint | Microsoft Viva | Microsoft Learn

[Compliance considerations]

[What and Why:]

The updated Notebooks experience in the Microsoft 365 Copilot app helps users keep project work organized across conversations. Notebooks bring chats, generated content, and reference materials together in a lightweight, persistent workspace, making it easier to stay in context and move work forward. This update complements the existing Notebooks experience in OneNote, which remains unchanged. Notebooks stay in sync across the Microsoft 365 Copilot app and OneNote, allowing users to move between experiences without losing context.

This message is associated with Roadmap ID 562662.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected: Users with a Microsoft 365 Copilot (Premium) license

Platforms/Services:

• Microsoft 365 Copilot app (web)
• OneNote

What will happen:

• Users with a Microsoft 365 Copilot license will see Notebooks in the Microsoft 365 Copilot app once rollout reaches their tenant.

Screenshot: Notebooks experience in the Microsoft 365 Copilot app:



• The existing Copilot Notebooks offering in the Microsoft 365 Copilot app continues to be referred to as Notebooks; the entry point and existing Notebook data remain in place.
• Notebooks in OneNote are unchanged. Users can continue working with Copilot Notebooks in OneNote.
• Notebooks stay in sync between the Microsoft 365 Copilot app and OneNote, and users can open Notebooks in either experience.
• Content created from a Notebook—including Word documents, PowerPoint presentations, Excel spreadsheets, Copilot Pages, and other supported objects—remains associated with that Notebook.
• Default state: On for eligible users once rollout reaches the tenant.
• Admin controls: Governed by existing Microsoft 365 Copilot policies; there is no separate admin toggle for Notebooks.

[Action Required / Recommendations:]

No admin action is required.

We recommend that admins:

• Inform end users that Notebooks is the workspace name in the Microsoft 365 Copilot app.
• Reinforce that Notebooks in OneNote remain available and unchanged.
• Update internal documentation or helpdesk guidance, if applicable, to reference Notebooks as the organizing workspace in the Copilot app.

Notebooks in the Microsoft 365 Copilot app are governed by your organization’s existing Microsoft 365 Copilot policies.

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

[Compliance considerations:]

This change introduces a new way for users to interact with generative AI by organizing Copilot chats and outputs in a persistent Notebook workspace. No other compliance impacts were identified.