2026 CW 05 Microsoft 365 Message Center changes

from 01/26/2026 to 02/01/2026

27 Office 365 Message Center Items were changed and
18 Office 365 Message Center Items were added

Please note: Only common Message Center messages are in this list you should always check your Message Center for additional messages

Subscibe to cloudscout.one Enterprise plan to get individual reports for your Office 365 tenant

Changes

MC End Time changes

MC ID MC Title Old Value New Value MC Action required by
MC1019312 (Updated) Microsoft Teams: Meeting participants can request collaborative annotation sessions 03/30/2026 09:00:00 2026-05-30T09:00:00Z N/A
MC1092459 (Updated) Microsoft Viva Insights: New prompt categories in the Microsoft Copilot Dashboard 03/02/2026 08:00:00 2026-03-30T09:00:00Z N/A
MC1108848 (Updated) Changing output format for some database properties in Exchange Online cmdlets 01/05/2026 08:00:00 2026-05-31T09:00:00Z N/A
MC1134737 (Updated) Microsoft Teams: Private channels increased limits and transition to group compliance 03/30/2026 10:00:00 2026-04-30T10:00:00Z N/A
MC1138786 (Updated) Viva Glint: Focus area enhancements and retirement of goal periods 03/23/2026 09:00:00 2026-02-27T09:00:00Z N/A
MC1151242 (Updated) Microsoft Teams: Improved organization chart in Profile Card (Desktop, Mac, Web) 03/30/2026 10:00:00 2026-05-11T10:00:00Z N/A
MC1155311 (Updated) Viva Engage: Agents in Viva Engage communities Public Preview 04/01/2026 09:00:00 2026-05-25T09:00:00Z N/A
MC1157712 (Updated) Microsoft OneNote | Sensitivity labels now available on desktop, web, iOS, Android, and Mac 03/02/2026 09:00:00 2026-03-30T10:00:00Z N/A
MC1182688 (Updated) Microsoft Teams Rooms on Android: Recording and transcription controls (Teams Rooms Pro required) 04/20/2026 10:00:00 2026-05-11T10:00:00Z N/A
MC1183608 (Updated) Rate my call feedback experience update in Microsoft Teams 03/02/2026 09:00:00 2026-03-30T10:00:00Z N/A
MC1184992 (Updated) Microsoft Teams: Improvements to "Activity in other accounts and orgs panel" 04/20/2026 09:00:00 2026-05-25T09:00:00Z N/A
MC1187781 (Updated) Viva Engage: Community feeds improvements 02/28/2026 09:00:00 2026-03-30T10:00:00Z N/A
MC1188599 (Updated) Microsoft 365: Modern Access Request and Access Denied web page 03/13/2026 08:00:00 2026-04-20T09:00:00Z N/A
MC1192253 (Updated) Microsoft Teams: Network Device Interface (NDI) automatic binaries update for macOS 02/16/2026 09:00:00 2026-03-23T09:00:00Z N/A
MC1192665 (Updated) Microsoft 365 admin center: Copilot settings – readiness 03/28/2026 08:00:00 2026-05-04T09:00:00Z N/A
MC1218712 (Updated) Microsoft Teams: Meeting notes now available for instant meetings 08/08/2026 09:00:00 2026-08-10T09:00:00Z N/A
MC1219793 (Updated) Brand impersonation protection for Teams Calling 04/01/2026 09:00:00 2026-04-27T09:00:00Z N/A
MC1219794 (Updated) Microsoft Teams: External domains anomalies report 04/30/2026 09:00:00 2026-04-20T09:00:00Z N/A
MC786329 (Updated) Exchange Online to retire Basic Auth for Client Submission (SMTP AUTH) 11/03/2025 09:00:00 2026-03-30T10:00:00Z N/A

MC How Affect changes

MC ID MC Title Old Value New Value MC Action required by
MC1155311 (Updated) Viva Engage: Agents in Viva Engage communities Public Preview Who is affected: Viva Engage community admins with Microsoft 365 Copilot licenses; Global and Engage admins managing Viva Engage networks

What will happen:

During Public Preview:

Admins can opt their network into the preview via the Engage admin center: Engage admin center > Tenant Settings > Enable Community Agent Public Preview.

Once enabled, admins can add agents to any community they manage.

Figure i. Add agent to community

The agent will proactively draft answers to unanswered questions using past conversations.

By default, the agent posts answers automatically.

Admins can configure whether the agent posts answers automatically or only after approval.

Figure ii. Configure the agent to require answer review before posting

If Require review is enabled, admins and designated experts will be notified when the agent drafts an answer. They can approve, edit, or dismiss the response.

Figure iii. Community admins and experts can review agent suggestions

Coming soon (General Availability):

The agent will only use content that all community members can access.

Admins must be owners of the SharePoint sites they wish to configure.

Admins can add additional SharePoint sites to expand the agent's grounding knowledge.

The agent will be grounded by default on the community's SharePoint site.

All Microsoft 365 Copilot licensed users will have access to the Community Agent by default.

The Community Agent Public Preview toggle will be retired.

 Who is affected: Viva Engage community admins and members with Microsoft 365 Copilot licenses; Global and Engage admins managing Viva Engage networks

What will happen:

During Public Preview:

Admins can opt their network into the preview via the Engage admin center: Engage admin center > Tenant Settings > Enable Community Agent Public Preview.

Once enabled, admins can add agents to any community they manage.

Figure i. Add agent to community

The agent will proactively draft answers to unanswered questions using past conversations.

By default, the agent posts answers automatically.

Admins can configure whether the agent posts answers automatically or only after approval and if tagging by community members is enabled.

Figure ii. Configure the agent's capabilities and knowledge sources

[Grounding on SharePoint sites outside the community]

Community admins can add SharePoint sites and libraries outside the community as additional grounding sources (for sites/libraries they administer).

When an admin adds a site or library, they'll be prompted to grant the community's Microsoft 365 group Read access if it doesn't already have permission.

The agent only drafts answers using content that all community members can view (Read).

By default, the agent uses the community's SharePoint site and library. Any sites outside the community are optional and add to (not replace) the default grounding.

If Require review is enabled, admins and designated experts will be notified when the agent drafts an answer. They can approve, edit, or dismiss the response.

Figure iii. Community admins and experts can review agent suggestions

If tagging by community members is enabled, then community members can @-mention the agent in messages.

Coming soon (General Availability):

The agent will only use content that all community members can access.

Admins must be owners of the SharePoint sites they wish to configure.

Admins can add additional SharePoint sites to expand the agent's grounding knowledge.

The agent will be grounded by default on the community's SharePoint site.

Community members can tag the community agent in community posts.

All Microsoft 365 Copilot licensed users will have access to the Community Agent by default.

The Community Agent Public Preview toggle will be retired.

 N/A
MC1184992 (Updated) Microsoft Teams: Improvements to "Activity in other accounts and orgs panel" Who is affected: All Microsoft Teams users with multi‑tenant, multi‑account configurations.

What will happen:

Users gain an improved centralized panel for viewing cross‑organization and cross-account activity notifications, eliminating the need to manually switch organizations or accounts to check notification and activity details. This improves responsiveness and reduces context switching.

The entry point for the panel that shows Activity in other accounts and orgs will move from the top-right corner to the bottom-left sidebar in Teams. The entry point icon will appear only when you have more than one account or tenant available to you.

The entry point icon will display a count of total missed cross‑org and cross‑account activity notifications.

Selecting the icon will open a panel which will show missed activity notifications across all orgs and accounts, grouped by each tenant. If there is no missed activity in a tenant, it will not appear in the panel.

Selecting an activity inside the panel opens it in a child window, preserving the context in the main window.

Users can pin up to 3 tenants to the sidebar to stay updated. Pinned tenants remain in the sidebar even if there is no missed activity.

Selecting a pinned tenant shows a panel with missed activity notifications from that tenant only. Notifications from pinned tenants do not appear in the main panel for activity in other accounts and orgs.

The feature is enabled by default for tenants where multi‑tenant or multi-accounts are supported and available.

No admin configuration is required, the updated panel respects existing tenant and account policies.

Review our new documentation here: Activity in other accounts and orgs - Microsoft Teams | Microsoft Learn.

 Who is affected: All Microsoft Teams users with multi‑tenant, multi‑account configurations.

What will happen:

Users gain an improved centralized panel for viewing cross‑organization and cross-account activity notifications, eliminating the need to manually switch organizations or accounts to check notification and activity details. This improves responsiveness and reduces context switching.

The entry point for the panel that shows Activity in other accounts and orgs will move from the top-right corner to the bottom-left sidebar in Teams. The entry point icon will appear only when you have more than one account or tenant available to you.

The entry point icon will display a count of total missed cross‑org and cross‑account activity notifications.

Selecting the icon will open a panel which will show missed activity notifications across all orgs and accounts, grouped by each tenant. If there is no missed activity in a tenant, it will not appear in the panel.

Selecting an activity inside the panel opens it in a child window, preserving the context in the main window.

Users can pin up to 3 tenants to the sidebar to stay updated. Pinned tenants remain in the sidebar even if there is no missed activity.

Selecting a pinned tenant shows a panel with missed activity notifications from that tenant only. Notifications from pinned tenants do not appear in the main panel for activity in other accounts and orgs.

The feature is enabled by default for tenants where multi‑tenant or multi-accounts are supported and available.

No admin configuration is required, the updated panel respects existing tenant and account policies.

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

 N/A
MC1192665 (Updated) Microsoft 365 admin center: Copilot settings – readiness Who is affected: Admins managing Microsoft 365 tenants with Copilot capabilities.

What will happen:

A new Readiness pivot will appear under Copilot > Settings in the Microsoft 365 admin center.

Admins will see grouped configuration sets aligned to key administrative outcomes.

Each package includes Microsoft's recommended presets, a personalized readiness assessment, and contextual insights.

No changes will be made automatically; admins can review and apply configurations as needed.

The experience is designed to reduce setup complexity and improve governance and security alignment.

No Microsoft 365 Copilot license is required to use this feature. Admins can configure both Copilot Chat and Microsoft 365 Copilot settings without needing a license.		 Who is affected: Admins managing Microsoft 365 tenants with Copilot capabilities. What will happen:

A new Readiness pivot will appear under Copilot > Settings in the Microsoft 365 admin center.

Admins will see grouped configuration sets aligned to key administrative outcomes.

Each package includes Microsoft's recommended presets, a personalized readiness assessment, and contextual insights.

No changes will be made automatically; admins can review and apply configurations as needed.

The experience is designed to reduce setup complexity and improve governance and security alignment.

No Microsoft 365 Copilot license is required to use this feature. Admins can configure both Copilot Chat and Microsoft 365 Copilot settings without needing a license.		 N/A
MC1219794 (Updated) Microsoft Teams: External domains anomalies report Who is affected:

Teams administrators can view this report for their Microsoft 365 tenant if their organization collaborates with external organizations.

What will happen:

A new External domains anomalies report will be available in the Microsoft Teams admin center under Protection reports.

Admins can select Communication anomalies, choose a date range, and run the report to view results:

Insights include external domains with unusual communication activity:

External domain name

Total anomalies detected

New 1:1 chat threads created by that domain

New group chat threads created by that domain

A Block option is available directly in the report for managing external domains		 Who is affected:

Teams administrators can view this report for their Microsoft 365 tenant if their organization collaborates with external organizations.

What will happen:

A new External domains anomalies report will be available in the Microsoft Teams admin center under Protection reports.

Admins can select Communication anomalies, choose a date range, and run the report to view results:

Insights include external domains with unusual communication activity:

External domain name

Total anomalies detected

New 1:1 threads created by that domain

New group threads created by that domain

A Block option is available directly in the report for managing external domains		 N/A
MC1220762 (Updated) Retirement notice: MDE and XDR Advanced Hunting APIs retiring; migrate to Microsoft Graph Security API Who is affected:

Organizations using the MDE API or XDR API for automation, integration, or custom workflows.

You are receiving this message because our reporting indicates your organization may be using these APIs.

What will happen:

The MDE and XDR APIs will stop functioning after February 1, 2027.

Existing scripts, automations, and workflows that rely on these APIs will fail if not updated.

The Microsoft Graph Security API will be the supported API for accessing Microsoft security data.

No automatic migration will occur; manual updates will be required.		 Who is affected:

Organizations using the MDE or XDR Advanced Hunting API for automation, integration, or custom workflows.

You are receiving this message because our reporting indicates your organization may be using these APIs.

What will happen:

The MDE and XDR Advanced Hunting APIs will stop functioning after February 1, 2027.

Existing scripts, automations, and workflows that rely on these APIs will fail if not updated.

The Microsoft Graph Security API will be the supported API for accessing Microsoft security data.

No automatic migration will occur; manual updates will be required.		 01/31/2027
MC772556 (Updated) Microsoft Teams: Shorter meeting URLs The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode>

To make meeting URL shorter, we are removing several parameters such as tenant ID, conversation ID etc. This change serves two main goals: 1) improving usability of URL during sharing and 2) making the URL more secure and less susceptible to malicious attacks.

Here are some details about how meeting links work and when they expire:

In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire.

Every meeting link expires in 60 days after the scheduled event or in 8 hours, if it was created as Meet Now. Learn more about expiration timelines for different types of meetings.

With the Short Meeting URL release, expiration limit will be applied to all newly created links.

Once the change to Short Meeting URL is released, all newly created meetings will expire as described in the documentation: 60 days after meeting ends for scheduled meetings and 8 hours after creation for Meet Now. Once this expiry period is over, in case someone clicks the link (e.g. outside of Teams app OR in the meeting details inside Teams calendar section), they will be unable to join the meeting.

Note: Old links created before short meeting URL release will continue working as it previously was (user will be able to join even after the documented expiry limits).

The reason why we are making this change is simple: security is our topmost priority. Maintaining a high security level is essential to protect sensitive data, prevent financial losses, ensure business continuity, and meet compliance and legal obligations. It is a critical aspect of modern digital life and business operations. This adjustment is designed to enhance the security of Teams meeting links, thereby better safeguarding the customer tenant. We want to be on par with modern security standards, that's why the new behavior is a step in the right direction that we must take. It's not possible to keep the current behavior. If you think it breaks some of your business processes, please leave comment to the MC post and describe your case there.

Recommendations in case the meeting link has expired:

For meeting organizer: We recommend scheduling a new meeting. If the meeting organizer got removed from the tenant someone else should reschedule their meetings from scratch.

For participant: Please reach out to the meeting organizer and ask them to reschedule the meeting or send you an updated link.		 The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode>

To make meeting URL shorter, we are removing several parameters such as tenant ID, conversation ID etc. This change serves two main goals: 1) improving usability of URL during sharing and 2) making the URL more secure and less susceptible to malicious attacks.

Here are some details about how meeting links work and when they expire:

In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire.

MeetNow meetings expire 60 days after creation. Learn more about expiration timelines for different types of meetings.

With the Short Meeting URL release, expiration limit will be applied to all newly created links.

Once the change to Short Meeting URL is released, all newly created meetings will expire as described in the documentation: 60 days after meeting ends for scheduled meetings and 60 days after creation for MeetNow meetings. Once this expiry period is over, in case someone clicks the link (e.g. outside of Teams app OR in the meeting details inside Teams calendar section), they will be unable to join the meeting.

Note: Old links created before short meeting URL release will continue working as it previously was (user will be able to join even after the documented expiry limits).

The reason why we are making this change is simple: security is our topmost priority. Maintaining a high security level is essential to protect sensitive data, prevent financial losses, ensure business continuity, and meet compliance and legal obligations. It is a critical aspect of modern digital life and business operations. This adjustment is designed to enhance the security of Teams meeting links, thereby better safeguarding the customer tenant. We want to be on par with modern security standards, that's why the new behavior is a step in the right direction that we must take. It's not possible to keep the current behavior. If you think it breaks some of your business processes, please leave comment to the MC post and describe your case there.

Recommendations in case the meeting link has expired:

For meeting organizer: We recommend scheduling a new meeting. If the meeting organizer got removed from the tenant someone else should reschedule their meetings from scratch.

For participant: Please reach out to the meeting organizer and ask them to reschedule the meeting or send you an updated link.		 N/A
MC786329 (Updated) Exchange Online to retire Basic Auth for Client Submission (SMTP AUTH) The SMTP AUTH Clients Submission Report in the Exchange admin center has been updated to show if Basic auth or OAuth is being used to submit email to Exchange Online. Starting in July 2025, we will send monthly Message Center posts to tenants who are using Basic auth with Client Submission (SMTP AUTH) to alert them to the upcoming change.

Starting March 1st 2026 (previously September 2025) we will gradually start rejecting Basic Auth requests to the Client Submission (SMTP AUTH) endpoints, increasing to 100% rejection by the end of the April 2026.

The Client Submission (SMTP AUTH) endpoints in scope for this change are:

* smtp.office365.com

* smtp-legacy.office365.com

Once Basic auth is permanently disabled, any clients or apps connecting using Basic auth with Client Submission (SMTP AUTH) will receive this response:

* 550 5.7.30 Basic authentication is not supported for Client Submission.		 The SMTP AUTH Clients Submission Report in the Exchange admin center has been updated to show if Basic auth or OAuth is being used to submit email to Exchange Online.

The removal of Basic Auth from SMTP AUTH Client Submission has been put on hold (previously beginning March 1st, 2026, and completing April 30th, 2026).		 N/A

MC Messages changes

MC ID MC Title Old Value New Value MC Action required by
MC1019312 (Updated) Microsoft Teams: Meeting participants can request collaborative annotation sessions Updated December 8, 2025: We have updated the timeline. Thank you for your patience.

Coming soon for Microsoft Teams: Meeting participants will be able to request an annotation session while someone else is sharing their screen.

This message applies to Teams for Windows desktop and Teams for Mac desktop. (Users can view and annotate in Teams on the web but cannot initiate annotations.)

This message is associated with Microsoft 365 Roadmap ID 89975.

[When this will happen:]

Targeted Release: We will begin rolling out early February 2026 (previously early January) and expect to complete by mid-February 2026 (previously mid-January).

General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-February 2026 (previously mid-January) and expect to complete by late February 2026 (previously late January).		 Updated January 27, 2026: We have updated the timeline. Thank you for your patience.

Coming soon for Microsoft Teams: Meeting participants will be able to request an annotation session while someone else is sharing their screen.

This message applies to Teams for Windows desktop and Teams for Mac desktop. (Users can view and annotate in Teams on the web but cannot initiate annotations.)

This message is associated with Microsoft 365 Roadmap ID 89975.

[When this will happen:]

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

General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out late March 2026 (previously mid-February) and expect to complete by late April 2026 (previously late February).		 N/A
MC1062453 (Updated) Changes to how users install Microsoft 365 apps from the Microsoft 365 Copilot app Updated December 11, 2025: No new updates on this feature rollout yet. We expect to share a status update by the end of January.

The My account portal will be replaced by a new modal dialog within the Microsoft 365 Copilot app (formerly Office.com) on web and desktop. The new modal will support end user self-installs that are currently available on the My account portal (Office, Project, Visio, and Skype for Business).

[When this will happen:]

Targeted Release: We will communicate via Message center when we are ready to proceed.

General Availability (Worldwide): We will communicate via Message center when we are ready to proceed.		 Updated January 30, 2026: Updated January 30, 2026: No new updates on this feature rollout yet. We expect to share a status update by the end of March. In the meantime, we have updated the Conditional Access Policy and Office Deployment documentation with a note that Conditional Access Policies may block Microsoft 365 self-installs.

The My account portal will be replaced by a new modal dialog within the Microsoft 365 Copilot app (formerly Office.com) on web and desktop. The new modal will support end user self-installs that are currently available on the My account portal (Office, Project, Visio, and Skype for Business).

[When this will happen:]

Targeted Release: We will communicate via Message center when we are ready to proceed.

General Availability (Worldwide): We will communicate via Message center when we are ready to proceed.		 N/A
MC1092459 (Updated) Microsoft Viva Insights: New prompt categories in the Microsoft Copilot Dashboard Updated January 14, 2026: We have updated the timeline. Thank you for your patience.

Prompt categories will be available in Microsoft Copilot Dashboard in Microsoft Viva Insights on the web to help you understand key Copilot use cases for your organization. In Microsoft Copilot Chat (work), which is grounded in work data, these prompt categories will include Ask and find, Catch up, Draft and brainstorm, and Other. These metrics will be added to the metrics library in the advanced insights app.

Learn more about Copilot Dashboard licensing requirements in Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

This message is associated with Microsoft 365 Roadmap ID 486698.

Public Preview: We will begin rolling out in early September 2025 (previously mid-September) and will complete by late September 2025

General Availability (Worldwide): We will begin rolling late January 2026 (previously mid-January) and expect to complete by end of January 2026 (previously end of December 2025).		 Updated January 29, 2026: We have updated the timeline. Thank you for your patience.

Prompt categories will be available in Microsoft Copilot Dashboard in Microsoft Viva Insights on the web to help you understand key Copilot use cases for your organization. In Microsoft Copilot Chat (work), which is grounded in work data, these prompt categories will include Ask and find, Catch up, Draft and brainstorm, and Other. These metrics will be added to the metrics library in the advanced insights app.

Learn more about Copilot Dashboard licensing requirements in Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

This message is associated with Microsoft 365 Roadmap ID 486698.

Public Preview: We will begin rolling out in early September 2025 (previously mid-September) and will complete by late September 2025

General Availability (Worldwide): We will begin rolling late February 2026 (previously late January) and expect to complete by end of February 2026 (previously end of January).		 N/A
MC1108848 (Updated) Changing output format for some database properties in Exchange Online cmdlets Updated August 21, 2025: We have updated the timeline. Thank you for your patience.

We're updating the output format of certain properties returned by Exchange Online PowerShell cmdlets to improve performance and align with backend service optimizations. This change reduces unnecessary data retrieval and enhances consistency across services.

[When this will happen:]

Rollout will begin in October 2025 (previously August) and complete by November 2025.		 Updated January 28, 2026: We have updated timelines for enforcement. The scope of the change remains unchanged. Thank you for your patience.

We're updating the output format of certain properties returned by Exchange Online PowerShell cmdlets to improve performance and align with backend service optimizations. This change reduces unnecessary data retrieval and enhances consistency across services.

[When this will happen:]

Rollout will begin in February 2026 (previously October 2025) and complete by April 2026 (previously November 2025).		 N/A
MC1117115 (Updated) Updates to custom scripting in sites and Classic Publishing site creation Updated September 2, 2025: Upcoming SharePoint Online changes may impact your organization. Please review the below.

We are implementing the following changes to custom scripting and classic publishing in SharePoint Online.

1. Disablement of custom scripting

Custom scripting will be disabled by default (setting DenyAddAndCustomizePages to 1 or $true) for sites created with the following templates:

BLANKINTERNETCONTAINER#0 = Classic Publishing Portal Site

CMSPUBLISHING#0 = Classic Publishing Site

BLANKINTERNET#0 = Classic Publishing Site Blank

CSPCONTAINER#0 = SharePoint Embedded Site

NOTE:

Existing classic publishing sites created with the templates listed above will have custom scripting disabled by default.

Disabling custom scripting does not affect the execution of scripts that have already been added to a site or page.

Refer to this documentation to learn more about the security considerations of ungoverned scripting.

2. Ability to set site property bag valued without requiring custom scripting enablement.

Users no longer need to set DenyAddAndCustomizePages to $false or 0 (i.e. enable custom scripting) in a site to manage site property bag values. We have introduced a new AllowWebPropertyBagUpdateWhenDenyAddAndCustomizePagesIsEnabled setting at the site level and at the tenant level to allow adding/managing site property bag values. Please see documentation here for tenant level setting and here for the site level setting.

3. Classic publishing sites creation and feature activation changes

Users will no longer be able to create new classic publishing related site collections or activate publishing features in existing site collections. This applies to both UX and API interactions.

Sites collections with the following templates cannot be created:

BLANKINTERNETCONTAINER#0 = Publishing Portal Site

CMSPUBLISHING#0 = Publishing Site

BLANKINTERNET#0 = Publishing Site Blank

ENTERWIKI#0 = Enterprise Wiki

SRCHCEN#0 = Enterprise Search Center

SPSSITES#0 = Site Directory

SPSNHOME#0 = News Home Site

PRODUCTCATALOG#0 = Product Catalog

SPSREPORTCENTER#0 = Report Center

SPSTOPIC#0 = Topic Area Template

Existing classic publishing enabled site collections are unaffected and can continue regular usage, including creation of sub sites.

[When this will happen]

Both changes, the extended custom scripting governance and the new classic publishing restrictions, will take effect starting September 15, 2025.		 Updated January 29, 2026: We are updating this post as a reminder. Upcoming SharePoint Online changes may impact your organization. Please review the below.

We are implementing the following changes to custom scripting and classic publishing in SharePoint Online.

1. Disablement of custom scripting

Custom scripting will be disabled by default (setting DenyAddAndCustomizePages to 1 or $true) for sites created with the following templates:

BLANKINTERNETCONTAINER#0 = Classic Publishing Portal Site

CMSPUBLISHING#0 = Classic Publishing Site

BLANKINTERNET#0 = Classic Publishing Site Blank

CSPCONTAINER#0 = SharePoint Embedded Site

NOTE:

Existing classic publishing sites created with the templates listed above will have custom scripting disabled by default.

Disabling custom scripting does not affect the execution of scripts that have already been added to a site or page.

Refer to this documentation to learn more about the security considerations of ungoverned scripting.

2. Ability to set site property bag valued without requiring custom scripting enablement.

Users no longer need to set DenyAddAndCustomizePages to $false or 0 (i.e. enable custom scripting) in a site to manage site property bag values. We have introduced a new AllowWebPropertyBagUpdateWhenDenyAddAndCustomizePagesIsEnabled setting at the site level and at the tenant level to allow adding/managing site property bag values. Please see documentation here for tenant level setting and here for the site level setting.

3. Classic publishing sites creation and feature activation changes

Users will no longer be able to create new classic publishing related site collections or activate publishing features in existing site collections. This applies to both UX and API interactions.

Sites collections with the following templates cannot be created:

BLANKINTERNETCONTAINER#0 = Publishing Portal Site

CMSPUBLISHING#0 = Publishing Site

BLANKINTERNET#0 = Publishing Site Blank

ENTERWIKI#0 = Enterprise Wiki

SRCHCEN#0 = Enterprise Search Center

SPSSITES#0 = Site Directory

SPSNHOME#0 = News Home Site

PRODUCTCATALOG#0 = Product Catalog

SPSREPORTCENTER#0 = Report Center

SPSTOPIC#0 = Topic Area Template

Existing classic publishing enabled site collections are unaffected and can continue regular usage, including creation of sub sites.

[When this will happen]

Both changes, the extended custom scripting governance and the new classic publishing restrictions, will take effect starting September 15, 2025.		 N/A
MC1121517 (Updated) Introducing the New Workflows Experience in Microsoft Teams Updated October 17, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We're introducing a new Workflows experience in Microsoft Teams that is rebuilt from the ground up based on feedback.

The Workflows app helps you automate repetitive tasks and streamline everyday processes across Teams and Microsoft 365. Whether you're scheduling messages, managing approvals, syncing updates across apps, or triggering actions from chat messages, Workflows makes it easy to build automations in just a few clicks. It's powered by Power Automate and designed to help you stay focused on what matters most.

This new version addresses previous concerns around complexity and performance, delivering a faster, more intuitive, and streamlined interface. With the updated experience, users can now create powerful automations in three steps or fewer.

This release is part of our broader effort to make automation more accessible and impactful for every information worker. Whether you're new to automation or a seasoned pro, the new Workflows app is designed to meet you where you work-and help you get more done with less effort. This message is associated with Microsoft 365 Roadmap ID 491632.

When this will happen

Public Preview & Targeted Release: We will begin rolling out in September 2025.

General Availability (Worldwide): We will begin rolling out in late January 2026 (previously October).		 Updated January 30, 2026: We have updated the timeline. Thank you for your patience.

Introduction

We're introducing a new Workflows experience in Microsoft Teams that is rebuilt from the ground up based on feedback.

The Workflows app helps you automate repetitive tasks and streamline everyday processes across Teams and Microsoft 365. Whether you're scheduling messages, managing approvals, syncing updates across apps, or triggering actions from chat messages, Workflows makes it easy to build automations in just a few clicks. It's powered by Power Automate and designed to help you stay focused on what matters most.

This new version addresses previous concerns around complexity and performance, delivering a faster, more intuitive, and streamlined interface. With the updated experience, users can now create powerful automations in three steps or fewer.

This release is part of our broader effort to make automation more accessible and impactful for every information worker. Whether you're new to automation or a seasoned pro, the new Workflows app is designed to meet you where you work-and help you get more done with less effort. This message is associated with Microsoft 365 Roadmap ID 491632.

When this will happen

Public Preview & Targeted Release: We will begin rolling out in September 2025.

General Availability (Worldwide): We will begin rolling out in late February 2026 (previously late January).		 N/A
MC1134737 (Updated) Microsoft Teams: Private channels increased limits and transition to group compliance Updated January 12, 2026: We have updated the content. Thank you for your patience.

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.

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.

Private channels can now have up to 5000 members, instead of 250.

Meetings can now be scheduled in private channels.

Compliance policies for private channels are part of the team's group policies instead of the individual user level.

The migration of private channels to the updated capabilities will begin in early October 2025 and continue through January 2026 (previously December 2025). During this period, private channels will continue to operate normally. Admins and compliance managers should complete any required policy changes by October 2025 (previosly September), before the migration begins. Changes to private channel limits and meeting scheduling will follow in February 2026. Migration can start or end at different times for each tenant during the rollout period. To track progress, a new PowerShell command will be available for tenants to check whether their migration has started or is completed. This post will be updated soon with details on the PowerShell command.

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 January 2026 (previously mid-December 2025). Updated channel limits and meeting scheduling will begin rollout in early February 2026 and we expect to complete by end of February 2026.

[Action required by compliance managers and admins]

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.

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.

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

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.

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.

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.

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.

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.

6. 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 will be available for tenants to check whether their migration has started or is completed. The command will be -

Get-TenantPrivateChannelMigrationStatus -TenantId <tenantId>

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 January 12, 2026: We have updated the content. Thank you for your patience.

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.

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.

Private channels can now have up to 5000 members, instead of 250.

Meetings can now be scheduled in private channels.

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 February 2026. 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 early March 2026.

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 February 2026. Updated channel limits and meeting scheduling will complete in March 2026.

[Action required by compliance managers and admins]

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.

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.

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

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.

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.

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.

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.

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.

6. 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 will be available for tenants to check whether their migration has started or is completed. The command will be -

Get-TenantPrivateChannelMigrationStatus -TenantId <tenantId>

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.

 N/A
MC1138786 (Updated) Viva Glint: Focus area enhancements and retirement of goal periods Updated January 14, 2026: We have updated the timeline. Thank you for your patience.

Introduction

We're introducing enhancements to the focus area experience in Viva Glint to improve how organizations track and act on employee feedback. With this update, focus areas will now be tied to survey cycles, and goal periods will be retired. This change simplifies reporting and aligns focus areas more closely with survey insights.

This update is associated with Microsoft 365 Roadmap ID 498922.

When this will happen

General availability: We will begin rolling out mid-February 2026 (previously mid-January) and expect to complete by mid-February 2026 (previously late January).		 Updated January 27, 2026: We have updated the timeline. Thank you for your patience.

Introduction

We're introducing enhancements to the focus area experience in Viva Glint to improve how organizations track and act on employee feedback. With this update, focus areas will now be tied to survey cycles, and goal periods will be retired. This change simplifies reporting and aligns focus areas more closely with survey insights.

This update is associated with Microsoft 365 Roadmap ID 498922.

When this will happen

General availability: We are pleased to announce this feature is now available.		 N/A
MC1151242 (Updated) Microsoft Teams: Improved organization chart in Profile Card (Desktop, Mac, Web) Updated January 20, 2026: We have updated the timeline. Thank you for your patience.

We're introducing an enhanced organization chart experience in the Profile Card in Microsoft Teams for Windows Desktop, Mac, and Teams on the web. This update improves the user interface and navigation while maintaining the core browsing functionality. These changes are based on user feedback to streamline org chart exploration and reduce friction in navigating team structures.

This feature is associated with Microsoft 365 Roadmap ID: 500696.

When this will happen:

Targeted Release: We will begin rolling out in early February 2026 (previously late January) and expect to complete in mid-February 2026 (previously mid-December 2025).

General Availability (Worldwide): We will begin rolling out in mid-February 2026 (previously mid-January) and expect to complete in late February 2026 (previously late January).		 Updated January 29, 2026: We have updated the timeline. Thank you for your patience.

We're introducing an enhanced organization chart experience in the Profile Card in Microsoft Teams for Windows Desktop, Mac, and Teams on the web. This update improves the user interface and navigation while maintaining the core browsing functionality. These changes are based on user feedback to streamline org chart exploration and reduce friction in navigating team structures.

This feature is associated with Microsoft 365 Roadmap ID: 500696.

When this will happen:

Targeted Release: We will begin rolling out in mid-March 2026 (previously early February) and expect to complete in late March 2026 (previously mid-February).

General Availability (Worldwide): We will begin rolling out in late March 2026 (previously mid-February) and expect to complete in early April 2026 (previously late February).		 N/A
MC1155311 (Updated) Viva Engage: Agents in Viva Engage communities Public Preview Updated September 22, 2025: We have updated the content Thank you for your patience.

[Introduction]

Agent in Viva Engage communities are now available in Public Preview. Community admins can add agents to communities to enhance knowledge sharing by drafting answers to questions without best or verified answers based on community content.

Shortly after public preview begins, we'll be enhancing agents in communities with SharePoint grounding to improve the accuracy and relevance of AI-generated answers. This update allows the agent to use content from SharePoint sites that community members can access, helping ensure responses are contextually grounded and backed by trusted sources. Agents in communities will only draft answers with content that all community members have access to. You can set up your agent with before SharePoint grounding is available and add it later.

[When this will happen:]

Agents in communities Public Preview: Begins September 18th, expected to be complete by late September

SharePoint Grounding Public Preview (Worldwide): Begins late September 2025, expected to complete by early October 2025

General Availability (Worldwide): Begins late January 2026, expected to complete by late February 2026

 Updated January 26, 2026: We have updated the content Thank you for your patience.

[Introduction]

Agent in Viva Engage communities are now available in Public Preview. Community admins can add agents to communities to help draft answers to questions without best or verified answers based on community content and add context to posts by answering follow up questions using the community's conversations and SharePoint site and library.

We're now adding the option for community admins to specify additional SharePoint sites outside the community as grounding sources. The agent will only use sites that community admins select, and it drafts answers from items that community members can view (Read).

We are also adding a new capability: tagging by community members. Tagging by community members enables Microsoft 365 copilot-licensed users to @-mention the community agent in the comments and replies of threads with follow up questions and requests to add context to posts. When tagged, the community agent will reply in the post. Tagging by community members will be enabled by default, but can be disabled by community admins in the agent settings.

[When this will happen:]

Agents in communities Public Preview: available now

SharePoint Grounding on Community site and library Public Preview (Worldwide): available now

Grounding on SharePoint sites and libraries outside the community and tagging by community members Public Preview (worldwide): Starting Feb. 16th, expected to complete by mid-March.

General Availability (Worldwide): Begins late March 2026, expected to complete by late April 2026

 N/A
MC1157712 (Updated) Microsoft OneNote | Sensitivity labels now available on desktop, web, iOS, Android, and Mac Updated January 2, 2026: We have updated the content and timeline. Thank you for your patience.

Introduction

We're introducing support for Microsoft Purview sensitivity labels in OneNote. This update enables users to manually classify and protect OneNote sections using the same compliance standards available across Microsoft 365 apps. Labels can be applied to each OneNote Section, helping ensure sensitive content is encrypted, access-controlled, and aligned with organizational policies. This change supports consistent data protection across platforms and endpoints.

This message is associated with Microsoft 365 Roadmap ID 500020.

When this will happen

General Availability (Worldwide, GCC, GCCH, and DoD): We expect to complete the rollout by late January 2026.		 Updated January 30 2026: We have updated the timeline. Thank you for your patience.

Introduction

We're introducing support for Microsoft Purview sensitivity labels in OneNote. This update enables users to manually classify and protect OneNote sections using the same compliance standards available across Microsoft 365 apps. Labels can be applied to each OneNote Section, helping ensure sensitive content is encrypted, access-controlled, and aligned with organizational policies. This change supports consistent data protection across platforms and endpoints.

This message is associated with Microsoft 365 Roadmap ID 500020.

When this will happen

General Availability (Worldwide, GCC, GCCH, and DoD): We expect to complete the rollout by late February 2026 (previously late January).		 N/A
MC1182688 (Updated) Microsoft Teams Rooms on Android: Recording and transcription controls (Teams Rooms Pro required) Updated January 13, 2026: We have updated the timeline. Thank you for your patience.

Microsoft is introducing the ability to start, stop, and restart meeting recording and transcription directly from Microsoft Teams Rooms on Android devices. This enhancement supports a more seamless meeting experience by removing the need for a companion device to initiate these actions. Spoken language for the meeting can also be changed during the session. This functionality is available with Teams Rooms Pro licensing.

When this will happen:

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

General Availability (GCCH and DoD): We will begin rolling out end of February 2026 (previously early February) and expect to complete by mid-March 2026 (previously mid-February).		 Updated January 28, 2026: We have updated the timeline. Thank you for your patience.

Microsoft is introducing the ability to start, stop, and restart meeting recording and transcription directly from Microsoft Teams Rooms on Android devices. This enhancement supports a more seamless meeting experience by removing the need for a companion device to initiate these actions. Spoken language for the meeting can also be changed during the session. This functionality is available with Teams Rooms Pro licensing.

When this will happen:

General Availability (Worldwide and GCC): We will begin rolling out mid-February 2026 (previously end of January) and expect to complete by early March 2026 (previously mid-February).

General Availability (GCCH and DoD): We will begin rolling out mid-March 2026 (previously end of February) and expect to complete by early April 2026 (previously mid-March).		 N/A
MC1183608 (Updated) Rate my call feedback experience update in Microsoft Teams Updated December 11, 2025: We have updated the timeline. Thank you for your patience.

[Introduction]

The Rate My Call survey is a feedback screen that the Teams client will occasionally present to users after their Teams call or meeting has completed. Currently, the rating presents 1-5 stars on the first page and a list of potential issues (called problem tokens) on the second page.

We will be rolling out a new streamlined feedback experience for Teams on Windows, Mac, and Web that presents the feedback on a single screen with a thumbs up / thumbs down rating system and problem tokens for the user to select, plus an area to provide details. In testing, we found higher feedback returns with this new design, and clearer insights into call quality issues.

Screenshot 1: New Rate My Call User Interface

[When this will happen:]

General Availability/Targeted Release: Rollout begins late January 2026 (previously early December 2025), completes by late January 2026 (previously mid-December 2025).

 Updated January 28, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

The Rate My Call survey is a feedback screen that the Teams client will occasionally present to users after their Teams call or meeting has completed. Currently, the rating presents 1-5 stars on the first page and a list of potential issues (called problem tokens) on the second page.

We will be rolling out a new streamlined feedback experience for Teams on Windows, Mac, and Web that presents the feedback on a single screen with a thumbs up / thumbs down rating system and problem tokens for the user to select, plus an area to provide details. In testing, we found higher feedback returns with this new design, and clearer insights into call quality issues.

Screenshot 1: New Rate My Call User Interface

[When this will happen:]

General Availability/Targeted Release: Rollout begins mid-February 2026 (previously late January), completes by late February 2026 (previously late January).

 N/A
MC1184992 (Updated) Microsoft Teams: Improvements to "Activity in other accounts and orgs panel" Updated November 12, 2025: We have added a documentation link. Thank you for your patience.

[Introduction]

We're improving the panel which shows your Activity in other accounts and orgs in Microsoft Teams to streamline how users triage and respond to cross‑tenant activity. This update reduces the need to switch tenants, helping users stay in context and collaborate more efficiently across organizations.

This message applies to Teams for Windows desktop and Teams for Mac desktop.

[When this will happen:]

Targeted Release: Begins rolling out November 16, 2025; expected to complete by November 20, 2025.

General Availability (Worldwide): Begins rolling out late January 2026; expected to complete by late February 2026.

General Availability (GCC, GCC High): Begins rolling out early February 2026; expected to complete by late February 2026.

General Availability (DoD): Begins rolling out mid-February 2026; expected to complete by mid-March 2026.		 Updated January 30, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

We're improving the panel which shows your Activity in other accounts and orgs in Microsoft Teams to streamline how users triage and respond to cross‑tenant activity. This update reduces the need to switch tenants, helping users stay in context and collaborate more efficiently across organizations.

This message applies to Teams for Windows desktop and Teams for Mac desktop.

[When this will happen:]

Targeted Release: Begins rolling out November 16, 2025; expected to complete by November 20, 2025.

General Availability (Worldwide): Begins rolling out mid-March 2026 (previously late January); expected to complete by late March 2026 (previously late February).

General Availability (GCC, GCC High): Begins rolling out mid-March 2026 (previously early February); expected to complete by late March 2026 (previously late February).

General Availability (DoD): Begins rolling out late March 2026 (previously mid-February); expected to complete by mid-April 2026 (previously mid-March).		 N/A
MC1187781 (Updated) Viva Engage: Community feeds improvements [Introduction:]

We're introducing a simpler way to view conversations in Viva Engage communities, organized by recent posts rather than recent activity. This new view is designed to make it easier for users to follow discussions and will be available as an option, alongside the current system, for those who prefer sorting by recent activity and filtering to new conversations only.

This message is associated with Microsoft 365 Roadmap ID 513275.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in January 2026.		 Updated January 27, 2026: We have updated the timeline. Thank you for your patience.

[Introduction:]

We're introducing a simpler way to view conversations in Viva Engage communities, organized by recent posts rather than recent activity. This new view is designed to make it easier for users to follow discussions and will be available as an option, alongside the current system, for those who prefer sorting by recent activity and filtering to new conversations only.

This message is associated with Microsoft 365 Roadmap ID 513275.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in February 2026 (previously January).		 N/A
MC1187799 (Updated) Microsoft Word, Excel, and PowerPoint agents: A new Copilot experience for content creation Updated January 22, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

We're introducing new Word, Excel, and PowerPoint agents in Microsoft 365 Copilot to help users create documents, workbooks, and presentations more efficiently in Copilot Chat within the Frontier program. These agents assist with creating documents, workbooks, and presentations by using web and enterprise grounding. Each agent supports multi-turn chat, enabling user to refine content through an interactive back-and-forth conversation.

[When this will happen:]

General Availability: We will begin rolling out on January 29, 2026.		 Updated January 28, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

We're introducing new Word, Excel, and PowerPoint agents in Microsoft 365 Copilot to help users create documents, workbooks, and presentations more efficiently in Copilot Chat within the Frontier program. These agents assist with creating documents, workbooks, and presentations by using web and enterprise grounding. Each agent supports multi-turn chat, enabling user to refine content through an interactive back-and-forth conversation.

[When this will happen:]

General Availability: We will begin rolling out on February 5, 2026 (previously January 29).		 N/A
MC1188599 (Updated) Microsoft 365: Modern Access Request and Access Denied web page [Introduction:]

We're introducing a visual refresh of the Access Request and Access Denied page experience across Microsoft 365, redesigned to help users quickly request access to content such as documents, SharePoint sites, or Teams meeting recordings. This update features modern Fluent illustrations, animations, and clearer messaging to make it easier to understand and resolve access issues for a more seamless collaboration experience.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in early January 2026 and expect to complete by early February 2026.		 Updated January 29, 2026: We have updated the timeline. Thank you for your patience.

[Introduction:]

We're introducing a visual refresh of the Access Request and Access Denied page experience across Microsoft 365, redesigned to help users quickly request access to content such as documents, SharePoint sites, or Teams meeting recordings. This update features modern Fluent illustrations, animations, and clearer messaging to make it easier to understand and resolve access issues for a more seamless collaboration experience.

This message is associated with Roadmap ID 553214.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in February 2026 (previously early January) and expect to complete by March 2026 (previously early February).		 N/A
MC1192253 (Updated) Microsoft Teams: Network Device Interface (NDI) automatic binaries update for macOS [Introduction]

We're introducing automatic installation and updates for the Network Device Interface (NDI) in Microsoft Teams on macOS devices. NDI allows organizations to broadcast audio and video streams from Teams meetings to local networks, enabling advanced production scenarios such as live streaming or integrating with professional video systems. This enhancement eliminates manual steps, making it easier to use NDI in Teams.

[When this will happen:]

General Availability (Worldwide, GCC, GCCH, DoD): Rollout will begin early January 2026 and is expected to complete by mid-January 2026.		 Updated January 30, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

We're introducing automatic installation and updates for the Network Device Interface (NDI) in Microsoft Teams on macOS devices. NDI allows organizations to broadcast audio and video streams from Teams meetings to local networks, enabling advanced production scenarios such as live streaming or integrating with professional video systems. This enhancement eliminates manual steps, making it easier to use NDI in Teams.

[When this will happen:]

General Availability (Worldwide, GCC, GCCH, DoD): Rollout will begin early January 2026 and is expected to complete by mid-February 2026 (previously mid-January).		 N/A
MC1192665 (Updated) Microsoft 365 admin center: Copilot settings – readiness Copilot readiness in the Microsoft 365 admin center provides a centralized experience for applying Microsoft's recommended settings, policies, and actions for Copilot. It organizes these into predefined packages so admins can quickly deploy Copilot securely and confidently.

To support IT admins in navigating the fast-paced AI landscape, Microsoft is introducing Copilot Readiness Packages in the Microsoft 365 Admin Center. These packages offer a centralized experience to discover Microsoft's recommended admin presets, grouped by key administrative outcomes. Each package includes a personalized readiness assessment, contextual insights, and step-by-step guidance-helping admins deploy Copilot securely, confidently, and efficiently.

This message is associated with Microsoft 365 Roadmap ID 526793.

[When this will happen]

Targeted Release: Begins mid-December 2025; completes mid-January 2026.

General Availability (Worldwide): Begins mid-January 2026; completes late February 2026.		 Updated January 30, 2026: We have updated the timeline. Thank you for your patience.

Copilot readiness in the Microsoft 365 admin center provides a centralized experience for applying Microsoft's recommended settings, policies, and actions for Copilot. It organizes these into predefined packages so admins can quickly deploy Copilot securely and confidently.

To support IT admins in navigating the fast-paced AI landscape, Microsoft is introducing Copilot Readiness Packages in the Microsoft 365 Admin Center. These packages offer a centralized experience to discover Microsoft's recommended admin presets, grouped by key administrative outcomes. Each package includes a personalized readiness assessment, contextual insights, and step-by-step guidance-helping admins deploy Copilot securely, confidently, and efficiently.

This message is associated with Microsoft 365 Roadmap ID 526793.

[When this will happen]

Targeted Release: Begins mid-February 2026 (previously mid-December 2025); completes mid-February 2026 (previously mid-January).

General Availability (Worldwide): Begins mid-March 2026 (previously mid-January); completes by end of March 2026 (previously late February).		 N/A
MC1215071 (Updated) Microsoft Teams admin center: New Teams External Collaboration Administrator role [Introduction]

We're excited to announce the rollout of a new built-in role-based access control (RBAC) role in the Microsoft Teams admin center called Teams External Collaboration Administrator. This role provides targeted administrative capabilities for managing external collaboration settings (Federation) in Teams, enabling organizations to delegate responsibilities securely without granting full Teams admin permissions.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in late January 2026 and expect to complete by mid-February 2026.		 Updated January 30, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

We're excited to announce the rollout of a new built-in role-based access control (RBAC) role in the Microsoft Teams admin center called Teams External Collaboration Administrator. This role provides targeted administrative capabilities for managing external collaboration settings (Federation) in Teams, enabling organizations to delegate responsibilities securely without granting full Teams admin permissions.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in early February 2026 (previously late January) and expect to complete by mid-February 2026.		 N/A
MC1218712 (Updated) Microsoft Teams: Meeting notes now available for instant meetings [Introduction]

Teams meeting Notes, powered by Loop, are now available for instant calls and meetings, like those started from Meet now and calls started from chat. Meeting notes are Loop components in Teams meetings and chats that allow users to collaboratively build agendas, capture notes, and create action items. Once added, they stay in sync and can be shared and edited in the Loop app in your web browser.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web and is associated with Microsoft 365 Roadmap ID 541831.

[When this will happen:]

Targeted Release: We will begin rollout early February 2026 and expect to complete late February 2026.

General Availability (Worldwide): We will begin rollout late February 2026 and expect to complete late March 2026.

General Availability (GCC): We will begin rollout late April 2026 and expect to complete late May 2026.

General Availability (GCC High): We will begin rollout mid May 2026 and expect to complete mid June 2026.

General Availability (DoD): We will begin rollout early June 2026 and expect to complete early July 2026.		 Updated January 26, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

Teams meeting Notes, powered by Loop, are now available for instant calls and meetings, like those started from Meet now and calls started from chat. Meeting notes are Loop components in Teams meetings and chats that allow users to collaboratively build agendas, capture notes, and create action items. Once added, they stay in sync and can be shared and edited in the Loop app in your web browser.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web and is associated with Microsoft 365 Roadmap ID 541831.

[When this will happen:]

Targeted Release: We will begin rollout mid-March 2026 (previously early February) and expect to complete late March 2026 (previously late February).

General Availability (Worldwide): We will begin rollout early April 2026 (previously late February) and expect to complete late April 2026 (previously late March).

General Availability (GCC): We will begin rollout mid-May 2026 (previously late April) and expect to complete late May 2026.

General Availability (GCC High): We will begin rollout late May 2026 (previously mid-May) and expect to complete mid-June 2026.

General Availability (DoD): We will begin rollout early June 2026 and expect to complete early July 2026.		 N/A
MC1219793 (Updated) Brand impersonation protection for Teams Calling [Introduction]

Brand Impersonation Protection for Teams Calling adds proactive safeguards against fraudulent or deceptive external callers who attempt to appear as trusted organizations. This helps reduce social-engineering risks and improves tenant security when users receive first-contact external calls. This update aligns with Microsoft's ongoing investments in caller identity protection and secure collaboration.

This message is associated with Microsoft 365 Roadmap ID 543239.

[When this will happen:]

Targeted Release: Rollout will begin mid-February 2026 and is expected to complete by late February 2026.

General Availability: Timelines will be communicated in a future message.		 Updated January 26, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

Brand Impersonation Protection for Teams Calling adds proactive safeguards against fraudulent or deceptive external callers who attempt to appear as trusted organizations. This helps reduce social-engineering risks and improves tenant security when users receive first-contact external calls. This update aligns with Microsoft's ongoing investments in caller identity protection and secure collaboration.

This message is associated with Microsoft 365 Roadmap ID 543239.

[When this will happen:]

Targeted Release: Rollout will begin mid-March 2026 (previously mid-February) and is expected to complete by late March 2026 (previously late February).

General Availability: Timelines will be communicated in a future message.		 N/A
MC1219794 (Updated) Microsoft Teams: External domains anomalies report [Introduction]

To help admins detect unusual or potentially risky interactions with external organizations, Microsoft Teams is introducing the External domains anomalies report. This report analyzes cross-tenant communication patterns for your tenant and highlights sudden spikes or abnormal engagement activity. These insights support proactive investigation and help protect your organization while enabling secure external collaboration.

This message is associated with Microsoft 365 Roadmap ID 536572.

[When this will happen]

General Availability (Worldwide): Rolling out in late February 2026 and expected to complete in March 2026.		 Updated January 29, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

To help admins detect unusual or potentially risky interactions with external organizations, Microsoft Teams is introducing the External domains anomalies report. This report analyzes cross-tenant communication patterns for your tenant and highlights sudden spikes or abnormal engagement activity. These insights support proactive investigation and help protect your organization while enabling secure external collaboration.

This message is associated with Microsoft 365 Roadmap ID 536572.

[When this will happen]

General Availability (Worldwide): Rolling out in early March 2026 (previously late February) and expected to complete in mid-March 2026.		 N/A
MC1220762 (Updated) Retirement notice: MDE and XDR Advanced Hunting APIs retiring; migrate to Microsoft Graph Security API [Introduction]

We're retiring the Microsoft Defender for Endpoint (MDE) API and XDR API and transitioning customers to the Microsoft Graph Security API. This update aligns our security integrations with a unified interface and schema across Microsoft Defender products. The Microsoft Graph Security API provides broader data coverage, improved consistency, and better scalability for automation and security workflows.

[When this will happen]

Retirement start: February 6, 2026

Full retirement: February 1, 2027

After February 1, 2027, the MDE and XDR APIs will no longer function.		 Updated January 26, 2026: We have updated the content. Thank you for your patience.

[Introduction]

We're retiring the Microsoft Defender for Endpoint (MDE) API and XDR Advanced Hunting API and transitioning customers to the Microsoft Graph Security API. This update aligns our security integrations with a unified interface and schema across Microsoft Defender products. The Microsoft Graph Security API provides broader data coverage, improved consistency, and better scalability for automation and security workflows.

[When this will happen]

Retirement start: February 6, 2026

Full retirement: February 1, 2027

After February 1, 2027, the MDE and XDR APIs will no longer function.		 01/31/2027
MC1220762 (Updated) Retirement notice: MDE and XDR Advanced Hunting APIs retiring; migrate to Microsoft Graph Security API Updated January 26, 2026: We have updated the content. Thank you for your patience.

[Introduction]

We're retiring the Microsoft Defender for Endpoint (MDE) API and XDR Advanced Hunting API and transitioning customers to the Microsoft Graph Security API. This update aligns our security integrations with a unified interface and schema across Microsoft Defender products. The Microsoft Graph Security API provides broader data coverage, improved consistency, and better scalability for automation and security workflows.

[When this will happen]

Retirement start: February 6, 2026

Full retirement: February 1, 2027

After February 1, 2027, the MDE and XDR APIs will no longer function.		 Updated January 26, 2026: We have updated the content. Thank you for your patience.

[Introduction]

We're retiring the Microsoft Defender for Endpoint (MDE) Advanced Hunting API and Microsoft Defender XDR Advanced Hunting API and transitioning customers to the Microsoft Graph Security API. This update aligns our security integrations with a unified interface and schema across Microsoft Defender products. The Microsoft Graph Security API provides broader data coverage, improved consistency, and better scalability for automation and security workflows.

[When this will happen]

Retirement start: February 6, 2026

Full retirement: February 1, 2027

After February 1, 2027, the MDE and XDR APIs will no longer function.		 01/31/2027
MC786329 (Updated) Exchange Online to retire Basic Auth for Client Submission (SMTP AUTH) Updated June 12, 2025: We have delayed the Basic Auth removal from SMTP AUTH Client Submission to begin March 1st 2026 and complete by April 30th 2026 in order to give customers more time to adopt alternatives. Expect no further delays beyond this date. Please review the information below for more details.

Updated October 18, 2024: We have updated the SMTP AUTH Clients Submission Report in the Exchange admin center, adding the Authentication Protocol column to show if Basic auth or OAuth is being used to submit email to Exchange Online. The data will build up over the next 90 days. Thank you for your patience.

Today, we are announcing that Exchange Online will permanently remove support for Basic authentication with Client Submission (SMTP AUTH) gradually beginning with a small percentage of submission rejections for all tenants on March 1st 2026 and reaching 100% rejections on April 30th 2026, (previously September 2025). After this time, applications and devices will no longer be able to use Basic auth as an authentication method and must use OAuth when using SMTP AUTH to send email.

Basic auth is a legacy authentication method that sends usernames and passwords in plain text over the network. This makes it vulnerable to credential theft, phishing, and brute force attacks. To improve the protection of our customers and their data, we are retiring Basic auth from Client Submission (SMTP AUTH) and encouraging customers to use modern authentication methods that are more secure.

[When this will happen:]

We will be making this change beginning March 1st, 2026, and completing April 30th, 2026 (previously September 2025).		 Updated January 27, 2026: Based on customer feedback and visibility into adoption progress, we are refining the Exchange Online SMTP AUTH Basic Authentication Deprecation timeline to provide clearer milestones and additional runway.

Now to December 2026: SMTP AUTH Basic Authentication behavior remains unchanged.

End of December 2026: SMTP AUTH Basic Authentication will be disabled by default for existing tenants. Administrators will still be able to enable it if needed.

New tenants created after December 2026: SMTP AUTH Basic Authentication will be unavailable by default. OAuth will be the supported authentication method.

Second half of 2027: Microsoft will announce the final removal date for SMTP AUTH Basic Authentication.

We will provide detailed information in a follow up Message Center Post.

Updated October 18, 2024: We have updated the SMTP AUTH Clients Submission Report in the Exchange admin center, adding the Authentication Protocol column to show if Basic auth or OAuth is being used to submit email to Exchange Online. The data will build up over the next 90 days. Thank you for your patience.

The SMTP AUTH Basic Authentication Deprecation has been put on hold. In 2027, Microsoft will announce the final removal date for SMTP AUTH Basic Authentication.

Once Basic Auth is removed from SMTP AUTH, applications and devices will no longer be able to use Basic auth as an authentication method and must use OAuth when using SMTP AUTH to send email.

Basic auth is a legacy authentication method that sends usernames and passwords in plain text over the network. This makes it vulnerable to credential theft, phishing, and brute force attacks.

[When this will happen:]

The removal of Basic Auth from SMTP AUTH Client Submission has been put on hold (previously beginning March 1st, 2026, and completing April 30th, 2026).		 N/A

MC MessageTagNames changes

MC ID MC Title Old Value New Value MC Action required by
MC1187781 (Updated) Viva Engage: Community feeds improvements New feature, User impact, Admin impact Updated message, New feature, User impact, Admin impact N/A
MC1188599 (Updated) Microsoft 365: Modern Access Request and Access Denied web page Feature update, User impact, Admin impact Updated message, Feature update, User impact, Admin impact N/A
MC1192253 (Updated) Microsoft Teams: Network Device Interface (NDI) automatic binaries update for macOS Feature update, User impact Updated message, Feature update, User impact N/A
MC1192665 (Updated) Microsoft 365 admin center: Copilot settings – readiness New feature, User impact, Admin impact Updated message, New feature, User impact, Admin impact N/A
MC1215071 (Updated) Microsoft Teams admin center: New Teams External Collaboration Administrator role New feature, Admin impact Updated message, New feature, Admin impact N/A
MC1218712 (Updated) Microsoft Teams: Meeting notes now available for instant meetings New feature, User impact Updated message, New feature, User impact N/A
MC1219793 (Updated) Brand impersonation protection for Teams Calling New feature, User impact, Admin impact Updated message, New feature, User impact, Admin impact N/A
MC1219794 (Updated) Microsoft Teams: External domains anomalies report New feature, User impact, Admin impact Updated message, New feature, User impact, Admin impact N/A
MC1220762 (Updated) Retirement notice: MDE and XDR Advanced Hunting APIs retiring; migrate to Microsoft Graph Security API User impact, Admin impact, Retirement Updated message, User impact, Admin impact, Retirement 01/31/2027

MC prepare changes

MC ID MC Title Old Value New Value MC Action required by
MC1062453 (Updated) Changes to how users install Microsoft 365 apps from the Microsoft 365 Copilot app If you allow users to self-install apps:

Please remove direct links to the My account portal (https://portal.office.com/account) in your self-install communications. Instead, please refer your users to the official Microsoft documentation for installing Office (Download, install or reinstall Microsoft 365 or Office 2024 on PC or Mac). This article will be updated to describe the new self-installs experience when it is released.

If you do not allow users to install apps:

You can continue to use the Microsoft 365 admin center installation options setting or the m365AppsInstallationOptions API to block self-installs. If you already configured these settings, users will still be blocked from installing apps in the new experience.

Blocking Microsoft Admin Portals using Conditional Access Policies will no longer block self-installs. If you have used this setting to block self-installations, you will need to use one of the settings listed above instead.

https://learn.microsoft.com/graph/api/m365appsinstallationoptions-update?view=graph-rest-1.0&tabs=http

https://learn.microsoft.com/microsoft-365-apps/deploy/manage-software-download-settings-office-365

https://m365.cloud.microsoft/

https://portal.office.com/account/

https://support.microsoft.com/office/download-install-or-reinstall-microsoft-365-or-office-2024-on-a-pc-or-mac-4414eaaf-0478-48be-9c42-23adc4716658		 If you allow users to self-install apps:

Please remove direct links to the My account portal (https://portal.office.com/account) in your self-install communications. Instead, please refer your users to the official Microsoft documentation for installing Office (Download, install or reinstall Microsoft 365 or Office 2024 on PC or Mac). This article will be updated to describe the new self-installs experience when it is released.

If you do not allow users to install apps:

You can continue to use the Microsoft 365 admin center installation options setting or the m365AppsInstallationOptions API to block self-installs. If you already configured these settings, users will still be blocked from installing apps in the new experience.

Blocking Microsoft Admin Portals using Conditional Access Policies will no longer block self-installs. If you have used this setting to block self-installations, you will need to use one of the settings listed above instead.

https://learn.microsoft.com/entra/identity/conditional-access/concept-conditional-access-cloud-apps?tabs=powershell#microsoft-admin-portals

https://learn.microsoft.com/graph/api/m365appsinstallationoptions-update?view=graph-rest-1.0&tabs=http

https://learn.microsoft.com/microsoft-365-apps/deploy/manage-software-download-settings-office-365

https://learn.microsoft.com/microsoft-365-apps/deploy/plan-microsoft-365-apps

https://m365.cloud.microsoft/

https://portal.office.com/account/

https://support.microsoft.com/office/download-install-or-reinstall-microsoft-365-or-office-2024-on-a-pc-or-mac-4414eaaf-0478-48be-9c42-23adc4716658		 N/A
MC1108848 (Updated) Changing output format for some database properties in Exchange Online cmdlets No action is required. There are no settings or controls to manage this change. If you have scripts that parse these property values, we recommend reviewing them to ensure compatibility. No action is required. There are no settings or controls to manage this change. If you have scripts that parse these property values, we recommend reviewing them to ensure compatibility.

The complete list of cmdlets impacted is as follows:

Cmdlet Output Type

Add-DistributionGroupMemberMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient

Get-DistributionGroupMemberMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient

Get-FederatedOrganizationIdentifier Microsoft.Exchange.Data.Directory.Management.FederatedOrganizationIdWithDomainStatus

Get-Mailbox Microsoft.Exchange.Data.Directory.Management.Mailbox

New-MailboxMicrosoft.Exchange.Data.Directory.Management.MailboxPlan

Get-MailboxPlanMicrosoft.Exchange.Data.Directory.Management.MailboxPlan

Get-MailUserMicrosoft.Exchange.Data.Directory.Management.MailUser

New-MailUser Microsoft.Exchange.Data.Directory.Management.MailUser

Get-RecipientMicrosoft.Exchange.Data.Directory.Management.ReducedRecipient

Add-RoleGroupMember Microsoft.Exchange.Data.Directory.Management.ReducedRecipient

Get-RoleGroupMember Microsoft.Exchange.Data.Directory.Management.ReducedRecipient

New-SyncMailPublicFolderMicrosoft.Exchange.Data.Directory.Recipient.ADPublicFolder

The affected properties for each Output Type are as follows:

Output TypeProperty

Microsoft.Exchange.Data.Directory.Recipient.ADPublicFolderDatabase

Microsoft.Exchange.Data.Directory.Recipient.ADPublicFolderHomeMTA

Microsoft.Exchange.Data.Directory.Management.FederatedOrganizationIdWithDomainStatusDelegationTrustLink

Microsoft.Exchange.Data.Directory.Management.MailboxDatabase

Microsoft.Exchange.Data.Directory.Management.MailboxPreviousDatabase

Microsoft.Exchange.Data.Directory.Management.MailboxDisabledArchiveDatabase

Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveTargetMDB

Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveSourceMDB

Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveTargetArchiveMDB

Microsoft.Exchange.Data.Directory.Management.MailboxMailboxMoveSourceArchiveMDB

Microsoft.Exchange.Data.Directory.Management.MailboxPlanDatabase

Microsoft.Exchange.Data.Directory.Management.MailboxPlanPreviousDatabase

Microsoft.Exchange.Data.Directory.Management.MailboxPlanDisabledArchiveDatabase

Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveTargetMDB

Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveSourceMDB

Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveTargetArchiveMDB

Microsoft.Exchange.Data.Directory.Management.MailboxPlanMailboxMoveSourceArchiveMDB

Microsoft.Exchange.Data.Directory.Management.MailUserDisabledArchiveDatabase

 N/A
MC1117115 (Updated) Updates to custom scripting in sites and Classic Publishing site creation We recommend taking the following actions to prepare for these upcoming changes.

1. Inform owners of the classic publishing sites in your organization of these upcoming changes. Promote switching to use of Modern sites. Refer to this guide.

2. To temporarily opt out of the custom scripting enforcement in classic publishing sites for your tenant until March 15, 2026, use the following PowerShell command:

Set-SPOTenant -DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites $true

3. To temporarily opt out of custom scripting enforcement for a specific site (with any template) with tenant admin approval (effective for 24 hours), use the following PowerShell command:

Set-SPOSite <SiteURL> -DenyAddAndCustomizePages $false

4. If you need to allow the creation of new classic publishing site collections or enable publishing feature activations, use the following PowerShell command set the flag to allow.

Set-SPOTenant -AllowClassicPublishingSiteCreation $true

NOTE:

You need to install the latest (16.0.26211.12010 or higher) SharePoint Online Management Shell in order to run the commands above.

The DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites command is scheduled to end starting on March 15, 2026, while all other commands are expected to remain functional beyond that date.

[Compliance considerations]

There is no impact or change to compliance.

[Referenced content]

Security considerations of allowing custom script - SharePoint in Microsoft 365 | Microsoft Learn

Allow or prevent custom script - SharePoint in Microsoft 365 | Microsoft Learn

SharePoint modernization guidance | Microsoft Learn

https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script

https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script#features-affected-when-custom-script-is-blocked

https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-guidance

https://learn.microsoft.com/en-us/sharepoint/security-considerations-of-allowing-custom-script

https://learn.microsoft.com/powershell/module/sharepoint-online/set-sposite?view=sharepoint-ps#-allowwebpropertybagupdatewhendenyaddandcustomizepagesisenabled

https://learn.microsoft.com/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps#-allowwebpropertybagupdatewhendenyaddandcustomizepagesisenabled

https://learn.microsoft.com/sharepoint/dev/transform/modernize-guidance

https://learn.microsoft.com/sharepoint/security-considerations-of-allowing-custom-script

https://www.microsoft.com/en-us/download/details.aspx?id=35588&msockid=1928b372f07766b62b63a78cf1426719		 We recommend taking the following actions to prepare for these upcoming changes.

1. Inform owners of the classic publishing sites in your organization of these upcoming changes. Promote switching to use of Modern sites. Refer to this guide.

2. The following tenant-level opt-out operation, used to allow custom scripting changes in classic publishing sites, will be retired starting March 15, 2026. Please ensure appropriate actions are taken ahead of this change.

Set-SPOTenant -DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites $true

3. Customers may still temporarily opt out of custom scripting enforcement for a specific site (any template) with tenant admin approval. This opt-out is effective for 24 hours and can be enabled using the following PowerShell command:

Set-SPOSite <SiteURL> -DenyAddAndCustomizePages $false

4. If you need to allow the creation of new classic publishing site collections or enable publishing feature activations, use the following PowerShell command set the flag to allow.

Set-SPOTenant -AllowClassicPublishingSiteCreation $true

NOTE:

You need to install the latest (16.0.26211.12010 or higher) SharePoint Online Management Shell in order to run the commands above.

The DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites command is scheduled to end starting on March 15, 2026, while all other commands are expected to remain functional beyond that date.

[Compliance considerations]

There is no impact or change to compliance.

[Referenced content]

Security considerations of allowing custom script - SharePoint in Microsoft 365 | Microsoft Learn

Allow or prevent custom script - SharePoint in Microsoft 365 | Microsoft Learn

SharePoint modernization guidance | Microsoft Learn

https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script

https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script#features-affected-when-custom-script-is-blocked

https://learn.microsoft.com/en-us/sharepoint/dev/transform/modernize-guidance

https://learn.microsoft.com/en-us/sharepoint/security-considerations-of-allowing-custom-script

https://learn.microsoft.com/powershell/module/sharepoint-online/set-sposite?view=sharepoint-ps#-allowwebpropertybagupdatewhendenyaddandcustomizepagesisenabled

https://learn.microsoft.com/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps#-allowwebpropertybagupdatewhendenyaddandcustomizepagesisenabled

https://learn.microsoft.com/sharepoint/dev/transform/modernize-guidance

https://learn.microsoft.com/sharepoint/security-considerations-of-allowing-custom-script

https://www.microsoft.com/en-us/download/details.aspx?id=35588&msockid=1928b372f07766b62b63a78cf1426719		 N/A
MC1184992 (Updated) Microsoft Teams: Improvements to "Activity in other accounts and orgs panel" Communicate this change to users, including the new location of the Activity in other accounts and orgs panel and the ability to pin tenants to the sidebar.

Monitor adoption and gather feedback for future iterations.

No admin action is required for rollout.

Known issue: Cross-cloud notifications do not appear in the Activity in other accounts and orgs panel at this time. This capability is actively being worked on and is expected to be available by the end of November 2025.

[Compliance considerations:]

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

https://learn.microsoft.com/microsoftteams/activity-in-other-accounts-orgs		 Communicate this change to users, including the new location of the Activity in other accounts and orgs panel and the ability to pin tenants to the sidebar.

Monitor adoption and gather feedback for future iterations.

No admin action is required for rollout.

Known issue: Cross-cloud notifications do not appear in the Activity in other accounts and orgs panel at this time. This capability is actively being worked on and is expected to be available by the end of November 2025.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.		 N/A
MC1188599 (Updated) Microsoft 365: Modern Access Request and Access Denied web page No action is required to enable this update; it will be applied automatically.

However, to ensure a smooth experience for your users, we recommend the following:

Communicate this change to helpdesk and support staff so they can assist users who may have questions about the new visuals or messaging.

Update internal documentation if you reference the Access Request or Access Denied experience in training materials or support guides.

Review any custom workflows or access request processes to ensure they align with the updated experience.

Monitor user feedback after rollout to identify any confusion or support needs related to the new design.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.		 No action is required to enable this update; it will be applied automatically.

However, to ensure a smooth experience for your users, we recommend the following:

Communicate this change to helpdesk and support staff so they can assist users who may have questions about the new visuals or messaging.

Update internal documentation if you reference the Access Request or Access Denied experience in training materials or support guides.

Review any custom workflows or access request processes to ensure they align with the updated experience.

Monitor user feedback after rollout to identify any confusion or support needs related to the new design.

[Compliance considerations:]

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

https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=553214#Roadmap		 N/A
MC1217638 (Updated) Improvements to meeting threads in Microsoft Teams channels No action is required. This update will roll out automatically.

Optional: Communicate this change to helpdesk staff to reduce potential confusion.

For more information on channel meetings, visit: Channel meetings in Teams.

[Compliance considerations:]

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

https://learn.microsoft.com/microsoftteams/meetings-channels		 No action is required. This update will roll out automatically.

Optional: Communicate this change to helpdesk staff to reduce potential confusion.

For more information on channel meetings, visit: Meetings in Teams.

[Compliance considerations:]

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

https://learn.microsoft.com/microsoftteams/plan-meetings		 N/A
MC1220762 (Updated) Retirement notice: MDE and XDR Advanced Hunting APIs retiring; migrate to Microsoft Graph Security API Migrate all existing API workflows to the Microsoft Graph Security API by January 31, 2027.

Update internal documentation, automation scripts, and integration endpoints to use the Microsoft Graph Security API.

Communicate these changes to your security operations, engineering, and development teams.

Review Microsoft documentation to plan your migration: Use the Microsoft Graph security API.

If your organization uses custom solutions, validate that new queries and response schemas work as expected before the retirement date.

Learn more:

Advanced hunting - Use the Microsoft Graph security API | Microsoft Graph | Microsoft Learn

Migrate from the older APIs - Use the Microsoft Graph security API | Microsoft Graph | Microsoft Learn

(to be retired) Microsoft Defender for Endpoint (MDE) API

(to be retired) Microsoft Defender XDR API

[Compliance considerations]

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

https://learn.microsoft.com/defender-endpoint/api/run-advanced-query-api

https://learn.microsoft.com/defender-xdr/api-overview

https://learn.microsoft.com/graph/api/resources/security-api-overview?view=graph-rest-1.0

https://learn.microsoft.com/graph/api/resources/security-api-overview?view=graph-rest-1.0#advanced-hunting

https://learn.microsoft.com/graph/api/resources/security-api-overview?view=graph-rest-1.0#migrate-from-the-older-apis		 Migrate all existing API workflows to the Microsoft Graph Security API by January 31, 2027.

Update internal documentation, automation scripts, and integration endpoints to use the Microsoft Graph Security API.

Communicate these changes to your security operations, engineering, and development teams.

Review Microsoft documentation to plan your migration: Use the Microsoft Graph security API.

If your organization uses custom solutions, validate that new queries and response schemas work as expected before the retirement date.

Learn more:

Advanced hunting - Use the Microsoft Graph security API | Microsoft Graph | Microsoft Learn

Migrate from the older APIs - Use the Microsoft Graph security API | Microsoft Graph | Microsoft Learn

(to be retired) Advanced Hunting API - Microsoft Defender for Endpoint | Microsoft Learn

(to be retired) Microsoft Defender XDR advanced hunting API - Microsoft Defender XDR | Microsoft Learn

[Compliance considerations]

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

https://learn.microsoft.com/defender-endpoint/api/run-advanced-query-api

https://learn.microsoft.com/defender-xdr/api-advanced-hunting

https://learn.microsoft.com/graph/api/resources/security-api-overview?view=graph-rest-1.0

https://learn.microsoft.com/graph/api/resources/security-api-overview?view=graph-rest-1.0#advanced-hunting

https://learn.microsoft.com/graph/api/resources/security-api-overview?view=graph-rest-1.0#migrate-from-the-older-apis		 01/31/2027
MC786329 (Updated) Exchange Online to retire Basic Auth for Client Submission (SMTP AUTH) If your client supports OAuth, follow these steps: Authenticate an IMAP, POP or SMTP connection using OAuth

If your client doesn't support OAuth and you must use Basic Auth with Client Submission (SMTP AUTH), you will need to switch to one of the following alternatives before April 2026, previously September 2025:

* If you are using basic authentication with Client Submission (SMTP AUTH) to send emails to recipients internal to your tenant, you can use Microsoft 365 High Volume Email. Please visit this site to learn more: Manage high volume emails for Microsoft 365 Public preview

* If you are using basic authentication with Client Submission (SMTP AUTH) to send emails to recipients internal and external to your tenant, you can use Azure Communication Services Email. Please visit this site to learn more: Overview of Azure Communication Services email

* If you have an Exchange Server on-premises in a hybrid configuration, you can use Basic auth to authenticate with the Exchange Server on-premises or configure the Exchange Server on-premises with a Receive connector that allows anonymous relay on Exchange servers. Please visit this site to learn more: Allow anonymous relay on Exchange servers

Regardless of the volume of email, if you must use Basic auth to send email with Exchange Online, then you must use one of the alternatives or a 3P solution.

We understand that this change requires some adjustments, but we believe that this is a necessary step to enhance the security and reliability of our email service and your data.

https://learn.microsoft.com/azure/communication-services/concepts/email/email-overview

https://learn.microsoft.com/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth

https://learn.microsoft.com/exchange/mail-flow/connectors/allow-anonymous-relay?view=exchserver-2019

https://learn.microsoft.com/Exchange/mail-flow-best-practices/high-volume-mails-m365		 The removal of Basic Auth from SMTP AUTH Client Submission has been put on hold (previously beginning March 1st, 2026, and completing April 30th, 2026)

If your client supports OAuth, follow these steps: Authenticate an IMAP, POP or SMTP connection using OAuth

If your client doesn't support OAuth and you must use Basic Auth with Client Submission (SMTP AUTH), you will need to switch to one of the following alternatives following the timeline that will be announced in 2027 (previously April 2026):

* If you are using basic authentication with Client Submission (SMTP AUTH) to send emails to recipients internal to your tenant, you can use Microsoft 365 High Volume Email. Please visit this site to learn more: Manage high volume emails for Microsoft 365 Public preview

* If you have an Exchange Server on-premises in a hybrid configuration, you can use Basic auth to authenticate with the Exchange Server on-premises or configure the Exchange Server on-premises with a Receive connector that allows anonymous relay on Exchange servers. Please visit this site to learn more: Allow anonymous relay on Exchange servers

Regardless of the volume of email, if you must use Basic auth to send email with Exchange Online, then you must use one of the alternatives or a 3P solution.

We understand that this change requires some adjustments, but we believe that this is a necessary step to enhance the security and reliability of our email service and your data.

https://learn.microsoft.com/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth

https://learn.microsoft.com/exchange/mail-flow/connectors/allow-anonymous-relay?view=exchserver-2019

https://learn.microsoft.com/Exchange/mail-flow-best-practices/high-volume-mails-m365		 N/A

MC Title changes

MC ID MC Title Old Value New Value MC Action required by
MC1187781 (Updated) Viva Engage: Community feeds improvements Viva Engage: Community feeds improvements (Updated) Viva Engage: Community feeds improvements N/A
MC1188599 (Updated) Microsoft 365: Modern Access Request and Access Denied web page Microsoft 365: Modern Access Request and Access Denied web page (Updated) Microsoft 365: Modern Access Request and Access Denied web page N/A
MC1192253 (Updated) Microsoft Teams: Network Device Interface (NDI) automatic binaries update for macOS Microsoft Teams: Network Device Interface (NDI) automatic binaries update for macOS (Updated) Microsoft Teams: Network Device Interface (NDI) automatic binaries update for macOS N/A
MC1192665 (Updated) Microsoft 365 admin center: Copilot settings – readiness Microsoft 365 admin center: Copilot settings – readiness (Updated) Microsoft 365 admin center: Copilot settings – readiness N/A
MC1215071 (Updated) Microsoft Teams admin center: New Teams External Collaboration Administrator role Microsoft Teams admin center: New Teams External Collaboration Administrator role (Updated) Microsoft Teams admin center: New Teams External Collaboration Administrator role N/A
MC1218712 (Updated) Microsoft Teams: Meeting notes now available for instant meetings Microsoft Teams: Meeting notes now available for instant meetings (Updated) Microsoft Teams: Meeting notes now available for instant meetings N/A
MC1219793 (Updated) Brand impersonation protection for Teams Calling Brand impersonation protection for Teams Calling (Updated) Brand impersonation protection for Teams Calling N/A
MC1219794 (Updated) Microsoft Teams: External domains anomalies report Microsoft Teams: External domains anomalies report (Updated) Microsoft Teams: External domains anomalies report N/A
MC1220762 (Updated) Retirement notice: MDE and XDR Advanced Hunting APIs retiring; migrate to Microsoft Graph Security API Retirement notice: MDE and XDR APIs retiring; migrate to Microsoft Graph Security API (Updated) Retirement notice: MDE and XDR Advanced Hunting APIs retiring; migrate to Microsoft Graph Security API 01/31/2027

CW05 New Office 365 Message Center items

MC ID MC Title MC Category MC Workload MC Major Change MC Action required by
MC1222652 Outlook mobile: Users can open and send Outlook File Template (OFT) files Stay Informed Exchange Online False N/A
MC1222651 Automatic synchronization with device time zone, no client restart required Stay Informed Microsoft Teams False N/A
MC1222648 Microsoft Viva Glint: Copilot will default to ON and move to VFAM as the single control Plan For Change Microsoft Viva True N/A
MC1222981 SharePoint: Migrate the Maps web part to Azure Maps Plan For Change SharePoint Online True N/A
MC1222980 Microsoft 365 Copilot: Pay-as-you-go consumption for the Copilot Retrieval API Stay Informed Microsoft 365 Copilot Chat False N/A
MC1222979 New Built-in Alert Tuning Rules optimize your incident and alert queues Stay Informed Microsoft Defender XDR False N/A
MC1222977 Microsoft Defender for Android: End of support for Android 10 devices Plan For Change Microsoft Defender XDR True 03/20/2026
MC1222976 Email customization is now available in Site Lifecycle Management Policies Stay Informed SharePoint Online False N/A
MC1223294 Updates available for Microsoft 365 Apps for Current Channel Stay Informed Microsoft 365 apps False N/A
MC1223828 Microsoft Teams: Report a suspicious call Stay Informed Microsoft Teams, Microsoft Defender XDR False N/A
MC1223827 Microsoft Teams: New Drafts quick view Stay Informed Microsoft Teams False N/A
MC1223826 Open Outlook emails directly in Copilot chat Stay Informed Microsoft 365 Copilot Chat False N/A
MC1223820 Microsoft Teams: View code blocks on mobile Stay Informed Microsoft Teams False N/A
MC1224565 Trust DigiCert Global Root G2 certificate authority to avoid Exchange Online email disruption Plan For Change Exchange Online True 04/29/2026
MC1224564 Updated feedback experience for Microsoft Planner Stay Informed Planner False N/A
MC1225195 Drawn electronic signatures with eSignature for Microsoft 365 Stay Informed SharePoint Online, Microsoft 365 apps False N/A
MC1225193 Copilot Studio product terms update for Bing query data Stay Informed Microsoft Power Automate in Microsoft 365, Microsoft Copilot (Microsoft 365), Microsoft 365 Copilot Chat False N/A
MC1225192 Microsoft Entra ID Governance: Azure subscription required to continue using guest governance features Plan For Change Microsoft Entra True N/A

Leave a Reply

Share to MS Teams

Login to your account

Welcome Back, We Missed You!