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

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

With this release, users can discover and add SharePoint agents directly within Microsoft Teams chats on Desktop and Mac. Agents can be added via the Add Agents and Bots option in the chat roster dropdown, which opens the in-context store for discovery and selection. This enables users to quickly bring SharePoint agents into conversations to support collaboration.

Additionally, SharePoint agents are available in the Teams Store under the Agents category, making them easier to find and deploy across Teams experiences.

This message is associated with Microsoft 365 Roadmap ID 515465.

[When this will happen]

• Targeted Release: Rolling out in mid-October 2026 (previously mid-July) and expected to complete in late October 2026 (previously late July).
• General Availability: Rolling out in late October 2026 (previously late July) and expected to complete by late November 2026 (previously late August).

[How this affects your organization]

• Who is affected: All users of Microsoft Teams on Desktop and Mac.
• What will happen:
  • Users will be able to discover and add SharePoint agents from the in-context store in Teams chats.
  • SharePoint agents will be available in the Teams Store under the Agents category.
  • Agents can be added via the Add Agents and Bots option in the chat roster dropdown.
  • No admin action is required; the feature is enabled by default.
  • Existing policies are respected; no changes to admin controls are needed.

[What you can do to prepare]

• Ensure that intended users have E3 or E5 (with Teams) licensing, and one of the following options: 
  • Microsoft 365 Copilot license OR
  • Pay-as-you-go (PAYG) separately setup for SharePoint agents on MAC.

• Inform helpdesk staff in case users have questions about accessing or using SharePoint agents.
• Share this update with users to highlight new collaboration opportunities.
• Update internal documentation if you maintain guidance on Teams agents or bots.

Learn more: Share an agent from SharePoint in Teams | Microsoft Support

[Compliance considerations]

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

Updated June 11, 2026: We have updated this post as a reminder. We’re ready to begin the General Availability (GA) rollout of the new SharePoint experience on June 15, with deployment continuing over the subsequent weeks. Based on feedback from users in the preview program, we are simplifying item-keeping experiences across SharePoint and aligning on a single Favorites gesture that is consistent with the rest of Microsoft 365.

As part of this change:

• Followed Sites will become Favorite Sites.
• Saved for Later for pages and news posts will become Favorites.

This is a naming and experience update that will be reflected across all SharePoint surfaces where these experiences appear, providing a more consistent and streamlined experience for users across Microsoft 365. Existing followed sites and saved content will be preserved and automatically transition to the Favorites experience.

Additionally, as previously communicated, we are retiring Featured Links and encouraging customers to use modern alternatives such as Global Navigation, which can be configured to surface important organizational resources and destinations.

Previous update: We began the Targeted Release (TR) rollout on May 5, with an expected ramp to 100% TR by the end of the week. All customers and users in the TR program will automatically receive the new SharePoint experience, with no option to opt out at either the tenant or user level.

• We recommend that customers explore the experience ahead of TR to ensure readiness.
• For users and tenants already opted in via EAP or Public Preview, we will preserve their current state, their experience as of Monday will remain unchanged.

[Introduction]

We are introducing a new SharePoint experience that includes a redesigned SharePoint app bar, a refreshed SharePoint start page for finding sites, content, and news, and support for AI-assisted creation, management, and discovery features. The new experience applies to all SharePoint users. Some capabilities in this experience use AI. Access to those capabilities requires a Microsoft 365 Copilot license.

This message is associated with Microsoft 365 Roadmap ID 547732.

Before the new experience rolls out broadly, it will be available as a public preview. During the preview period, administrators can enable the experience for their tenant to evaluate the changes and prepare users. When enabled during preview, the experience applies to all users in the tenant. Users may opt out of the new experience during the preview period.

When the public preview ends, Targeted Release rollout will begin, followed by General Availability (GA). Starting with Targeted Release, the new SharePoint experience will automatically apply to all tenants and users. Any tenant-level preview settings or individual user opt-outs from the preview period will be overridden, and no controls will remain. We recommend customers try the experience ahead of TR to be better prepared.

[When this will happen]

• Public Preview: Rolling out in early March 2026; expected completion by late April 2026.
• Targeted Release: Rolling out in early May 2026 (previously late April); expected completion by mid-May 2026 (previously June).
• General Availability (Worldwide, GCC, GCC High, DoD): Rolling out in mid-June 2026 (previously early May); expected completion by mid-July 2026 (previously end of July).

[How this affects your organization]

Who is affected

• All SharePoint users
• Users with a Microsoft 365 Copilot license will have access to AI capabilities included in this experience.
  

What will happen

When the new experience is enabled—either during preview or as part of the Targeted Release and General Availability (GA) rollout—users will see an updated SharePoint app bar that introduces entry points for discovering content, publishing communications, and building SharePoint solutions.

The updated app bar includes:

Discover

A refreshed start experience to find relevant sites, content, and news.

Publish 

A unified publishing hub that brings together pages, news, and campaign-style communications powered by Amplify.

Build 

A centralized place where makers can create and manage SharePoint sites, lists, libraries, and AI-powered agents from a single surface.

The app bar will also include:

• OneDrive – Provides quick access to files.
• Home – Appears when a Home site with global navigation is configured in the tenant.

Additional updates include:

• Updated page, news, library, and list experiences with improved content visibility
• Neutral theming applied across SharePoint product surfaces (site-level branding remains unchanged)

[What you can do to prepare]

If you plan to enable the preview experience:

• Enable the setting in the SharePoint admin center: Settings → SharePoint → New SharePoint Experience
• Review documentation: Enable the new SharePoint experience (preview) | SharePoint in Microsoft 365 | SharePoint | Microsoft Learn
• Review changes to the SharePoint navigation experience, including the new app bar: SharePoint App Bar
• Communicate expected UI changes to helpdesk teams and users before enabling the preview.
• Update internal documentation that references SharePoint navigation or app bar elements.

[Compliance considerations]

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

Updated June 12, 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 mid-June 2026 (previously early June) and expect to complete in mid-June 2026 (previously early June).
• General Availability (GCC): We will begin rolling out in mid-June 2026 (previously early June) and expect to complete in mid-June 2026 (previously end of June).

[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 June 12, 2026: The same set of updates will also apply to the PDF previewer. Thank you for your patience. 

[Introduction]

To provide a more consistent and predictable file viewing experience, we’re updating the user interface for text, image and zip file previewers in Outlook for Android. These changes align text, image and zip previewers with the existing preview experience for Word, Excel, and PowerPoint files.

[When this will happen:]

• General Availability (Worldwide): Rollout begins late April 2026 and completes by mid-May 2026

[How this affects your organization:]

Who is affected:

• All users viewing text, image and zip file attachments in Outlook for Android

What will happen:

• Users will see updated styling in text, image and zip file previewers to match other Office file previewers.
• The overflow action menu will:
  • Display updated icons
  • Use a revised action order consistent with Word, Excel, and PowerPoint previewers
• A new Expand button will appear in the action bar, making it easier to enter full-screen mode.
• The feature is enabled by default and does not change existing policies or workflows.

[What you can do to prepare:]

• No action is required; the update is enabled automatically
• Optionally notify users and helpdesk staff of the UI refresh
• Update internal documentation or screenshots if applicable

[Compliance considerations:]

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

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

[Introduction]

We are introducing recipient groups for eSignature in Microsoft 365. Recipient groups allow a single recipient slot to be assigned to multiple people, where the first person to sign fulfills the signing requirement. This update helps make signature workflows more reliable by reducing delays when a specific signer is unavailable, without changing existing tenant policies.

This message is associated with Microsoft 365 Roadmap ID 560822.

[When this will happen]

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

[How this affects your organization]

Who is affected

• Users who create eSignature requests in Microsoft Word
• Microsoft 365 tenants that use eSignature for Microsoft 365

What will happen

• Users can assign up to 10 people to a single recipient slot: 

  

• The first person in the recipient group to sign fulfills the signing requirement for the group.
• Signature workflows are less likely to stall due to individual signer availability.
• The feature is enabled by default and respects existing tenant policies.

[What you can do to prepare]

• No action is required from admins.
• Consider informing users who rely on eSignature workflows about this improvement.

[Compliance considerations]

Updated June 12, 2026: We have updated the timeline. 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 policy 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. Starting July 2027, unlicensed ODBs that remain unpaid will be at risk of being deleted.

[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 expanding model choice in Microsoft 365 Copilot so you can pick the right model for the job. Claude Fable 5 (preview) is available as a default-off option in Copilot Cowork (Frontier), with limited private preview extensibility in Copilot in Excel and PowerPoint.

This model is designed to support longer, more complex tasks such as multi-step knowledge work, coding, and visual reasoning.

Claude Fable 5 is off by default and admin controlled. Unlike other models currently available in Microsoft 365 Copilot, this model requires data retention by the model provider Anthropic and is subject to Anthropic terms. Organizations can choose whether and how to enable the model to evaluate these advanced capabilities.

[Rollout Schedule]

• Frontier Preview (opt-in): Beginning in early June 2026 and expected to complete in early June 2026.
• Availability may vary by region and tenant configuration.

Note: Frontier is an opt-in private and public preview program.

[Impact on your organization]

Who is affected

• Admins managing Microsoft 365 Copilot
• Users in tenants where the model is enabled

Platforms/Services

• Microsoft 365 Copilot
• Copilot Cowork (Frontier)

What will happen

• Claude Fable 5 is off by default and must be explicitly enabled by an admin.
• Admins can enable the model and scope access to specific users or groups.
• This model is a preview model with data retention.
• When enabled, users will see the message: “Some models require data retention: your prompts and responses are retained by the model provider.“
• Data used with this model is retained by Anthropic as an independent processor.
• Use of this model is subject to Anthropic terms, Data Protection Addendum, and data retention practices for Mythos-class models.
• No changes to data handling for other Microsoft 365 Copilot models.
• This model is intended for evaluation and experimentation, not production use.

[Action required / recommendations]

No action is required if you do not plan to enable this model.

If you plan to enable Claude Fable 5 (Preview):

• Review your organization’s compliance, privacy, and data retention requirements.
• Evaluate whether preview models with data retention meet your governance policies.
• Enable the model in the Microsoft 365 admin center and scope access appropriately.
• Communicate the data retention behavior and implications to users before enabling.
• Update internal documentation and helpdesk guidance.

Learn more:

• Anthropic models in Microsoft Online Services | Microsoft Support
• Get Started with Frontier | Microsoft Frontier
• Microsoft 365 Copilot release notes | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn
• Preview AI models in Microsoft Online Services | Microsoft Support

[Compliance considerations]

[What and Why]

Planner Agent chat in Microsoft Planner brings the existing Planner Agent from Microsoft 365 Copilot directly into the Planner experience as an embedded chat interface. This allows users to ask questions about their plans, identify priorities, and take action without leaving Planner.

This experience is available in basic plans in Planner.

This update improves productivity by surfacing existing AI capabilities in context, helping users manage tasks, organize work, and gain insights more efficiently.

This change does not introduce a new agent or modify how customer data is processed. It makes existing Planner Agent capabilities more accessible within the Planner workflow.

This message is associated with Microsoft 365 Roadmap ID 560532.

[Rollout Schedule]

• Targeted Release: Rollout begins in mid-June 2026 and is expected to complete by mid-June 2026.

[Impact on Your Organization]

Who is affected

• Microsoft 365 tenants where users are enrolled in the Frontier program
• Users with an eligible Microsoft 365 Copilot license

Once a tenant is enrolled in the Frontier program, eligible features may be enabled by default for users within that program.

Platforms/Services

• Planner on the web
• Microsoft 365 Copilot

What will happen

This update adds an embedded Planner Agent chat experience within basic plans in Planner and does not replace or remove any existing functionality.

• Planner Agent chat will appear as an embedded experience.
• The feature is enabled by default for eligible Frontier users.
• Access to this feature is governed by existing Planner Agent and Copilot controls. If the Planner Agent is disabled, users will not have access to this experience. Admins can manage or disable access using existing controls.
• Users can interact with the Planner Agent directly within Planner to:
  • Ask natural language questions, for example “Show my top tasks for today”
  • Identify high priority or at-risk work
  • Apply AI generated filters to focus on key tasks
  • Draft updates and manage task hierarchy through interactive task cards
  • Create structured plans organized by goals and buckets
  • Access contextual insights based on permitted Microsoft 365 data such as emails, meetings, and files

[Action Required/Recommendations]

No action is required to enable this feature.

To prepare for this rollout, you can:

• Identify users who would benefit from early access to Frontier features.
• Add those users to a Microsoft Entra ID group and configure Frontier access.
• Confirm users have eligible Microsoft 365 Copilot licenses.
• Review and configure agent settings in the Microsoft 365 admin center.
• Update internal documentation and support readiness materials.

Learn more:

• Frontier program | Microsoft 365 Copilot | Microsoft
• Manage agents in the Microsoft 365 admin center | Microsoft Learn

Additional documentation will be provided as it becomes available.

[Compliance considerations]

[What and Why]

Microsoft Teams is updating the port and domain requirements for Real-Time Messaging Protocol (RTMP)-In, which enables organizers to stream content into meetings, webinars, and town halls using external hardware or software encoders. This change improves reliability and scalability for Teams streaming scenarios.

[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

• Admins managing Microsoft Teams meetings, webinars, and town halls
• Event organizers who use RTMP-In with external encoders

Platforms/Services

• Microsoft Teams (meetings, webinars, and town halls)

What will happen

• New meetings, webinars, and town halls that use RTMP-In will require updated network access.
• Admins must allow the required ports and domain endpoints for RTMP-In streaming.
• Existing meetings, webinars, and town halls already configured with RTMP-In will continue to function through the end of 2026.
• RTMP-In continues to allow organizers to stream content into Teams from external hardware or software encoders.
• Without these updates, organizers may be unable to create or stream RTMP-In events, and newly created events may fail after mid-July 2026.

Required network endpoints:

• Ports: 50118 and 50119 (RTMP/RTMPS)
• Domain: *.rtmpingest.mcr.teams.cloud.microsoft

[Action Required/Recommendations]

Action required by mid-July 2026.

• Review your organization’s firewall and network configuration.
• Allow outbound access to:
• Ports 50118 and 50119 (RTMP/RTMPS)
• Domain: *.rtmpingest.mcr.teams.cloud.microsoft
• Validate connectivity against official Microsoft 365 endpoint and firewall guidance.
• Communicate this change to your networking and IT teams.
• Update internal documentation if you support RTMP-In streaming scenarios.

Learn more: Manage RTMP-In for Teams meetings, webinars, and town halls | Microsoft Teams | Microsoft Learn

[Compliance considerations]

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

• Browse a curated catalog of all available governance rules from a single location.
• Identify defaults and accept them quickly using the “Recommended” badge on 6 key rules.
• Add, configure, and apply rules to Environment Groups in a streamlined workflow.
• Enforce consistent governance across all environments within a group with fewer clicks.

• Rules for environment groups
• Rules Gallery

[What and Why]

Microsoft is expanding the availability of the Legal agent in Microsoft 365 Copilot in Word to Frontier users worldwide in Public Preview.

The Legal agent was previously released in Frontier preview for users located in the United States only. This update expands access globally, enabling more organizations to benefit from this capability.

The Legal agent is a vertical-specific Microsoft 365 Copilot experience designed for legal professionals, built directly into Word. It helps legal teams review and negotiate contracts by identifying risks, comparing clauses to internal playbooks, and proposing edits using Word’s native tracked changes.

This update helps reduce manual review time while keeping legal professionals fully in control of document workflows.

[Rollout Schedule]

• Frontier Preview: Available starting in mid-June 2026.
• General Availability (Worldwide): Available starting in early July 2026.

[Impact on Your Organization] 

Who is affected

• Organizations enrolled in the Microsoft 365 Copilot Frontier program
• Users with Microsoft 365 Copilot licenses, particularly legal professionals (for example, in-house counsel, contract managers, legal ops)

Organizations not enrolled in the Frontier program are not impacted.

Platforms/Services

• Microsoft Word (Copilot) – desktop and web
• Microsoft 365 Copilot (Frontier)

What will happen

• A new Legal agent will be available in Copilot Chat in Word via the “+” (plus) menu.
• Users can:
  • Review contracts to identify risks and non-standard clauses
  • Generate redlines using Word tracked changes
  • Compare clauses against internal legal playbooks
  • Analyze document sections for compliance with internal standards
  • Receive responses grounded in document content with citations
• The feature is enabled by default for tenants enrolled in Frontier.
• No separate installation is required.
• The feature is available immediately after users update to a supported version of Word.
• Availability depends on:
• Frontier program enrollment
• Microsoft 365 Copilot licensing
• There is no dedicated admin or user toggle to disable this feature
• Access is controlled through Frontier enrollment and Copilot license assignment.

[Action Required / Recommendations]

No action is required if you do not plan to use this feature.

If you plan to use this feature:

• Enroll your tenant in the Frontier Public Preview program.
• Ensure Microsoft 365 Copilot licenses are assigned to eligible users.
• Review internal legal workflows that may benefit from:
  • Contract analysis
  • Playbook-based reviews
  • AI-assisted redlining
• Communicate this capability to legal teams.
• Update internal documentation or helpdesk guidance if applicable.

[Compliance considerations]

For more information visit Get Started with Legal agent in Word and Transparency Documentation 

[What and Why]

We’ve made updates to Microsoft Defender for Endpoint on Linux network connectivity requirements.

 As part of this update, Defender for Endpoint on Linux now uses new service URLs to deliver internal configuration updates and new capabilities.

[Rollout schedule]

• General Availability (Worldwide, GCC, GCC High, DoD): Available now

[Impact on your organization]

Who is affected

• Organizations using Microsoft Defender for Endpoint on Linux devices

Platforms and services

• Microsoft Defender for Endpoint
• Linux endpoints

What will happen

• Defender for Endpoint on Linux now uses the following service URLs to deliver internal configuration updates and new capabilities:
  • Commercial: https://config.edge.skype.com/config/v1
  • DoD: https://config.ecs.dod.teams.microsoft.us/config/v1
  • GCC High: https://config.ecs.gov.teams.microsoft.us/config/v1
  • GCC Moderate: https://gccmod.ecs.office.com/config/v1
• Important:
  • You only need to allowlist the URL applicable to your tenant type.
  • URLs containing skype, teams, or office are shared Microsoft infrastructure endpoints (not tied to those products), with these terms retained as a legacy artifact for backward compatibility.
• These URLs are used to securely deliver internal configuration updates from Microsoft to Defender for Endpoint agents running on Linux devices to support the following scenarios:
  • Mitigation of critical issues – In rare cases, configuration updates can be rapidly deployed to adjust or disable specific features to contain impact while a permanent fix is developed.
  • Runtime configurations – Microsoft continuously monitors endpoint health and performance and may push internal configuration updates to optimize resource usage and improve detection accuracy.
  • Feature rollout and innovation – These URLs are used to roll out new features and enhancements in a phased manner. While capabilities are delivered through these endpoints, enabling or disabling specific features remains under customer control. For example, a feature such as Behaviour Monitoring may be made available via these URLs, but customers can choose whether to enable it.
• We understand the importance of transparency and control. While the contents of these configurations are internal to Microsoft and not externally exposed, they are validated and governed by strict security and compliance standards. These updates do not modify customer-defined policies or configurations.
• If the required URL is not allowlisted, devices may:
  • Miss critical configuration updates
  • Not receive the latest product features and enhancements
• There is no change to user experience.

[Action required or recommendations]

• Review your network configuration and ensure that the appropriate URL for your tenant type is allowlisted for outbound connectivity from Linux endpoints.
• No action is required if the appropriate URL is already allowlisted.

Learn more:

• Microsoft Defender for Endpoint streamlined connectivity URLs – commercial | Microsoft Defender for Endpoint | Microsoft Defender | Microsoft Learn
• Microsoft Defender for Endpoint streamlined connectivity URLs – US government environments | Microsoft Defender for Endpoint | Microsoft Learn

[Compliance considerations]

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

[What and why]

Users will now be able to control their channel notification settings using three presets: All new messages, Mentions and replies, and Mute. Users can further customize the selected preset to manage notifications for unfollowed threads, tag mentions, channel mentions, and team mentions within each channel, as well as control banner notifications for the channel

This gives users more control over what is important in each channel, leading to an improved triaging experience and reduced noise.

This message is associated with Microsoft 365 Roadmap ID 565132.

[Rollout schedule]

• General Availability
  • Worldwide: Rollout will begin in late July 2026 and is expected to complete in August 2026.
  • GCC and GCC High: Rollout will begin in late July 2026 and is expected to complete by early August 2026.
  • DoD: Rollout will begin in late July 2026 and is expected to complete by mid-August 2026.

[Impact on your organization]

Who is affected

•  Users in GCC, GCC High, and DoD environments using Microsoft Teams channels

Platforms and services

• Microsoft Teams across desktop, web, and mobile
• Windows, Mac, iOS, Android

What will happen

• Users will see new preset channel notification options:
  • All new messages
  • Mentions and replies
  • Mute
• Users can customize each preset to manage:
  • Unfollowed threads
  • Tag mentions
  • Channel mentions
  • Team mentions
• Existing notification behavior remains unchanged unless users modify their settings.
• The feature is enabled by default for all users.
• No changes are required to existing admin settings or policies.

[Action required]

No action is required.

Recommendations:

• Inform helpdesk teams about this change, as users may have questions about updated notification behavior.
• Update internal documentation or training materials if you reference Teams notifications.

[Compliance considerations]

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

• April 2026 – Enforcement Phase with manual rollback: With installation of the April 2026 Windows security update, default Kerberos behavior changes so domain controllers use AES‑SHA1-only encryption for accounts without explicit encryption type settings, and Enforcement mode is enabled by default on Windows domain controllers. Audit mode remains available as a manual rollback option until July 2026.
• July 2026 – Enforcement Phase: With installation of the July 2026 Windows security update, Audit mode is removed, and Enforcement mode becomes the only available behavior for supported Windows domain controllers.

[What and Why]

We are introducing new triggers in Microsoft Purview Insider Risk Management (IRM) data leak policies that incorporate signals from Microsoft Fabric, cloud storage apps (Box, Dropbox, Google Drive), and cloud services (Azure, Amazon Web Services).

These enhancements help organizations better detect and manage insider risk by expanding visibility into user activities across multi-cloud and analytics environments. This supports stronger compliance monitoring and risk detection aligned with modern hybrid data usage.

This message is associated with Microsoft 365 Roadmap ID 560399.

[Rollout Schedule]

• Public Preview: Began in early June 2026 and completes by late June 2026.
• General Availability (Worldwide): Begins in early July 2026 and completes by late July 2026.

[Impact on Your Organization]

Who is affected

• Admins managing Microsoft Purview Insider Risk Management
• Organizations using IRM data leak policies
• Tenants with activity across Microsoft Fabric or supported third-party cloud platforms

Platforms/Services

• Microsoft Purview Insider Risk Management
• Microsoft Fabric (Power BI, Lakehouse)
• Cloud storage apps (Box, Dropbox, Google Drive)
• Cloud services (Azure, AWS)

What will happen

• Admins can configure new policy triggers based on user activity in:
  • Microsoft Fabric workloads (Power BI, Lakehouse)
  • Cloud storage apps (Box, Dropbox, Google Drive)
  • Cloud services (Azure, AWS)
• These triggers:
  • Define which users enter policy scope
  • Work alongside indicators that calculate risk scores
• This expands IRM visibility to include multi-cloud and analytics scenarios.
• The feature is available within the Data leaks policy template.
• Feature availability depends on admin configuration (not automatically enforced until configured).

[Action Required / Recommendations]

No immediate action is required. To take advantage of this update:

• Review your Insider Risk Management policies in Microsoft Purview.
• Evaluate whether to incorporate new triggers for:
  • Microsoft Fabric activities
  • External cloud storage and services
• Update or create Data leak policies using the new trigger options.
• Inform security and compliance teams of expanded monitoring capabilities.

Learn more: Learn about Insider Risk Management policy templates | Microsoft Purview | Microsoft Learn

[Compliance Considerations]