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

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

You can now switch between accounts on the Copilot chat tab on iOS and Android. Simply swipe left to open the left-navigation and select from the list of supported accounts.

This message is associated with Microsoft 365 Roadmap ID 490213

[When this will happen:]

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

[How this will affect your organization:]

Currently, users are only able to access the Copilot Chat tab with their default account or privacy, even if they have other accounts that support Copilot. With account-switching on iOS and Android, users will be able to access Copilot Chat from other accounts that support Copilot, enabling them to access their chat history and graph data associated with those accounts.

iOS:

Android:

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Updated June 9, 2026: Prompt categories are now available to all customers via Public Preview in the Microsoft Copilot Dashboard in Microsoft Viva Insights. We have incorporated initial customer feedback and are continuing to evaluate additional enhancements to the prompt categories, including potential updates to the category set and underlying experience. Based on this ongoing evaluation, we will share further updates regarding future release plans, including General Availability, at a later date. Thank you for your patience. 

Prompt categories will be available in Microsoft Copilot Dashboard in Microsoft Viva Insights on the web to help you understand key Copilot use cases for your organization. In Microsoft Copilot Chat (work), which is grounded in work data, these prompt categories will include Ask and find, Catch up, Draft and brainstorm, and Other. These metrics will be added to the metrics library in the advanced insights app.

Learn more about Copilot Dashboard licensing requirements in Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

Public Preview: Now available.

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

[How this will affect your organization:]

Users enabled to view Copilot dashboard will see these updates:

1. Adoption tab: Prompt categories will be available at Viva Insights > Microsoft Copilot Dashboard > Adoption > Adoption by app > Copilot Chat (work) dropdown:

2. Impact tab: Admins can go to Viva Insights > Microsoft Copilot Dashboard > Impact > Copilot chat card > Explore more button to access the prompt categories as metrics in the Copilot impact trend section and the Comparison between groups section:

This change will be available by default.

[What you need to do to prepare:]

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

Review and assess the impact for your organization. You might consider reviewing with your works council and updating your training and documentation as appropriate.

Learn more: Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

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

[Introduction:]

We’re updating Memory in Microsoft 365 Copilot to improve personalization and enhance the user experience. With this update, Copilot will personalize responses using chat history, helping users receive more relevant and contextual replies. We’re also introducing refreshed user controls in Copilot settings to make it easier to view and manage Saved Memory. This will be available to all Copilot Chat users.

Control over personalization using chat history is also available, with details for users via the settings screen. 

[When this will happen:]

• Public Preview (Frontier): Begins rolling out mid-November 2025.
• General Availability: Begins early January 2026 (previously early November 2025) and is expected to completed in July 2026 (previously May).

[How this affects your organization:]

All users of Microsoft 365 Copilot in tenants where Memory is enabled.

What will happen:

• Copilot will use chat history to personalize responses, making interactions more tailored and helpful:

 

• Users will see a redesigned Memory settings page that improves visibility and control over what Copilot remembers.
• Existing admin and user-level Memory settings are respected. If Memory is toggled off, it will remain off.
• No changes to admin controls or policy enforcement.

[What you can do to prepare:]

• Review the updated Memory settings experience with your users once available.
• No admin action is required unless you wish to update internal documentation or training materials.

Learn more:

• Enhanced personalization control overview | Microsoft Graph | Microsoft Learn 
• enhancedPersonalizationSetting resource type | Microsoft Graph | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

We’re expanding Microsoft Purview Data Loss Prevention (DLP) controls to provide broader governance for Microsoft 365 Copilot. With this update, DLP policies that prevent Copilot from processing content based on sensitivity labels will now apply to Word, Excel, and PowerPoint files regardless of where they are stored. This enhancement responds to customer feedback requesting more consistent protection coverage across local and cloud-based file locations.

This feature is associated with Microsoft 365 Roadmap ID 557255.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Organizations using Microsoft Purview DLP to restrict Copilot processing of sensitivity-labeled content
• Admins who manage Purview DLP policies
• Users working with Microsoft 365 Copilot in Word, Excel, or PowerPoint

What will happen

• DLP policies that restrict Copilot from processing sensitivity‑labeled files will apply to Word, Excel, and PowerPoint files in all storage locations, including:
  • SharePoint
  • OneDrive for Business
  • Local device storage
  • Other storage locations accessible to Office apps
• When a DLP policy blocks Copilot processing, Copilot will not process the file’s content in Word, Excel, or PowerPoint.
• Existing DLP policies will continue to function normally; no policy migration or reconfiguration is required.
• The feature will be on by default for tenants with relevant DLP rules configured.
• Users will see consistent DLP enforcement when invoking Copilot in supported Microsoft 365 apps.

Implementation detail:

This update does not modify Copilot capabilities. Instead, Office clients and AugLoop have been enhanced so AugLoop can read a file’s sensitivity label directly from the client. Today, AugLoop retrieves the label by calling Microsoft Graph using the file’s SharePoint or OneDrive URL, which limits DLP enforcement to files stored in OneDrive and SharePoint. By enabling the client to provide the label, DLP enforcement now applies uniformly across all storage locations, including local files.

[What you can do to prepare]

No action is required to enable this feature.

If your organization uses DLP controls for Copilot, you may optionally:

• Review existing DLP policies that include sensitivity-label-based restrictions
• Update internal documentation or helpdesk guidance if needed
• Communicate this enhancement to relevant security or compliance teams

Learn about managing DLP policies: Learn about data loss prevention | Microsoft Purview | Microsoft Learn

[Compliance considerations]

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

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

[Introduction]

Microsoft Teams Rooms on Android will soon be able to join third-party meetings using Session Initiation Protocol (SIP). This capability enables seamless cross-platform interoperability, allowing users to connect to external meeting services directly from Teams Rooms on Android devices while maintaining a consistent and reliable meeting experience across diverse meeting platforms.

This message is associated with Microsoft 365 Roadmap ID 558539.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Organizations with Microsoft Teams Rooms on Android devices
• Organizations that host or join third-party meetings from shared meeting spaces
• Admins managing Teams Rooms on Android devices licensed with Teams Rooms Pro

What will happen:

• Users will be able to join supported third-party meetings (for example, Zoom or Webex) directly from Teams Rooms on Android devices when the meeting invitation includes a Session Initiation Protocol (SIP) video meeting address.
• This feature is off by default. Availability of this capability depends on Teams Rooms Pro licensing and appropriate device configuration. 

[What you can do to prepare:]

• Test the feature with your lower-ring Teams Rooms on Android devices.
• Prepare educational material for users in advance of release.
• Identify users who frequently collaborate with external organizations using third-party meeting platforms and communicate upcoming capabilities.
• Ensure that all Teams Rooms on Android devices that require this functionality are licensed with Teams Rooms Pro.
• Update internal documentation for meeting room usage if applicable.
• Communicate this change to your helpdesk and support teams.

Learn more: SIP and H.323 Dialing with Teams Rooms | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

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

• CVE-2026-45585: Windows BitLocker Security Feature Bypass Vulnerability

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

[Introduction]

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

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

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

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

What will happen:

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

[What you can do to prepare:].

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

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

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

[Compliance considerations:]

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

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

[What and Why:]

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

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

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected:

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

Platforms/Services:

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

What will happen:

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

>

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

2. Start from the Site Template Gallery

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



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

[Action Required / Recommendations:]

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

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

[Compliance considerations:]

• Account executive overview to understand the current state across accounts.
• Deal rescue to identify and unblock stalled opportunities.
• Renewal risk and expansion to protect revenue first, then grow.
• Territory patch rebalancing to decide where to double down or pull back.
• Segment and industry performance to determine where to place bets.

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

[What and Why]

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

Rollout Schedule

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

[Impact on Your Organization]

Who is affected

• Users accessing Viva Learning in Microsoft Teams mobile

Platforms / Services

• Microsoft Teams (mobile)
• Viva Learning

What will happen

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

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



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



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

[Action Required / Recommendations]

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

[Compliance Considerations]

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

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

[What and Why:]

We’re introducing a new Microsoft Secure Score recommendation in Microsoft Defender for Endpoint (MDE) to help organizations reduce unnecessary inbound exposure from the public internet. This update strengthens your enterprise security posture by giving admins clear visibility into internet-facing devices, helping validate whether exposure is expected, approved, and appropriately secured. By highlighting potential attack surface risks, this recommendation supports proactive risk reduction and aligns with Microsoft’s commitment to enterprise-ready security and manageability.

[Rollout Schedule:]

• Public Preview (Worldwide): Rollout started on June 3, 2026.
• General Availability (Worldwide): We will begin rolling out in mid-June 2026 (previously early June) and expect to complete by end of June 2026 (previously mid-June).

[Impact on Your Organization:]

Who is affected: Admins managing Microsoft Defender for Endpoint and Microsoft Secure Score

Platforms/Services: Microsoft Defender for Endpoint, Microsoft Secure Score

What will happen:

• A new Secure Score recommendation, “Reduce unnecessary inbound internet exposure on internet-facing devices,” will appear.

Screenshot: New Secure Score recommendation in Microsoft Defender:

• Admins will gain visibility into devices with observed inbound connectivity from the public internet.
• Devices or services reachable from the internet will be identified for review.
• Secure Score will reflect progress as remediation or validation actions are taken.
• The recommendation is on by default and requires no configuration to appear.
• No user experience changes.

[Action Required / Recommendations:]

No immediate action is required to enable this feature.

Recommended actions for admins:

• Review the new recommendation in Microsoft Secure Score once it appears.
• Identify devices flagged as internet-facing.
• Validate whether each exposure is expected, approved, and required.
• Follow provided remediation guidance to reduce unnecessary exposure.
• For devices that must remain internet-facing:
  • Ensure the exposure is approved, documented, and properly secured.
  • Consider applying an exception where the risk is accepted by your organization.

For more information, review documentation on Microsoft Defender for Endpoint and Microsoft Secure Score in Microsoft Learn.

[Compliance considerations:]

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

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

[What and Why:]

We’re updating how unlicensed OneDrive accounts are retained to help organizations manage storage more predictably and reduce long-term unmanaged data. This update introduces enforced lifecycle stages for unlicensed OneDrive accounts that remain unpaid for an extended period, ensuring clearer storage governance while giving admins multiple options to preserve data when needed.

[Rollout Schedule:]

General Availability (Worldwide): This change will be implemented starting early July 2026 and introduces a lifecycle with staged enforcement actions and built‑in time for admins to take action before restrictions apply.

[Impact on Your Organization:]

Who is affected:

• Tenants with unlicensed OneDrive accounts created after license removal or user deletion.

Platforms / Services:

• OneDrive for Business
• SharePoint Online

What will happen:

• Day 60: Unlicensed OneDrive becomes read-only.
• Day 93: OneDrive is archived:
  • Users cannot access the content directly.
  • Content remains available for eDiscovery and legal holds.
• Up to 12 cumulative months of non‑payment:
  
  • If the account remains unpaid and no action is taken, the OneDrive data is at risk of being deleted.
    
• If a license is reassigned or billing is enabled before deletion, the OneDrive exits retention enforcement and resumes normal behavior.
• This change is on by default and does not require tenant opt‑in.

[Action Required / Recommendations:]

Admins should review unlicensed OneDrive accounts and take one or more of the following actions as appropriate:

• Reassign a OneDrive license to the user.
• Enable pay‑as‑you‑go billing for:
  • Unlicensed OneDrive archive storage, or
  • Unlicensed OneDrive standard storage.
• Migrate content to another OneDrive or SharePoint location.
• Adjust retention policies so data is deleted when no longer required.
• Take no action if the data is no longer needed and can be deleted after the 365th unlicensed day.
• Review the following Learn article: Manage unlicensed OneDrive user accounts – SharePoint in Microsoft 365 | Microsoft Learn

No action is required if appropriate licensing, billing, or retention settings are already in place.

[Compliance considerations:]

[What and Why:]

We’re retiring the current Sora video generation experience (Sora 2) available through the Frontier program as part of our ongoing investment in next-generation video capabilities. This transition enables improved scalability, performance, and future innovation in Copilot-powered video creation. A new video experience is in development and will be communicated when available.

[Rollout Schedule:]

Retirement begins mid-June 2026 and completes by late June 2026.

[Impact on Your Organization:]

Who is affected: Organizations participating in the Frontier program with access to the Sora video generation experience

Platforms/Services: Frontier program (Sora video experience in Copilot Create)

What will happen:

• The current Sora experience in Frontier will be retired
• Users will no longer be able to access or generate new videos using Sora after retirement completion
• Previously generated videos will remain accessible to users
• No new activations or deployments of Sora in Frontier will be supported
• This change impacts only the Frontier program and does not affect other Microsoft 365 services

[Action Required/Recommendations:]

No action is required.

• Inform stakeholders about the retirement of Sora in the Frontier program
• Review any internal dependencies on the Sora video generation experience
• Monitor Message center communications for updates on the replacement video model

[Compliance considerations:]

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

[What and Why:]

We’re refreshing the Outlook Actionable Messages onboarding portal with a modernized experience and a new URL to improve usability, strengthen security, and streamline onboarding for developers and administrators. This refresh aligns with Microsoft’s enterprise-ready security standards and provides a more modern, intuitive experience for managing actionable message integrations.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected:

• Administrators and developers who manage or onboard Outlook Actionable Messages integrations.

Platforms/Services:

• Outlook Actionable Messages onboarding portal (web)
• Exchange Online / Outlook ecosystem

What will happen:

• Admins will see a refreshed onboarding portal UI with improved navigation and clarity for common tasks.
• A new portal URL will replace the existing onboarding endpoint: https://aka.ms/ActionableMessagesPortal
• Security enhancements aligned with Microsoft enterprise standards will be applied.
• The legacy portal URL will be retired after the transition period.
• There are no changes to existing actionable message functionality or runtime behavior.

[Action Required / Recommendations:]

If you manage Outlook Actionable Messages, we recommend the following actions:

• Review and update any bookmarks, scripts, or tools that reference the legacy onboarding portal URL.
• Communicate the updated portal URL and experience to developers and administrators in your organization.
• Update internal documentation or onboarding guides that reference the legacy portal.
• Visit the updated portal after rollout and validate your existing onboarding workflows.

Learn more: Get started with actionable messages in Office 365 | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

[What and Why:]

We’re introducing support in Microsoft Purview Data Lifecycle Management (DLM) to apply retention and deletion policies to Microsoft Planner content. This enhancement allows compliance administrators to manage Planner tasks using enterprise-grade governance controls, helping organizations meet regulatory and internal compliance requirements while reducing manual data management.

This change is associated with Microsoft 365 Roadmap ID 486828.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected: Compliance and IT administrators managing Microsoft Purview and Microsoft Planner.

Platforms/Services:

• Microsoft Purview
• Microsoft Planner
• Microsoft 365

What will happen:

• Admins can create and apply DLM retention policies to Microsoft Planner tasks.
• Planner tasks will be retained or deleted automatically based on their individual creation date or last modified date.
• Policies can be scoped to user and group-backed Planner plans.
• There is no immediate user experience change unless a retention or deletion policy is configured and enforced.
• Existing Purview compliance capabilities remain unchanged and are respected.

[Action Required / Recommendations:]

If you do not require retention or deletion controls for Planner:

• No action is required at this time.

If you want to manage Planner data lifecycle:

• Review your organization’s compliance and data retention requirements for Planner content.
• Configure Data Lifecycle Management retention policies in Microsoft Purview for:
  • Planner roster plans
  • Planner group-backed plans
• Update internal compliance documentation to include Planner data governance.
• Inform compliance and legal stakeholders of the new coverage for Planner content.

Compliance Considerations:

[What and Why:]

Microsoft Purview Endpoint Data Loss Prevention (DLP) is improving how file extension conditions are configured to help ensure policies are accurate, reliable, and efficient. By limiting file extension selection to supported, scannable file types, this update reduces misconfiguration risk and improves enforcement consistency across endpoints while maintaining existing protection coverage.

This change aligns Endpoint DLP configuration with supported enforcement capabilities and helps admins create policies that behave as expected.

This message is associated with Microsoft 365 Roadmap ID 562993.

[Rollout Schedule:]

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:

• Microsoft 365 administrators managing Microsoft Purview Endpoint DLP device policies.

Platforms/Services:

• Microsoft Purview
• Endpoint Data Loss Prevention
• Supported Windows endpoints

What will happen:

• Endpoint DLP now includes a pre‑curated list of supported file extensions for the File extension condition.
• Only file types that are supported and can be scanned appear in the picker.
• Free‑form text entry for file extensions is no longer available.
• Existing policies continue to enforce as they do today unless edited.
• If an edited policy contains unsupported file extensions, those entries must be removed before the policy can be saved.
• To maintain coverage for unsupported or non‑scannable file types, use the Apply restrictions to only unsupported file extensions feature. Learn more: Help protect against sharing of a defined set of unsupported files. 
• Your overall protection posture does not change with this update.

Screenshot 1: Add file extension options:



Screenshot 2: Unsupported file extension warning in Microsoft Purview policy settings:

[Action Required / Recommendations:]

• No action required if you are not modifying existing policies.
• If you plan to edit or create a policy:
  • Review your current file extension list.
  • Keep supported file extensions.
  • Remove unsupported file extensions and use Apply restrictions to only unsupported file extensions feature instead.
  • Use the curated list when adding new supported file types.

Learn more:

• Learn about Endpoint data loss prevention | Microsoft Learn (will be updated before rollout)
• Conditions supported for Endpoints | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

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

[What and Why:]

We’re updating the PDF preview experience in Outlook for iOS. This change adds support for Microsoft Information Protection (MIP)–labeled PDFs and introduces a built-in controls toolbar to improve navigation and search when viewing PDF attachments.

This message is associated with Roadmap ID 564970.

[Rollout Schedule:]

General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins in early July 2026 and is expected to complete by early September 2026.

[Impact on Your Organization:]

Who is affected: All users who view PDF attachments in Outlook for iOS.

Platforms/Services:

• Outlook for iOS (mobile)
• PDF attachment preview

What will happen:

• Users can preview MIP-labeled (protected) PDF files directly in Outlook for iOS.
• A controls toolbar appears at the bottom of the PDF preview, enabling:
• Zoom in and out
• Page navigation
• Keyword search within the PDF
• The Open in Copilot button has moved to the More (…) menu in the upper-right corner.
• The feature is enabled by default.
• No changes are made to current admin configurations or user workflows beyond the enhanced preview experience.

[Action Required / Recommendations:]

• No action is required. This feature is enabled automatically.
• Consider notifying end users about the improved PDF preview and new toolbar controls to reduce help desk inquiries.
• Update internal documentation or training materials if you reference Outlook mobile PDF behavior.

[Compliance considerations:]

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

[What and Why:]

Microsoft Purview Endpoint Data Loss Prevention (DLP) is introducing the ability to protect sensitive files even when they reside in commonly excluded Windows folders such as AppData directories and temporary folders. Previously, files stored in these excluded paths were not subjected to Endpoint DLP policy enforcement. With this update, policy checks will apply during key egress actions, including copying, printing, saving to network shares, and uploading to cloud services, helping reduce the risk of sensitive data leaving your organization from these user-writable locations. 

This message is associated with Microsoft 365 Roadmap ID 562992.

[Rollout Schedule:]

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

[How this will affect your organization:]

Who is affected: Admins and users in organizations that use Microsoft Purview Endpoint Data Loss Prevention (DLP) on Windows devices

Platforms:

• Microsoft Purview compliance portal
• Windows endpoints supported by Microsoft Purview Endpoint DLP
• Microsoft Defender anti-malware client version 4.18.26051 or later required

What will happen:

With this update, admins can extend Endpoint DLP protection to files stored in excluded Windows folders (for example, %AppData% and temporary directories) during egress activities. 

• Users in audit mode can continue their actions, which will be logged for review. 
• Users in block mode will be prevented from performing restricted actions (for example, copying to removable media, uploading to cloud services, or printing) 
• If both audit and block policies apply to a user, block takes precedence 

This change improves protection coverage by addressing scenarios where sensitive data in excluded paths may have previously gone unmonitored. 

Screenshot: Endpoint DLP settings for excluded Windows folders and file egress activities:

[Action Required / Recommendations:]

• Before enabling this feature, you must first deploy anti-malware Client version 4.18.26051 or later  
• Review excluded folder paths: Identify which excluded paths (such as AppData and temporary directories) contain or could contain sensitive files and should be added to the protected exclusion paths list.  
• Stage your rollout: Start with an audit-mode pilot to assess impact before enabling enforcement. 
• Update DLP policies: Extend existing Endpoint DLP policies to cover protected excluded folders where applicable.
• Educate users and support teams: Inform them of expected behavior changes, including potentially blocked actions such as copy, print, or upload operations.

[Compliance considerations:]

[What and Why:]

We’re introducing the first phase of a simplified, more consistent design and navigation experience in Viva Engage to help users focus on conversations and community engagement. This update aligns Engage’s web and Teams experiences with modern Microsoft design patterns, reduces visual clutter, and improves usability across screen sizes.

[Rollout Schedule:]

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

[Impact on Your Organization:]

• Who is affected: All users who access Viva Engage on the web or in Microsoft Teams.
• Platforms / Services: Viva Engage (Web), Viva Engage app in Microsoft Teams.

What will happen:

• Users will see an updated layout and navigation with consistent design patterns across Viva Engage pages on web and in Microsoft Teams.
• A more consistent right-side panel will appear across all pages, showing the most relevant information alongside conversations to keep conversation content front and center.

Screenshot 1: Home feed with the new right-side panel on a wide screen:



Screenshot 2: Home feed with the new right-side panel on a narrow screen:



Screenshot 3: Community page with reconsolidated modules on right-side panel for community members: 



Screenshot 4: Community page with reconsolidated modules on right-side panel for community admins:



Screenshot 5: Membership page with tabs for Settings, Members, Agents for community admins when clicked on the right-side panel for People:



• On the web, users will see a better-fitting layout:
  • A wider content area and right-side panel on larger screens.
  • A narrow mode of the right-side panel on smaller screens.
• Community navigation is simplified:
  • Redundant or empty entry points are removed.
  • Existing modules are consolidated from the header into the right-side panel.
  • Modules that are not relevant to a community (for example, events or campaigns when there is nothing to show) are hidden automatically
  • In a community, users will see a dedicated membership page, replacing the previous Members panel. Community admins will see additional tabs for Agents, and Settings.
• Two older, low-use modules are removed from the community right-side panel:
  • The intelligent importer for populating questions and answers.
  • Community resources for the linked SharePoint library and site. This remains available through the overflow menu in the Files tab.
• The update is enabled by default. No admin configuration or policy changes are required.

[What and Why]

Copilot Notebooks will be available in Microsoft 365 Copilot Chat for users with Copilot Chat (Basic) and M365 Copilot (Basic) experiences. This update expands Copilot Notebooks beyond users with a Microsoft 365 Copilot add-on license to include additional Copilot Chat users. Copilot Notebooks provides a persistent, AI-powered workspace where users can organize content, add references, and interact with Copilot to reason over their materials in one place.

[Rollout Schedule]

• General Availability (Worldwide): Rollout will begin in mid-June 2026.

[Impact on Your Organization]

Who is affected

• Users with access to Copilot Chat (Basic) and M365 Copilot (Basic) experiences
  • Copilot Notebooks availability varies by endpoint.
• Admins managing Copilot, Loop, and SharePoint storage

Platforms/Services

• Microsoft 365 Copilot Chat (web)
• Microsoft Loop / SharePoint Embedded
• Web, desktop, and mobile

What will happen

• Copilot Notebooks will be available to eligible users in Microsoft 365 Copilot Chat. This includes users with:
  • Copilot Chat (Basic)
  • M365 Copilot (Basic)
• Copilot Notebooks in OneNote will not be available to Copilot Chat (Basic) users at this time.
• Users can create persistent notebooks to organize content with Copilot.
• Notebook content is stored in user-owned SharePoint Embedded containers shared with Microsoft Loop.
• These containers appear as “Loop” in the SharePoint admin center, PowerShell, and Microsoft Purview.
• Notebook content counts toward your organization’s SharePoint storage quota.
• Existing admin configurations and policies for Copilot Notebooks and Loop (including Cloud Policy) are respected.
• The feature is enabled by default where Copilot Notebooks is allowed.
• Documentation describing Copilot Notebooks availability will be updated to reflect this change.

[Action Required / Recommendations]

No immediate action is required.

You may want to:

• Review your Copilot Notebooks and Loop configuration to ensure alignment with your organization’s policies.
• Review SharePoint storage usage, as Copilot Notebooks content contributes to tenant storage.
• Inform helpdesk and end users about this new capability.

Learn more:

• Admin policies for Copilot Pages and Copilot Notebooks | Microsoft 365 | Microsoft Learn
• How Copilot Chat works with and without a Microsoft 365 Copilot license | Microsoft Support
• Requirements for Copilot Pages and Copilot Notebooks | Microsoft 365 | Microsoft Learn

[Compliance considerations]

[Introduction]

Microsoft 365 Copilot in Word now includes additional capabilities that are native to Word and support complex document edits. These capabilities allow users to work with tracked changes, comments, document structure, and page elements while respecting existing formatting and preserving collaboration history.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Users with Microsoft 365 Copilot using Word on Windows desktop and Mac
• Public Preview is available to eligible preview and Frontier program participants

What will happen

• Copilot enables Track Changes with word-level precision, with changes visible by default.
• Users can turn on Track Changes from Copilot.
• Copilot supports creating, reading, replying to, and managing comments anchored to document text.
• Users can insert and update a Table of Contents using Word heading styles.
• Copilot can manage headers, footers, columns, margins, and dynamic fields such as page numbers and dates.
• Copilot shows progress messages for multi-step edits in real time.
• Changes are made directly in the document while preserving formatting and collaboration history.
• These capabilities are available by default to eligible Copilot users in Word.

[What you can do to prepare]

No action is required

You may want to:

• Inform users about expanded Copilot capabilities in Word.
• Review example prompts to understand usage scenarios.
• Update internal documentation for document collaboration workflows if applicable.

Example prompts:

• Revise with precision. Turn on Track Changes and tighten the Executive Summary. Clarify vague words and spell out acronyms without rewriting entire sentences unless necessary.  
• Flag items for review. In the Risk Factors section, flag unclear content and add comments for Finance validation or legal signoff based on what came up in last week’s review meeting. 
• Format for readability. Create a Table of Contents, add a header with the document title and today’s date, and include page numbers in the footer.
• Review pending changes. Go through all unresolved tracked changes and comments and create a short ‘Review Summary’ section at the top that captures (1) proposed changes in the document and (2) open questions from comments. 

Learn more: Copilot in Word: New Capabilities for Document Workflows | Microsoft Community Hub

[Compliance considerations]

[What and Why]

We’re adding search templates to Microsoft Purview Data Security Investigations to provide pre-configured search queries for common data security scenarios such as data exfiltration, compromised mailboxes, personal data exposure, and risky AI interactions. These templates help investigators quickly and consistently scope investigations in just a few clicks instead of manually building queries, reducing setup time and lowering the barrier for less-experienced analysts. Users can select a template, provide minimal inputs (such as a user or site), and begin their investigation.

This message is associated with Microsoft 365 Roadmap ID 560326.

[Rollout Schedule]

General Availability (Worldwide): Available now

[Impact on Your Organization]

Who is affected

Security analysts and investigators using Microsoft Purview Data Security Investigations

Platforms/Services

• Microsoft Purview (web)
• Data Security Investigations solution

What will happen

• Investigators can start a new investigation using prebuilt templates instead of creating search queries from scratch.
• Templates cover common data security scenarios and require only minimal inputs (for example, user, mailbox, or SharePoint site) to start an investigation.
• Investigations are automatically scoped and ready to run once inputs are provided.
• This reduces manual setup time and helps standardize investigation workflows.
• Existing investigations and custom queries are not affected.
• The feature will be available by default where Data Security Investigations is enabled.

Screenshot – Creating an investigation from a template in Data Security Investigations: 

Typical workflow:

1. Create a new investigation in Data Security Investigations.
2. Select a template that matches your scenario.
3. Provide the required inputs.
4. Run the query to open a scoped investigation.

[Action Required/Recommendations]

No admin action is required.

Recommended actions:

• Inform your security and investigation teams about this capability
• Encourage teams to use templates to standardize investigation workflows
• Review internal investigation procedures and update documentation if needed

Learn more:

• Data Security Investigations | Microsoft Purview
• Learn about Data Security Investigations | Microsoft Purview | Microsoft Learn

[Compliance considerations]

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

• This security update includes improvements that were a part of update KB5089573 (released May 26, 2026).
• This update expands high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Devices receive the new certificates only after demonstrating sufficient successful update signals, maintaining a controlled and phased rollout.
• This update includes a resolution for CVE‑2026‑45585 (BitLocker security feature bypass). The mitigation script remains part of the guidance and does not need to be reverted.