from 12/26/2022 to 01/01/2023
7 Office 365 Message Center Items were changed and 2 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 |
|---|---|---|---|---|
| MC295027 | (Updated) Rich text and images in Planner task notes | 01/20/2023 09:00:00 | 2023-03-03T09:00:00Z | N/A |
| MC362283 | (Updated) Updates to the Zero-hour auto purge (ZAP) alerts | 01/06/2023 08:00:00 | 2023-02-17T08:00:00Z | N/A |
| MC403644 | (Updated) OneDrive: Sharing Experience - Share Menu Dropdown | 12/20/2022 08:00:00 | 2023-03-02T08:00:00Z | N/A |
| MC447338 | (Updated) New home experience for Viva Connections desktop | 04/29/2023 10:00:00 | 2023-04-30T10:00:00Z | N/A |
| MC466201 | (Updated) Azure Active Directory (AAD) and Microsoft (MSA) accounts can be linked to earn Microsoft Rewards points | 01/13/2023 09:00:00 | 2023-02-28T09:00:00Z | 12/11/2022 |
MC Messages changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC295027 | (Updated) Rich text and images in Planner task notes | Updated November 3, 2022: We have updated the content below to reflect support for images will be coming in the future and we will communicate via Message center when available. Thank you for your patience. We are adding support for rich text (bold, italics, underline, etc.) in the Planner task notes field. Support for images is coming in the future. NOTE: We will update this post once we have Microsoft Graph documentation for the new rich text task notes field available. This message is associated with Microsoft 365 Roadmap ID 85688. [When this will happen:] We expect to begin rolling out the new rich text task notes field in early December (previously late October) and we expect to complete the rollout by mid-December (previously mid-November). |
Updated December 27, 2022: We have updated the rollout timeline below. Thank you for your patience. We are adding support for rich text (bold, italics, underline, etc.) in the Planner task notes field. Support for images is coming in the future. NOTE: We will update this post once we have Microsoft Graph documentation for the new rich text task notes field available. This message is associated with Microsoft 365 Roadmap ID 85688. [When this will happen:] We expect to begin rolling out the new rich text task notes field in mid-January (previously early December) and we expect to complete the rollout by late January (previously mid-December). |
N/A |
| MC362283 | (Updated) Updates to the Zero-hour auto purge (ZAP) alerts | Updated October 31, 2022: We have updated the rollout timeline below. Thank you for your patience. We will be updating the current zero-hour auto purge (ZAP) alerts and introduce a new ZAP alert that will notify you if a message has not been removed by ZAP. Updates to the ZAP alerts will include: Scoping the success ZAP alerts for only ZAP related scenarios. You will no longer be alerted as part of the ZAP alert for Dynamic Delivery scenarios. A new failure ZAP alert is being introduced. You will receive an alert when a message was not successfully removed from the mailbox. Manual action will be required to remediate the message. The alert will be correlated and linked to both Automated Investigation and Response (AIR) and Incidents. The alert will be on by default and can be configured in alert policies. This message is associated with Microsoft 365 Roadmap ID 93206. [When this will happen:] We expect these updates to roll out in early November (previously mid-October) and expect to be complete by early December (previously mid-November). |
Updated December 27, 2022: We have updated the rollout timeline below. Thank you for your patience. We will be updating the current zero-hour auto purge (ZAP) alerts and introduce a new ZAP alert that will notify you if a message has not been removed by ZAP. Updates to the ZAP alerts will include: Scoping the success ZAP alerts for only ZAP related scenarios. You will no longer be alerted as part of the ZAP alert for Dynamic Delivery scenarios. A new failure ZAP alert is being introduced. You will receive an alert when a message was not successfully removed from the mailbox. Manual action will be required to remediate the message. The alert will be correlated and linked to both Automated Investigation and Response (AIR) and Incidents. The alert will be on by default and can be configured in alert policies. This message is associated with Microsoft 365 Roadmap ID 93206. [When this will happen:] We expect these updates to roll out in early November (previously mid-October) and expect to be complete by mid-January (previously early December). |
N/A |
| MC403644 | (Updated) OneDrive: Sharing Experience - Share Menu Dropdown | Updated September 27, 2022: We have updated the rollout timeline below. Thank you for your patience. We’re updating the Share button in Microsoft OneDrive to provide easy access to additional sharing options. When you select Share in OneDrive for Business on Web, you'll see a contextual menu with all choices available to you for sharing files or folders with your teammates. This message is associated with Microsoft 365 Roadmap ID 83727 |
Updated December 27, 2022: We have updated the rollout timeline below. Thank you for your patience. We’re updating the Share button in Microsoft OneDrive to provide easy access to additional sharing options. When you select Share in OneDrive for Business on Web, you'll see a contextual menu with all choices available to you for sharing files or folders with your teammates. This message is associated with Microsoft 365 Roadmap ID 83727 |
N/A |
| MC441534 | Basic Authentication – Monthly Usage Report - September 2022 | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022. We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022. We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
N/A |
| MC441534 | Basic Authentication – Monthly Usage Report - September 2022 | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022. We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of {MonthName}, we detected the following usage: Exchange ActiveSync: {ActiveSync} POP: {POP} IMAP: {IMAP} Outlook Windows: {Outlook} Outlook for Mac/Exchange Web Services: {Webservices} Exchange Remote PowerShell: {PowerShell} Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022. We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
N/A |
| MC441534 | Basic Authentication – Monthly Usage Report - September 2022 | We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022. We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 89 POP: 0 IMAP: 0 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
We're making some changes to improve the security of your tenant. We announced in 2019 that we would be retiring Basic Authentication for legacy protocols, and in September 2021, we confirmed that we would begin to disable Basic Authentication for in-use protocols beginning October 2022. We previously communicated this change via Message Center: MC191153 (Sept. ‘19), MC204828 (Feb. ‘20), MC208814 (April ‘20), MC237741 (Feb. ‘21) and MC286990 (Sep. ’21). You can always read the latest information about our plans to turn off Basic Authentication here. Based on our telemetry, there may be some users in your tenant currently using Basic Authentication and we expect these users to be affected when these changes take place. In the month of September, we detected the following usage: Exchange ActiveSync: 1 POP: 0 IMAP: 1 Outlook Windows: 0 Outlook for Mac/Exchange Web Services: 0 Exchange Remote PowerShell: 0 Please note these numbers only reflect the count of unique users who have successfully authenticated to these services in the specified month, they do not reflect successful access to mailboxes or data (for example, a user may authenticate using IMAP, but may be denied access to the mailbox due to configuration or policy). If you want to block users or apps being able to authenticate at all using legacy protocols, we recommend using Authentication Polices. To investigate this usage further, we recommend you use Azure AD Sign-in Reports which can provide detailed user, IP and client details for these authentications. |
N/A |
| MC447338 | (Updated) New home experience for Viva Connections desktop | Updated October 27, 2022: We have updated the content below with additional information. Thank you for your patience. A new desktop experience is being released for Viva Connections that’s easier and faster to set up and optimizes content to deliver a modern employee experience. The new Viva Connections desktop design serves as a new home experience option that centers essential job tasks, personalized content, easy access to other Viva experiences, and better aligns with the mobile experience. It uses existing assets from your organization’s home site and Viva Connection’s Dashboard, Feed, and Resources. If your organization already has Viva Connections set up, you’ll have the option to choose to keep the existing desktop experiences that features the home site or to use the new home experience. Learn more about the new Viva Connections home experience. If you haven’t set up Viva Connections yet, the default experience includes starter cards on the Dashboard but otherwise doesn’t impact the current mobile experience. |
Updated December 27, 2022: The New home experiences for Viva Connections desktop will start rolling out to production tenants through Q1 of next calendar year. Customers with existing home sites can choose to keep their existing desktop experience using our new PowerShell command that is already available to all customers since mid-November. More information about the PowerShell command is captured in this doc: Customize and edit the Viva Connections home experience. A new desktop experience is being released for Viva Connections that’s easier and faster to set up and optimizes content to deliver a modern employee experience. The new Viva Connections desktop design serves as a new home experience option that centers essential job tasks, personalized content, easy access to other Viva experiences, and better aligns with the mobile experience. It uses existing assets from your organization’s home site and Viva Connection’s Dashboard, Feed, and Resources. If your organization already has Viva Connections set up, you’ll have the option to choose to keep the existing desktop experiences that features the home site or to use the new home experience. Learn more about the new Viva Connections home experience. If you haven’t set up Viva Connections yet, the default experience includes starter cards on the Dashboard but otherwise doesn’t impact the current mobile experience. |
N/A |
| MC466201 | (Updated) Azure Active Directory (AAD) and Microsoft (MSA) accounts can be linked to earn Microsoft Rewards points | Microsoft now offers the ability to link an Azure Active Directory (AAD) work account and a personal Microsoft account (MSA). With this change, AAD users with a linked MSA account can now earn Microsoft Rewards points for Microsoft Bing searches done in their browser or Windows search box while signed in with their AAD account. This expanded Rewards eligibility was made based on user feedback. The ability to link accounts will be enabled by default so account linking is available to an organization’s employees, but still requires employees to opt-in. The choice to link accounts is in an employee’s hands, and they need to take action to connect their AAD and MSA accounts. Account linking will not change any group policies. Personal and work searches will not be linked, and there is no change to how searches are stored. Microsoft’s principles for data security and privacy in the enterprise still hold, which ensures that confidential organizational information including search history will not be collected on AAD accounts even after accounts are linked. Microsoft will not collect any new data for targeted advertising as a result of this change. [When will this happen] Admin control (via PowerShell) available now. Account linking will be enabled no earlier than December 11, 2022 and will honor enabled/disabled settings. |
Updated December 27, 2022: We are providing additional guidance for your information: After December 10, admins can turn off account linking using PowerShell script (outlined below). After January 17, the toggle to enable or disable the feature will be available in Microsoft 365 Admin portal Settings page. Until then, please use the PowerShell script. Microsoft now offers the ability to link an Azure Active Directory (AAD) work account and a personal Microsoft account (MSA). With this change, AAD users with a linked MSA account can now earn Microsoft Rewards points for Microsoft Bing searches done in their browser or Windows search box while signed in with their AAD account. This expanded Rewards eligibility was made based on user feedback. The ability to link accounts will be enabled by default so account linking is available to an organization’s employees, but still requires employees to opt-in. The choice to link accounts is in an employee’s hands, and they need to take action to connect their AAD and MSA accounts. Account linking will not change any group policies. Personal and work searches will not be linked, and there is no change to how searches are stored. Microsoft’s principles for data security and privacy in the enterprise still hold, which ensures that confidential organizational information including search history will not be collected on AAD accounts even after accounts are linked. Microsoft will not collect any new data for targeted advertising as a result of this change. [When will this happen] Admin control (via PowerShell) available now. After January 17, the toggle to enable or disable the feature will be available in Microsoft 365 Admin portal Settings page. Until then, please use the PowerShell script. |
12/11/2022 |
| MC484925 | (Updated) Microsoft Outlook: Extend Sensitivity Label to Meetings (preview) | Sensitivity labeling will soon be available for meetings in Outlook for preview.
This message is associated with Microsoft 365 Roadmap ID 98924 GA: We will begin rollout out in early February 2023 and expect to complete rollout by late February 2023. |
Updated December 27, 2022: We have updated the rollout timeline below. Thank you for your patience. Sensitivity labeling will soon be available for meetings in Outlook for preview. This message is associated with Microsoft 365 Roadmap ID 98924 GA: We will begin rollout out in mid-February 2023 (previously early February 2023) and expect to complete rollout by late February 2023. |
N/A |
MC MessageTagNames changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC466201 | (Updated) Azure Active Directory (AAD) and Microsoft (MSA) accounts can be linked to earn Microsoft Rewards points | New feature, User impact, Admin impact | Updated message, New feature, User impact, Admin impact | 12/11/2022 |
| MC484925 | (Updated) Microsoft Outlook: Extend Sensitivity Label to Meetings (preview) | New feature, User impact, Admin impact | Updated message, New feature, User impact, Admin impact | N/A |
MC Title changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC466201 | (Updated) Azure Active Directory (AAD) and Microsoft (MSA) accounts can be linked to earn Microsoft Rewards points | Azure Active Directory (AAD) and Microsoft (MSA) accounts can be linked to earn Microsoft Rewards points | (Updated) Azure Active Directory (AAD) and Microsoft (MSA) accounts can be linked to earn Microsoft Rewards points | 12/11/2022 |
| MC484925 | (Updated) Microsoft Outlook: Extend Sensitivity Label to Meetings (preview) | Microsoft Outlook: Extend Sensitivity Label to Meetings (preview) | (Updated) Microsoft Outlook: Extend Sensitivity Label to Meetings (preview) | N/A |
CW01 New Office 365 Message Center items
| MC ID | MC Title | MC Category | MC Workload | MC Major Change | MC Action required by |
|---|---|---|---|---|---|
| MC492903 | Microsoft Teams: Presenter Window Improvements in Screen Sharing | Stay Informed | Microsoft Teams | False | N/A |
| MC492896 | Updated opt-in setting for Microsoft Defender for Identity | Plan For Change | Microsoft 365 Defender | False | N/A |
