Microsoft Roadmap, messagecenter and blogs updates from 11-03-2025

Updated March 10, 2025: We have updated the title. Thank you for your patience.

EEEU, which stands for Everyone Except External Users, is a permission setting used in Microsoft SharePoint and Microsoft OneDrive to manage access to content. This setting allows all internal users in an organization to access certain content while excluding external users. We discourage use of this setting due to concerns about inadvertent oversharing of user data.

[What is changing]

Starting April 10, 2025 and ending by September 30, 2025, we will run logic to detect and remove the EEEU permission from the root site of each user’s OneDrive and the default document library in OneDrive.

[How this will affect your organization:]

Before this retirement, apps, processes, or users may be able to discover and access content from OneDrive because of the inadvertent presence of EEEU in the root web and default document library in OneDrive. After the EEEU permission is removed, these apps, processes, and users will lose access to the content from the affected OneDrive accounts. Users, processes, and apps that were granted direct permissions to specific files and folders of a OneDrive account will not be impacted and will continue to retain their access.

We recommend OneDrive owners and OneDrive admins give explicit permission to individual files and folders in OneDrive to be accessed by one or more users or apps.

[What you need to do to prepare:]

This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change and update relevant documentation. If you have questions or wish to discuss more, please open a support ticket.

Learn more: The section called Use Microsoft Entra groups and dynamic membership instead of default claims in Grant Everyone claim to external users in Microsoft 365 – Microsoft 365 | Microsoft Learn

Updated March 10, 2025: We have updated the content. Thank you for your patience

Coming soon to Microsoft Teams: The Facilitator agent can take notes during your Teams meetings and chats. The Facilitator synthesizes key information from the conversations, so users can catch up quickly. In meetings, the Facilitator allows everyone to co-author real-time notes and collaborate seamlessly. In chat, the Facilitator creates and maintains an up-to-date summary of important information as the conversation happens, including key decisions, actions items, and open questions to resolve.

This message is associated with Microsoft 365 Roadmap ID 478611.

We introduced the Targeted Release preview of this feature in MC937709 (Updated) Facilitator in Teams Meetings and Chats (published and updated November 2024).

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

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

[When this will happen:]

General Availability (Worldwide): We will begin rolling out early April 2025 and expect to complete by late April 2025.

[How this will affect your organization:]

After this rollout, the Facilitator app will be on by default unless all apps are blocked by your organization. As an admin, you control whether Facilitator will be available to your entire organization or to a certain group of users. Learn more: Set up Facilitator in Microsoft Teams for collaborative AI notes – Microsoft Teams | Microsoft Learn

Facilitator and Microsoft 365 are built on Microsoft’s comprehensive approach to security, compliance, and privacy. As a part of the security promise, you can discover, protect, and govern AI interactions with Facilitator through Microsoft Purview. Microsoft Purview Data Security Posture Management (DSPM) for AI helps IT and security teams proactively discover and manage data risks. Use DSPM for AI in conjunction with other Microsoft Purview capabilities such as Audit, eDiscovery, and Data Lifecycle Management to ensure data security and compliance for your organization. Learn more about Microsoft Purview here: Microsoft Purview data security and compliance protections for Microsoft 365 Copilot and other generative AI apps | Microsoft Learn.

Improvements planned for the future: AI-generated notes in chats will move to an editable canvas. This canvas will be backed by a Microsoft SharePoint Embedded file and document management system. We will provide more details closer to the feature’s release. Learn more: SharePoint Embedded Overview | Microsoft Learn

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

Known Limitations

Sensitivity labels applied to the meeting will not automatically be applied to the meeting notes file. For example, if an organizer marks a meeting as highly confidential and turns on AI-generated notes, those notes will not be marked as highly confidential. The suggested workaround is to not use Facilitator in meetings where sensitive information will be discussed. This limitation will be documented in admin and end user documentation at release. Microsoft is actively working on meeting sensitivity label inheritance to notes and will provide more updates as they are available.

• If you’re using Microsoft 365 Copilot in your organization (with your work or school account): Data, Privacy, and Security for Microsoft 365 Copilot | Microsoft Learn.
• Admin documentation: Set up Facilitator in Microsoft Teams for collaborative AI notes – Microsoft Teams | Microsoft Learn (will be updated before rollout)
• User documentation (meetings): Automate notetaking in Microsoft Teams meetings – Microsoft Support (will be updated before rollout)
• User documentation (chats): Keep track of chats with AI notes in Microsoft Teams – Microsoft Support (will be updated before rollout)

Updated March 10, 2025: We have updated the content. Thank you for your patience.

To reduce the risk of misuse and abuse of Exchange Online resources and ensure service availability for all users, we’ll soon introduce new tenant-level outbound email limits, known as the Tenant External Recipient Rate Limit or TERRL. The TERRL restricts the number of external recipients a tenant can send email to per day. If the limit is exceeded further messages sent to external recipients from the tenant will be blocked until the volume for the last 24 hours drops below the quota. A tenant’s TERRL quota is calculated based on the number of email licenses a tenant has purchased. Here is the formula used to calculate a tenant’s quota:

500 * (Purchased Email Licenses^0.7) + 9500

To help admins plan and track their outbound email volume, you’ll find a new report in the Exchange admin center: EAC > Reports > Mail flow > Tenant Outbound External Recipients Rate. This report shows the current volume of external recipients, your tenant’s daily quota, how much of the quota is used, and the number of recipients that were blocked if the limit was exceeded. The report will also show if enforcement for the limit is enabled or disabled. For example, for tenants who have more than 500 email licenses it will show “Disabled” until May 1st, the day we’ll start to enable enforcement for tenants who have more than 500 licenses.

[When this will happen:]

This change will roll out in progressive stages over the month of March as per the following rollout schedule:

[How this will affect your organization:]

If your tenant exceeds its daily outbound sending limit further messages sent to external recipients will be blocked and senders will receive one of the following bounce messages (also known as Non-Delivery Receipts or NDRs):

• Trial tenants: 550 5.7.232 – Your message can’t be sent because your trial tenant has exceeded its daily limit for sending email to external recipients (tenant external recipient rate limit)
• Non-trial tenants: 550 5.7.233 – Your message can’t be sent because your tenant exceeded its daily limit for sending email to external recipients (tenant external recipient rate limit)

[What you need to do to prepare:]

Check the report in the EAC to see your tenant’s quota and current daily outbound email volume and whether or not any messages will be blocked once the TERRL is enabled for your tenant. If your current outbound email volume is well below the quota, you don’t have to do anything. If your outbound email volume is near or exceeding your quota, consider using Azure Communication Services email for high-volume email to external recipients instead. ACS email which offers significant advantages and features for high-volume email, especially for external recipients. Messages sent using ACS email are not counted against your Tenant External Recipient Rate Limit quota.

For more information about the Tenant External Recipient Rate feature and report please see this blog post:

• Introducing Exchange Online Tenant Outbound Email Limits

Updated March 10, 2025: We have updated the content. Thank you for your patience.

We will soon introduce a new limit on dynamic distribution groups (DDGs) in Microsoft Exchange Online. Each organization will be limited to a maximum of 3,000 DDGs. After this limit is reached, admins will need to remove existing DDGs before creating new ones. Learn more: Exchange Online limits – Service Descriptions | Microsoft Learn

[When this will happen:]

General Availability (Worldwide, GCC): We will begin enforcing this limit in early April 2025.

[How this will affect your organization:]

If your organization has fewer than 3,000 DDGs, this change will not impact you. However, after your organization reaches this limit, you will not be able to create new DDGs until some existing DDGs are removed.

This change will be on by default and cannot be turned off by admins.

[What you need to do to prepare:]

The enforcement of the DDG limit will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation.

We recommend reviewing the usage of Dynamic Distribution Groups (DDGs) in your organization and removing any DDGs that are no longer needed. You can use the Dynamic distribution groups report in the Exchange admin center (EAC) to see the number of DDGs in your organization and insights into their usage. To access this report, go to the EAC > Reports > Mail flow > Dynamic distribution group report. Learn more: Dynamic Distribution Groups report in the new EAC in Exchange Online | Microsoft Learn

1. Ensure that all Windows domain controllers and Windows clients are updated with a Windows security update released on or after April 9, 2024.
2. Review Audit events that are visible in Compatibility mode. This will help identify which devices have not been updated with a Windows security update released on or after April 9, 2024.
3. Install the April 2025 Windows update on all Windows domain controllers and Windows clients, once it becomes available later this year. Enforcement mode will be fully enabled in your environment. This will properly mitigate the vulnerabilities described in CVE-2024-26248 and CVE-2024-29056.

• KB5037754: How to manage PAC Validation changes related to CVE-2024-26248 and CVE-2024-29056
• KB5020805: How to manage Kerberos protocol changes related to CVE-2022-37967

Updated March 10, 2025: We have updated the rollout timeline below. Thank you for your patience.

Before this rollout, Microsoft Teams chat and Microsoft 365 Copilot interactions are available together to be included or excluded in the Microsoft Purview Data Lifecycle Management policy in the Purview compliance center.

After this rollout, admins can have separate policies for Copilot interactions. Also, admins can separate Teams chat from Copilot interactions to create new retention policies for Copilot messages only.

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

This message is associated with Microsoft 365 Roadmap ID 407897.

[When this will happen:]

Public Preview: We will begin rolling out early March 2025 (previously mid-February) and expect to complete by mid-March 2025 (previously late February).

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

[How this will affect your organization:]

Admins will be able to separate existing Teams Chat from Copilot interactions:

This feature is available by default for admins to configure from the Data Lifecycle Management Retention policies.

Separate Copilot retention policies from Teams chats:

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

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

Updated March 10, 2025: There are additional details available regarding the Microsoft Search in Bing retirement.

• Some Microsoft Search answers will no longer be available after March 31, 2025, including Q&As and location answers. Recommended bookmarks will also be retired; you can keep them by manually publishing or exporting them by April 30, 2025. Please see the FAQ for more information.
• Work or school search history on Bing.com will be available through March 31, 2025. Individuals who wish to keep their recent search history must download it by March 31 by signing in with their Entra ID, going to Options on Bing.com, and selecting “Search history.” There is no control available for IT admins to download search terms on behalf of users.
• To help users on Bing.com, a banner to redirect to M365.cloud.microsoft will be shown in Edge if search terms are high likelihood of being work-related. For more details, please see the FAQ available at Guidance for retiring Microsoft Search in Bing for your organization.
• Note: Microsoft Edge version 134.0.3124.51+ is required for the work search functionality described below.

Microsoft Search in Bing, the search experience for work and school available on Bing.com, is being deprecated. The last day of its availability is on March 31, 2025. This change is being made as we streamline search experiences and focus on enhancing core productivity tools.

The Microsoft Edge for Business address bar and the Windows search box will continue to support work and school search, with some adjustments detailed below.

Details of the Change

After March 31, 2025, Microsoft Search in Bing will no longer be available, with changes as follows:

• Bing.com will no longer show work or school search results. Consequently, there will not be a dedicated page of work or school results and users’ work or school profiles will no longer appear on Bing.com. However, selecting the Work or School tab on Bing.com will redirect users to the new Microsoft Search experience on M365.cloud.microsoft (formerly Office.com and Microsoft365.com).
• Search boxes you’ve configured to point to Microsoft Search in Bing will no longer provide work or school results.
• The Edge for Business address bar and Windows search box will continue to support work and school search with some adjustments, including:
  • The Edge for Business address bar will no longer return work or school search results on a Bing.com page but will continue to provide suggested results in the address bar. In addition, the address bar will send users to work and school results on M365.cloud.microsoft rather than Bing.com. Users of the address bar can continue to find work-related documents, bookmarks, and people in suggested results—clicking on these suggestions takes users to work or school results on M365.cloud.microsoft. Users can also type “work” in the address bar, hit the tab key, then input their work- or school-related query to get results on a M365.cloud.microsoft page. Work and school search results will include documents, people, and bookmarks. Work search for documents will be available initially, with additional content types available as quickly as possible.
  • The Windows search box will no longer display organization branding nor the “Work” or “School” tab but will continue to support work and school search. Search for documents and people remains available. will be available initially, with additional content types available as quickly as possible. With these changes, users will see some UX changes in the Windows search box.

As before, the core Microsoft Search experience remains accessible through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online.

• Additionally, Entra ID sign-in will no longer be available on Bing.com, since work and school search is no longer available on Bing.com.

An FAQ and further details are now available at Guidance for retiring Microsoft Search in Bing for your organization, which will be updated regularly.

[When will this happen:]

The last day of availability of Microsoft Search in Bing is March 31, 2025.

[How this affects your organization:]

For organizations using Microsoft Search in Bing, users will need to transition to using Microsoft Search through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online.

Users who are accustomed to using the Edge for Business address bar and the Windows search box can continue to conduct work searches through these endpoints entry points, with the expectation that there will be some adjustment in these experiences after the deprecation date. (For details on changes, please refer to the FAQ: https://aka.ms/MSBFAQ.)

Users who click on suggestions in the Edge for Business address bar or Windows search box may be redirected to Microsoft365.com before March 31, 2025. Also, as we begin testing the retirement experience, a small set of users may find before March 31 that Bing is intermittently unavailable as an entry point for work search. We recommend that you proactively inform your users of the change and direct them to M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. Adding M365.cloud.microsoft to their favorites or to the favorites bar in Edge for Business may be a helpful alternative pathway.

[What you can do to prepare:]

Customers should prepare to stop using Microsoft Search in Bing by March 31, 2025, and transition to using Microsoft Search through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. We recommend that you inform users about the upcoming change and the alternatives available.

Adding your preferred entry point from this set to favorites or favorites bar in Edge may be a helpful alternative pathway. Admins can easily set favorites in Edge for their organization, please see details here.

Additionally, users can continue to use the Edge for Business address bar and the Windows search box, with some changes expected. Please educate users that they should now type “work” in the address bar, hit the tab key, then type in their work-related query to get work results on a M365.cloud.microsoft page.

If your organization is using the AddressBarMicrosoftSearchInBingProviderEnabled policy today, you should update to the AddressBarWorkSearchResultsEnabled policy, if the policy is still needed.

The new policy, AddressBarWorkSearchResultsEnabled, will be available starting in early March, with Edge for Business version 134 (ahead of the Microsoft Search in Bing deprecation). This allows admins to configure the display of work suggestions in the address bar. If the policy is enabled or not configured, users who are signed into Edge for Business with their Entra ID can view internal work-related suggestions, such as bookmarks, files, and people results powered by Microsoft 365, in the Edge for Business address bar suggestion dropdown. If the policy is disabled, Entra ID signed-in users will not see internal workplace results in the Microsoft Edge address bar suggestion dropdown.

Admins who wish to set their own deprecation date prior to March 31, 2025, can turn off Microsoft Search in Bing by going to the Microsoft 365 admin center > Settings > Search & Intelligence.

Regarding SafeSearch settings:

• If you had set the search experience for your organization to “School search,” SafeSearch was set to Strict by default. If you’d like to ensure that your users continue to have SafeSearch set to Strict after the Microsoft Search in Bing retirement, you can map www.bing.com to strict.bing.com at a network level. See Blocking adult content with SafeSearch or blocking Chat for more details.

Updated March 10, 2025: We have updated the rollout timeline below. Thank you for your patience.

Coming soon to Microsoft SharePoint: The new Preview mode can be used to understand how Pages and News posts will appear on different device types when viewed by an audience.

This message is associated with Microsoft 365 Roadmap ID 473452.

[When this will happen:]

Targeted Release: We will begin rolling out late March 2025 (previously mid-February) and expect to complete by mid-April 2025 (previously late March).

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-April 2025 (previously late March) and expect to complete by early May 2025 (previously late April).

[How this will affect your organization:]

After this rollout, a Preview button will display in the command bar while users are editing Pages and News posts in SharePoint. After selecting Preview, users can see what the page will look like in view mode for the audience. When previewing Pages, users can navigate between Desktop and Mobile device types. When previewing News posts, users can also choose to view the email version as Desktop or Mobile device types.

This change will be available by default.

[What you need to do to prepare:]

You may want to notify users, update your user training, and prepare your help desk.

This rollout will happen automatically by the specified date with no admin action required before or after the rollout.

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