2022 CW 43 Microsoft 365 Message Center changes

from 10/17/2022 to 10/23/2022

12 Office 365 Message Center Items were changed and 26 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
MC333941 (Updated) New Fluent Emoji style coming to Teams emojis and reactions 10/31/2022 08:00:00 2022-12-16T08:00:00Z N/A
MC360766 (Updated) Loop components in Outlook Mail Preview 01/30/2023 08:00:00 2022-10-28T09:00:00Z N/A
MC381943 (Updated) General availability of Microsoft Defender for Endpoint alerts in Insider Risk Management 10/31/2022 08:00:00 2022-11-30T08:00:00Z N/A
MC408689 (Updated) View Video Recordings and Attendance Reports Inside LMS 12/23/2022 08:00:00 2023-01-23T08:00:00Z N/A
MC415187 (Updated) Get Adobe PDF experience in Microsoft Teams 11/30/2022 09:00:00 2022-12-30T09:00:00Z N/A
MC434658 Meeting Category Trends and Details in the Viva Insights App in Teams and Meeting Category Insights Card in Digest Email 11/30/2022 09:00:00 2023-02-03T09:00:00Z N/A
MC442111 (updated) Microsoft Purview Information Protection: User-defined permissions support domain name restrictions 12/30/2022 09:00:00 2023-01-30T09:00:00Z N/A
MC447316 Take action: Out-of-band update to address issues after installing the October 2022 Windows security updates 10/17/2023 23:26:23 2023-10-18T23:42:56Z N/A
MC447327 (Updated) App configuration policy managed app settings can be targeted to device type for Intune managed devices 01/30/2023 09:00:00 2023-02-28T09:00:00Z N/A

MC IsMajorChange changes

MC ID MC Title Old Value New Value MC Action required by
MC447990 DCOM authentication hardening: What you need to know False True 03/23/2023

MC Messages changes

MC ID MC Title Old Value New Value MC Action required by
MC333941 (Updated) New Fluent Emoji style coming to Teams emojis and reactions Updated September 1, 2022: We have updated the rollout timeline below. Thank you for your patience.

This update will have Teams joining Microsoft 365 and Windows in updating all emojis and reactions to the new Microsoft Fluent emoji style, bringing users a more vibrant and expressive emoji experience.

This message is associated with Microsoft 365 Roadmap ID 88277

[When this will happen:]

We will begin rolling this out in late February and expect to complete rollout by late September (previously late August).

Updated October 17, 2022: We have updated the rollout timeline below. Thank you for your patience.

This update will have Teams joining Microsoft 365 and Windows in updating all emojis and reactions to the new Microsoft Fluent emoji style, bringing users a more vibrant and expressive emoji experience.

This message is associated with Microsoft 365 Roadmap ID 88277

[When this will happen:]

We will begin rolling this out in late February and expect to complete rollout by mid-November (previously late September).

N/A
MC360766 (Updated) Loop components in Outlook Mail Preview Updated September 21, 2022: We have updated the rollout timeline below. Thank you for your patience.

Loop components are live, interactive, collaborative objects that you can embed in team chats and now also on emails. When you send a Loop component, everyone in the email can edit it inline—and see changes instantly. That means you can collaborate right inside an email message. To give it a try, compose a new email or reply to an existing one and insert a Loop component via the toolbar or copy and paste components between email and Teams chats.

This message is associated with Microsoft 365 Roadmap ID 93234

[When this will happen:]

We will begin rolling out to Outlook on the web Targeted release in early August (previously late May) and expect it to be completed by late August (previously late June).

We will begin rolling out to Outlook Windows desktop Current Channel (Preview) in early August (previously late May) and expect it to be completed by late September (previously late August).

General availability of Loop components for Outlook on the Web and Windows desktop is expected to begin in November (previously September) and complete by late December (previously late September)

Updated October 21, 2022: We have updated the rollout timeline below. Thank you for your patience.

Loop components are live, interactive, collaborative objects that you can embed in team chats and now also on emails. When you send a Loop component, everyone in the email can edit it inline—and see changes instantly. That means you can collaborate right inside an email message. To give it a try, compose a new email or reply to an existing one and insert a Loop component via the toolbar or copy and paste components between email and Teams chats.

This message is associated with Microsoft 365 Roadmap ID 93234

[When this will happen:]

We will begin rolling out to Outlook on the web Targeted release in early August (previously late May) and expect it to be completed by late August (previously late June).

We will begin rolling out to Outlook Windows desktop Current Channel (Preview) in early August (previously late May) and expect it to be completed by late September (previously late August).

General availability of Loop components for Outlook on the Web and Windows desktop is expected to begin in December (previously November) and complete by late January (previously late December)

N/A
MC381943 (Updated) General availability of Microsoft Defender for Endpoint alerts in Insider Risk Management Updated August 9, 2022: We have updated the rollout timeline below. Thank you for your patience.

Currently available in public preview, Microsoft Defender for Endpoint alerts will soon be generally available for use within the Insider Risk Management solution in the Microsoft Purview compliance portal.

This message is associated with Microsoft 365 Roadmap ID 83965

[When this will happen:]

Rollout will begin in early July (previously late May) and is expected to be complete by late September (previously early August).
Updated October 19, 2022: We have updated the rollout timeline below. Thank you for your patience.

Currently available in public preview, Microsoft Defender for Endpoint alerts will soon be generally available for use within the Insider Risk Management solution in the Microsoft Purview compliance portal.

This message is associated with Microsoft 365 Roadmap ID 83965

[When this will happen:]

Rollout will begin in early July (previously late May) and is expected to be complete by late October (previously late September).
N/A
MC408689 (Updated) View Video Recordings and Attendance Reports Inside LMS Updated September 29, 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 mid-September and expect to complete rollout by late November (previously late September).
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).
N/A
MC415187 (Updated) Get Adobe PDF experience in Microsoft Teams Updated September 14, 2022: We have updated the rollout timeline below. Thank you for your patience.

Now you can set Adobe Acrobat as the default app to view and edit PDF files in the Microsoft Teams. Once done, all PDF files from the chat, channel, and files app will open directly in the Acrobat app within Teams. Your end-users don't need an Adobe Acrobat subscription or an Adobe ID to view, search, comment and annotate PDF files. However, to Create, Organize, Combine, or Export a PDF, the tenant users will need an Adobe Acrobat subscription.

This message is associated with Microsoft 365 Roadmap ID 95128

[When this will happen:]

Public Preview: This is now available in public preview.

Standard Release: We will begin rolling out early October 2022 (previously early September 2022) and expect to complete by late October 2022 (previously late September 2022).

Updated October 17, 2022: We have updated the rollout timeline below. Thank you for your patience.

Now you can set Adobe Acrobat as the default app to view and edit PDF files in the Microsoft Teams. Once done, all PDF files from the chat, channel, and files app will open directly in the Acrobat app within Teams. Your end-users don't need an Adobe Acrobat subscription or an Adobe ID to view, search, comment and annotate PDF files. However, to Create, Organize, Combine, or Export a PDF, the tenant users will need an Adobe Acrobat subscription.

This message is associated with Microsoft 365 Roadmap ID 95128

[When this will happen:]

Public Preview: This is now available in public preview.

Standard Release: We will begin rolling out early November 2022 (previously early October 2022) and expect to complete by late November 2022 (previously late October 2022).

N/A
MC434658 Meeting Category Trends and Details in the Viva Insights App in Teams and Meeting Category Insights Card in Digest Email Categories in Outlook and Teams allow users to easily tag, label, and group calendar events. In the Viva Insights app in Teams, using meeting category insights in the Effective meetings tab, users can see a percentage breakdown of how they are distributing their time across their categories.

An upcoming update to this feature will allow users to:

See how their meeting time distribution has changed over the last 3 months, the last 4 weeks, and the next 4 weeks under meeting trends

View the list of meetings in each category, with details including meeting name, total time spent, duration of each instance, and cadence, under meeting details

We are also releasing a new card in the Digest email from Microsoft Viva that summarizes their meeting category insights. In this card, users will be able to see up to 3 categories in which they have spent the most time over the last 4 weeks. This card will show the percentage of time each category contributed to the user’s total meeting time in the last 4 weeks, as well as how that percentage has changed from the previous 4 weeks. The explore more button provides an easy way to navigate to meeting category insights in the Viva Insights app, where users can explore percentage breakdown, trends, and details.

These features will be available for users who have a Viva Insights subscription.

This message is associated with Microsoft 365 Roadmap ID 98164

[When this will happen:]

We will begin rolling out in mid-October and expect to complete rollout by late October.

Updated October 21, 2022: We have updated the rollout timeline below. Thank you for your patience.

Categories in Outlook and Teams allow users to easily tag, label, and group calendar events. In the Viva Insights app in Teams, using meeting category insights in the Effective meetings tab, users can see a percentage breakdown of how they are distributing their time across their categories.

An upcoming update to this feature will allow users to:

See how their meeting time distribution has changed over the last 3 months, the last 4 weeks, and the next 4 weeks under meeting trends

View the list of meetings in each category, with details including meeting name, total time spent, duration of each instance, and cadence, under meeting details

We are also releasing a new card in the Digest email from Microsoft Viva that summarizes their meeting category insights. In this card, users will be able to see up to 3 categories in which they have spent the most time over the last 4 weeks. This card will show the percentage of time each category contributed to the user’s total meeting time in the last 4 weeks, as well as how that percentage has changed from the previous 4 weeks. The explore more button provides an easy way to navigate to meeting category insights in the Viva Insights app, where users can explore percentage breakdown, trends, and details.

These features will be available for users who have a Viva Insights subscription.

This message is associated with Microsoft 365 Roadmap ID 98164

[When this will happen:]

We will begin rolling out in early November (previously mid-October) and expect to complete rollout by early January (previously late October).

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
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
MC442111 (updated) Microsoft Purview Information Protection: User-defined permissions support domain name restrictions Coming soon to public preview and general availability, we're updating the options for custom permissions, also referred to as user-defined permissions, to support domain name restrictions.

This message is associated with Microsoft 365 Roadmap ID 98131.

[When this will happen:]

Rollout to public preview will begin in mid-October and is expected to be complete by late-October.

Rollout to general availability will begin in early November and is expected to be complete by end of November.
Updated October 21, 2022: We have updated the rollout timeline below. Thank you for your patience.

Coming soon to public preview and general availability, we're updating the options for custom permissions, also referred to as user-defined permissions, to support domain name restrictions.

This message is associated with Microsoft 365 Roadmap ID 98131.

[When this will happen:]

Rollout to public preview will begin in mid-November (previously mid-October) and is expected to be complete by late November (previously late October).

Rollout to general availability will begin in early December (previously early November) and is expected to be complete by end of December (previously end of November).

N/A
MC445202 (Updated) Microsoft Teams: Browser Screen Pop for Incoming PSTN Calls An automatic browser screen will now launch for users when an incoming PSTN call is accepted in Microsoft Teams. The browser screen will display relevant information to the user (CRM data, case data, etc.).

This message is associated with Microsoft 365 Roadmap ID 98054

[When this will happen:]

WW and GCC: We will begin rolling out in early November and expect rollout to be completed by late November.

GCCH and DoD: We will begin rolling out in December.
Updated October 17, 2022: We have updated the content below to show as intended. Thank you for your patience.

An automatic browser screen will now launch for users when an incoming PSTN call is accepted in Microsoft Teams. The browser screen will display relevant information to the user (CRM data, case data, etc.).

This message is associated with Microsoft 365 Roadmap ID 98054

[When this will happen:]

WW and GCC: We will begin rolling out in early November and expect rollout to be completed by late November.

GCCH and DoD: We will begin rolling out in December.
N/A
MC447316 Take action: Out-of-band update to address issues after installing the October 2022 Windows security updates Microsoft is releasing Out-of-band updates today, October 17, 2022, for some versions of Windows. This update addresses a known issue that might cause SSL/TLS handshakes to fail.

All versions are available only on the Microsoft Update Catalog and will not be offered through Windows Update. For instructions, see the release notes for your OS listed below. Note: Organizations can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager.

Cumulative updates:

Windows 11, version 21H2: KB5020387

Windows Server 2022: KB5020436

Windows 10, version 20H2; Windows 10, version 21H1; Windows 10, version 22H1; Windows 10 Enterprise LTSC 2021: KB5020435

Windows 10 Enterprise LTSC 2019; Windows Server 2019: KB5020438

Windows 10 2016 LTSB; Windows Server 2016: We are working on a resolution and estimate a solution will be available in the coming days.

Windows 10 2015 LTSB; We are working on a resolution and estimate a solution will be available in the coming days.

Note: You do not need to apply any previous update before installing these cumulative updates.

Standalone Updates:

Windows 8.1; Windows Server 2012 R2: KB5020447

Windows Server 2012: KB5020449

Windows 7 SP1; Windows Server 2008 R2 SP1: KB5020448

Note: If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of October 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are normally using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released October 11, 2022 to receive the quality updates for October 2022.

Updated October 18, 2022

Microsoft is releasing Out-of-band updates today, October 17, 2022, for some versions of Windows. This update addresses a known issue that might cause SSL/TLS handshakes to fail.

All versions are available only on the Microsoft Update Catalog and will not be offered through Windows Update. For instructions, see the release notes for your OS listed below. Note: Organizations can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager.

Cumulative updates:

Windows 11, version 21H2: KB5020387

Windows Server 2022: KB5020436

Windows 10, version 20H2; Windows 10, version 21H1; Windows 10, version 22H1; Windows 10 Enterprise LTSC 2021: KB5020435

Windows 10 Enterprise LTSC 2019; Windows Server 2019: KB5020438

Windows 10 2016 LTSB; Windows Server 2016: KB5020439

Windows 10 2015 LTSB; KB5020440

Note: You do not need to apply any previous update before installing these cumulative updates.

Standalone Updates:

Windows 8.1; Windows Server 2012 R2: KB5020447

Windows Server 2012: KB5020449

Windows 7 SP1; Windows Server 2008 R2 SP1: KB5020448

Note: If you are using security only updates for these versions of Windows Server, you only need to install these standalone updates for the month of October 2022. Security only updates are not cumulative, and you will also need to install all previous Security only updates to be fully up to date. Monthly rollup updates are cumulative and include security and all quality updates. If you are normally using Monthly rollup updates, you will need to install both the standalone updates listed above to resolve this issue, and install the Monthly rollups released October 11, 2022 to receive the quality updates for October 2022.

N/A
MC447327 (Updated) App configuration policy managed app settings can be targeted to device type for Intune managed devices Expected mid-to-late November 2022, admins will be able to target app configuration policies (ACP) managed app settings to devices based on their device type. Currently, ACP policies for managed apps are targeted to all device types, this change will allow the flexibility to target different policies to Intune-managed or unmanaged devices. Updated October 18, 2022: We have updated the timing of this change below. Thank you for your patience.

In an upcoming release, admins will be able to target app configuration policies (ACP) managed app settings to devices based on their device type. Currently, ACP policies for managed apps are targeted to all device types, this change will allow the flexibility to target different policies to Intune-managed or unmanaged devices.
N/A
MC447990 DCOM authentication hardening: What you need to know A new blog article tells the comprehensive story of the ongoing Distributed Component Object Model (DCOM) authentication hardening process: DCOM authentication hardening: What you need to know. Previously documented in KB5004442, this article informs the timeline of the phased rollout, ultimately leading to default enablement for the security of servers and client devices. Keep your organization protected with the latest Windows updates, enable or test DCOM authentication hardening, and monitor for compatibility with our troubleshooting guidance for several common scenarios for Windows devices.

When will this happen:

As explained in KB5004442, the phased rollout of DCOM authentication hardening changes follows the timeline originally established June 2021:

September 2021: The September 2021 update fixed several compatibility issues and introduced event logs for additional monitoring.

June 2022: All updates beginning with June 2022 programmatically enable the requirements of Packet Level Integrity (RPC_C_AUTHN_LEVEL_PKT_INTEGRITY), unless an admin manually disables them.

November 2022: The November 8 update will automatically raise authentication level for all non-anonymous activation requests from DCOM clients to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY if it’s below Packet Integrity.

March 2023: Finally, DCOM authentication hardening will be enabled by default to prevent any malicious actors from accessing your server and networked devices.

A new blog article tells the comprehensive story of the ongoing Distributed Component Object Model (DCOM) authentication hardening process: DCOM authentication hardening: What you need to know. This article explains the timeline of the phased rollout documented in KB5004442, and the key dates which ultimately lead to default enablement for the security of servers and client devices. Keep your organization protected with the latest Windows updates, enable or test DCOM authentication hardening, and monitor for compatibility with our troubleshooting guidance for several common scenarios for Windows devices.

When will this happen:

As explained in KB5004442, the phased rollout of DCOM authentication hardening changes follows the timeline originally established since June 2021:

September 2021: The September 2021 update fixed several compatibility issues and introduced event logs for additional monitoring.

June 2022: All updates beginning with June 2022 programmatically enable the requirements of Packet Level Integrity (RPC_C_AUTHN_LEVEL_PKT_INTEGRITY), unless an admin manually disables them.

November 2022: The November 8 update will automatically raise authentication level for all non-anonymous activation requests from DCOM clients to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY if it’s below Packet Integrity.

March 2023: Finally, DCOM authentication hardening will be enabled by default to help prevent malicious actors from accessing your server and networked devices.

03/23/2023

MC MessageTagNames changes

MC ID MC Title Old Value New Value MC Action required by
MC434658 Meeting Category Trends and Details in the Viva Insights App in Teams and Meeting Category Insights Card in Digest Email New feature, User impact Updated message, New feature, User impact N/A
MC442111 (updated) Microsoft Purview Information Protection: User-defined permissions support domain name restrictions New feature, Admin impact Updated message, New feature, Admin impact N/A
MC445202 (Updated) Microsoft Teams: Browser Screen Pop for Incoming PSTN Calls New feature, User impact, Admin impact Updated message, New feature, User impact, Admin impact N/A
MC447327 (Updated) App configuration policy managed app settings can be targeted to device type for Intune managed devices Feature update, Admin impact Updated message, Feature update, Admin impact N/A

MC prepare changes

MC ID MC Title Old Value New Value MC Action required by
MC360766 (Updated) Loop components in Outlook Mail Preview Loop components are enabled by default to organizations. Loop components do not currently support eDiscovery workflows. If your organization leverages eDiscovery workflows, evaluate the risks. To disable this feature for your organization, follow the instruction outlined in this article: Manage Loop components in SharePoint

To learn more about loop components and how your organization could better leverage them. Consider reading: First things to know about Loop components

https://docs.microsoft.com/sharepoint/manage-loop-components

https://support.microsoft.com/office/first-things-to-know-about-loop-components-ee2a584b-5785-4dd6-8a2d-956131a29c81

https://www.microsoft.com/microsoft-365/roadmap?rtc=1%26filters=&searchterms=93234
Loop components are enabled by default to organizations. Loop components do not currently support eDiscovery workflows. If your organization leverages eDiscovery workflows, evaluate the risks. To disable this feature for your organization, follow the instructions outlined in this article: Manage Loop components in SharePoint

Note: There has been an update in October 2022 for Outlook admin experience controls.

To learn more about loop components and how your organization could better leverage them. Consider reading: First things to know about Loop components

https://docs.microsoft.com/sharepoint/manage-loop-components

https://support.microsoft.com/office/first-things-to-know-about-loop-components-ee2a584b-5785-4dd6-8a2d-956131a29c81

https://www.microsoft.com/microsoft-365/roadmap?rtc=1%26filters=&searchterms=93234
N/A
MC447316 Take action: Out-of-band update to address issues after installing the October 2022 Windows security updates https://learn.microsoft.com/windows/release-health/status-windows-server-2022#2924msgdesc

https://support.microsoft.com/help/5020387

https://support.microsoft.com/help/5020435

https://support.microsoft.com/help/5020436

https://support.microsoft.com/help/5020438

https://support.microsoft.com/help/5020447

https://support.microsoft.com/help/5020448

https://support.microsoft.com/help/5020449
https://learn.microsoft.com/windows/release-health/resolved-issues-windows-server-2022#2924msgdesc

https://support.microsoft.com/help/5020387

https://support.microsoft.com/help/5020435

https://support.microsoft.com/help/5020436

https://support.microsoft.com/help/5020438

https://support.microsoft.com/help/5020439

https://support.microsoft.com/help/5020440

https://support.microsoft.com/help/5020447

https://support.microsoft.com/help/5020448

https://support.microsoft.com/help/5020449
N/A

MC Start Time changes

MC ID MC Title Old Value New Value MC Action required by
MC447316 Take action: Out-of-band update to address issues after installing the October 2022 Windows security updates 10/17/2022 23:26:23 2022-10-18T23:42:56Z N/A
MC447990 DCOM authentication hardening: What you need to know 10/19/2022 23:31:25 2022-10-20T21:38:51Z 03/23/2023

MC Title changes

MC ID MC Title Old Value New Value MC Action required by
MC442111 (updated) Microsoft Purview Information Protection: User-defined permissions support domain name restrictions Microsoft Purview Information Protection: User-defined permissions support domain name restrictions (updated) Microsoft Purview Information Protection: User-defined permissions support domain name restrictions N/A
MC445202 (Updated) Microsoft Teams: Browser Screen Pop for Incoming PSTN Calls Microsoft Teams: Browser Screen Pop for Incoming PSTN Calls (Updated) Microsoft Teams: Browser Screen Pop for Incoming PSTN Calls N/A
MC447327 (Updated) App configuration policy managed app settings can be targeted to device type for Intune managed devices Plan for Change: App configuration policy managed app settings can be targeted to device type for Intune managed devices (Updated) App configuration policy managed app settings can be targeted to device type for Intune managed devices N/A
MC447990 DCOM authentication hardening: What you need to know DCOM authentication hardening: What you need to know DCOM authentication hardening: What you need to know 03/23/2023

CW43 New Office 365 Message Center items

MC ID MC Title MC Category MC Workload MC Major Change MC Action required by
MC447341 Microsoft Graph to Support HTTP/2 as of September 2023 Stay Informed Identity Service, Microsoft 365 suite False N/A
MC447340 Microsoft Defender for Endpoint on Mac is Retiring Support of MacOS Catalina Plan For Change Microsoft Defender for Cloud Apps True 12/15/2022
MC447339 Quarantine Admin Role Required for Exchange Admins for Quarantine Operations Stay Informed Exchange Online, Microsoft 365 Defender False 01/06/2023
MC447338 New home experience for Viva Connections desktop Stay Informed Microsoft Viva False N/A
MC447334 Planner Due Date Digest Email design update Stay Informed Planner False N/A
MC447330 Microsoft Purview | eDiscovery (Premium): New role for review set tag management Stay Informed Microsoft 365 suite False N/A
MC447328 What’s new in the Windows 365 Enterprise update for October 2022 Stay Informed Windows 365 False N/A
MC447327 (Updated) App configuration policy managed app settings can be targeted to device type for Intune managed devices Plan For Change Microsoft Intune False N/A
MC447320 Important information about your Microsoft Power Apps service Plan For Change Power Apps False N/A
MC447316 Take action: Out-of-band update to address issues after installing the October 2022 Windows security updates Prevent Or Fix Issue Windows False N/A
MC447310 Important Azure Information Protection (AIP) Portal updates Stay Informed Microsoft 365 suite False N/A
MC447307 Announcement of automatic deletion of inactive Microsoft Dataverse for Teams environments Stay Informed Dynamics 365 Apps False N/A
MC447541 Making the everyday easier with new experiences available in Windows 11 Stay Informed Windows False N/A
MC447540 Windows 10, version 22H2 is now available Prevent Or Fix Issue Windows False N/A
MC447689 Microsoft Defender for Cloud Apps Alert/sms retirement update Plan For Change Microsoft 365 Defender True N/A
MC447686 Microsoft Teams zero-install link unfurling Stay Informed Microsoft Teams False N/A
MC447685 New Teams Powered Encoder events Stay Informed Microsoft Teams False N/A
MC447684 Retirement of Legacy Microsoft Defender Online Alerts Plan For Change Microsoft 365 Defender True N/A
MC447681 Microsoft Hardware Support New Self-Serve Feature Stay Informed Microsoft 365 Apps False N/A
MC448008 Reminder: Announcement of automatic deletion of inactive Microsoft Dataverse for Teams environments Plan For Change Microsoft Teams True N/A
MC447991 Announcing Windows Update for Business reports Stay Informed Windows False N/A
MC447990 DCOM authentication hardening: What you need to know Prevent Or Fix Issue Windows True 03/23/2023
MC448371 Updates to network endpoints for Microsoft Intune Plan For Change Microsoft Intune False N/A
MC448368 Announcing de-duplication of contacts in Outlook Web Stay Informed Office for the web, Microsoft 365 Apps False N/A
MC448361 Microsoft Viva: MyAnalytics dashboard redirects to Viva Insights web app Plan For Change Exchange Online True N/A
MC448356 New praise compose experience in Teams and praise trends in Viva Insights Stay Informed Microsoft Viva False N/A

Login to your account

Welcome Back, We Missed You!