from 06/16/2025 to 06/22/2025
11 Office 365 Message Center Items were changed and
19 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 Action Required By changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1094051 | (Updated) Support Update for SharePoint Framework Field Customizers in Lists and Document Libraries | 06/30/2026 09:00:00 | N/A | N/A |
MC End Time changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1075905 | (Updated) Microsoft 365 admin center: Onboard SharePoint agents as a Pay-as-you-go scenario | 07/28/2025 09:00:00 | 2025-08-25T09:00:00Z | N/A |
| MC1090689 | (Updated) Microsoft Teams: Enhanced peripheral data in Pro Management portal reports for BYOD spaces | 09/29/2025 09:00:00 | 2025-10-06T09:00:00Z | N/A |
| MC714520 | (Updated) Apps for the web: Grid view for tasks in Microsoft To Do web version and To Do inside Microsoft Outlook | 07/07/2025 09:00:00 | 2025-09-08T09:00:00Z | N/A |
| MC926899 | (Updated) Microsoft Purview | Data Lifecycle Management: Separate Copilot retention policies from Teams chats | 07/28/2025 09:00:00 | 2025-11-10T08:00:00Z | N/A |
| MC927963 | (Updated) New Microsoft Outlook for Windows: People Hub improvements | 09/08/2025 09:00:00 | 2025-10-20T09:00:00Z | N/A |
MC How Affect changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1061107 | (Updated) Microsoft 365 Copilot in Viva Glint: Viva Glint admin can enable Copilot for the Company admin user role | Before this rollout, the Copilot feature control is disabled for the Viva Glint admin user role in the Viva Glint survey Program Setup. Viva Glint admin users need to add themselves to another user role to enable Copilot. This restriction is a Copilot enablement blocker for customers. This rollout will not impact the tenant administrator's workflow. This is an enhancement to the Viva Glint service administrator's workflow. This change will be on by default. How to enable Copilot in Viva Glint in the Program Summary > Reporting tab |
Before this rollout, because all feature controls are disabled for the Viva Glint admin user role in the Viva Glint survey Program Setup. Viva Glint admin users need to add themselves to another user role to enable Copilot. This restriction is a Copilot enablement blocker for customers. This rollout will not impact the tenant administrator's workflow. This is an enhancement to the Viva Glint service administrator's workflow. This change will be on by default. How to enable Copilot in Viva Glint in General Settings |
N/A |
| MC1072404 | (Updated) New Microsoft Outlook and Outlook for the web: Admin setting for inheriting a S/MIME signature on reply | After this rollout, you can use the new setting called NoSignOnReply to define Signing on Reply and Reply all. Using this setting, admins can define inheritance of S/MIME signature for its users. The NoSignOnReply setting is available in Microsoft Entra ID (formerly Active Directory). NoSignOnReply = $False. This is the default state. When value = False, Reply and Reply all will inherit the S/MIME signature. Users will need to go to S/MIME settings and remove S/MIME signature. NoSignOnReply = $True. Reply and Reply all will not inherit S/MIME signature. In cases where incoming email has S/MIME encryption and a signature attached, this setting will only inherit encryption and not the signature. This setting can be useful in scenarios where your organization has not configured S/MIME signatures for its users. The default behavior is consistent with classic Outlook. As an alternative, admins can configure this setting with the cmdlet Set-SmimeConfig (Set-SmimeConfig (ExchangePowerShell) | Microsoft Learn. Admins can configure this setting in the Microsoft Exchange Management Shell or the Microsoft Exchange Online Shell. |
After this rollout, you can use the new setting called NoSignOnReply to define Signing on Reply and Reply all. Using this setting, admins can define inheritance of S/MIME signature for its users. The NoSignOnReply setting is available in Microsoft Entra ID (formerly Active Directory). NoSignOnReply = $False. When value = False, Reply and Reply all will inherit the S/MIME signature. Users will need to go to S/MIME settings and remove S/MIME signature. NoSignOnReply = $TrueThis is the default state. Reply and Reply all will not inherit S/MIME signature. In cases where incoming email has S/MIME encryption and a signature attached, this setting will only inherit encryption and not the signature. This setting can be useful in scenarios where your organization has not configured S/MIME signatures for its users. As an alternative, admins can configure this setting with the cmdlet Set-SmimeConfig (Set-SmimeConfig (ExchangePowerShell) | Microsoft Learn. Admins can configure this setting in the Microsoft Exchange Management Shell or the Microsoft Exchange Online Shell. |
N/A |
| MC1075905 | (Updated) Microsoft 365 admin center: Onboard SharePoint agents as a Pay-as-you-go scenario | Admins can set up Pay-as-you-go for SharePoint Agents in Copilot under "Billing & usage". They can connect Billing Policies to SharePoint Agents, allowing end users within those policies to use SharePoint Agents. | Admins can set up Pay-as-you-go for SharePoint Agents in Copilot under "Billing & usage". They can connect Billing Policies to SharePoint Agents, allowing end users within those policies to use SharePoint Agents. Users in organizations with 50 or more Microsoft 365 Copilot licenses have had promotional access to SharePoint Agents since January 2025. With this promotional access ending June 30, admins will need to enable Pay-as-you-go billing to allow users in their organization without a Microsoft 365 Copilot license to continue using SharePoint Agents. Departmental billing enables organizations using Pay-as-you-go billing to allocate costs across business units and manage spend more precisely. |
N/A |
| MC1093235 | (Updated) Text Prediction turned off by default in Outlook | Text Prediction will be turned off by default for all users, including those who currently have it enabled. After the change, users will no longer see predictive text suggestions while composing email messages unless they manually re-enable the feature in Outlook settings. | Text Prediction will be turned off by default for all users of New Outlook for Windows and Outlook on the web, including those who currently have it enabled. On Outlook for iOS and Android, only new users will have the default set to off. After the change, users will no longer see predictive text suggestions while composing email messages unless they manually re-enable the feature in Outlook settings. | N/A |
| MC1094051 | (Updated) Support Update for SharePoint Framework Field Customizers in Lists and Document Libraries | If your organization uses SharePoint Lists or Document Libraries with SPFx Field Customizers, please note the following impacts after the retirement date: Field Customizers will no longer render custom code. Column data will display using the default rendering based on column type. Other SPFx extensions, such as Command Set Customizers and Application Customizers, will continue to function as expected. We recommend transitioning to Column Formatting for visual customizations. For scenarios requiring third-party code execution, continue using Command Set Customizers or Application Customizers. |
There is no impact to your organization as of now. In future depending on updated timelines, SharePoint Lists or Document Libraries with SPFx Field Customizers may get affected: Field Customizers will no longer render custom code. Column data will display using the default rendering based on column type. Other SPFx extensions, such as Command Set Customizers and Application Customizers, will continue to function as expected. We recommend transitioning to Column Formatting for visual customizations. For scenarios requiring third-party code execution, continue using Command Set Customizers or Application Customizers. |
N/A |
| MC1097272 | Microsoft 365 Upcoming Secure by Default Settings Changes | The following settings will be updated: SettingsImpact Block legacy browser authentication to SharePoint and OneDrive using RPS (Relying Party Suite)Legacy authentication protocols like RPS (Relying Party Suite) are vulnerable to brute-force and phishing attacks due to non-modern authentication. Blocking this prevents applications that are using outdated methods from accessing SharePoint and OneDrive via browser. To use PowerShell to block legacy browser authentication, see Set-SPOTenant. Block FPRPC (FrontPage Remote Procedure Call) protocol for Office file opensFrontPage Remote Procedure Call (FPRPC) is a legacy protocol used for remote web page authoring. While no longer widely used, Legacy protocols such as FPRPC can be more susceptible to compromise and blocking FPRPC helps reduce exposure to vulnerabilities. With this change, FPRPC will be blocked for opening files, preventing the use of this non-modern protocol in Microsoft 365 clients. To learn how to block the FPRPC protocol, see turn on web content filtering. Require admin consent for third-party apps accessing files and sitesUsers allowing third-party apps to access file and site content can lead to overexposure of an organization's content. Requiring admins to consent to this access can help reduce overexposure. With this change, Microsoft managed App Consent Policies will be enabled, and users will be unable to consent to third party applications accessing their files and sites by default. Instead, they can request administrators to consent on their behalf. To configure admin consent, follow instructions here: configuring the Admin Consent workflow. Customers who have already blocked user consent or applied custom user consent settings will not be affected by this change. Admins can also configure granular app access policies, such as limiting user access to the application for specific users or groups. Learn more here. These changes are on by default and apply to all Microsoft 365 tenants. No additional licensing is required. |
The following settings will be updated: SettingsImpact Block legacy browser authentication to SharePoint and OneDrive using RPS (Relying Party Suite)Legacy authentication protocols like RPS (Relying Party Suite) are vulnerable to brute-force and phishing attacks due to non-modern authentication. Blocking this prevents applications that are using outdated methods from accessing SharePoint and OneDrive via browser. To use PowerShell to block legacy browser authentication, see Set-SPOTenant. Block FPRPC (FrontPage Remote Procedure Call) protocol for Office file opensFrontPage Remote Procedure Call (FPRPC) is a legacy protocol used for remote web page authoring. While no longer widely used, Legacy protocols such as FPRPC can be more susceptible to compromise and blocking FPRPC helps reduce exposure to vulnerabilities. With this change, FPRPC will be blocked for opening files, preventing the use of this non-modern protocol in Microsoft 365 clients. To learn how to block the FPRPC protocol, see turn on web content filtering. Require admin consent for third-party apps accessing files and sitesUsers allowing third-party apps to access file and site content can lead to overexposure of an organization's content. Requiring admins to consent to this access can help reduce overexposure. With this change, Microsoft managed App Consent Policies will be enabled, and users will be unable to consent to third party applications accessing their files and sites by default. Instead, they can request administrators to consent on their behalf. To configure admin consent, follow instructions here: Configuring the Admin Consent workflow. Customers who have already blocked user consent, turned on our previously recommended consent settings, or applied custom user consent settings will not be affected by this change. Admins can also configure granular app access policies, such as limiting user access to the application for specific users or groups. Learn more here. These changes are on by default and apply to all Microsoft 365 tenants. No additional licensing is required. |
N/A |
MC Messages changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1047250 | (Updated) Microsoft Teams: Sensitivity labels on collaborative meeting notes and Microsoft Loop components | Updated May 28, 2025: We have updated the timeline below. Thank you for your patience. Coming soon: New security features for Microsoft Loop in Microsoft Teams for organizations that have enabled sensitivity labels (also known as Microsoft Information Protection or MIP). Before this rollout, Microsoft Loop supports users or admins adding file-level sensitivity labels on all .loop files (including Loop components, Loop pages, and Microsoft Copilot Pages) in the Loop app (on the web and for iOS/Android) and new Microsoft Outlook for Windows and Outlook for the web, classic Outlook for Windows, Outlook for Mac, Outlook on Android and iOS. Copilot Pages is included in Microsoft 365 licenses. After this rollout, we will support file-level sensitivity labels in Loop components and collaborative meeting notes in Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android. [When this will happen:] General Availability (Worldwide): We will begin rolling out in early April 2025 and expect to complete by early June 2025 (previously late May). |
Updated June 17, 2025: We have updated the timeline below. Thank you for your patience. Coming soon: New security features for Microsoft Loop in Microsoft Teams for organizations that have enabled sensitivity labels (also known as Microsoft Information Protection or MIP). Before this rollout, Microsoft Loop supports users or admins adding file-level sensitivity labels on all .loop files (including Loop components, Loop pages, and Microsoft Copilot Pages) in the Loop app (on the web and for iOS/Android) and new Microsoft Outlook for Windows and Outlook for the web, classic Outlook for Windows, Outlook for Mac, Outlook on Android and iOS. Copilot Pages is included in Microsoft 365 licenses. After this rollout, we will support file-level sensitivity labels in Loop components and collaborative meeting notes in Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android. [When this will happen:] General Availability (Worldwide): We will begin rolling out in early April 2025 and expect to complete by early July 2025 (previously early June). |
N/A |
| MC1061107 | (Updated) Microsoft 365 Copilot in Viva Glint: Viva Glint admin can enable Copilot for the Company admin user role | Updated May 6, 2025: We have updated the timeline below. Thank you for your patience. Coming soon: The Microsoft Viva Glint admin can enable the Microsoft Copilot feature control for the Company admin user role in the Viva Glint survey Program Setup. Admins can enable the control in the Reporting tab of the Program Summary setup. A license for Viva Glint, Microsoft Viva Suite, or Microsoft Viva Workforce Analytics and Employee Feedback is required to access this feature. This message applies to Glint for the web. This message is associated with Microsoft 365 Roadmap ID 489219. [When this will happen:] General Availability (Worldwide): We will begin rolling out late July 2025 (previously mid-May) and expect to complete by late August 2025 (previously mid-May). |
Updated June 17, 2025: We have updated the feature description below. Thank you for your patience. Coming soon: The Microsoft Viva Glint admin can enable the Microsoft Copilot feature control for the Company admin user role in the Viva Glint General Settings. A license for Viva Glint, Microsoft Viva Suite, or Microsoft Viva Workforce Analytics and Employee Feedback is required to access this feature. This message applies to Glint for the web. This message is associated with Microsoft 365 Roadmap ID 489219. [When this will happen:] General Availability (Worldwide): We will begin rolling out late July 2025 (previously mid-May) and expect to complete by late August 2025 (previously mid-May). |
N/A |
| MC1072404 | (Updated) New Microsoft Outlook and Outlook for the web: Admin setting for inheriting a S/MIME signature on reply | New Microsoft Outlook for Windows desktop and Microsoft Outlook for the web will soon support an admin setting to define the application of S/MIME signatures in "reply to" scenarios. This setting enables admins to define if an S/MIME signature will be inherited by default in Reply and Reply all scenarios.
[When this will happen:] |
Updated June 17, 2025: We have updated the timeline below. Thank you for your patience. New Microsoft Outlook for Windows desktop will soon support an admin setting to define the application of S/MIME signatures in "reply to" scenarios. This setting enables admins to define if an S/MIME signature will be inherited by default in Reply and Reply all scenarios. [When this will happen:] For new Outlook for Windows desktop: General Availability (Worldwide): we will begin rolling out early July 2025 (previously mid-June) and expect to complete by mid-July 2025 (previously late June). General Availability (GCC): We will begin rolling out mid-July 2025 (previously late June) and expect to complete by early August 2025 (previously early July). For Outlook for Web: After further review we have decided not to proceed with this change at this time for Outlook for Web. We apologize for any inconvenience. |
N/A |
| MC1075905 | (Updated) Microsoft 365 admin center: Onboard SharePoint agents as a Pay-as-you-go scenario | Introducing pay-as-you-go departmental billing for SharePoint Agents in Copilot Control System. [When this will happen:] General Availability (Worldwide): Starting early June 2025, M365 Administrators can set up Pay-as-you-go for SharePoint Agents via Copilot Control System. Administrators can add billing polices and connect to SharePoint Agents to establish departmental chargeback and billing. |
Updated June 17, 2025: We have updated the content. Thank you for your patience. Introducing pay-as-you-go departmental billing for SharePoint Agents in Copilot Control System. [When this will happen:] General Availability (Worldwide): Starting early June 2025, M365 Administrators can set up Pay-as-you-go for SharePoint Agents via Copilot Control System. Administrators can add billing polices and connect to SharePoint Agents to establish departmental chargeback and billing. |
N/A |
| MC1090689 | (Updated) Microsoft Teams: Enhanced peripheral data in Pro Management portal reports for BYOD spaces | We're adding new peripheral health reporting capabilities to the Pro Management portal, enabling admins to proactively monitor device issues in bring your own device (BYOD) rooms and desks. These reports help identify when peripherals are faulty, missing, moved, or undetectable by a PC-allowing admins to take action before users report problems. Reports for rooms require a Teams Shared Devices license. Desk reporting is currently in public preview. This change is associated with Microsoft 365 Roadmap ID: 493319 [When this will happen:] General Availability (Worldwide and GCC): Rollout will begin in early July 2025 and is expected to complete by late July 2025. |
Updated June 16, 2025: We have updated the timeline below. Thank you for your patience. We're adding new peripheral health reporting capabilities to the Pro Management portal, enabling admins to proactively monitor device issues in bring your own device (BYOD) rooms and desks. These reports help identify when peripherals are faulty, missing, moved, or undetectable by a PC-allowing admins to take action before users report problems. Reports for rooms require a Teams Shared Devices license. Desk reporting is currently in public preview. This change is associated with Microsoft 365 Roadmap ID: 493319 [When this will happen:] General Availability (Worldwide and GCC): Rollout will begin in early September 2025 (previously early July) and is expected to complete by late September 2025 (previously late July). |
N/A |
| MC1093235 | (Updated) Text Prediction turned off by default in Outlook | We're updating the default setting for the Text Prediction feature in Outlook to improve user control and reduce unintended suggestions. This change affects New Outlook for Windows, Outlook on the web, and Outlook for iOS and Android. [When this will happen:] This change will begin rolling out on July 1, 2025. |
Updated June 17, 2025: We have updated the content. Thank you for your patience. We're updating the default setting for the Text Prediction feature in Outlook to improve user control and reduce unintended suggestions. This change affects New Outlook for Windows, Outlook on the web, and Outlook for iOS and Android. [When this will happen:] This change will begin rolling out on July 1, 2025. |
N/A |
| MC1094051 | (Updated) Support Update for SharePoint Framework Field Customizers in Lists and Document Libraries | We will be retiring the SharePoint Framework (SPFx) Field Customizers feature from SharePoint Lists and Document Libraries on June 30, 2026. Moving forward, we recommend using Column Formatting, where we will continue to invest in new capabilities and improvements. [When this will happen:] This change will take effect on June 30, 2026. |
Updated June 20, 2025: We will not be proceeding with this change at this time. Thank you for your patience. We will be retiring the SharePoint Framework (SPFx) Field Customizers feature from SharePoint Lists and Document Libraries. In many cases, we recommend alternatives like using Column Formatters and disabling SPFx Field customizers. This would help with better performance with modern experience that is continuously updated. [When this will happen:] We are currently assessing the timelines and will update this post as plans progress. You can be assured that it will be communicated well in advance, with ample time to manage transition effectively. |
N/A |
| MC714520 | (Updated) Apps for the web: Grid view for tasks in Microsoft To Do web version and To Do inside Microsoft Outlook | Updated April 23, 2025: We have updated the timeline below. Thank you for your patience. In Microsoft 365 apps for the web, users can see their tasks in a grid view and can update details inline in To Do on web and To Do app inside Microsoft Outlook. This message is associated with Microsoft 365 Roadmap ID 381749 [When this will happen:] General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rolling out late April 2024 (previously early April) and expect to complete by mid-May 2025 (previously mid-April). |
Updated June 17, 2025: We have updated the timeline below. Thank you for your patience. In Microsoft 365 apps for the web, users can see their tasks in a grid view and can update details inline in To Do on web and To Do app inside Microsoft Outlook. This message is associated with Microsoft 365 Roadmap ID 381749 [When this will happen:] General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rolling out late April 2024 (previously early April) and expect to complete by early July 2025 (previously late May). |
N/A |
| MC926899 | (Updated) Microsoft Purview | Data Lifecycle Management: Separate Copilot retention policies from Teams chats | Updated May 21, 2025: We have updated the content. Thank you for your patience. Admins can follow the in-product message while editing the policy and make the required changes using PowerShell cmdlets to configure a Teams chat policy or Copilot policy. If there are existing policies covering other locations together with Teams chat and Copilot interactions in a single policy, admins can create equivalent new policies including the other locations from UI or using PowerShell cmdlets. Before this rollout, Microsoft Teams chat and Microsoft 365 Copilot interactions are available together to be included or excluded in the Microsoft Purview Data Lifecycle Management policy in the Purview compliance center. After this rollout, admins can have separate policies for Copilot interactions. Also, admins can separate Teams chat from Copilot interactions to create new retention policies for Copilot messages only. A Microsoft 365 Copilot license is required to use this feature. This message is associated with Microsoft 365 Roadmap ID 407897. [When this will happen:] Public Preview: We will begin rolling out early May 2025 (previously early March) and expect to complete by mid-May 2025 (previously mid-March). General Availability (Worldwide): We will begin rolling out early June 2025 (previously late March) and expect to complete by mid-June 2025 (previously late March). |
Updated June 16, 2025: We have updated the timeline below. Thank you for your patience. Admins can follow the in-product message while editing the policy and make the required changes using PowerShell cmdlets to configure a Teams chat policy or Copilot policy. If there are existing policies covering other locations together with Teams chat and Copilot interactions in a single policy, admins can create equivalent new policies including the other locations from UI or using PowerShell cmdlets. Before this rollout, Microsoft Teams chat and Microsoft 365 Copilot interactions are available together to be included or excluded in the Microsoft Purview Data Lifecycle Management policy in the Purview compliance center. After this rollout, admins can have separate policies for Copilot interactions. Also, admins can separate Teams chat from Copilot interactions to create new retention policies for Copilot messages only. A Microsoft 365 Copilot license is required to use this feature. This message is associated with Microsoft 365 Roadmap ID 407897. [When this will happen:] Public Preview: We will begin rolling out early May 2025 (previously early March) and expect to complete by mid-May 2025 (previously mid-March). General Availability (Worldwide): We will begin rolling out mid-September 2025 (previously early June) and expect to complete by late September 2025 (previously late June). |
N/A |
| MC927963 | (Updated) New Microsoft Outlook for Windows: People Hub improvements | Updated April 17, 2025: We have updated the rollout timeline below. Thank you for your patience. You are receiving this message because our reporting indicates you may be using new Microsoft Outlook for Windows in your organization. Coming soon for new Outlook for Windows: an updated People Hub with a modern contact management experience that will retrieve and display high-quality, complete, coherent, and up-to-date information about the people that matter the most to you. This message is associated with Microsoft 365 Roadmap ID 413114. [When this will happen:] Targeted release: We will begin rolling out early June 2025 (previously mid-April) and expect to complete by late June 2025 (previously mid-May). General Availability (Worldwide): We will begin rolling out early July 2025 (previously late May) and expect to complete by late July 2025 (previously mid-June). |
Updated June 17, 2025: We have updated the timeline below. Thank you for your patience. You are receiving this message because our reporting indicates you may be using new Microsoft Outlook for Windows in your organization. Coming soon for new Outlook for Windows: an updated People Hub with a modern contact management experience that will retrieve and display high-quality, complete, coherent, and up-to-date information about the people that matter the most to you. This message is associated with Microsoft 365 Roadmap ID 413114. [When this will happen:] Targeted release: We will begin rolling out mid-June 2025 (previously early June) and expect to complete by mid-July 2025 (previously late June). General Availability (Worldwide): We will begin rolling out mid-August 2025 (previously early July) and expect to complete by early September 2025 (previously late July). |
N/A |
MC MessageTagNames changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1072404 | (Updated) New Microsoft Outlook and Outlook for the web: Admin setting for inheriting a S/MIME signature on reply | Feature update, User impact, Admin impact | Updated message, Feature update, User impact, Admin impact | N/A |
| MC1075905 | (Updated) Microsoft 365 admin center: Onboard SharePoint agents as a Pay-as-you-go scenario | New feature, User impact, Admin impact | Updated message, New feature, User impact, Admin impact | N/A |
| MC1090689 | (Updated) Microsoft Teams: Enhanced peripheral data in Pro Management portal reports for BYOD spaces | New feature, Admin impact | Updated message, New feature, Admin impact | N/A |
| MC1093235 | (Updated) Text Prediction turned off by default in Outlook | Feature update, User impact | Updated message, Feature update, User impact | N/A |
| MC1094051 | (Updated) Support Update for SharePoint Framework Field Customizers in Lists and Document Libraries | User impact, Admin impact, Retirement | Updated message, User impact, Admin impact, Retirement | N/A |
MC prepare changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1094051 | (Updated) Support Update for SharePoint Framework Field Customizers in Lists and Document Libraries | Review your current use of Field Customizers and begin planning your transition. Note: There will be no option to extend the use of Field Customizers beyond June 30, 2026. Additional information: Support update for SharePoint framework field customizers in lists and document libraries https://learn.microsoft.com/sharepoint/dev/declarative-customization/column-formatting https://learn.microsoft.com/sharepoint/dev/spfx/extensions/get-started/build-a-hello-world-extension https://learn.microsoft.com/sharepoint/dev/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api https://learn.microsoft.com/sharepoint/dev/spfx/extensions/get-started/building-simple-field-customizer https://support.microsoft.com/office/0eccc64e-4512-47df-9da0-d855be22fb0a |
Review your current use of Field Customizers and begin planning your transition. Additional information: Support update for SharePoint framework field customizers in lists and document libraries https://learn.microsoft.com/sharepoint/dev/declarative-customization/column-formatting https://learn.microsoft.com/sharepoint/dev/spfx/extensions/get-started/build-a-hello-world-extension https://learn.microsoft.com/sharepoint/dev/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api https://learn.microsoft.com/sharepoint/dev/spfx/extensions/get-started/building-simple-field-customizer https://support.microsoft.com/office/0eccc64e-4512-47df-9da0-d855be22fb0a |
N/A |
| MC1097272 | Microsoft 365 Upcoming Secure by Default Settings Changes | We recommend the following actions: Assess current configurations: As applicable, identify current configurations for RPS or FPRPC protocols and review third-party apps that access SharePoint and OneDrive content. Notify stakeholders: Inform IT admins, app owners, and security teams about the upcoming changes. Update documentation: Ensure internal guidance reflects the new defaults and admin consent process. Configure Admin Consent workflow: If third party apps access is applicable for your organization, learn how to set up the workflow: Configuring admin consent workflow. Additional considerations Does the change alter how existing customer data is processed, stored, or accessed? Yes - it blocks access to content via legacy authentication protocols. https://aka.ms/AppConsentLearn https://aka.ms/entra-app-access https://go.microsoft.com/fwlink/p/?linkid=2324508 https://go.microsoft.com/fwlink/p/?linkid=2324509 https://go.microsoft.com/fwlink/p/?linkid=2324703 https://learn.microsoft.com/en-us/defender-endpoint/web-content-filtering https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies https://learn.microsoft.com/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps |
We recommend the following actions: Assess current configurations: As applicable, identify current configurations for RPS or FPRPC protocols. Notify stakeholders: Inform IT admins, app owners, and security teams about the upcoming changes. Update documentation: Ensure internal guidance reflects the new defaults and admin consent process. Configure Admin Consent workflow: If third party apps access is applicable for your organization, learn how to set up the workflow: Configuring admin consent workflow. Additional considerations Does the change alter how existing customer data is processed, stored, or accessed? Yes - it blocks access to content via legacy authentication protocols. https://aka.ms/entra-app-access https://go.microsoft.com/fwlink/p/?linkid=2324508 https://go.microsoft.com/fwlink/p/?linkid=2324509 https://go.microsoft.com/fwlink/p/?linkid=2324703 https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/configure-admin-consent-workflow https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/manage-app-consent-policies https://learn.microsoft.com/en-us/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps#-legacybrowserauthprotocolsenabled https://learn.microsoft.com/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps |
N/A |
MC Title changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1072404 | (Updated) New Microsoft Outlook and Outlook for the web: Admin setting for inheriting a S/MIME signature on reply | New Microsoft Outlook and Outlook for the web: Admin setting for inheriting a S/MIME signature on reply | (Updated) New Microsoft Outlook and Outlook for the web: Admin setting for inheriting a S/MIME signature on reply | N/A |
| MC1075905 | (Updated) Microsoft 365 admin center: Onboard SharePoint agents as a Pay-as-you-go scenario | Microsoft 365 admin center: Onboard SharePoint agents as a Pay-as-you-go scenario | (Updated) Microsoft 365 admin center: Onboard SharePoint agents as a Pay-as-you-go scenario | N/A |
| MC1090689 | (Updated) Microsoft Teams: Enhanced peripheral data in Pro Management portal reports for BYOD spaces | Microsoft Teams: Enhanced peripheral data in Pro Management portal reports for BYOD spaces | (Updated) Microsoft Teams: Enhanced peripheral data in Pro Management portal reports for BYOD spaces | N/A |
| MC1093235 | (Updated) Text Prediction turned off by default in Outlook | Text Prediction turned off by default in Outlook | (Updated) Text Prediction turned off by default in Outlook | N/A |
| MC1094051 | (Updated) Support Update for SharePoint Framework Field Customizers in Lists and Document Libraries | Support Update for SharePoint Framework Field Customizers in Lists and Document Libraries | (Updated) Support Update for SharePoint Framework Field Customizers in Lists and Document Libraries | N/A |
CW25 New Office 365 Message Center items
| MC ID | MC Title | MC Category | MC Workload | MC Major Change | MC Action required by |
|---|---|---|---|---|---|
| MC1096222 | Microsoft Viva Engage: Updating icons for certain activity types with a standard icon | Stay Informed | Microsoft Viva | False | N/A |
| MC1096218 | Microsoft 365 Copilot: Extending Copilot Chat to Microsoft 365 apps | Plan For Change | Microsoft 365 suite | False | N/A |
| MC1096179 | Microsoft 365 Copilot for Sales - Get AI-powered insights with enhanced pre-meeting card | Stay Informed | Dynamics 365 Apps | False | N/A |
| MC1097272 | Microsoft 365 Upcoming Secure by Default Settings Changes | Plan For Change | Microsoft Entra | True | N/A |
| MC1097225 | Microsoft Entra ID: Upcoming changes to support passkey profiles in the authentication methods policy (preview) | Plan For Change | Microsoft Entra | True | N/A |
| MC1097223 | Plan for Change: Intune moving to support iOS/iPadOS 17 and higher later this year | Plan For Change | Microsoft Intune | False | N/A |
| MC1097219 | Plan for Change: Intune moving to support macOS 14 and higher later this year | Plan For Change | Microsoft Intune | False | N/A |
| MC1097162 | Updates available for Microsoft 365 Apps for Current Channel | Stay Informed | Microsoft 365 apps | False | N/A |
| MC1096885 | Mail Bombing Detection technology in Microsoft Defender for Office 365 | Plan For Change | Exchange Online, Microsoft Defender XDR | False | N/A |
| MC1098174 | Microsoft Teams: In-app survey feedback policies will be managed by default with Microsoft 365 Cloud Policy | Plan For Change | Microsoft Teams | False | N/A |
| MC1098161 | Microsoft 365 Copilot Chat: Now Easily Accessible from the Teams Chat List | Plan For Change | Microsoft Teams | False | N/A |
| MC1098946 | Limit on number of users or groups that can be added to workspace roles in Fabric and Power BI | Plan For Change | Power BI | True | N/A |
| MC1098943 | Microsoft Defender for Office 365: AI-powered submissions response for improved result explainability | Stay Informed | Microsoft Defender XDR | False | N/A |
| MC1098937 | Microsoft Teams: Presenters can promote attendees to the green room | Stay Informed | Microsoft Teams | False | N/A |
| MC1098935 | Microsoft SharePoint: Header and Footer enhancements | Stay Informed | SharePoint Online | False | N/A |
| MC1098932 | Microsoft Outlook for Mac desktop: Retiring the admin preference to switch to legacy Outlook | Plan For Change | Microsoft 365 apps | True | N/A |
| MC1099693 | Microsoft Teams: App ratings will be visible in context | Stay Informed | Microsoft Teams | False | N/A |
| MC1099692 | Microsoft Copilot: Access SharePoint agents in the Microsoft 365 Copilot app | Plan For Change | SharePoint Online, Microsoft Copilot (Microsoft 365) | False | N/A |
| MC1099690 | Changes to case creation process in Purview portal when confirming alerts from Defender XDR portal | Plan For Change | Microsoft Purview | False | N/A |
