Microsoft Roadmap, messagecenter and blogs updates from 08-07-2026

Updated July 7, 2026: We have updated the timeline. Thank you for your patience.

Coming soon for Microsoft Teams: A new setting that allows users to view incoming calls in a small window in Teams to prevent disruptions. Users will be able to take a call in the small window and continue to see what they were working on before the call.

This message applies to Teams on Windows desktop, Teams on Mac desktop, Teams for the web, and Teams for iOS/Android.

This message is associated with Microsoft 365 Roadmap ID 482747.

[When this will happen:]

Targeted Release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025.

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

General Availability (GCC): We will begin rolling out early April 2026 (previously early February) and expect to complete by mid-April 2026 (previously mid-February).

General Availability: (GCC High, DoD): We will begin rolling out early May 2026 (previously early February) and expect to complete by late July 2026 (previously end of June).

[How this will affect your organization:]

Before this rollout: Teams users are disrupted by the larger Teams screen when viewing an incoming call.

After this rollout: Teams users can turn on this setting to view calls in a small window. Note that both large and small windows are resizable:

This feature will be on by default.

[What you need to do to prepare:]

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

Updated July 7, 2026: We have heard the concern from customers to remediate channels without owners, in the timeline we provided. Hence we are proceeding with migrating these channels as-is and will retain them. To clarify, we will not be deleting these channels as previously communicated. We do continue to encourage all admins to remediate channels in this state as soon as possible. We will complete the migration for these ownerless channels in the public cloud by 31st July 2026.

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 July 7, 2026: We have updated the timeline and added description of a new sub-feature for In-Meeting. Thank you for your patience. 

We’re excited to announce that we are making Copilot Chat available as a side-by-side experience in Teams. This will help users access the power of M365 and Web data in addition to current capabilities of Copilot in Chats, Channels, Calling, and Meeting. On Teams desktop (Windows and Mac) and web, users can open Copilot Chat from the Copilot icon located on the top right corner in these surfaces. Copilot Chat will be available in Teams for users with a Microsoft 365 Copilot license. 

Additionally, a new in-meeting control lets users stop Teams from processing spoken audio during a meeting. When this control is on, Teams stops processing spoken audio — including transcription and recording — and Copilot will not use or reference anything said during this time. If Facilitator is active, it will also be turned off. Users will also be prevented from restarting recording, transcription, or Facilitator while this control is in effect.

This change is associated with Microsoft 365 Roadmap ID: 501107

Screenshot: Copilot Chat in Teams (Windows desktop) for users with a Microsoft 365 Copilot license. UI elements subject to change. 

[When this will happen:]

Chats, Channels, and Post Meeting + Calling Recaps:

• Public Preview: Rollout of this change starts in early October and completes in the weeks following.
• General Availability: Rollout of this change starts mid-November and completes in the weeks following.

In-Meeting and in-Calls:

• Public Preview: Rollout of this change starts in early December and completes in the weeks following.
• General Availability: Rollout of this change started mid-January 2026 and completed early March 2026. 

In-Meeting Control

• General Availability: Rollout of this change starts September 2026 (previously July) and is expected to complete in September 2026 (previously July).

[How this affects your organization:]

Who is affected: Users with a Microsoft 365 Copilot license using Teams on Windows desktop, Mac desktop, or web (Chrome, Edge, Firefox, Safari).

What will happen:

• You can now create new Copilot Chat sessions or access other sessions within any conversation window. When you reopen Copilot Chat, it will always default back to the latest used session that was within the conversation window.
• Upon completion of the migration, all prior Copilot history will not be migrated into the new Copilot Chat experience. However, you can still access prior history by clicking on the More Options menu (…) located on the top right corner of your conversation window. An entry point to access history will be available within the More Options menu (…) of channel thread summaries as well. Within the menu, you find and select the View Copilot history option to access prior history.
• In-Meeting: A new in‑meeting control lets users stop Teams from processing spoken audio during a meeting. When this control is on, Teams stops processing spoken audio — including transcription and recording — and Copilot will not use or reference anything said during this time. If Facilitator is active, it will also be turned off. Users will also be prevented from restarting recording, transcription, or Facilitator while this control is in effect.
• After the meeting: Copilot and Facilitator will only have access to recordings or transcripts from periods when audio processing was active.

Supported Platforms

Web 

• Chrome 
• Edge 
• Firefox 
• Safari 

Desktop 

• Windows 
• Mac 

[What you can do to prepare:]

Admin action required

To ensure Microsoft Copilot is available in Teams meetings, tenant administrators must allow the Microsoft 365 Copilot app.

If the Microsoft 365 Copilot app is not allowed at the tenant level, users may not see the Copilot entry point in Teams meetings, even when Copilot licenses are assigned.

Admins should review Teams app permission and app setup policies to confirm that the Microsoft 365 Copilot app is allowed for the intended users. Copilot availability in Teams meetings depends on both licensing and app enablement.

For more information, see the public documentation on managing Copilot access: https://learn.microsoft.com/copilot/manage

[Compliance considerations:]

Updated July 7, 2026: We have updated the timeline. This feature is now available. Thank you for your patience. 

Introduction

We’re excited to announce that Microsoft Teams now supports apps in Private channels. This update enables richer collaboration scenarios across teams and organizations by allowing users to add and use apps—including bots, tabs, and message extensions—directly within Private channels. This change aligns with customer feedback requesting more consistent and flexible app experiences across collaboration spaces. Support for apps in Private Channels follows the same model as that for shared channels, ensuring a unified experience for users and developers.

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

When this will happen:

• Targeted release: Rollout begins mid-January 2026, and we expect to complete by late January 2026.
• General availability (Worldwide): This feature is now available.

How this affects your organization:

Who is affected:

• All Microsoft Teams users who participate in Private Channels
• Admins managing Teams app policies
• Developers maintaining Teams apps

What’s changing:

• Apps can now be added to Private Channels. Previously, only a limited set of tabs were supported.
• This feature is available by default.
• All apps marked to work in Private and Shared Channels will be available.
• Channel owners or members can add apps to a Private Channel, with new governance and consent controls.
• A new channel setting allows owners to control who can add apps.
• Apps must be explicitly added to each channel; installing at the team level will no longer apply to Shared or Private Channels.

  Screenshot 1: Apps must be added per channel. Users are prompted for consent when interacting with an app that hasn’t been added. Apps are available through all standard discovery entry points.

  

  Screenshot 2: Manage apps in your channels from the new Apps tab in Manage channel settings.

  

•  Guest users can use supported apps depending on app and admin settings.
• Only apps updated by developers to support Private Channel functionality and allowed by admins will be available.
• Support for apps in Private Channels will follow the same model and require similar updates.

What you can do to prepare:

Admins:

• Review your Teams app policies and ensure required apps are updated for Private Channel support.
• Communicate this change to helpdesk staff.
• Update internal documentation if you detail this feature.
• Confirm that apps used in Private Channels are permitted by your organization’s app governance policies.

• Update your app manifest to include supportsChannelFeatures: tier1 as part of the latest manifest version.
• Use channel-specific APIs for membership, storage, and permissions. Do not assume team membership equals channel membership.
• Review and update Resource-Specific Consent (RSC) permissions if required.
• Test your app in Private Channels and with different user roles (internal, guest) to validate functionality.
• For apps with advanced scenarios (e.g., file access, cross-channel data, custom permissions), review the full developer guidance for targeted updates.

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

Updated July 7, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

We’re enhancing Microsoft Purview Content Explorer with new summary metrics to improve visibility into scanning and classification activities. These updates will help admins identify unscanned files and monitor classification trends, enabling better data governance and informed decisions.

This message is associated with Roadmap ID 526796.

[When this will happen:]

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

[How this affects your organization:]

• Who is affected: Admins managing Microsoft Purview Information Protection and using Content Explorer.
• What will happen:
  • A new Unscanned Files Summary will display the count and percentage of files not scanned for classification.
  • Classification History Insights will show trends and details of classification changes over time.
  • These metrics will appear in Content Explorer alongside existing Sensitive Information Types (SITs) and labels.
  • Admins can explore the new metrics to identify gaps and use on-demand classification capabilities to retrigger scans if needed.
  • No changes to existing policies or configurations; the feature is enabled by default.

    

[What you can do to prepare:]

• No action is required.
• These metrics will automatically appear in Content Explorer.

[Compliance considerations:]

Updated July 7, 2026: We have paused release to GA at this time. We will communicate via Message center when we are ready to proceed. Thank you for your patience. 

[Introduction]

We are improving the Microsoft Teams meeting experience when the active meeting window is minimized. This update helps users stay engaged in meetings while multitasking across other apps. With this change, users can perform key in-meeting actions—such as raising their hand and sending reactions—without restoring the full Teams meeting window. Users can also choose between two different minimized views, depending on how much meeting context they want to keep visible while they work.

This change does not affect the experience when users are sharing their screen in a Teams meeting.

This message applies to Teams for Windows desktop and Teams for Mac desktop. It is associated with Microsoft 365 Roadmap ID 557179.

[When this will happen:]

• Targeted Release: Rollout begins mid-May 2026 (previously early May) and is expected to complete by late May 2026 (previously early May).
• General Availability (Worldwide): We will share GA dates when available. 

[How this affects your organization:]

Who is affected:

• All users who join and participate in Microsoft Teams meetings.

What will happen:

• When users minimize a Teams meeting window, a new minimized meeting experience appears automatically.
• Users can raise their hand and send reactions without restoring the full Microsoft Teams meeting window.
• Users can choose between two minimized views:
• Expanded view: Displays up to four participant videos.



• Compact view: Does not display participant video and takes up less screen space.



• The feature is enabled by default and does not require any admin configuration.
• There is no change to the meeting experience while screen sharing.

[What you can do to prepare:]

• No action is required.
• Consider notifying users and helpdesk staff about the new minimized meeting views in Microsoft Teams.
• Update internal training or support documentation if it references Teams meeting window behavior.

[Compliance considerations:]

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

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

The Queues app on Microsoft Teams mobile (iOS and Android) allows calling representatives and supervisor leads to manage call queues and handle customer calls while away from their desks. This update extends existing Queues functionality to the Teams mobile app, enabling users to manage queue participation and review call activity from a mobile device.

This message is associated with Microsoft 365 Roadmap ID 559386.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Organizations using Microsoft Teams Phone
• Users licensed with Teams Phone and Teams Premium
• Calling representatives and supervisor leads managing call queues
• Teams mobile app users (iOS and Android)

What will happen:

• Calling representatives and supervisor leads will be able to:
  • View the call queues they are assigned to directly from the Teams mobile app.
  • Review queue details, including the full list of queue members.
  • View queue-related call history on mobile devices.
• Calling representatives will be able to:
  • Opt in or opt out of queue call routing while on the go.
• Supervisor leads will be able to:
  • Bulk manage queue participation for their teams from mobile
• The experience:
  • Is enabled by default for eligible users.
  • Respects existing licensing, policies, and administrative controls.
  • Matches the governance model of the desktop Queues app.

This mobile access helps teams respond faster, manage calls more efficiently, and maintain a consistent customer experience regardless of location.

Screenshot 1: Queues home view:

Screenshot 2: Queue details view:

[What you can do to prepare:]

No action is required.

You may optionally:

• Ensure impacted users are licensed with Teams Phone and Teams Premium.
• Inform calling representatives and supervisor leads who rely on mobile-first workflows about this new capability.
• Update internal helpdesk or user documentation to reference mobile queue management.

Learn more: Manage Queues app for Microsoft Teams – Microsoft Teams | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

Updated July 7, 2026: We have updated the content and timeline. Thank you for your patience. 

[Introduction]

We are enhancing how Microsoft Defender for Office 365 identifies and manages promotional email. Promotional messages will be tagged as “promotions” (previously “Bulk” in preview) and can be moved automatically to a new Promotions folder. The system learns from user actions, such as moving messages into or out of the Promotions folder and applies those preferences to future messages. These improvements reduce inbox clutter and help users stay focused while still receiving promotional content they want.

[When this will happen]

• Public Preview (Limited): We will begin rolling out in mid-April 2026 and expect to complete by mid-May 2026 (previously end of April). To be included in the public preview program, send an email to [email protected] indicating: Organization name, Tenant ID and your onmicrosoft.com domain (e.g contoso.onmicrosoft.com). Slots are limited and will close on May 15th, 2026.
• General Availability (Worldwide): We will begin rolling out in late July 2026 (previously early July) and expect to complete by late August 2026 (previously late July).
• General Availability (DoD, GCC, GCC High): We will begin rolling out in late July 2026 (previously early July) and expect to complete by early August 2026 (previously mid-August).

[How this affects your organization]

Who is affected

• All organizations that use Microsoft Defender for Office 365 across Worldwide, GCC, GCC High, and DoD clouds

What will happen

• Incoming promotional messages will be tagged as “promotions.” (previously “Bulk” in private and public preview)
• If the Bulk Moves Enabled setting is turned on, tagged messages will automatically move to a Promotions folder created in user mailboxes.
• The system will learn from user actions when they move messages into or out of the Promotions folder. Future messages will follow the learned behavior.
• Users will be able to create inbox rules that reference the promotions tag.
• During the Public Preview: 
  • Tagging will be opt-in and configured using Exchange transport rules.
  • Folder routing will be enabled through anti-spam policy settings (“Bulk moves enabled”).
  • Both features will be able to be scoped to pilot security groups for a staged rollout.
• At Worldwide General Availability, tagging will be enabled by default for all tenants and will always remain that way.
• For the tagging experience, supported outlooks clients are Outlook on the web and outlook for Windows. Other client such as Outlook for IOS/Android and classic outlook will follow subsequently
• For the promotions folder experiences, Outlook on the web, outlook for Windows, Outlook for IOS/Android and classic outlook are all supported. 

Figure one – Admin configuration for tagging using exchange transport rule (required for public preview opt-In):

Figure two – Admin configuration for Bulk moves enabled to provision the promotions folder:

Figure three – System tagging of “Promotions” in outlook client and promotions folder (previously  tagged as “Bulk” in private and public preview):

Figure four – User inbox rules using the promotions” tag:

[What you can do to prepare]

• To be included in the public preview program, send an email to [email protected] indicating: Organization name, Tenant ID and your onmicrosoft.com domain (e.g contoso.onmicrosoft.com). Slots are limited and will close on April 30th, 2026.
• Review your internal mailbox and message handling guidance and update training materials if needed.
• If you plan to participate in the Public Preview, review your Exchange transport rule and anti-spam policy configurations to determine if you want to opt-in.
• Monitor the product documentation. You can review the following: Bulk email detection and bulk complaint level (BCL) in cloud organizations

[Compliance considerations]

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

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

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

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

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

What will happen:

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



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

[What you can do to prepare:]

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

[Compliance considerations:]

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

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We are retiring support for legacy Transport Layer Security (TLS) versions for POP3 and IMAP4 connections to Exchange Online. This change improves security and aligns with current industry standards. TLS 1.0 and TLS 1.1 are no longer considered secure. Most modern email clients already use TLS 1.2 or later. 

[When this will happen]

• Rollout start: August 1, 2026
• Rollout end: December 31, 2026

The rollout will occur gradually worldwide.

[How this affects your organization]

Who is affected

• Microsoft 365 tenants using POP3 or IMAP4 with Exchange Online
• Admins managing email clients, applications, or devices that use POP or IMAP

What will happen

• POP3 and IMAP4 connections will require TLS 1.2 or later.
• Connections using TLS 1.0 or TLS 1.1 will fail.
• Modern email clients are not expected to be affected.
• Legacy applications or devices may stop connecting.
• Custom or embedded systems may require updates.

[What you can do to prepare]

• If you use POP or IMAP with Exchange Online, ensure email clients, applications, and libraries support TLS 1.2 or later and do not use legacy TLS endpoints.
• Review all POP and IMAP clients in your organization.
• Confirm support for TLS 1.2 or later.
• Update or replace clients that rely on legacy TLS.
• Validate TLS support with third‑party vendors.
• Inform helpdesk and operations teams.

No action is required if all connections already use TLS 1.2 or later.

[Compliance considerations]

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

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing a standardized preview experience for Word, Excel, and PowerPoint files in Microsoft Teams across desktop and mobile platforms. This update improves performance, reliability, and consistency when previewing files, resulting in faster load times and fewer preview failures. Availability varies by platform; PowerPoint and Excel are supported on iOS and Android, while Word preview is currently available on iOS only.

This message is associated with Roadmap ID 558679.

[When this will happen:]

• General Availability (Worldwide):  Rollout will be completed by late July 2026 (previously late June).

[How this affects your organization:]

Who is affected:

• All Microsoft Teams users who preview Word, Excel, and PowerPoint files
• Mobile users on iOS and Android (platform-specific availability applies)

What will happen:

• Users will experience faster file preview load times in Teams.
• A standardized preview experience will be applied across Word, Excel, and PowerPoint files in Teams, with availability varying by platform:
  • PowerPoint and Excel previewers available on iOS and Android
  • Word previewer available on iOS only (Android support coming later)
• Users will be able to open protected files directly within Teams previews.
• Feature is enabled by default with no admin configuration required.
• This update does not change existing file storage, sharing permissions, or policies.

Screenshot: Standardized preview experience for Word, Excel, and PowerPoint:

>

[What you can do to prepare:]

• No action is required from admins; the feature will be automatically enabled.
• Inform helpdesk and support staff of the updated preview experience.
• Update internal documentation referencing file previews in Teams.
• Communicate the improved experience to users if appropriate.

[Compliance considerations:]

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

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

To improve discoverability and customization of keyboard shortcuts in Microsoft Teams, we’re adding search functionality to the Keyboard shortcuts dialog. This enhancement helps users quickly find shortcuts by either the action name or the key combination, reducing time spent scanning long lists and making shortcut customization easier and more efficient.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. It is associated with Roadmap ID 562413.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• All Microsoft Teams users who access the Keyboard shortcuts dialog.

What will happen:

• Users can search for keyboard shortcuts by:
  • The name of the action (for example, “Mute” or “Open settings”).
  • The keyboard shortcut combination (for example, “Ctrl+Shift+M”).
• The enhancement applies to:
  • Viewing existing shortcuts.
  • Customizing personal keyboard shortcuts.
• The feature is enabled by default.
• Existing Teams policies and admin configurations are respected.
• No changes to user workflows unless users choose to search or customize shortcuts.

Screenshot 1: Default keyboard shortcut dialog experience:



Screenshot 2: Use the search box in the upper-right corner to enter a keyword and find relevant keyboard shortcuts:

[What you can do to prepare:]

• No action is required.
• Consider the following optional steps:
  • Inform helpdesk and support teams about the improved shortcut discovery experience.
  • Update internal user training or documentation that references Teams keyboard shortcuts.
  • Share a short tip with users highlighting that shortcuts can now be searched by name or key combination.

[Compliance considerations:]

The change allows users to choose whether to use the new search capability within the Keyboard shortcuts dialog. No other compliance impacts have been identified.

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing an update to how front-of-room (FoR) displays behave in Microsoft Teams Rooms on Android during webinars and structured meetings. This change ensures that when a Teams Room joins as a presenter, the in-room display defaults to the attendee view—creating a clearer and more professional experience for in-room participants, especially in hybrid scenarios where presenters and attendees are co-located.

This message is associated with Roadmap ID 559602.

[When this will happen:]

• 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).
• General Availability (GCC, GCC High, DoD): We will begin rolling out in mid-June 2026 and expect to complete by late July 2026 (previously late June).

[How this affects your organization:]

Who is affected:

• Organizations using Microsoft Teams Rooms on Android
• Meeting organizers and presenters running webinars or structured meetings
• In-room participants viewing front-of-room displays
• A Teams Rooms Pro license is needed to use this feature

What will happen:

• The front-of-room display will default to attendee view when joining webinars or structured meetings.
• In-room audiences will not see presenter tools such as Green Room or backstage controls.
• Presenters will retain full control from the Teams Rooms console, including:
  • Managing Green Room and off-stage participants.
  • Switching display modes (e.g., to presenter view when needed).
• The feature is enabled by default and requires no configuration.
• There is no impact to remote attendees or their experience.
• Existing Teams Rooms functionality and policies remain unchanged.

Screenshot 1: Front-of-room webinar experience with Manage screen mode on and the user in presenter view:

Screenshot 2: Console view in presenter view:

Screenshot 3: Front-of-room webinar experience with the user in attendee view:

Screenshot 4: Console view with the user in attendee view:

[What you can do to prepare:]

• No action is required to enable this feature.
• Verify device readiness: Ensure Teams Rooms on Android devices are updated.
• Validate meeting room setup: Confirm displays and consoles function as expected.
• Educate organizers and presenters on the updated experience.
• Update internal documentation.

[Compliance considerations:]

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

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why]

We are introducing Infographics in Microsoft Copilot Notebooks, a new capability that enables users to transform notebook content into clear, structured visual summaries generated from grounded references. This feature improves clarity, reduces manual effort, and helps teams share insights faster. It supports personal and team productivity by enabling users to communicate complex ideas more effectively within their existing workflow.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected

Users with access to Microsoft Copilot Notebooks in Microsoft 365 tenants

Platforms/Services

Microsoft Copilot Notebooks in Microsoft 365 apps (web)

What will happen

• Users can generate infographics directly from notebook content.
• Infographics are created using grounded references in the notebook.
• Users can preview generated infographics.
• Users can copy or download infographics for reuse.
• Generated infographics are automatically saved within the notebook.
• The feature is enabled by default for eligible users.
• Existing Microsoft 365 and Copilot admin policies are respected.
• This is an additive capability and does not disrupt existing workflows.

[Action Required/Recommendations]

No action is required.

Recommended:

• Inform users about this new capability.
• Update internal documentation if you reference Copilot Notebooks.
• Review existing Copilot policies to ensure alignment with your organization’s requirements.

[Compliance considerations]

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Microsoft Teams is improving the quick sharing experience by enabling search for cloud files directly within the attach file picker. This helps users find and attach the right files more quickly when sharing in chats and channels.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. It is associated with Roadmap ID 560814.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Users who share and attach files in Microsoft Teams chats and channels using the quick sharing (Attach) experience.
• Organizations that use cloud files available through Microsoft 365 (for example, OneDrive and SharePoint) in Teams.

What will happen:

• Users will be able to search for cloud files directly in the attach file picker during the quick sharing experience.
• The change reduces time spent browsing folders during file attachment.
• Users will only see files they already have permission to access.
• No changes are expected to existing file sharing permissions or policies.

[What you can do to prepare:]

• No action is required.
• Optional: Inform your helpdesk that users may notice a new search capability when attaching cloud files in Teams.
• Optional: Update internal documentation or training materials related to sharing and attaching files in Teams.

[Compliance considerations:]

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing a Quick Share option for images in Microsoft Teams to help users share visual content faster across chats and channels. This update extends Quick Share to images in Teams, allowing users to quickly share or copy image links directly from familiar interaction points, while preserving existing permissions.

This message is Associated with Roadmap ID 560816

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Users who share or interact with images in Microsoft Teams chats, channels, and shared tabs

What will happen:

• Users will see a Quick Share option for images in Microsoft Teams.
• The option is available from:
  • Hover actions
  • Right‑click context menus
  • Overflow menus
  • Shared tabs
• Users can quickly:
  • Share images
  • Copy image links
• Existing Microsoft Teams and Microsoft 365 sharing permissions continue to apply.
• The feature is enabled by default.
• No new admin controls are introduced.

Screenshot 1: Microsoft Teams chat and channel environment where images are shared and viewed:



Screenshot 2: When an image is present in a Teams chat or channel, users can access image‑level actions directly from the image:

[What you can do to prepare:]

• No action is required.
• Consider notifying helpdesk or support teams about this Microsoft Teams image‑sharing enhancement.

[Compliance considerations:]

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing a new file download manager experience in Microsoft Teams to streamline file downloads and reduce on-screen interruptions. This update simplifies download notifications while still making it easy for users to find downloaded files after the download completes.

This message is associated with Roadmap ID 560815.

[When this will happen:]

• Targeted Release: We will begin rolling out in early June 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 late July 2026 (previously late June).

[How this affects your organization:]

Who is affected:

• All users downloading files in Microsoft Teams (desktop and web)
• All tenants worldwide

What will happen:

• File download notifications in Teams will automatically dismiss after approximately 4 seconds.
• Users will have an option to open or locate downloaded files after the download completes.
• The experience is enabled by default.
• Existing file permissions, storage locations, and security controls remain unchanged.

[What you can do to prepare:]

• No action is required.
• Optionally, inform helpdesk or support teams about the updated download behavior to reduce user questions.
• Update internal documentation if it references the Teams file download experience.

[Compliance considerations:]

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

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

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

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

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

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

What will happen:

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

[What you can do to prepare:].

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

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

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

[Compliance considerations:]

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

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

To improve endpoint performance and focus on higher-value network telemetry, Microsoft is removing SMB signature inspection events from Advanced Hunting in Microsoft Defender for Endpoint. This change reflects observed low customer value for SMB signature data on endpoints and our continued investment in more advanced SMB visibility through Zeek-based network capabilities. 

[When this will happen:]

The rollout to Worldwide, GCC, GCC High, and DoD will begin on July 13, 2026, and will complete shortly thereafter across all tenants.

[How this affects your organization:]

Who is affected:

• Security administrators and analysts using Microsoft Defender for Endpoint Advanced Hunting
• Organizations with custom detection rules, hunting queries, scheduled queries, or automated workflows that reference SMB signature inspection events

What will happen:

• Events with ActionType = “NetworkSignatureInspected” and SignatureName = “SMB_Client” will no longer be generated.
• Queries, detections, or workflows that rely on these events will stop returning results after the rollout.
• Other network signature inspection events remain unchanged.
• The change is on by default and does not require tenant configuration.

[What you can do to prepare:]

To continue identifying SMB traffic in Advanced Hunting, we recommend filtering on port 445, the standard port used by SMB, in the DeviceNetworkEvents table, which remains fully supported.

• Review custom detection rules, saved hunting queries, scheduled queries, and automated workflows for references to SMB_Client.
• Update affected queries to identify SMB traffic using port-based filtering.
• Validate updated queries return the expected results before July 1, 2026.

Query update example

Replace:

DeviceNetworkEvents
| where ActionType == "NetworkSignatureInspected"
| extend SignatureName = tostring(parse_json(AdditionalFields).SignatureName)
| where SignatureName == "SMB_Client"

With:

DeviceNetworkEvents
| where RemotePort == 445 or LocalPort == 445

For questions or feedback regarding this change, contact Microsoft Support or your Microsoft account representative.

[Compliance considerations:]

• Admin monitoring and reporting: The removal of SMB signature inspection events changes available Advanced Hunting telemetry and may affect how administrators monitor or investigate SMB activity.

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why:]

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

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

This message is associated with Microsoft 365 Roadmap ID 562993.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected:

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

Platforms/Services:

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

What will happen:

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

Screenshot 1: Add file extension options:



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

[Action Required / Recommendations:]

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

Learn more:

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

[Compliance considerations:]

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

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why:]

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

This message is associated with Microsoft 365 Roadmap ID 562992.

[Rollout Schedule:]

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

[How this will affect your organization:]

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

Platforms:

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

What will happen:

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

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

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

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

[Action Required / Recommendations:]

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

[Compliance considerations:]

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why:]

Admins can now scope which users and groups have their activities audited when Just-in-time protection is enabled in Microsoft Purview Endpoint Data Loss Prevention.

Previously, when Just-in-time protection was turned on, user activities were logged automatically for users who were not targeted by policies. With this update, audit logging must be explicitly configured so that only users or groups included in the audit scope have their activities logged. This change gives organizations greater control over audit signal collection and helps reduce unnecessary audit noise.

This message is associated with Microsoft 365 Roadmap ID 562991.

[Rollout Schedule:]

Global: We will begin rolling out in mid-September 2026 (previously early July) and expect to complete by end of September 2026 (previously early July).

[Impact on Your Organization:]

Who is affected: Admins managing Microsoft Purview Endpoint Data Loss Prevention and Just-in-time protection settings.

Platforms/Services:

• Microsoft Purview
• Endpoint Data Loss Prevention
• Activity explorer.

What will happen:

• Just-in-time audit behavior is now managed through the Audit covered user activities setting under Settings > Data loss prevention > Just-in-time protection. Under the Devices tab, turn on Audit covered user activities.

Screenshot: Just-in-time protection settings with Audit covered user activities turned on:



• Users included in audit scope will not see enforcement actions, and their activities will be recorded in Activity explorer.
• Users included in block scope will be prevented from completing actions while files are evaluated for sensitive information. Their activities are recorded in Activity explorer.
• Users not included in audit or block scope will not have activities covered by Just-in-time protection recorded.
• Audited activities include printing, transfers to removable media or network shares, copying or moving files using Remote Desktop Protocol or an unapproved Bluetooth app, and uploading files to a restricted cloud service domain.

[Action Required / Recommendations:]

• Deploy anti-malware client version 4.18.26060 or later before enabling this feature.
• Review your existing Just-in-time configuration to identify users currently generating audit events.
• Explicitly add all users or groups that should continue generating Just-in-time audit events to the audit scope.
• Validate your configuration to ensure expected activities appear in Activity explorer.

Learn more: Get started with Microsoft Purview Data Loss Prevention just-in-time protection | Microsoft Learn

[Compliance considerations:]

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We are introducing a new capability that allows users to connect Microsoft Teams meetings to existing Microsoft Planner plans.

Currently, Teams meetings automatically create separate Planner plans for meeting-related tasks, which can result in tasks for the same initiative being spread across multiple plans. This update enables users to link meetings to an existing plan so tasks can be tracked in a single location, improving organization and continuity across ongoing work.

This message is associated with Roadmap ID 561490.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Users who create or participate in Microsoft Teams meetings and use Microsoft Planner 
• Organizations with Teams, Planner, and Loop enabled

What will happen:

• Users will be able to link a Teams meeting to an existing Planner plan.
• Tasks created during meetings can be added to the selected existing plan.
• If no plan is selected, meetings will continue to create a new Planner plan.
• This feature will be available by default.
• Facilitator (the meeting task automation capability) can create tasks in the selected plan.
• Users can manually create tasks if Facilitator is disabled. 
• No changes to existing plans or previously created plans.

Learn more: Facilitator in Microsoft Teams meetings | Microsoft Support

[What you can do to prepare:]

• No action is required.
• You may want to:
  • Ensure that Teams, Planner, and Loop are enabled in your tenant.
  • Review whether Facilitator should be enabled for automated task creation scenarios.
  • Update internal documentation or task management guidance if applicable.
  • Inform helpdesk staff and users about this new option for organizing meeting tasks.

[Compliance considerations:]

Updated July 7, 2026: We have updated the content. Thank you for your patience. 

[What and Why:]

We are updating Viva Insights Copilot Analytics to remove the Viva Insights license requirement for managers to access team views. After this change, eligible managers and their delegates can access manager-scoped Copilot Analytics insights without requiring an assigned Viva Insights license or service plan.

This update reduces access barriers, supports broader Copilot adoption across organizations, and enables admins to more accurately define and manage the eligible manager population—while continuing to respect existing admin controls and manager settings.

[Rollout Schedule:]

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

During this period, the rollout will occur in two phases: the license requirement for managers will be removed first, followed by the requirement removal for individuals on a manager’s team.

[Impact on Your Organization:]

Who is affected:

• Administrators and leaders using Viva Insights Copilot Analytics
• Organizations with manager-scoped insights enabled
• Users permitted through Viva Insights VFAM controls
• Tenants with at least 50 Microsoft 365 Copilot (Premium) licenses or 50 Viva Insights licenses assigned

Platforms/Services:

• Viva Insights (web)
• Microsoft 365 Copilot Analytics

What will happen:

• The license requirement for managers to access team insights views will be removed (phase 1: removal of license requirement for managers; phase 2: removal of license requirement for individuals on managers’ teams).
• Eligible managers and delegates will gain access based on admin configuration, not license assignment.
• The feature will be enabled by default.
• Admins can manage access through the Manager settings page in Viva Insights.
• Existing admin controls and manager settings will continue to be respected.

[Action Required / Recommendations:]

No immediate action is required. We recommend that you:

• Review the update and assess impact on reporting, governance, and manager access policies.
• Verify access to manager-scoped team views in Viva Insights admin settings.
• Communicate the change to newly eligible managers.
• Engage your works council or employee representatives, if applicable.

Learn more: Configure manager settings | Microsoft Learn (will be updated prior to rollout)

[Compliance considerations:]

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

Updated July 7, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why]

Copilot Notebook, a new Copilot-powered workspace in OneNote, helps users organize, reason over, and take action on their content. This feature brings advanced Copilot capabilities directly into OneNote on Mac, enabling users to generate insights, structure ideas, and work more effectively within their notes.

A Microsoft 365 Copilot license is required to access this feature.

This message is associated with Microsoft 365 Roadmap ID 565863.

[Rollout Schedule]

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

[Impact on Your Organization]

Who is affected

• Users with a Microsoft 365 Copilot license using OneNote on Mac

Platforms/Services

• OneNote for Mac
• Microsoft 365 Copilot

What will happen

• Copilot Notebook will be available within OneNote on Mac as a new Copilot-enabled workspace.
• Users will be able to access AI-powered capabilities to organize, analyze, and act on their notebook content.
• This feature is enabled by default for users with a Microsoft 365 Copilot license.
• There is no admin control to disable the feature. Only users assigned the required license will have access. 
• There are no changes to existing admin configurations or policies.

[Action Required/Recommendation]

No action is required.

You may consider the following:

• Inform users about the availability of Copilot Notebook in OneNote for Mac.
• Ensure eligible users have appropriate Microsoft 365 Copilot licenses assigned.
• Confirm they are running the latest version of OneNote on Mac to access this feature.
• Review internal documentation or training materials to include this feature if applicable.

Learn more: [To be updated closer to launch.] What are Microsoft 365 Copilot Notebooks in OneNote? | Microsoft Support

[Compliance considerations]

[What and Why:]

Starting July 2, 2026, roadmap updates for Microsoft Copilot Studio and associated agent experiences will be published to the Microsoft 365 Roadmap, giving you a single, consistent place to track upcoming features. Release Planner will no longer be maintained as a source for this roadmap information. This change makes it easier to stay informed and plan for what’s coming—all from one location. This transition also aligns roadmap information with experiences that are easier for AI-powered tools and agents to discover and consume. By consolidating roadmap content within the Microsoft 365 Roadmap, customers benefit from a more consistent and accessible source of information for both human users and AI-assisted workflows.

[Rollout Schedule:]

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

[Impact on Your Organization:]

Who is affected:

• Admins and users who rely on Release Planner for roadmap visibility into Microsoft Copilot Studio and associated agent experiences

Platforms/Services:

• Microsoft 365 Roadmap (web)
• Microsoft Copilot Studio
• Sales Agent, Finance Agent, Service Agent 

What will happen:

• Roadmap content for Microsoft Copilot Studio and associated agent experiences will move from Release Planner to the Microsoft 365 Roadmap. 
• All future roadmap updates will be published in the Microsoft 365 public roadmap 
• Existing Release Planner links and entry points will automatically redirect to the new location 
• Some Release Planner-specific planning capabilities, such as custom release plans, will no longer be available after this transition. The Microsoft 365 Roadmap continues to evolve, providing a more consistent, actionable way to track changes alongside clearer Message Center communications and release timing. 
• Customers who previously relied on Release Planner for customized tracking can use Microsoft 365 public roadmap capabilities together with insights powered by MCP (Model Context Protocol) for deeper tracking and analysis. These experiences support more proactive planning with greater clarity and confidence by reducing manual tracking and surfacing more relevant, role-aware insights. 

[Action Required / Recommendations:]

No immediate action is required.

We recommend the following to ensure a smooth transition:

• Update any saved bookmarks to point to the Microsoft 365 Roadmap
• Begin using the Microsoft 365 Roadmap as your primary source for roadmap visibility
• Communicate this update to relevant stakeholders who rely on Release Planner
• Review and update any internal documentation that references Release Planner 

Resources:

• Microsoft MCP for Enterprise – Provides tenant-scoped, role-based insights from your Message Center and Service Health data to support impact analysis and stakeholder readiness. 
• Microsoft Release Communications MCP Server – Enables natural language access to Microsoft 365 roadmap and update information to help answer questions and monitor upcoming changes.
• Microsoft 365 Roadmap 
• Microsoft 365 Copilot release notes
• Microsoft 365 Copilot Roadmap Webinar – Register today

We will continue to share updates through Message Center as needed.

[Compliance Considerations:]

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

• Top-level agent invocation and lower-level execution spans, such as tool calls and output messages.
• Agent execution events, including:
  • InvokeAgent
  • ExecuteTool
  • OutputMessages
• OpenTelemetry-aligned attributes for agents, conversations and tools.

[What and Why:]

Microsoft is simplifying taskbar pinning management from the Microsoft 365 admin center by focusing the built-in pinning control exclusively on the Microsoft 365 Copilot app. Companion apps (Files, Calendar, and People) will no longer be pinned through this control.

This change improves deployment consistency and manageability by establishing Microsoft 365 Copilot as the primary productivity entry point while reducing unintended companion app pinning. Organizations that require companion app pinning can continue using Microsoft Intune taskbar policies.

[Rollout Schedule:]

• General Availability (Worldwide): Beginning in mid-July 2026; expected to complete by late July 2026

[Impact on Your Organization:]

Who is affected:

• Administrators using Microsoft 365 admin center taskbar pinning controls
• All Microsoft 365 tenants worldwide

Platforms/Services:

• Windows
• Microsoft 365 Copilot
• Microsoft 365 admin center
• Microsoft Intune

What will happen:

• The Microsoft 365 admin center taskbar pinning control will continue to pin the Microsoft 365 Copilot app.
• The Microsoft 365 admin center taskbar pinning control will no longer pin companion apps:
  • Files
  • Calendar
  • People
• Existing taskbar pins for companion apps will remain unchanged.
• Existing companion app pins will not be removed by this update.
• The change will apply automatically to all tenants.
• Organizations can continue managing companion app taskbar pinning through custom Intune taskbar policies.
• No change is being made to the Microsoft 365 Copilot app pinning experience delivered through the Microsoft 365 admin center.

[Action Required/Recommendations:]

No action is required if you use the Microsoft 365 admin center taskbar pinning control only to deploy the Microsoft 365 Copilot app.

Recommended actions:

• Review whether your organization currently relies on the Microsoft 365 admin center to pin Files, Calendar, or People apps.
• If companion app pinning is required going forward, transition management to Microsoft Intune taskbar policies before rollout completion.
• Notify endpoint management teams responsible for Windows deployment and configuration management.
• Update any internal deployment documentation that references companion app pinning through the Microsoft 365 admin center.
• Review existing taskbar configuration standards to determine whether additional Intune controls are needed.

[Compliance Considerations:]

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

[Introduction]

We’re retiring the Exchange Web Services (EWS)–based controls used to enable or disable Personal Bookings (Bookings with me) in Microsoft Bookings. Beginning August 5, 2026, access to Personal Bookings will be managed exclusively through OWA Mailbox Policy settings.

This change aligns with Microsoft’s Exchange Online management and security principles, while providing a single, consistent administrative experience.

[When this will happen]

• Now: The OWA Mailbox Policy setting for Personal Bookings is available.
• August 5, 2026: EWS‑based Personal Bookings controls will be retired.

[How this affects your organization]

Who is affected

• Microsoft 365 administrators managing Microsoft Bookings and Exchange Online
• Organizations currently using EWS organization configuration or per‑user CAS mailbox settings to control Personal Bookings

What will happen

• After August 5, 2026, admins will no longer be able to manage Personal Bookings access using:
  • Set-OrganizationConfig (EWS settings)
  • EWS‑related parameters in Set-CASMailbox
• The default OWA Mailbox Policy is tenant‑configurable and may already include customized Personal Bookings settings.
• Any existing EWS‑based Personal Bookings configuration will be ignored.
• Access to Personal Bookings will be determined only by the OWA Mailbox Policy assigned to the user.
• If no custom OWA Mailbox Policy is assigned to a user, Personal Bookings availability will follow the settings configured in the tenant’s default OWA Mailbox Policy (OwaMailboxPolicy-Default).
• If your default OWA Mailbox Policy already reflects your intended Personal Bookings access state, no additional changes are required.

[What you can do to prepare]

Administrators should complete migration of any existing EWS‑based Personal Bookings controls to OWA Mailbox Policy before August 5, 2026, to avoid unintended changes to user access.

The following steps require Exchange Online PowerShell.

There is no change to the Personal Bookings user experience. This change affects only how administrators manage access.

Migrate your existing EWS‑based Personal Bookings controls to the new OWA Mailbox Policy

Review your current EWS‑based configuration

• Organization‑wide:

Get-OrganizationConfig | Select-Object EwsEnabled,EwsApplicationAccessPolicy,EwsBlockList,EwsAllowList

• Per user:

Get-CASMailbox -Identity | Select EwsEnabled,EwsApplicationAccessPolicy,EwsBlockList,EwsAllow

Configure Personal Bookings using OWA Mailbox Policy

Disable Personal Bookings for the entire organization

• Admin should run following PowerShell commands:

Set-OwaMailboxPolicy -Identity "OwaMailboxPolicy-Default" -PersonalBookingsDisabled $true

• Verification:

Get-OwaMailboxPolicy -Identity "OwaMailboxPolicy-Default" | Select PersonalBookingsDisabled

Enable Personal Bookings for specific users only

• Disable Personal Bookings org‑wide using the steps above.
• Create a custom policy:

New-OwaMailboxPolicy -Name "BwmEnablePolicy"

• Assign the policy to selected users:

Set-CASMailbox -Identity <smtp> -OwaMailboxPolicy "BwmEnablePolicy"

Disable Personal Bookings for specific users only (all others are enabled)

• Ensure Personal Bookings is enabled org‑wide:

Set-OwaMailboxPolicy -Identity "OwaMailboxPolicy-Default" -PersonalBookingsDisabled $false

• Create and configure a custom policy:

New-OwaMailboxPolicy -Name "BwmDisablePolicy"

Set-OwaMailboxPolicy -Identity "BwmDisablePolicy" -PersonalBookingsDisabled $true

• Assign the policy:

Set-CASMailbox -Identity <smtp> -OwaMailboxPolicy “BwmDisablePolicy”

After migrating

• Validate assigned OWA Mailbox Policies.
• Remove any EWS allow or block list entries related to Personal Bookings.
• Update internal administrative documentation.
• Notify helpdesk and Exchange administrators of the change.

Learn more: Turn off Personal Bookings | Microsoft Bookings | Microsoft 365 | Microsoft Learn

[Compliance considerations]

In 2018, we announced that we were no longer making feature updates to Exchange Web Services (EWS) in Exchange Online, and we advised developers to move to Microsoft Graph.

In September 2023, we announced that on October 1, 2026, we will start blocking EWS requests to Exchange Online.

We are now less than 12 months from October 1, 2026. We have made progress on closing most parity gaps with more changes in development to be released in the coming quarters. Please refer to Deprecation of Exchange Web Services in Exchange Online for up-to-date guidance and roadmap information.  

You are receiving this notification because there are EWS applications in your tenant.

If you haven’t already, start the process of working with your application development organization and your application vendors to either sunset or migrate active EWS applications on your tenant to the Graph API, Power Platform, or Copilot Declarative Agents.

The vast majority of custom EWS applications can be safely migrated to alternative technologies today.

[When this will happen:]

October 1, 2026

[How this affects your organization:]

In October 2026 we will begin disabling EWS on all M365 tenants worldwide. EWS Applications that have not been migrated will stop functioning.

The following applications on your tenant use EWS:

Entra Application IDs with EWS traffic and recommendations for next steps:

Apple Mail for Mac (f8d98a96-0999-43f5-8af3-69971c7bb423) – Apple Mail for Mac – See note on Apple applications below

Next Steps

1. Review your application portfolio now to get an understanding of which apps need to be updated by your organization and which ones require updates from vendors.
2. While EWS applications are active on your tenant, lower your risk of a successful attack by reviewing and updating the security practices for your organization. In particular, enable Multi Factor Authentication (MFA) for all users including test accounts.
3. Prioritize EWS app modernization on your engineering schedule to ensure enough time to address any functionality gaps
4. Disable EWS in your tenant or enable Baseline Security Mode when you no longer have applications that depend on it.

Note on Apple Mail for Mac

We provide a set of open-source tools and tutorials to aid in discovery, analysis and AI assisted modernization of EWS applications.

Thank you in advance for taking steps to improve the security posture of your M365 tenant. We are extremely excited about the growing opportunities that the Microsoft 365 platform offers to developers, and we remain fully committed to our journey to empower developers with the best features and tools.