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

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

Coming soon to Microsoft Teams: When users connect to their organization’s Wi-Fi, Teams can automatically check them in to a building or a reserved desk. This makes it easier for users to coordinate work with their coworkers and connect in person.

This feature is off by default in every tenant and requires tenant admins you to take action to turn it on and configure it. After you turn it on, end-users remain in control and can choose whether to share their work location with their coworkers.

This message applies to Teams for Windows and Teams for macOS.

This message is associated with Microsoft 365 Roadmap ID 488800.

[When this will happen:]

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

[How this will affect your organization:]

This feature allows you to map Wi-Fi access points (BSSIDs) networks and devices to buildings, which allows your users to have their work location automatically updated when they connect. This is a major improvement over the current experience which relies on end-users to manually set their work location. When this feature is configured and enabled, Teams can automatically update the work location of users who connect their laptop to your organization’s Wi-Fi network or peripherals. The feature can leverages the mapping between your building names and your Wi-Fi networks to set the work location of your users to the right building. It can also leverage mappings to specific peripherals, such as monitors. Teams uses the same policy to enable or disable automatic updates of work location for Wi-Fi and peripherals. Learn more: New-CsTeamsWorkLocationDetectionPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn

Teams will not update the location of your users if they connect after their working hours (which they can configure in their Microsoft Teams or Outlook Calendar). Also, their work location will be cleared at the end of their working hours.

[What you need to do to prepare:]

Wi-Fi check-in is off by default, but it can greatly improve the experience of your users. We recommend turning it on and configuring it in your tenant.

Update as of June 2, 2026 – We have updated the timeline. Thank you for your patience. 

Migration of channels is complete with a few pending channels for which we have shared more information here for admin remediation. Admins must take action within 30 days, by end of July, 2026, to remediate specific private channel configurations that are currently not eligible for migration. There are two impacted scenarios.

• The first includes private channels with no users, where the roster is empty and the channel is inaccessible to any tenant user.
• The second includes private channels that contain only guest users and no in-tenant owners. In both cases, these channels cannot be migrated in their current state.

To complete migration of these channels, admins are required to add at least one in-tenant user as an owner to each affected private channel by end of July, 2026. This ensures the channels have valid ownership and meet requirements. If no action is taken by end of July 2026, impacted channels will be soft deleted and remain recoverable for 30 days. After this period, they will be permanently deleted. All deletions will continue to honor applicable retention policies, legal holds, and compliance requirements.

To identify impacted channels, admins can use the updated powershell cmdlet Get-TenantPrivateChannelMigrationStatus – which now provides per-channel details for channels in the above state. Once identified, admins can use Microsoft Graph APIs to add in-tenant users as channel owners and complete remediation. Please see FAQ below for sample response and additional data.

We are in the process of expanding higher limits for membership and number of private channels in private channels as well as meeting support, targeting completion in May 2026.

New limits for private channels will rollout starting late April 2026. Private channels not yet migrated would not receive new limits until their migration is complete.

In response to customer feedback, we are introducing enhanced flexibility, greater scalability, and streamlined compliance management for private channels in Microsoft Teams.

Note: It is important for compliance managers to review and take appropriate action before migration starts for these changes to private channels.

[What’s changing?]

Private channels will transition use a channel mailbox instead of individual user mailboxes.

Organizations with compliance policies (retention, legal hold, data loss prevention, or eDiscovery) for private channels must review these policies and must apply policies to the Microsoft 365 group for the channel’s team before migration begins to ensure continuity of the policy for a private channel. Existing policies will continue to apply to user mailboxes; post-migration, new data will be governed by policies on the group. Note that policies applied to the team’s group can apply to all channels in the team.

After the transition to updated private channels in your organization, private channels will be updated as follows.

1. Private channels are no longer limited to 30 per team. Instead, private channels can be added up to the limit of 1000 total channels per team.
2. Private channels can now have up to 5000 members, instead of 250.
3. Meetings can now be scheduled in private channels.
4. Compliance policies for private channels are part of the team’s group policies instead of the individual user level.

The migration of private channels will begin in early October 2025 and continue through late April 2026 (previously March). During this period, private channels will continue to operate normally. Admins and compliance managers should complete any required policy changes by October 2025, before the migration begins. Changes to private channel limits and meeting scheduling will follow in late April through early May 2026 (previously early April).

As part of this change, newly created private channels will not be created with a document library by default; the root folder is used as a default location for any new files.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out private channel migration early October 2025 (previously late September) and expect to complete by late April 2026 (previously March). Updated channel limits and meeting scheduling will complete in early May 2026 (previously April). Restricted clouds rollout will begin in April 2026 (previously March).

[Action required by compliance managers and admins]

1. Purview eDiscovery and Legal Hold

With this change, private channel data will move from user mailboxes to the group mailbox, aligning with how shared channels data is stored. Previously, legal holds were applied to user mailboxes since private channel data resided in each member’s mailbox. Post-migration, the latest version of private channel message data from each user’s mailbox is moved to the private channel’s group mailbox. Message edits and deleted messages will not be copied into the group mailbox.

Note: For users on hold, copies of message edits and deleted messages will remain in the user’s preserved library folder until the hold expires, while the latest version of private channel message data from each user’s mailbox is copied to the private channel’s group mailbox.

Before migration

If a legal hold exists for a private channel, admins must also apply the policy to the team’s group, in addition to the policy already applied to users’ mailboxes, in order for a hold to apply to new data generated and stored in the private channel’s mailbox. Note that policies applied to the team’s group can apply to all channels in the team.



Screenshot 1: Setting up a new hold in Microsoft Purview compliance portal.

After migration

For existing holds admins will need to ensure that the hold is applied to the user mailbox as well as the new group mailbox, in order for a hold to apply to existing and new message data. Any new legal holds will need to be applied to the group.

For complete eDiscovery, include both the private channel’s users’ mailboxes and the team’s group mailbox to retrieve pre-migration messages, message history, and post-migration new content.



Screenshot 2: Configuring an eDiscovery search in Microsoft Purview compliance portal.

2. Purview Data Loss Prevention (DLP)

With this change, private channel messages will be included as a part of the DLP policy scoped to the private channel’s team’s group, as opposed to the user mailbox.

Before migration

Admins must modify the “Teams chat and channel messages” policy for private channels to add the team’s group containing the private channel, in addition to the user mailbox, in order to include new private channel messages in a policy. Note that policies applied to the team’s group can apply to all channels in the team.

After migration

Ensure that “Teams chat and channel messages” policy for private channels is scoped to the team’s group containing the private channel.



Screenshot 3: Configuring a data loss prevention policy in Microsoft Purview compliance portal.

3. Purview Retention Policy

After this change, creation of new private channel-specific policies will not be possible in the Purview portal. Instead, “Teams channel messages” policies applied to the team’s group will now include private channels. Existing private channel policies will remain in effect and preserve all held message data in user mailboxes. Editing of existing policies will not be supported but policies can be removed.

Before migration

Apply current private channel retention policies (previously on user mailboxes) to Teams channel messages to include the team’s group, in order to include new private channel messages in a policy. In Microsoft Purview compliance portal, go to solutions > Data Lifecycle Management > Retention policies. Note that policies applied to the team’s group can apply to all channels in the team.

After migration

If the parent team’s group retention policy differs from the private channel’s policy, create a new or equivalent policy to ensure consistent retention.



Screenshot 4: Configuring “Teams channel messages” for a retention policy in Microsoft Purview compliance portal.




4. Microsoft policies for Optical Character Recognition

Before Migration:

• In Microsoft Purview compliance portal, go to Settings, -> Optical character recognition (OCR), -> Select locations and scope to [1] all users and groups or [2] specific users and groups

After Migration:

Set the settings for “all users and groups” to cover private channels as specific users and groups are not supported.

Frequently asked questions

1. How can admins identify a user’s private channel memberships?
   • Use Teams Admin Center under team settings, or run PowerShell: Get-TeamChannelUser to list members.
2. When is compliance manager action required?
   • If a policy (legal hold, eDiscovery, retention, DLP) applied to a user’s mailbox, in order to include private channel messages, differs from the team policies for the team hosting the private channel. Policies must be applied to the team’s group in order to include new private channel messages in a policy. Note that policies applied to the team’s group can apply to all channels in the team.
   • During eDiscovery for users on hold or during migration, search both user mailbox and group mailbox for complete data on a private channel.
3. What if no action is taken?
   • User-level policies will not apply to a private channel’s new message data. Team-level policies will apply to private channels.
4. Why isn’t Microsoft automatically applying policies from user mailboxes to a private channel’s team?
   • Tenant admins and compliance managers must assess and apply policies as needed. Group policies apply to all channels in the Team. Some user mailbox policies are intended for all of a user’s messages, and some are intended for private channel messages. Each organization must review and decide on policies.
5. Is there any impact to end users?
   • During migration, users may see duplicate search results in Teams searches—both links will navigate to the same content in Microsoft Teams.

When will migration happen for my tenant and how long will it take?

Migration can start or end at different times for each tenant during the rollout period and can take some weeks depending of the tenant. To track progress, a new PowerShell command is available for tenants to check whether their migration has started or is completed.

The command will be Get-TenantPrivateChannelMigrationStatus

Sample Response

TenantId                     : <tenantId>

MigrationStatus              : RequiresAdminAttention

MigrationStartTimeStamp      : 2/10/2026 6:48:20 AM

MigrationCompletionTimeStamp :

Details                      : (see parsed JSON below)

Parsed Details JSON

{

  “totalChannels”: 10,

  “migratedChannels”: 6,

  “failedChannels”: 1,

  “ownerlessChannels”: 2,

  “remainingChannels”: 1,

  “ownerlessChannelsDetails”: [

    {

      “channelThreadId”: “<channelId>@thread.tacv2”,

      “teamId”: “<teamId>”

    },

    ]

}

Note: The Details field is returned as a single JSON string. The formatted version above is shown for readability.

Please refer to this blog post for more information: New enhancements in Private Channels in Microsoft Teams unlock their full potential 

We appreciate your attention to this important update.

Please refer to this blog post for more information: New enhancements in Private Channels in Microsoft Teams unlock their full potential 

We appreciate your attention to this important update.

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

[Introduction]

We’re adding a new PowerShell cmdlet that lets administrators change the organizer of an existing meeting or meeting series in Exchange Online. This feature supports continuity when a meeting owner changes roles, goes on leave, or is offboarded—removing the need to recreate long‑running series. After the transfer, the new organizer can update meeting properties, and attendees within the tenant won’t need to re‑RSVP.

A future release will enable users to change the organizer directly in Modern Calendar experiences in Outlook on the web, the new Outlook, and Teams. For user‑initiated transfers, the new organizer must accept the meeting before the transfer completes.

This message is associated with Microsoft 365 Roadmap ID 554937.

[When this will happen]

General Availability 

• Worldwide and GCC: We will begin rolling out in late June 2026 (previously mid-May) and expect to complete in July 2026 (previously late June).
• GCC High and DoD: We will begin rolling out in July 2026 (previously mid-May) and expect to complete in August 2026 (previously late July).

[How this affects your organization]

Who is affected:

• Administrators managing Exchange Online
• Meeting organizers and attendees in your tenant may see updated organizer information when applicable.

What will happen:

• Administrators can use a new PowerShell cmdlet to change the organizer of an existing meeting or meeting series.
• The new organizer will have full control of the event, including recurrence, description, attendees, and meeting details.
• For attendees within the tenant, the existing event on attendees’ calendars will be silently updated to reflect the new organizer. These attendees won’t need to decline or reaccept the meeting.
• Attendees outside the tenant will receive 2 meeting messages – one ending the series with the previous organizer and another inviting them to a series with the new organizer. These attendees should reaccept the meeting.
• Meeting history is preserved, supporting continuity and reducing abandoned meeting series.
• This feature is enabled by default; no configuration is required.

No action is required. The feature will roll out automatically.

To prepare:

• Review upcoming public documentation for the cmdlet when it becomes available (a link will be added to this message).
• Update internal processes for organizer transitions, such as role changes or offboarding.
• You may test the cmdlet ahead of the user‑initiated organizer change experience coming to Outlook on the web, new Outlook, and Teams.

[Compliance considerations]

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

Updated June 2, 2026: We have updated the content and timeline. We are in the process of correcting an issue with setting the policy. We expect to complete in early July. Thank you for your patience.  

[Introduction]

We’re adding a new Exchange Online admin policy that gives admins more control over the default Mail Compose and Reply setting that determines whether commas are used as recipient separators.

This message is associated with Microsoft 365 Roadmap ID 557676.

[When this will happen]

• General availability (Worldwide): Rollout will begin in early April 2026 and complete by early July 2026 (previously mid-May).

[How this will affect your organization]

Who is affected

• Exchange Online administrators in New Outlook for Windows and Outlook for Web
• All users composing or replying to email in Outlook where no per‑user override is configured

What will happen

• A new admin policy will be available to set the tenant‑wide default for “Use commas as recipient separators.”
• Admins can choose whether the default is on or off for all users.
• If the policy is in effect, all users will have their setting default to the admin’s choice.
• Users may still toggle this setting in their Outlook client after the policy is set: 

  

• This update is especially useful for organizations whose contacts commonly use “Last name, First name” formats.
• No changes will occur automatically—tenants will retain existing behavior unless an admin modifies the policy.

[What you can do to prepare]

No action is required. If desired, you may configure the new admin policy after rollout if you want to establish a consistent default. You can set this value via Powershell with the command “Set-Organization Config -RecipientDelimeters <Boolean>.”

You may also consider the following actions: 

• Review your organization’s preferred recipient formatting conventions.
• Update internal documentation if your helpdesk or user‑training materials reference this setting.

[Compliance considerations]

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

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

[Introduction]

Intelligent summaries in Copilot Dashboard help you quickly understand what’s driving Copilot adoption in your organization. These AI‑generated insights highlight key usage trends, areas of success, and opportunities where focused attention can accelerate value. Suggested prompts guide deeper exploration of underlying drivers and adoption patterns.

This message is associated with Microsoft 365 Roadmap ID 557681.

[When this will happen]

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

[How this will affect your organization]

Who is affected

• Admins using the Microsoft 365 Copilot Dashboard in Microsoft Viva and Microsoft 365

What will happen

• Intelligent summaries will appear automatically in the Copilot Dashboard:

   

• Admins will see AI‑generated insights that highlight adoption trends and key usage patterns.
• Suggested prompts will be available to help admins drill into specific drivers and areas of opportunity.
• No configuration changes are required; the feature is on by default for eligible tenants.
• Existing admin controls and permissions remain unchanged.
• There is no user workflow impact.

[What you can do to prepare]

No action is required before rollout.

If helpful for your organization, you may:

• Notify helpdesk or training teams about the new summaries.
• Update internal documentation that references the Copilot Dashboard.
• Review updated online documentation, which will be refreshed as rollout begins in late April.
• If you choose not to use this feature, you can roll back by disabling intelligent summaries using available admin controls.

[Compliance considerations]

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

Updated June 3, 2026: We’ve decided not to move forward with the planned rename of “Surveys agent” to “Forms agent.” As a result, organizations that previously saw “Forms agent” may notice it reverting back to “Surveys agent.” There is no impact to functionality at this time, and no admin action is required. Future updates to the standalone agent experience in Microsoft 365 Copilot will be communicated through a separate Message Center post. We apologize for any confusion.

[Introduction]

To better align with Microsoft Forms branding and improve clarity for customers, the Surveys agent in Microsoft 365 Copilot is being renamed to Forms agent. This update is a naming and visual refresh only and does not introduce any functional changes. The rename helps users more easily associate the agent with Microsoft Forms capabilities.

Screenshot: The newly named agent provides the same experience:

[When this will happen:]

• General Availability (Worldwide): We will begin rolling out in late April 2026 and expect to complete by late May 2026.
• During a transitional period, users will see “Forms (formerly Surveys)” before the agent appears as “Forms.”

[How this affects your organization:]

Who is affected:

• All users who access the Surveys agent in Microsoft 365 Copilot
• A Microsoft 365 Copilot (Premium) license is required to use this feature

What will happen:

• The Surveys agent name will change to Forms agent.
• For a limited time, the agent will appear as “Forms (formerly Surveys).”
• The agent icon will update to align with Microsoft Forms branding.
• No functional changes to survey creation, distribution, or analysis.
• The feature remains enabled by default with no policy changes required.

[What you can do to prepare:]

No action is required.

We recommend the following optional steps:

• Inform helpdesk and support staff about the rename to reduce potential user confusion.
• Update any internal documentation or training materials that reference the “Surveys agent.”
• Share a brief internal notice with users highlighting that only the name and icon are changing.

[Compliance considerations:]

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

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

[Introduction]

Authoritative Sites enables administrators to designate specific SharePoint sites as trusted sources of organizational information. By prioritizing content from these sites in Copilot Chat and Copilot Search, this feature improves content reliability, enhances search relevance, and helps users quickly find accurate company information. This capability supports stronger governance and aligns Copilot responses with verified organizational content.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• SharePoint Online administrators
• Microsoft 365 administrators managing Copilot and search experiences
• Users interacting with Copilot Chat and Copilot Search
• A Microsoft 365 Copilot (Premium) license is required to use this feature

What will happen:

• Admins can designate SharePoint sites as authoritative using PowerShell.
• Content from authoritative sites will be prioritized in Copilot Chat responses and Copilot Search results.
• Users will see clearer indicators of trusted content in the user experience.

Screenshot: Example showing results labeled “From your organization,” helping users quickly identify trusted, internal content:



• The feature is off by default until configured by an admin.
• No changes occur to existing SharePoint permissions or content access.
• Improved relevance and trust in AI-driven responses grounded in authoritative content.

[What you can do to prepare:]

• Identify key SharePoint sites (for example: HR, Legal, Communications) that should be marked as authoritative.
• Configure authoritative sites using SharePoint Online PowerShell. Before running the commands, ensure the latest SharePoint Online Management Shell is installed.

Set-SPOSite -Identity "https://<tenant>.sharepoint.com/sites/<siteName>" -IsAuthoritative $true

• Validate configuration in Copilot Search and Chat experiences.
• Pilot with a limited group of users.
• Gather feedback and refine site selection.
• Update internal documentation and inform helpdesk teams.
• Review the following Learn article: SharePoint Authoritative Sites in Copilot Search

[Compliance considerations:]

[What and Why]

We are introducing a new category of agents called Autopilots—always-on agents that work autonomously, with their own identity, and act on your behalf within the permissions and policies you set. Microsoft Scout is our first Autopilot. Integrated across the Microsoft 365 apps your users rely on every day and powered by Work IQ, Microsoft Scout stays connected to user priorities, monitors what matters, and moves work forward across Teams, Outlook, OneDrive, and SharePoint—while respecting the security, identity, and governance guardrails defined by your organization.

Built on OpenClaw open-source technology and enterprise-grade controls, Microsoft Scout is available today through Frontier as an early desktop experience on Windows and macOS—the same experience Microsoft employees have been using—giving enrolled customers a chance to explore how Autopilots fit into their workflows.

Learn more at Introducing Microsoft Scout: Your always-on personal agent | Microsoft 365 Blog and Microsoft Scout (Frontier) documentation | Microsoft Learn 

[Rollout Schedule]

• Frontier (Preview): Available now for enrolled customers on Windows and macOS
• General availability: Broader rollout timing will be communicated at a later date

[Impact on Your Organization]

Who is affected

• Organizations enrolled in Frontier
• IT admins managing Intune, identity, and access controls
• Microsoft 365 admins
• End users who meet licensing and admin-configured prerequisites

Platforms / Services

• Microsoft 365
• Microsoft Scout desktop app (Windows, macOS)
• Microsoft Intune (policy configuration)
• GitHub Copilot (required for AI credit billing)

What will happen

• A Microsoft Scout desktop app will be available to tenants enrolled in Frontier.
• The feature is OFF by default and requires admin enablement.
• Users cannot sign in until all required admin prerequisites are completed.
• The Scout app runs locally on the user’s device and uses the user’s identity to operate.
• Access is gated by admin configuration, enrollment, and attestation.

[Action Required / Recommendations]

Admin actions (required)

• Configure required device and access policies in Intune.
• Complete the required admin opt-in and attestation (to be provided during setup) before enabling Microsoft Scout. This step is required due to data flows outside Microsoft 365.
• Ensure eligible users have appropriate GitHub Copilot licensing.

User actions

• Download and install the Microsoft Scout app (Frontier).
• Download Microsoft Scout: https://aka.ms/msscout 
• Sign in with a work account (after admin enablement).
• Sign in with a GitHub account.

Recommendations

• Review this feature with security and compliance stakeholders before enabling.
• Inform helpdesk teams that sign-in failures typically indicate missing prerequisites.
• Share enablement guidance with pilot users to set expectations for the Frontier experience.

Learn more: 

• Introduction to billing and licensing | Get started | Billing and payments | GitHub Docs
• Introducing Microsoft Scout: Your always-on personal agent | Microsoft 365 Blog
• Microsoft Scout (Frontier) documentation | Microsoft Learn
  
• Step 1: Set up Microsoft Intune | Microsoft Intune | Microsoft Learn

[Compliance considerations]

[What and Why]

We are performing planned maintenance to support upcoming updates to PowerPoint Live in Microsoft Teams, which will begin rolling out on June 30, 2026. To keep Teams Rooms aligned with these updates, ensure devices are running the latest supported app versions.

[Rollout Schedule]

Teams Rooms on Windows General Availability

• Worldwide and GCC:  Already available now.
• GCC High: We will begin rolling out in early June 2026 and expect to complete by mid-June 2026.
• DoD: We will begin rolling out in early June 2026 and expect to complete by mid-June 2026.

Teams Rooms on Android General Availability

• Worldwide and GCC: We will begin rolling out in mid-June 2026 and expect to complete by late June 2026.
• GCC High: We will begin rolling out in early July 2026 and expect to complete by mid-July 2026.
• DoD: We will begin rolling out in early July 2026 and expect to complete by mid-July 2026.

[Impact on Your Organization]

Who is affected

• Organizations using Microsoft Teams Rooms devices

Platforms/Services

Microsoft Teams

• Teams Rooms on Windows
• Teams Rooms on Android

What will happen

• Teams Rooms devices running outdated app versions may not fully support PowerPoint Live experience, including:
  • Synchronized media playback
  • Viewing real-time inking and annotation
• There is no change to existing admin policies.
• Functionality remains consistent once devices are updated.

[Action Required/Recommendations]

To maintain PowerPoint Live functionality, complete the following:

• Update Teams Rooms devices to supported versions:
  • Windows: Version 5.6.135 (available now)
  • Android: Version 1449/1.0.96.2026124903 (available mid-June 2026)
• Complete updates before June 30, 2026.
• Review device update processes to ensure compliance across all meeting rooms.
• Notify IT support/helpdesk teams of potential functionality impact if devices are not updated.

[Compliance Considerations]

[What and Why:]

To strengthen security and align with modern identity standards, OneDrive for iOS and Android will no longer support sign-ins using SharePoint Server on‑premises accounts. This change reflects Microsoft’s continued investment in enterprise-ready security, ensuring mobile access to files is protected by modern authentication, conditional access, and ongoing security updates. Personal Microsoft accounts and Microsoft 365 work or school accounts are not affected.

This update also aligns with the upcoming end of support for SharePoint Server 2016 and 2019 on July 14, 2026, helping organizations transition to supported, secure platforms.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected:

• Organizations with users who sign in to OneDrive mobile apps (iOS or Android) using SharePoint Server on‑premises accounts.

Platforms/Services:

• OneDrive for iOS
• OneDrive for Android
• SharePoint Server on‑premises (2016, 2019)

What will happen:

• OneDrive mobile apps will block sign-in using SharePoint Server on‑premises credentials.
• Users must sign in with a modern identity:
  • Microsoft 365 (work or school) account
  • Microsoft Entra ID (Azure AD) account
• Personal Microsoft accounts and existing Microsoft 365 sign-ins are unaffected.

[Action Required / Recommendations:]

• Identify users using OneDrive mobile with on‑premises accounts.
• Migrate identities to Microsoft 365 or Microsoft Entra ID.
• Plan SharePoint modernization, including migration to SharePoint Online where applicable.
• Communicate this change to helpdesk staff and end users.
• Update internal documentation related to OneDrive mobile access.

[Compliance considerations:]

[What and Why:]

We’re improving search behavior when users use the SharePoint app inside Microsoft Teams. When users search from Teams while they’re in the SharePoint app (also known as Viva Connections), search results and suggestions will be scoped to SharePoint content, helping users find relevant information faster without leaving Teams.

This message is associated with Microsoft 365 Roadmap ID 562015.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected: Users of the SharePoint app in Teams (Viva Connections) across all clouds

Platforms/Services:

• Microsoft Teams
• SharePoint Online
• Viva Connections

What will happen:

• When users select the Search icon in Teams while inside the SharePoint app (Viva Connections), search results are scoped to SharePoint global search.
• SharePoint search suggestions will appear directly in Teams.
• Pressing Enter opens the SharePoint search results page in SharePoint.
• The feature is enabled by default.
• Existing SharePoint permissions and search security trimming are respected.
• No changes are required to existing admin configurations or policies.

Screenshot: Search results are scoped to SharePoint when search is initiated from within the SharePoint app in Teams:

Learn more: Viva Connections on mobile devices | Microsoft Support (will be updated before rollout)

[Action Required / Recommendations:]

No action is required from administrators.

Consider the following recommendations:

• Inform helpdesk and end users that search behavior within the SharePoint app in Teams is becoming more targeted and SharePoint‑specific.
• Update internal documentation or training materials that reference Teams or SharePoint search behavior.
• Review SharePoint search configuration and content hygiene (optional) to ensure optimal results quality.

[Compliance considerations:]

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

[What and Why:]

Organizers can now determine whether a selected room or location is available when creating an event. Microsoft Teams Events app now surfaces room availability directly in the event creation experience, allowing organizers to check availability in real time without leaving the flow.

This message is associated with Microsoft 365 Roadmap ID 561647.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected: Organizers creating in‑person or hybrid events using the Microsoft Teams Events app

Platforms/Services: Microsoft Teams (Events app)

What will happen:

• Room availability is visible during the Microsoft Teams Events app event creation flow.

Screenshot: Scheduling form showing room availability while selecting a location or room for the event:



• Organizers no longer need to switch tools to check room availability.
• Scheduling conflicts can be identified before events are published.
• Room bookings are more reliable for in‑person and hybrid events.

[Action Required / Recommendations:]

• No action is required from admins.
• Optionally notify organizers about the updated scheduling experience.

[Compliance considerations:]

This change surfaces room availability data in Teams. No new data types, AI capabilities, or compliance controls are introduced.

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

• Current Channel

[When this will happen:]

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

[How this will affect your organization:]

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

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

[What you need to do to prepare:]

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

• Current Channel

• Introduction of the Reset invoice proposal workflow status form that is enabled if invoicing workflow is enabled.
• The ability to view and reset failed workflows by users in the project accountant or project manager role without the need to contact IT or support.
• Preservation of the existing workflow history for historical review and audit purposes.

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

Coming soon for Microsoft Purview: We are announcing the public preview of the integration of Adaptive protection with Data Lifecycle Management (DLM) to help you find the right balance to protect against data sabotage while enabling productivity. This new integration leverages DLM features to provide an additional control for Adaptive protection that automatically preserves items deleted by a user with an elevated risk level, so items can be restored if needed.

This message is associated with Microsoft 365 Roadmap ID 392839.

[When this will happen:]

Public preview: We will begin rolling out in late June 2024 (previously early May) and expect to complete by late July 2024 (previously mid-July).

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

[How this will affect your organization:]

After the rollout, and after you enable Adaptive protection for your tenant, the retention label and auto-apply policy for data lifecycle management will be automatically created for you. This policy will automatically include elevated risk users identified by Microsoft Purview | Insider Risk Management solution. If these users delete content from Microsoft SharePoint, Microsoft OneDrive, or Microsoft Exchange, a retention label is automatically applied to that content to retain it for 120 days. Retention labels are automatically applied to unlabeled content deleted by these users. When these users are no longer at the elevated risk level, they are automatically removed from the DLM policy, and the system will no longer keep a copy of content they delete. Any content copies previously retained when the user had an elevated risk level will be kept for the 120 days as specified by the retention label.

Unlike other retention labeling scenarios, users do not see the retention label, and you do not need to create or manage the retention label or policy. At this time, you can’t change the retention period or assign different policies based on the different risk levels, or for different locations. The single retention label and auto-labeling policy for your tenant is not visible in the Microsoft Purview compliance portal.

[What you need to do to prepare:]

Learn more: Learn about retention policies & labels to retain or delete | Microsoft Learn

If you’re using Adaptive protection and want to automatically retain content deleted by elevated risk users, follow these steps to turn on this new integration.

1. Sign in to the Microsoft Purview compliance portal.
2. Navigate to Data lifecycle management > Microsoft 365 > Adaptive protection settings in the top right corner.
3. Turn the setting ON and select Save.

If you’re not using Adaptive protection already, turn on Adaptive protection and the new feature will be enabled along with Adaptive protection.

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

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

 Coming soon to Microsoft Purview | Data Loss Prevention: When an admin wants to enable user email notifications, policy tips also need to be enabled and vice versa. After this rollout, notifications and policy tips will be decoupled, and admins can configure the following rules to enable:

1. Only a user email notification
2. Only a policy tip
3. A user email notification and a policy tip
4. No policy tips or user email notifications

After this rollout, policy tips and user email notifications will align with the behavior currently available with Microsoft Exchange.

This message is associated with Microsoft 365 Roadmap ID 394279.

[When this will happen:]

Public Preview: We will begin rolling out mid-April 2026 (previously February 20) and expect to complete by late April 2026 (previously late February).

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

[How this will affect your organization:]

After rollout, to configure policy tips and user email notifications, you can use PowerShell or Purview | Data Loss Prevention.

In PowerShell

After rollout, use the new parameter called -NotifyUserType with the cmdlets New-DlpComplianceRule and Set-DlpComplianceRule.

Use New-DlpComplianceRule to create a new rule. Use Set-DlpComplianceRule to update an existing rule.

• Default value: NotSet
• To enable a policy tip: PolicyTip
• To enable a user email notification: Email
• To enable a user email notification and a policy tip: Email,PolicyTip

Example 1: New-DlpComplianceRule -Name "PT rule" -Policy "Policy Name" -ContentContainsSensitiveInformation @{Name="India Unique Identification (Aadhaar) Number"} -NotifyUserType PolicyTip -NotifyUser SiteAdmin,LastModifier,Owner

Example 2: Set-DlpComplianceRule -Identity "Rule Name" -NotifyUserType Email

To check that the value is set correctly, check the following and check the parameter value for NotifyUserType:

Get-DlpComplianceRule -Identity "Rule Name" | fl

In Data Loss Prevention (DLP)

Before rollout:

After rollout:

DLP examples

Rule 1: Configured to only trigger a user email notification:

Rule 2: Configured to only trigger a policy tip:

Rule 3: Configured to trigger a user email notification and a policy tip:

[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 update any relevant documentation as appropriate.