from 12/19/2022 to 12/25/2022
4 Office 365 Message Center Items were changed and 7 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 |
|---|---|---|---|---|
| MC408689 | (Updated) View Video Recordings and Attendance Reports Inside LMS | 01/23/2023 08:00:00 | 2023-02-28T08:00:00Z | N/A |
| MC408994 | (Updated) Private drafts for SharePoint pages and news | 12/16/2022 08:00:00 | 2023-01-30T08:00:00Z | N/A |
MC How Affect changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC482179 | (Updated) New Service Plans for Microsoft 365 and Microsoft Viva SKUs | As part of our preparation for the release, you may see the following new service plans: If you are licensed Viva Suite customer, then you may see 'Viva Engage Communities & Communications' and 'Viva Engage Knowledge' service plans (for Viva Engage and Answers in Microsoft Viva premium experiences, respectively) If you are licensed Viva Topics customer, then you may see 'Viva Engage Knowledge' service plan (for Answers in Microsoft Viva premium experience) For all M365 / O365 customers, you may see 'Viva Engage Core' service plan (for Viva Engage basic / free experiences) |
As part of this step, you may notice the following service plans visible and available: Viva Engage Core: If you are an existing customer of any of the following SKUs, you may see this service plan available. This service plan is intended to support the currently available basic features* in Viva Engage currently available (Storylines, Communities etc.). Microsoft 365 Business Basic Microsoft 365 Basic Standard Microsoft Business Premium Office 365 (E1) Microsoft 365 E3 / Office 365 E3 Microsoft 365 E5 / Office 365 E5 Microsoft 365 F3 / Office 365 F3 Microsoft 365 F1 Viva Engage Communities and Communication: If you are an existing Microsoft Viva Suite customer, you may see this service plan available. This service plan will be used to provision the new Viva Engage features (Leadership Corner, Campaigns, AMA etc.) in early 2023. Viva Engage Knowledge: If you are an existing Microsoft Viva Suite or Viva Topics customer, you may see this service plan available. This service plan will be used to provision the new Answers in Microsoft Viva experiences in early 2023. * For more details, please refer to this blog post [What this means for you:] At this time there is no impact to your organization and no action is required from your end. Please note that these new service plans are in placeholding capacity as of now; they will be used to provision the new features and experiences in Viva Engage and Answers in Microsoft Viva in 2023. You may see these service plans ‘enabled’ for the users in your organization, however that will not enable any new features / experiences for them. We will be sharing additional information with you to control the feature roll out to your users when we make the features available. When we begin rolling out the availability of new experiences in early 2023, we will publish another Message Center post in January 2023 that will provide you with the list of action items so that you can control the feature enablement for your organizations as per your needs and requirements. Please find below some key questions and our response to them. Q: Why do I see the new service plans in SKU? A: Service plans are the mechanism to provide experiences to our customers. We have begun with preparatory steps to get ready to provide our new experiences in early 2023 and assigning placeholder service plans to the SKUs is the first step. Placeholding means the service plans are empty as of now and will be used to provision the new experiences early 2023 onwards. Q: What features do these service plans enable? A: These service plans will provision the new experiences starting in 2023, they don’t provision any experience today. When the new experiences are made available, feature enablement will still be controlled for you for your organization. Following are the sets of features to be enabled and supported by these service plans: Viva Engage Core – basic features* that are currently available in Viva Engage Viva Engage Communities and Communication – new upcoming experiences** in Viva Engage Viva Engage Knowledge – new upcoming experiences with Answers in Microsoft Viva * For more details, please refer to this blog post ** For more details, please refer to this blog post Q: Why are these service plans already assigned to all the users? A: The service plans have been enabled to the users to provide a smoother and easily controlled feature roll out process. You will still be able to control the roll out of the features to the users as per your requirements. We will shortly reach out with another post with details on feature roll out plan and how you can control the roll out for your organization. Q: Does this enable any app (such as Yammer) that I had previously disabled? A: These service plans have no impact on any app that you may have disabled for your users. Q: What if I disable Viva Engage Core service plan? A: This will not have any impact as of now. Q: What if I disable Viva Engage Communities & Communication service plan for my users? A: This will not have any impact as of now. However, if you disable them now, you may have to perform some extra steps in early 2023 to control the roll out of new features in Viva Engage (such a Leadership Corner, AMA, Campaigns etc.), when they are made available. Hence, we would suggest to not disable this service plan. Q: What if I disable Viva Engage Knowledge service plan for my users? A: This will not have any impact as of now. However, you may have to perform some extra steps in early 2023 to control the roll out of new features in Answers in Microsoft Viva, when they are made available. Hence, we would suggest to not disable this service plan. Q: Does this affect any other product in the SKU? A: This does not impact any other product or features that are currently in the SKU that you have purchased. Q: My organization was already using Viva Engage features (like Storylines, Communities) before Viva Engage Core; Why do we have this new service plan now and what will change? A: Currently, existing Yammer service plan provisions these features on Yammer as well as Viva Engage app in Teams for experience continuity. However, in the future, we plan to migrate to Viva Engage Core service plan to provision new features in Viva Engage app, while Yammer service plan will continue to provide access to Yammer. Q: How will I control the roll out of the new features to the users? A: These service plans do not provision any new features. As we make the new experiences and features available, we will share more detailed steps for you to prepare and control the roll out. No action is required from you at the moment. |
N/A |
MC Messages changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC408689 | (Updated) View Video Recordings and Attendance Reports Inside LMS | Updated October 18, 2022: We have updated the rollout timeline below. Thank you for your patience. The Microsoft Teams Meeting LTI app has now enabled users the access to meeting video recordings and attendance reports directly inside their LMS. The feature will be available to use in all of the LMS' that are incorporating the Teams Meeting LTI app. This message is associated with Microsoft 365 Roadmap ID 96402 [When this will happen:] We will begin rolling out in early December (previously mid-September) and expect to complete rollout by mid-December (previously late November). |
Updated December 22, 2022: We have updated the rollout timeline below. Thank you for your patience. The Microsoft Teams Meeting LTI app has now enabled users the access to meeting video recordings and attendance reports directly inside their LMS. The feature will be available to use in all of the LMS' that are incorporating the Teams Meeting LTI app. This message is associated with Microsoft 365 Roadmap ID 96402 [When this will happen:] We will begin rolling out in early January 2023 (previously early December 2022) and expect to complete rollout by late January 2023 (previously mid-December 2022). |
N/A |
| MC408994 | (Updated) Private drafts for SharePoint pages and news | Updated October 6, 2022: We have updated the rollout timeline below. Thank you for your patience. We’re adding the ability to create private drafts for pages and news posts. A private draft is visible only to the page author, the people the author chooses to share it with, and site admins. It's great for creating and editing content that’s not ready for others to see except the people you want to collaborate with. This message is associated with Microsoft 365 Roadmap ID 85629 |
Updated December 22, 2022: We have updated the rollout timeline below. Thank you for your patience. We’re adding the ability to create private drafts for pages and news posts. A private draft is visible only to the page author, the people the author chooses to share it with, and site admins. It's great for creating and editing content that’s not ready for others to see except the people you want to collaborate with. This message is associated with Microsoft 365 Roadmap ID 85629 |
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: 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. |
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 |
| 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: 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. |
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 |
| MC482179 | (Updated) New Service Plans for Microsoft 365 and Microsoft Viva SKUs | As previously announced, we will be releasing our new experiences for Viva Engage and Answers in Microsoft Viva in early 2023. [When this will happen:] Beginning in mid-December and expect to complete by late December. |
Updated December 19, 2022: We have updated the content below to provide more information. Thank you for your feedback. As previously announced, we will be releasing our new experiences for Viva Engage and Answers in Microsoft Viva in early 2023. We are now assigning the new service plans to the corresponding SKUs to get ready for the release. [When this will happen:] Beginning in mid-December 2022 and expect to complete by late December 2022. |
N/A |
MC MessageTagNames changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC482179 | (Updated) New Service Plans for Microsoft 365 and Microsoft Viva SKUs | Admin impact | Updated message, Admin impact | N/A |
MC prepare changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC482179 | (Updated) New Service Plans for Microsoft 365 and Microsoft Viva SKUs | At this time, there is no impact to your organization, and no action is required from your end. These service plans neither enable any new experiences at this time nor restore any deprecated or disabled experiences. We will begin rolling out the availability of new experiences in early 2023 in a phased manner. We will reach out with another post closer to the release timelines - to communicate roll-out timelines, what to expect, and any action items for you. |
https://techcommunity.microsoft.com/t5/microsoft-viva-blog/microsoft-viva-engage-is-now-generally-available/ba-p/3595300 | N/A |
MC Title changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC482179 | (Updated) New Service Plans for Microsoft 365 and Microsoft Viva SKUs | New Service Plans for Microsoft 365 and Microsoft Viva SKUs | (Updated) New Service Plans for Microsoft 365 and Microsoft Viva SKUs | N/A |
CW52 New Office 365 Message Center items
| MC ID | MC Title | MC Category | MC Workload | MC Major Change | MC Action required by |
|---|---|---|---|---|---|
| MC488588 | Virtual Appointment as a new Teams Meeting Template | Stay Informed | Microsoft Teams | False | N/A |
| MC488586 | Announcing Retirement of Remote PowerShell (RPS) protocol in Exchange Online PowerShell | Plan For Change | Exchange Online | True | N/A |
| MC489165 | Manage result layouts for SharePoint results in Microsoft Search | Stay Informed | SharePoint Online, Microsoft 365 apps for the web | False | N/A |
| MC489163 | Microsoft Viva: Meeting Prep Inline Suggestions Coming to Outlook with Viva Insights | Stay Informed | Microsoft Viva | False | N/A |
| MC489162 | Sharing a copy of praise in Viva Insights app in Teams and Teams Messaging Extension | Stay Informed | Microsoft Viva | False | N/A |
| MC489125 | Important information about Microsoft Power Automate emails | Plan For Change | Microsoft Power Automate | False | N/A |
| MC489705 | Take action: OOB update to address issues with new VMs managed by SCVMM and using Software Defined Networking (SDN) | Prevent Or Fix Issue | Windows | False | N/A |
