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

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

[Introduction]

Starting end of February 2026, we will introduce jailbreak and root detection for Entra credentials in the Microsoft Authenticator app on both iOS and Android platforms. This change enhances security by preventing Entra credentials from functioning on jailbroken/rooted devices. All existing Entra credentials on jailbroken or rooted devices will be blocked to protect your organization. This capability is secure by default and does not require any admin configuration or control.

[When this will happen] 

General Availability (Worldwide Android) rollout begins in end of February 2026 and is expected to complete in mid-year 2026 (previously April).

General Availability (Worldwide iOS) rollout begins in April 2026 (previously March) and is expected to complete in mid-year 2026 (previously April).

[How this affects your organization]

Who is affected: All users of Microsoft Authenticator on iOS and Android whose Entra credentials are registered on jailbroken or rooted device. This is going to be a continuous check.

What will happen:

• The feature is secure by default and enabled to all customers. There is no opt-out capability..
• Users on jailbroken or rooted devices will experience the following phased rollout. An estimated gap between 2 phases is ~ 1 month.
  • Phase 1 – Warning Mode: Users receive a warning that their device is jailbroken or rooted and will be blocked in the future (screenshots 1-4): 

  

  

  

  

  • Phase 2 – Blocking Mode: Users are blocked from registering Entra credentials or signing in via Authenticator (screenshots 5-8):

  

  

  

  

• Users on non-Jailbroken or non-rooted devices will not be affected.

[What you can do to prepare]

• Notify users about this upcoming change. Users will see error messages or banners in the Authenticator app during warning or blocking phases. These screens are dismissible but indicate the device status.
• Communicate to helpdesk staff that Authenticator will become unusable for Entra accounts on jailbroken or rooted devices.
• Update internal documentation if you reference Authenticator usage.
• No admin action is required to enable or configure this feature.

Learn more: About Microsoft Authenticator | Microsoft Support

[Compliance considerations]

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

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

[Introduction]

We’re introducing endpoint Data Loss Prevention (DLP) events as a queryable data source in Data Security Investigations (DSI) in Microsoft Purview. With this update, administrators can build endpoint DLP queries directly in DSI using filters such as date range, and DSI will automatically pull files associated with those events into the investigation for analysis. This integration helps security teams examine endpoint DLP activity at scale, reducing time and effort spent triaging individual alerts and improving the ability to identify patterns and potential data exfiltration scenarios.

This message is associated with Microsoft 365 Roadmap ID 558547.

[When this will happen]

• Public Preview: Rollout begins in early June 2026 (previously late April) and completes in late June 2026 (previously early June).
• General Availability (Worldwide): Rollout begins in late July 2026 (previously mid-June) and completes in late July 2026 (previously mid-June).

[How this will affect your organization]

Who is affected

Admins and security investigators using Data Security Investigations (DSI) and endpoint Data Loss Prevention (DLP) in the Microsoft Purview compliance portal.

What will happen

• A new Endpoint DLP tab will appear in the DSI search experience, alongside the existing Query Builder and Audit tabs.
• Admins and investigators can query endpoint DLP events using date range filters (additional filters coming soon).
• Files associated with matching endpoint DLP events will be automatically added to the investigation scope for analysis using DSI’s AI‑powered tools.
• This feature will appear automatically for eligible tenants when rollout completes. No admin action is required to enable it.
• There is no user impact.

[What you can do to prepare]

No action is required. Optionally, you may:

• Review how endpoint DLP query capabilities work within DSI.
• Update internal documentation for alert triage and investigation workflows, if applicable.
• Inform security teams and endpoint DLP administrators about this new capability.

Learn more: 

• Learn about Data Security Investigations | Microsoft Purview | Microsoft Learn
  
• Learn about Endpoint data loss prevention | Microsoft Purview | Microsoft Learn

[Compliance considerations]

Updated June 19, 2026: We’ve published new information and guidance about the unification of Semi-Annual Enterprise Channel and Monthly Enterprise Channel for Microsoft 365 Apps. For more information, see Upcoming channel unification: Semi-Annual Enterprise Channel to Monthly Enterprise Channel – Microsoft 365 Apps | Microsoft Learn

[Introduction]

Beginning in July 2026, Microsoft will unify the Semi-Annual Enterprise Channel (SAEC) and Monthly Enterprise Channel (MEC) into a single enterprise-focused update channel for Microsoft 365 Apps. This change is designed to simplify update management while continuing to provide a predictable, enterprise-ready servicing experience.

Over time, SAEC and MEC have both served customers who want an enterprise-focused experience with timely updates. Unifying these channels reduces complexity and overlap, helping organizations adopt new capabilities, security updates, and quality improvements more quickly. This unified approach also supports more consistent update expectations across devices and user groups, while maintaining Microsoft’s commitment to quality, manageability, and predictable servicing.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, and DoD): These changes will go into effect on July 14, 2026, with the Patch Tuesday update release.

[How this affects your organization:]

Who is affected:

• Microsoft 365 administrators managing update channels for Microsoft 365 Apps
• Organizations currently using the Semi-Annual Enterprise Channel (SAEC)
• There is no change or impact for devices on other channels such as Monthly Enterprise Channel (MEC), Current Channel (CC), or associated preview channels

What will happen:

• Devices currently configured for SAEC will receive the same feature and security updates as published to MEC.
• Existing update policies and configurations will continue to be respected.
• There is no change to Microsoft’s commitment to predictable servicing, quality, and enterprise manageability.
• Users are not expected to experience workflow changes as a result of this update.

[What you can do to prepare:]

• No action is required. If your organization currently uses SAEC, updates will continue to be published on a monthly basis.

Optional:

• Validate your servicing workflows. Confirm that your pilot, broad deployment, and rollback processes continue to meet your organization’s requirements.

Learn more:

• Overview of update channels for Microsoft 365 Apps | Microsoft Learn 
• As we get closer to rollout, we will share additional details about how this change will appear in admin experiences and documentation.

[Compliance considerations:]

Microsoft 365 Apps update channel selection remains an admin-managed configuration. This change simplifies channel options by unifying feature updates published to SAEC and MEC. (Note: Entra ID group-based control is not introduced by this change; scoping depends on how you deploy policy today, such as Intune group assignments.)

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

[Introduction]

Microsoft is updating an existing sensitivity label setting that controls whether certain connected experiences can analyze file content. This change extends support of this label setting to additional platforms and extends coverage of the label setting to include all connected experiences that analyze content in Word, Excel, and PowerPoint, rather than a subset of these experiences.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Organizations using Microsoft Purview sensitivity labels in Word, Excel, and PowerPoint
• Users opening files that have a sensitivity label configured with “Prevent some connected experiences that analyze content”

What will happen

• Files with this label setting will not be sent to any Microsoft connected experiences for content analysis.
• Previously, this label setting blocked only a subset of connected experiences; enforcement is now expanded in Word, Excel, and PowerPoint.
• This change applies automatically to existing labels configured with this setting.
• There is no change to label configuration, and the behavior is enforced by default once the feature rolls out.

[What you can do to prepare]

No action is required if your organization already uses sensitivity labels.

Optional recommended steps:

• Review sensitivity labels that use the “Prevent some connected experiences that analyze content” setting to confirm they align with your organization’s data handling expectations.
• Inform compliance and helpdesk teams that labeled files may no longer interact with connected experiences that analyze content in Word, Excel, and PowerPoint.
• Update internal documentation if you describe how sensitivity labels affect Office app functionality.

[Compliance considerations]

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

[What and Why:]

Enterprise Preview in Microsoft Edge introduces a streamlined way for admins to validate prerelease Edge builds directly within the Stable application. This reduces deployment friction and enables faster feedback loops while maintaining user productivity. Admins gain centralized controls and visibility in the Microsoft 365 admin center, allowing them to manage preview participation, monitor their flighting population, and receive recommendations.

This message is associated with Roadmap ID 557185.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected: Admins managing Microsoft Edge Update policies and users on devices with Microsoft Edge configured for Beta or Dev channels.

Platforms/Services: 

• Microsoft Edge (Stable application)
• Microsoft 365 admin center
• Edge Management Service

What will happen:

• Users can receive prerelease Edge builds directly within the Stable application. 
• By default, users can opt out of the preview experience when allowed by policy. 
• Built-in rollback enables users to switch between prerelease and Stable versions without reinstalling Edge.
• Admins can configure preview settings, monitor flighting populations, and view recommendations in one place.
• The new EdgePreviewEnrollmentType policy introduces user opt-out control:
  • Allow opt-out: Users can switch between prerelease and Stable channels.
  • Required: Users remain on the configured prerelease channel (similar to previous TargetChannel behavior).
• If your organization currently uses TargetChannel (Beta or Dev), this change enhances flexibility by introducing user-level control.

[Action Required / Recommendations:]

No action is required before rollout.

However, we recommend that admins:

• Review your current Edge update policies (Beta or Dev channels).
• Decide if users should be allowed to opt out:
  • Set EdgePreviewEnrollmentType to Allow opt-out (default behavior)
  • Or set EdgePreviewEnrollmentType to Required to enforce prerelease participation
• Monitor your preview population in the Microsoft 365 admin center or Edge Management Service.
• Communicate the change to IT support teams, especially regarding user opt-out and rollback capabilities.

Learn more

• Get started with Enterprise Preview in Microsoft Edge | Microsoft Learn
• EdgePreviewEnrollmentType | Microsoft Learn

[Compliance Considerations:]

[What and Why:]

Microsoft Teams is introducing the ability to open message links in a new window. This enhancement brings familiar browser-like behavior into Teams, enabling users to view linked messages, chats, or channels side by side without losing context in their current conversation. This update supports improved multitasking and collaboration efficiency, aligning with Microsoft’s goal of enhancing personal and team productivity.

This message is associated with Microsoft 365 Roadmap ID 565220.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected: All users of Microsoft Teams desktop applications (Windows and Mac).

Platforms/Services:

• Microsoft Teams (Windows desktop)
• Microsoft Teams (Mac desktop)
• Not available in Teams for web

What will happen:

• Users can open links to Teams messages, chats, or channels in a separate window.
• Users can access this feature by:
  • Selecting Open in new window from the link’s More options (•••) menu, or
  • Using Ctrl + click (Windows) or Cmd + click (Mac).
• This feature is enabled by default.
• No changes to existing policies or configurations are required.
• Users can compare conversations side by side without navigating away from their current context.

[Action Required/Recommendations:]

• No action is required.
• Inform helpdesk and support teams about this new capability.
• Share a brief communication to users highlighting the new multitasking functionality.
• Update internal training or documentation if you include Teams navigation guidance.

[Compliance considerations:]

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

[What and Why]

Eligible Microsoft Fabric and Power BI users can now create support tickets directly within Microsoft Fabric from the Help pane. This update brings ticket creation into the product experience, allowing Microsoft to automatically capture relevant context (such as tenant and artifact metadata) to improve troubleshooting efficiency and reduce time to resolution. This change also aligns support workflows more closely with where users encounter issues.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected

• Microsoft Fabric users, based on tenant admin configuration
• Fabric admins managing tenant settings

Platforms/Services

• Microsoft Fabric (web)
• Power BI (web)
• Power Platform Admin Center (PPAC)

What will happen

• Users can create support tickets directly from the Help pane from anywhere in Fabric. (They don’t need to navigate to the admin portal.)
• Users attempting to create support tickets for Power BI or Fabric from the Power Platform admin center (PPAC) will be redirected to the Fabric experience.
• When a ticket is created, Fabric includes contextual metadata (such as tenant and artifact identifiers) in the support request to assist troubleshooting.
• This experience provides more contextual information and centralizes support workflows within Fabric, improving troubleshooting and shifting where users initiate support requests.
• This experience is enabled by default; admins can control which users are able to create support tickets using existing tenant settings.

[Action Required / Recommendations]

Action may be required depending on your current configuration.

• Review tenant settings to ensure:
  • Users are routed to the appropriate support experience (Microsoft support or internal help desk), and
  • The correct users are permitted to create support tickets.
• If users are redirected to an internal help desk instead of creating tickets, verify the setting is configured correctly.
• Communicate this change to your helpdesk and support teams, especially if they currently rely on PPAC for ticket creation.
• Remind users to select the appropriate support plan and severity when submitting requests.
• Update internal documentation or support procedures, if applicable.

Learn more: Publish “Get Help” information – Help and support tenant settings | Microsoft Fabric | Microsoft Learn

[Compliance considerations]

[What and Why]

Organizations can now centrally create and publish curated prompts for Microsoft 365 Copilot Chat. Rather than relying on each employee to discover effective ways of working with Copilot, administrators can shape the experience by publishing prompts that reflect organizational priorities, terminology, and approved workflows. This capability is designed to shorten the path from Copilot deployment to realized business value by guiding users toward high-impact scenarios, reducing reliance on external training, and delivering a more consistent Copilot experience across teams and geographies.

This message is associated with Microsoft 365 Roadmap ID 486695.

[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 tenants with access to Microsoft 365 Copilot experiences
• Administrators managing Copilot experiences
• Users interacting with Copilot Chat

Platforms/Services

• Microsoft 365 Copilot
• Copilot Chat (web and integrated experiences)

What will happen

• Admins can create, publish, manage, and pin organization-specific prompts from the Microsoft 365 admin center, controlling what users see in Copilot.
• Published prompts will appear directly within Copilot Chat, where users encounter them when starting a session.
• Admins must create and publish at least one prompt before curated prompts will appear in Copilot Chat for users; until then, users will not see curated prompts.
• Prompts reflect organizational priorities, terminology, and approved workflows.
• Users will have a clearer, more relevant starting point when interacting with Copilot, improving both first-run and ongoing experiences.
• Built-in analytics will show which prompts are being used and how users engage with them, helping admins optimize their prompt library over time.
• The feature is available by default when it reaches your tenant.
• There is no change to existing Microsoft 365 Copilot licensing requirements.
• Existing Microsoft 365 Copilot governance, compliance, and security policies continue to apply.

New admin experience – view 1:

New admin experience – view 2:

New admin experience – view 3:

New user experience – view 4:

New user experience – view 5:

New user experience – view 6:

[Action Required/Recommendations]

No action is required. No additional security or compliance review is needed before using this feature.

To prepare and maximize value:

• Review potential business scenarios where curated prompts could improve productivity.
• Begin drafting and publishing an initial prompt library—at least one prompt must be published for curated prompts to appear to users.
• Plan internal communications to introduce curated prompts to users.
• After rollout, publish and pin high-value prompts from the Microsoft 365 admin center.
• Monitor usage analytics to refine and improve prompt effectiveness over time.

Learn more: Organizational prompts overview | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

[Compliance Considerations]

• June 19, 2026: Windows 11, version 26H2 is available to preview through the Windows Insiders Program. 
• Second half of 2026: Windows 11, version 26H2 will be generally available. 

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

Manage retention and deletion workflows for user-owned Loop workspaces such as Copilot Pages and the Loop personal workspace when users leave the organization.

This message is associated with Microsoft 365 Roadmap ID 421612

[When this will happen:]

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

[How this will affect your organization:]

Once available, admins will be able to manage retention and deletion workflows for user-owned Loop workspaces such as Copilot Pages and the Loop personal workspace when users leave the organization. Updates will include the ability to provide temporary access to other employees or administrators to save important data before deletion policies take effect.

More details will become available closer to the release date.

[What you need to do to prepare:]

There is nothing you need to do to prepare. These changes will roll to your tenant automatically.