2022 CW 23 Microsoft 365 Message Center changes

from 05/30/2022 to 06/05/2022

23 Office 365 Message Center Items were changed and 27 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
MC365786 (Updated) Configuration Change in Name parameter for Exchange Online 05/31/2022 09:00:00 2022-06-30T09:00:00Z 06/30/2022

MC End Time changes

MC ID MC Title Old Value New Value MC Action required by
MC284259 (Updated) Microsoft Forms new App "Polls" in Teams 06/30/2022 10:00:00 2022-07-22T10:00:00Z N/A
MC292796 (Updated) Co-organizer Meeting Role 07/22/2022 10:00:00 2022-07-31T10:00:00Z N/A
MC296205 (Updated) Multi-language Teams meeting invite control 07/22/2022 10:00:00 2022-08-26T10:00:00Z N/A
MC318990 (Updated) Forms: Allow up to 5 million Responses per Form/Quiz 06/30/2022 09:00:00 2022-07-22T09:00:00Z N/A
MC333945 (Updated) Updates to Threat Explorer and Email entity page 06/30/2022 09:00:00 2022-08-01T09:00:00Z N/A
MC341571 (Updated) Microsoft Teams: Casting from Teams desktop client to Microsoft Teams Rooms 06/30/2022 09:00:00 2022-08-05T09:00:00Z N/A
MC341572 (Updated) Microsoft Teams: Text Predictions for Teams Mobile (Android) 06/30/2022 09:00:00 2022-07-31T09:00:00Z N/A
MC341683 (Updated) Upcoming changes to Office 365 Management API events for Microsoft Defender for Office 365 07/29/2022 09:00:00 2022-08-31T09:00:00Z N/A
MC350768 (Updated) SharePoint: Create from the SharePoint app bar 07/01/2022 09:00:00 2022-09-30T09:00:00Z N/A
MC362277 (Updated) Display a message to Stream (Classic) end users 07/07/2022 09:00:00 2022-08-26T09:00:00Z N/A
MC365786 (Updated) Configuration Change in Name parameter for Exchange Online 08/31/2022 09:00:00 2022-09-30T09:00:00Z 06/30/2022
MC376706 (Updated) Microsoft Project usage data in Microsoft Admin Center 07/14/2022 09:00:00 2022-08-01T09:00:00Z N/A
MC384329 (Updated) Multitasking Panel for Meetings on iPad 07/07/2022 09:00:00 2022-07-29T09:00:00Z N/A

MC Messages changes

MC ID MC Title Old Value New Value MC Action required by
MC284259 (Updated) Microsoft Forms new App "Polls" in Teams Updated May 13, 2022: We have updated the rollout timeline below. Thank you for your patience.

Microsoft Forms has always focused on providing the best polling experience to our customers. However, according to customer feedback and telemetry, we have determined that many people don't know the "Forms" App provides polling capability in Teams.

To provide a better experience we are delivering a new Teams app specifically for polling capabilities. This new app will be discoverable in Teams meetings/chats as “Polls”.

This message is associated with Microsoft 365 Roadmap ID 84567

[When this will happen:]

We will begin rolling this out starting in Teams meetings and then moving to Teams chat in February (previously mid-October) and expect to complete by late May (previously late April).

The original "Forms" app will be retired from Teams meetings in March (previously January), and then will be retired from Teams chat in April (previously February). Once retired from meetings/chat the “Forms” app will only be available in the Teams channel tab to provide Survey capabilities.
Updated June 2, 2022: We have updated the rollout timeline below. Thank you for your patience.

Microsoft Forms has always focused on providing the best polling experience to our customers. However, according to customer feedback and telemetry, we have determined that many people don't know the "Forms" App provides polling capability in Teams.

To provide a better experience we are delivering a new Teams app specifically for polling capabilities. This new app will be discoverable in Teams meetings/chats as “Polls”.

This message is associated with Microsoft 365 Roadmap ID 84567

[When this will happen:]

We will begin rolling this out starting in Teams meetings and then moving to Teams chat in February (previously mid-October) and expect to complete by mid-June (previously late May).

The original "Forms" app will be retired from Teams meetings in March (previously January), and then will be retired from Teams chat in April (previously February). Once retired from meetings/chat the “Forms” app will only be available in the Teams channel tab to provide Survey capabilities.
N/A
MC292796 (Updated) Co-organizer Meeting Role Updated May 26, 2022: We have updated the rollout timeline below. Thank you for your patience.

Organizers will soon be able to assign the co-organizer meeting role to up to 10 specific people they invite to their meeting. Co-organizers will be granted most of the capabilities of the organizer in the meeting, including being able to access & modify the meeting options for the meeting.

Usage of the co-organizer role for a meeting will be optional. If users choose not to use the co-organizer feature, there will be no change.

This message is associated with Microsoft 365 Roadmap ID 81391.

[When this will happen:]

We expect this feature to begin rolling out in late May (previously mid-May) and expect the rollout to be complete by mid-June (previously late May).
Updated June 2, 2022: We have updated the rollout timeline below. Thank you for your patience.

Organizers will soon be able to assign the co-organizer meeting role to up to 10 specific people they invite to their meeting. Co-organizers will be granted most of the capabilities of the organizer in the meeting, including being able to access & modify the meeting options for the meeting.

Usage of the co-organizer role for a meeting will be optional. If users choose not to use the co-organizer feature, there will be no change.

This message is associated with Microsoft 365 Roadmap ID 81391.

[When this will happen:]

We expect this feature to begin rolling out in mid-June (previously late May) and expect the rollout to be complete by late June (previously mid-June).
N/A
MC296205 (Updated) Multi-language Teams meeting invite control Updated December 28, 2021: Based on learnings from our early rings, we have made the decision to make additional changes before we proceed with the rollout. We have updated the rollout timeline below. Thank you for your patience.

Multi-language Teams meeting invite control enables administrators to configure the join information languages in meeting invitations. Controlled by a new policy parameter, this feature allows the administrator to set up to two languages to replace the user preferred language when creating new Teams meeting invitations across all email platforms.

This message is associated with Microsoft 365 Roadmap ID 81521.

[When this will happen:]

We expect this update to begin rolling out in early May 2022 and expect the rollout to be fully completed by mid-June.

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

Multi-language Teams meeting invite control enables administrators to configure the join information languages in meeting invitations. Controlled by a new policy parameter, this feature allows the administrator to set up to two languages to replace the user preferred language when creating new Teams meeting invitations across all email platforms.

This message is associated with Microsoft 365 Roadmap ID 81521.

[When this will happen:]

Standard rollout targeting mid-June and complete by end of June.

GCC rollout targeting early July and complete by mid-July.

N/A
MC318990 (Updated) Forms: Allow up to 5 million Responses per Form/Quiz Updated April 29, 2022: We have updated the rollout timeline below. Thank you for your patience.

The number of responses allowed per Form/Quiz is being increased from 50,000 to 5 million. After a Form passes 50,000 responses, the form can continue to collect additional responses and the Form owner can export the results as a .csv file for further analysis

This message is associated with Microsoft 365 Roadmap ID 87750.

[When this will happen:]

Targeted Release is expected to begin in early March and will fully roll out for General Availability by early April.

Government Clouds: We expect to roll this out to government clouds beginning in mid-April and expect that rollout to be completed by late May (previously late April).
Updated June 2, 2022: We will not be moving forward with this feature for GCC-High or DoD organizations at this time and the supported number of responses will continue to be 50,000. We have updated the rollout timeline below for GCC organizations. Thank you for your patience.

The number of responses allowed per Form/Quiz is being increased from 50,000 to 5 million. After a Form passes 50,000 responses, the form can continue to collect additional responses and the Form owner can export the results as a .csv file for further analysis

This message is associated with Microsoft 365 Roadmap ID 87750.

[When this will happen:]

Targeted Release is expected to begin in early March and will fully roll out for General Availability by early April. - Complete

GCC: We expect to roll this out to government clouds beginning in mid-April and expect that rollout to be completed by mid-June (previously late May).
N/A
MC333945 (Updated) Updates to Threat Explorer and Email entity page Updated April 29, 2022: We have updated the rollout timeline below. Thank you for your patience.

As part of Hunting improvements, we are making updates to the Email entity page, and Threat Explorer and Real-Time Detections. These updates should help provide additional data points and context for security analysts. These updates include:

Updates to Email entity Page will include:

A section around Threat Detection Details which will contain information around Threat, the corresponding detection technology and if the detection ran into any additional context.

We will also light up additional email attributes like To, CC, Distribution list, Client information and forwarding (indicating if email forwarding was involved)

Override information would include the Primary override and Source (Primary override is the override which impacted the delivery of the email) as well as any additional overrides that were applicable to the email.

If a URL or a File was allowed due to a tenant policy like Tenant Allow/Block list, then that information would be shown in the entity views as well.

Updates to Threat Explorer will include:

Threat Explorer filters around System Override and System Override source would be renamed to Primary Override and Primary Override source to indicate the specific overrides which impacted the delivery of the email. This will help the analyst to locate malicious emails delivered due to potential config gaps, as well as identifying any tenant or user level configurations which have impacted the delivery of an email.

In addition to the name updates for the above 2 filters, we will also be lighting up new filters to cover scenarios like if an email contained forwarding or not.

[When this will happen:]

We expect these updates to begin rolling out in early March and expect the rollout to be completed by late May (previously late April).
Updated June 2, 2022: We have updated the rollout timeline below. Thank you for your patience.

As part of Hunting improvements, we are making updates to the Email entity page, and Threat Explorer and Real-Time Detections. These updates should help provide additional data points and context for security analysts. These updates include:

Updates to Email entity Page will include:

A section around Threat Detection Details which will contain information around Threat, the corresponding detection technology and if the detection ran into any additional context.

We will also light up additional email attributes like To, CC, Distribution list, Client information and forwarding (indicating if email forwarding was involved)

Override information would include the Primary override and Source (Primary override is the override which impacted the delivery of the email) as well as any additional overrides that were applicable to the email.

If a URL or a File was allowed due to a tenant policy like Tenant Allow/Block list, then that information would be shown in the entity views as well.

Updates to Threat Explorer will include:

Threat Explorer filters around System Override and System Override source would be renamed to Primary Override and Primary Override source to indicate the specific overrides which impacted the delivery of the email. This will help the analyst to locate malicious emails delivered due to potential config gaps, as well as identifying any tenant or user level configurations which have impacted the delivery of an email.

In addition to the name updates for the above 2 filters, we will also be lighting up new filters to cover scenarios like if an email contained forwarding or not.

[When this will happen:]

We expect these updates to begin rolling out in early March and expect the rollout to be completed by late June (previously late May).
N/A
MC341571 (Updated) Microsoft Teams: Casting from Teams desktop client to Microsoft Teams Rooms Updated April 29, 2022: We have updated the rollout timeline below. Thank you for your patience.

For quick ad-hoc sessions that don’t require setting up a formal meeting, people can use Teams casting to wirelessly connect to a Teams Room and display content from the Teams desktop client (Windows and Mac). Users can share their screen and cast content stored locally on their computer or accessible via Office 365.

This message is associated with Microsoft 365 Roadmap ID 88027.

[When this will happen:]

We expect this rollout to begin in mid-March and expect to complete the rollout by late May (previously late April).
Updated June 2, 2022: We have updated the rollout timeline below. Thank you for your patience.

For quick ad-hoc sessions that don’t require setting up a formal meeting, people can use Teams casting to wirelessly connect to a Teams Room and display content from the Teams desktop client (Windows and Mac). Users can share their screen and cast content stored locally on their computer or accessible via Office 365.

This message is associated with Microsoft 365 Roadmap ID 88027.

[When this will happen:]

We expect this rollout to begin in mid-March and expect to complete the rollout by late June (previously late May).
N/A
MC341572 (Updated) Microsoft Teams: Text Predictions for Teams Mobile (Android) Text predictions is coming to Teams for Android.

When you compose or reply to a message in Teams, Editor Text Predictions anticipates your writing and suggests a suitable word or phrase inline. This saves time and helps to reduce typos.

This message is associated with Microsoft 365 Roadmap ID 81573.

[When this will happen:]

We expect the rollout to begin in early April and expect the rollout to be completed by late May.
Updated June 2, 2022: We have updated the rollout timeline below. Thank you for your patience.

Text predictions is coming to Teams for Android.

When you compose or reply to a message in Teams, Editor Text Predictions anticipates your writing and suggests a suitable word or phrase inline. This saves time and helps to reduce typos.

This message is associated with Microsoft 365 Roadmap ID 81573.

[When this will happen:]

We expect the rollout to begin in early April and expect the rollout to be completed by late June (previously late May).
N/A
MC341683 (Updated) Upcoming changes to Office 365 Management API events for Microsoft Defender for Office 365 Updated May 06, 2022: We have updated the rollout timeline below. Thank you for your patience.

In alignment with the permanent redirection of the Office 365 Security & Compliance Center (SCC), and as previously mentioned (MC320940 - Feb 2022), we will be updating the deeplinks for Microsoft Defender for Office 365 events in Office 365 management API and the Unified Audit logs.

[When this will happen:]

We will begin rolling this out in late May (previously late April) and expect to complete rollout late June (previously mid-June).
Updated June 2, 2022: We have updated the rollout timeline below. Thank you for your patience.

In alignment with the permanent redirection of the Office 365 Security & Compliance Center (SCC), and as previously mentioned (MC320940 - Feb 2022), we will be updating the deeplinks for Microsoft Defender for Office 365 events in Office 365 management API and the Unified Audit logs.

[When this will happen:]

We will begin rolling this out in late June (previously late May) and expect to complete rollout late July (previously late June).
N/A
MC350371 (Updated) Teams PowerShell Module – versions older than 4.x.x to be retired Updated May 05, 2022: We are updating this post as a reminder of this upcoming change and provide additional information you may find helpful:

Teams PowerShell Module versions 4.2.0 & 4.3.0 have also been released with support for Proxy & few additional fixes. More details in Microsoft Teams PowerShell Release Notes.

While using Teams PowerShell Module versions 4.x.x or later, it’s recommended to not use any of the deprecated or unsupported cmdlets mentioned at Teams PowerShell Module - Supported Versions.

Upcoming, we will be retiring all Teams PowerShell Module (TPM) versions older than 4.x.x. Instead, we recommend updating the TPM module to the latest version which is where we will continue to invest our resources.

Note: If your organization has already updated to TPM version 4.x.x or above, you can safely disregard this message.

[When will this happen:]

We will begin retiring all Teams PowerShell Module (TPM) versions older than 4.x.x. in mid-June.
Updated May 31, 2022: This is the final reminder for this upcoming change. Starting June 15, 2022, all Teams PowerShell Module versions earlier than 4.x.x will be retired and will stop working. Please update to the latest Teams PowerShell Module version as soon as possible.

Teams PowerShell Module versions 4.2.0 & 4.3.0 have also been released with support for Proxy & few additional fixes. More details in Microsoft Teams PowerShell Release Notes.

While using Teams PowerShell Module versions 4.x.x or later, it’s recommended to not use any of the deprecated or unsupported cmdlets mentioned at Teams PowerShell Module - Supported Versions.

Upcoming, we will be retiring all Teams PowerShell Module (TPM) versions older than 4.x.x. Instead, we recommend updating the TPM module to the latest version which is where we will continue to invest our resources.

Note: If your organization has already updated to TPM version 4.x.x or above, you can safely disregard this message.

[When will this happen:]

We will begin retiring all Teams PowerShell Module (TPM) versions older than 4.x.x. in mid-June.
06/15/2022
MC350768 (Updated) SharePoint: Create from the SharePoint app bar Updated May 05, 2022: We have updated the rollout timeline below. Thank you for your patience.

Apologies for the delayed release of this new feature. Resources in the SharePoint app bar are expanding to include the ability to create sites, files, and lists as an action.

[Key points:]

Microsoft 365 Roadmap ID 82160

Timing:

Targeted Release (select users and entire org): will begin rolling out in mid-April and will complete by late April

Standard: will begin rolling out in mid-May (previously early May) and will complete by late May (previously mid-May).

Action: Action: review and assess

Roll-out: tenant level
Updated June 2, 2022: Based on learnings from our early rings, we have made the decision to make additional changes before we proceed with the rollout. The create command in the app bar will be temporarily removed to address some stability issues with the Office document creation. We will add this experience back to the app bar starting in late July. We have updated the rollout timeline below. Thank you for your patience.

Apologies for the delayed release of this new feature. Resources in the SharePoint app bar are expanding to include the ability to create sites, files, and lists as an action.

[Key points:]

Microsoft 365 Roadmap ID 82160

Timing:

Targeted Release (select users and entire org): will begin rolling out in late July (previously mid-April) and will complete by mid-August (previously late April)

Standard: will begin rolling out in mid-August (previously mid-May) and will complete by late August (previously late May).

Action: Action: review and assess

Roll-out: tenant level
N/A
MC360646 (Updated) Exchange Online Protection: Anti-malware policy notification settings change Updated May 17, 2022: We have updated the rollout timeline below. Thank you for your patience.

The previous Message Center post MC303513 (Dec '21) mentioned that we’re planning to retire the recipient and sender notification configuration in anti-malware policies. After reviewing customer feedback, we’re changing how we’re planning to retire those recipient and sender notifications.

The current notification settings are commonly used for messages that are blocked/quarantined as detected malware, or due to a file attachment in the common attachment filter settings.

As part of this change, we’re separating out the handling of notifications based on whether the message was scanned and found to be malicious vs. matches from the common attachment filter:

True malware: Both recipient and sender notifications will be retired. The message will be quarantined, and the selected quarantine policy configuration determines whether to send the end-user notifications. There is no option for sender notification.

Common attachment filter: Notifications are split into two distinct options that the admin can choose (one or the other):

Recipient notifications only: As with true malware detections, the selected quarantine policy configuration determines whether to send end-user notifications. There is no option for sender notifications.

Non delivery report (also known as NDR or bounce message)) to sender: The message is rejected in an NDR to the sender. The message is not quarantined, is not recoverable, and there’s no option for recipient notifications.

This message is associated with Microsoft 365 Roadmap ID 93212

[When this will happen:]

Starting early June (previously mid-May) and completion of deployment by late July (previously late June)

Updated June 1, 2022: We have updated this message to ensure visibility for affected organizations. Thank you for your patience.

The previous Message Center post MC303513 (Dec '21) mentioned that we’re planning to retire the recipient and sender notification configuration in anti-malware policies. After reviewing customer feedback, we’re changing how we’re planning to retire those recipient and sender notifications.

The current notification settings are commonly used for messages that are blocked/quarantined as detected malware, or due to a file attachment in the common attachment filter settings.

As part of this change, we’re separating out the handling of notifications based on whether the message was scanned and found to be malicious vs. matches from the common attachment filter:

True malware: Both recipient and sender notifications will be retired. The message will be quarantined, and the selected quarantine policy configuration determines whether to send the end-user notifications. There is no option for sender notification.

Common attachment filter: Notifications are split into two distinct options that the admin can choose (one or the other):

Recipient notifications only: As with true malware detections, the selected quarantine policy configuration determines whether to send end-user notifications. There is no option for sender notifications.

Non delivery report (also known as NDR or bounce message)) to sender: The message is rejected in an NDR to the sender. The message is not quarantined, is not recoverable, and there’s no option for recipient notifications.

This message is associated with Microsoft 365 Roadmap ID 93212

[When this will happen:]

Starting early June (previously mid-May) and completion of deployment by late July (previously late June)

N/A
MC360766 (Updated) Loop components in Outlook Mail Preview Updated May 10, 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 and Outlook Windows desktop Current Channel (Preview) in late May (previously early May) and expect it to be completed by late June (previously late May).

General availability of Loop components in Outlook for Web and Windows desktop is expected to begin in July.

Updated June 2, 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 and Outlook Windows desktop Current Channel (Preview) in late May (previously early May) and expect it to be completed by late June (previously late May).

General availability of Loop components in Outlook for Web and Windows desktop is expected to begin in July.

N/A
MC362277 (Updated) Display a message to Stream (Classic) end users Upcoming, we will be introducing a couple of features that will help you display a message to your Stream (Classic) end users and in addition, will allow them to see options to upload on either classic or new Stream (on SharePoint).

[When this will happen]

We will begin rolling this out in mid-May and expect to complete rollout late May.
Updated June 2, 2022: We have updated the rollout timeline below. Thank you for your patience.

Upcoming, we will be introducing a couple of features that will help you display a message to your Stream (Classic) end users and in addition, will allow them to see options to upload on either classic or new Stream (on SharePoint).

[When this will happen]

We will begin rolling this out in mid-May and expect to complete rollout in mid-July (previously late May).
N/A
MC365392 (Updated) Communication Compliance: Reduce detection to investigation time from 24 hours to 1 hour (preview) Coming soon to public preview, we're reducing detection to investigation time to enable your organization to respond promptly to Communication Compliance policy violations.

This message is associated with Microsoft 365 Roadmap ID 88915.

[When this will happen:]

Rollout will begin in late May and is expected to be complete by mid-June.
Updated May 31, 2022: We have updated the rollout timeline below. Thank you for your patience.

Coming soon to public preview, we're reducing detection to investigation time to enable your organization to respond promptly to Communication Compliance policy violations.

This message is associated with Microsoft 365 Roadmap ID 88915.

[When this will happen:]

Rollout will begin in mid-June (previously late May) and is expected to be complete by late June (previously mid-June).
N/A
MC365786 (Updated) Configuration Change in Name parameter for Exchange Online We're making some changes to the way Name parameter is being set in Exchange Online. We will be making a change to utilize unique ExternalDirectoryObjectId (EDOID) in the place of Name parameter in Exchange Online only.

[When this will happen:]

We will begin rolling this out in late May and expect to complete late July

[How this impacts your organization:]

After this change administrators may no longer be able to see subsequent CN value change in Exchange on-premises to be reflected in the object’s Name property in Exchange Online.

The updated naming logic would take effect only during new user creation. Existing users won’t get impacted in any way.

Please note that since we will start using EDOID as Name in Exchange Online, we shall stop allowing changes in CN to reflect in Name property in Exchange Online for all users (both new and existing).

Updated June 1, 2022: Based on customer feedback, we have made the decision to provide additional time for organizations to prepare for the change. We have updated the rollout timeline below. Thank you for your feedback.

We're making some changes to the way Name parameter is being set in Exchange Online. We will be making a change to utilize unique ExternalDirectoryObjectId (EDOID) in the place of Name parameter in Exchange Online only.

[When this will happen:]

We will begin rolling this out in late June (previously late May) and expect to complete late August (previously late July).

[How this impacts your organization:]

After this change administrators may no longer be able to see subsequent CN value change in Exchange on-premises to be reflected in the object’s Name property in Exchange Online.

The updated naming logic would take effect only during new user creation. Existing users won’t get impacted in any way.

Please note that since we will start using EDOID as Name in Exchange Online, we shall stop allowing changes in CN to reflect in Name property in Exchange Online for all users (both new and existing).

06/30/2022
MC376706 (Updated) Microsoft Project usage data in Microsoft Admin Center Project usage data will soon be included in the Microsoft Admin Center Customer facing usage reports.

This message is associated with Microsoft 365 Roadmap ID 93278

[When this will happen:]

We will begin rolling out in late May and expect to complete by mid-June.
Updated June 2, 2022: We have updated the rollout timeline below. Thank you for your patience.

Project usage data will soon be included in the Microsoft Admin Center Customer facing usage reports.

This message is associated with Microsoft 365 Roadmap ID 93278

[When this will happen:]

We will begin rolling out in early June (previously late May) and expect to complete by late June (previously mid-June).
N/A
MC378419 (Updated) Automatic groupings available in Teams for channel posts A new Automatic Grouping will be available in Teams as a suggestion to use in channel posts. Users will be able to use "@Team Owners" in a channel posting and all Team Owners will be notified. This functionality will be available in both Web and Mobile.

This message is associated with Microsoft 365 Roadmap ID: 94118

[When this will happen:]

Standard Release: We expect this rollout to begin in early May and expect the rollout to be completed by late June.

GCC: We expect this rollout to begin in late May and expect the rollout to be completed in early July.

GCC-H: We expect this rollout to begin in late May and expect the rollout to be completed in early July.

DoD: We expect this rollout to begin in late May and expect the rollout to be completed in early July.
Updated June 1, 2022: We have updated the content below for clarity. Thank you for your feedback.

A new Automatic Grouping will be available in Teams as a suggestion to use in channel posts. Users will be able to use "@Team Owners" in a channel posting and all Team Owners will be notified. This functionality will be available in both Desktop (including Web) and Mobile.

This message is associated with Microsoft 365 Roadmap ID: 94118

[When this will happen:]

Standard Release: We expect this rollout to begin in early May and expect the rollout to be completed by late June.

GCC: We expect this rollout to begin in late May and expect the rollout to be completed in early July.

GCC-H: We expect this rollout to begin in late May and expect the rollout to be completed in early July.

DoD: We expect this rollout to begin in late May and expect the rollout to be completed in early July.
N/A
MC379026 (Updated) New Yammer as only option for non-admin users We are pleased to announce that the next phase of the new Yammer experience rollout is a month away. With this change, all users will access the new Yammer experience, and the toggle for classic Yammer will be removed. Admins can still switch to the classic Yammer experience via a new toggle in the Yammer admin settings.

[Key points]

Timing: We will begin rolling this out in mid-June and expect to complete rollout late June.

Action: To get the most out of the Yammer experience, we recommend enabling the new version of Yammer now for all users and review the changes and assess the impact on your organization.

Roll-out: tenant level
Updated June 2, 2022: We have updated the content below to provide additional clarity. Thank you for your patience.

We are pleased to announce that the next phase of the new Yammer experience rollout is a month away. With this change, all users will access the new Yammer experience, and the toggle for classic Yammer will be removed. Admins can still switch to the classic Yammer experience via a new toggle in the Yammer admin settings.

[Key points]

Timing: We will begin rolling this out in mid-June and expect to complete rollout late June.

Action: To get the most out of the Yammer experience, we recommend enabling the new version of Yammer now for all users and review the changes and assess the impact on your organization.

Roll-out: tenant level
N/A
MC379407 (Updated) Exchange Online-Add, edit custom file types in Anti-malware policy In anti-malware policies, the common attachment filter allows you to select specific file types to block. Any email messages with these types of file attachment will be handled as per the policy settings. In addition to turning on the common attachment filter, you can customize the list of file types, but only by using the Set-MalwareFilterPolicy cmdlet in Exchange Online PowerShell.

We’re enhancing the anti-malware policy experience of anti-malware policy by adding the ability to view/add/remove custom file types in the anti-malware policy settings in the Microsoft 365 Defender portal.

This message is associated with Microsoft 365 Roadmap ID 85611

[When this will happen:]

Starting in mid-June and completion of the rollout by late July.

Updated June 01, 2022: We have updated this message to ensure visibility for affected organizations. Thank you for your patience.

In anti-malware policies, the common attachment filter allows you to select specific file types to block. Any email messages with these types of file attachment will be handled as per the policy settings. In addition to turning on the common attachment filter, you can customize the list of file types, but only by using the Set-MalwareFilterPolicy cmdlet in Exchange Online PowerShell.

We’re enhancing the anti-malware policy experience of anti-malware policy by adding the ability to view/add/remove custom file types in the anti-malware policy settings in the Microsoft 365 Defender portal.

This message is associated with Microsoft 365 Roadmap ID 85611

[When this will happen:]

Starting in mid-June and completion of the rollout by late July.

N/A
MC379408 (Updated) Exchange Online-Updates to the file type list in the common attachment filter In anti-malware policies, you can select specific file types to identify as malware using the common attachment filter. Any email message with attachments of these specific file types will be handled per the policy settings. You can configure this specific list of file types by selecting them from the pre-defined list in the policy properties in the Microsoft 365 Defender portal or by manually adding your own (custom) file types using the power shell Set-MalwareFilterPolicy cmdlet in Exchange Online PowerShell.

Based on internal research and best practices guidelines from industry and other organizations, we are updating the list of file types that are available for selection. Currently, there are 95+ file types in the list, of which 13 are pre-selected by default in the common attachment filter settings. We are expanding this list to cover over 200 file types, of which over 50 are selected by default.

After rollout, this new expanded list along with the default selection will automatically apply to:

Any new anti-malware policies that you create

The default anti-malware policy

The file selections in your existing anti-malware policies (enabled or not) will be retained and will not be updated automatically. You will need to manually update your existing policies with the recommended list of default file types (see below).

This message is associated with Microsoft 365 Roadmap ID 85611

[When this will happen:]

Starting mid-June and completion of deployment by late July

Updated June 1, 2022: We have updated this message to ensure visibility for affected organizations. Thank you for your patience.

In anti-malware policies, you can select specific file types to identify as malware using the common attachment filter. Any email message with attachments of these specific file types will be handled per the policy settings. You can configure this specific list of file types by selecting them from the pre-defined list in the policy properties in the Microsoft 365 Defender portal or by manually adding your own (custom) file types using the power shell Set-MalwareFilterPolicy cmdlet in Exchange Online PowerShell.

Based on internal research and best practices guidelines from industry and other organizations, we are updating the list of file types that are available for selection. Currently, there are 95+ file types in the list, of which 13 are pre-selected by default in the common attachment filter settings. We are expanding this list to cover over 200 file types, of which over 50 are selected by default.

After rollout, this new expanded list along with the default selection will automatically apply to:

Any new anti-malware policies that you create

The default anti-malware policy

The file selections in your existing anti-malware policies (enabled or not) will be retained and will not be updated automatically. You will need to manually update your existing policies with the recommended list of default file types (see below).

This message is associated with Microsoft 365 Roadmap ID 85611

[When this will happen:]

Starting mid-June and completion of deployment by late July

N/A
MC384329 (Updated) Multitasking Panel for Meetings on iPad The Teams Mobile meeting experience is being updated for the iPad. Users will now see a collapsible right panel during meetings, which enables richer multitasking experiences such as chat or viewing participant list alongside the ongoing meeting.

This message is associated with Microsoft 365 Roadmap ID 86923

[When this will happen:]

This feature will begin rollout in late May, and will complete rollout by early June.

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

The Teams Mobile meeting experience is being updated for the iPad. Users will now see a collapsible right panel during meetings, which enables richer multitasking experiences such as chat or viewing participant list alongside the ongoing meeting.

This message is associated with Microsoft 365 Roadmap ID 86923

[When this will happen:]

This feature will begin rollout in early June (previously late May) and will complete rollout by mid-June (previously early June).

N/A
MC384778 (Updated) Microsoft 365 Admin Center: GroupID to be Hidden by Default in Microsoft 365 Active User Reports We will be hiding the GroupID variable in Microsoft 365 Usage Reports in the ‘Groups activity’ section of the ‘Active users – Microsoft 365 Services’ and ‘Active Users – Microsoft 365 Apps’ from June 2023.

This message is associated with Microsoft 365 Roadmap ID 93308

[When this will happen:]

We will be rolling this out to all customers beginning in late June and complete roll out by late July.
Updated June 2, 2022: We have updated the content below for clarity. Thank you for your feedback.

We will be hiding the GroupID variable in Microsoft 365 Usage Reports in the ‘Groups activity’ section of the ‘Active users – Microsoft 365 Services’ and ‘Active Users – Microsoft 365 Apps’ from June 2023.

This message is associated with Microsoft 365 Roadmap ID 93308

[When this will happen:]

We will be rolling this out to all customers beginning in late June and complete roll out by late July.
N/A
MC386412 Flow.microsoft.com is moving to make.powerautomate.com Over the next several weeks (June-July 2022), we will be in the process of moving our Power Automate portal to a new common Power Platform infrastructure which will include new domains for the Power Automate portal. Once we enable this, the existing Power Automate URLs will start redirecting to the new URLs.

What actions do I need to take?

Overall, the new Power Automate Portal experience should look and feel mostly the same as the existing Power Automate portal.

However, you need to make sure that the new URLs are not blocked by your network so that they will work when the redirect occurs.

Here is the list of the new URLs that you need to make sure they are not blocked by your network:

Existing Power Automate URLs

*.flow.microsoft.com

flow.microsoft.com

New Power Automate URLs (After redirection is enabled)

*.powerautomate.com

make.powerautomate.com

If you are a US Government customer:

Existing Power Automate URLs

gov.flow.microsoft.us

high.flow.microsoft.us

flow.appsplatform.us

New Power Automate URLs (After redirection is enabled)

gov.flow.microsoft.us

high.flow.microsoft.us

flow.appsplatform.us

If you are a customer in China:

Existing Power Automate URLs

www.powerautomate.cn

New Power Automate URLs (After redirection is enabled)

make.powerautomate.cn

We have updated the following documentation to include the new URLs:

IP address configuration - Power Automate | Microsoft Docs

Power Automate US Government - Power Automate | Microsoft Docs

Note: These new sites may be accessible with your existing accounts today. However, unless redirect occurs automatically, these new sites are not officially released. Any access or other issues related to the new URLs should be reported to Microsoft only after the official release dates (i.e when URL automatically redirects).

Over the next several weeks (June-July 2022), we will be in the process of moving our Power Automate portal to a new common Power Platform infrastructure which will include new domains for the Power Automate portal. Once we enable this, the existing Power Automate URLs will start redirecting to the new URLs.

What actions do I need to take?

Overall, the new Power Automate Portal experience should look and feel mostly the same as the existing Power Automate portal.

However, you need to make sure that the new URLs are not blocked by your network so that they will work when the redirect occurs.

Here is the list of the new URLs that you need to make sure they are not blocked by your network:

Existing Power Automate URLs

*.flow.microsoft.com

flow.microsoft.com

New Power Automate URLs (After redirection is enabled)

*.powerautomate.com

make.powerautomate.com

If you are a US Government customer:

Existing Power Automate URLs

gov.flow.microsoft.us

high.flow.microsoft.us

flow.appsplatform.us

New Power Automate URLs (After redirection is enabled)

make.gov.powerautomate.us

make.high.powerautomate.us

make.powerautomate.appsplatform.us

If you are a customer in China:

Existing Power Automate URLs

www.powerautomate.cn

New Power Automate URLs (After redirection is enabled)

www.make.powerautomate.cn

We have updated the following documentation to include the new URLs:

IP address configuration - Power Automate | Microsoft Docs

Power Automate US Government - Power Automate | Microsoft Docs

Note: These new sites may be accessible with your existing accounts today. However, unless redirect occurs automatically, these new sites are not officially released. Any access or other issues related to the new URLs should be reported to Microsoft only after the official release dates (i.e when URL automatically redirects).

N/A

MC MessageTagNames changes

MC ID MC Title Old Value New Value MC Action required by
MC341572 (Updated) Microsoft Teams: Text Predictions for Teams Mobile (Android) New feature, User impact, Admin impact Updated message, New feature, User impact, Admin impact N/A
MC362277 (Updated) Display a message to Stream (Classic) end users New feature, User impact, Admin impact Updated message, New feature, User impact, Admin impact N/A
MC365392 (Updated) Communication Compliance: Reduce detection to investigation time from 24 hours to 1 hour (preview) New feature, Admin impact Updated message, New feature, Admin impact N/A
MC365786 (Updated) Configuration Change in Name parameter for Exchange Online Admin impact Updated message, Admin impact 06/30/2022
MC376706 (Updated) Microsoft Project usage data in Microsoft Admin Center New feature, Admin impact Updated message, New feature, Admin impact N/A
MC378419 (Updated) Automatic groupings available in Teams for channel posts Feature update, User impact Updated message, Feature update, User impact N/A
MC379026 (Updated) New Yammer as only option for non-admin users Feature update, Admin impact Updated message, Feature update, Admin impact N/A
MC379407 (Updated) Exchange Online-Add, edit custom file types in Anti-malware policy Feature update, Admin impact Updated message, Feature update, Admin impact N/A
MC379408 (Updated) Exchange Online-Updates to the file type list in the common attachment filter Feature update, Admin impact Updated message, Feature update, Admin impact N/A
MC384329 (Updated) Multitasking Panel for Meetings on iPad Feature update, User impact Updated message, Feature update, User impact N/A
MC384778 (Updated) Microsoft 365 Admin Center: GroupID to be Hidden by Default in Microsoft 365 Active User Reports User impact, Admin impact Updated message, User impact, Admin impact N/A

MC prepare changes

MC ID MC Title Old Value New Value MC Action required by
MC341572 (Updated) Microsoft Teams: Text Predictions for Teams Mobile (Android) Review your messaging policies and the policy setting for this feature.

https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=81573
Review your messaging policies and the policy setting for this feature.

https://www.microsoft.com/en-ww/microsoft-365/roadmap?filters=&searchterms=81573
N/A
MC379026 (Updated) New Yammer as only option for non-admin users You can use a trial tenant to test the experience without changing your existing Yammer network.

Additionally, you may consider updating your training and documentation, as well as sending out change communications within your organization as appropriate.

Learn more:

Yammer Adoption

New Yammer for admins: Bring new Yammer to your organization

https://aka.ms/YamResources

https://docs.microsoft.com/en-us/yammer/get-started-with-yammer/administrative-settings-opt-in-newyamme

You can use a trial tenant to test the experience without changing your existing Yammer network.

Additionally, you may consider updating your training and documentation, as well as sending out change communications within your organization as appropriate.

Note: Although the connectors will remain active in the new Yammer, their configuration can only be modified from the classic version of Yammer, by admin users.

Learn more:

Yammer Adoption

New Yammer for admins: Bring new Yammer to your organization

https://aka.ms/YamResources

https://docs.microsoft.com/en-us/yammer/get-started-with-yammer/administrative-settings-opt-in-newyamme

N/A
MC384778 (Updated) Microsoft 365 Admin Center: GroupID to be Hidden by Default in Microsoft 365 Active User Reports Global administrators can revert this change for their tenant and show identifiable user information if their organization’s privacy practices allow. This can be achieved in the Microsoft 365 admin center by going to Settings > Org Settings > Services and selecting Reports. Under Choose how to show user information, uncheck the statement 'In all reports, display de-identified names for users, groups, and sites', and then save your changes. Showing identifiable user information is a logged event in the Microsoft 365 compliance center audit log.

You are receiving this message because our reporting indicates one or more users in your organization are using or have access to Microsoft 365 usage reports in the admin center.

Learn More:

Microsoft 365 Reports in the Admin Center

https://docs.microsoft.com/microsoft-365/admin/activity-reports/activity-reports?view=o365-worldwide#show-user-details-in-the-reports

https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=93308
Global administrators can revert this change for their tenant and show identifiable user information if their organization’s privacy practices allow. This can be achieved in the Microsoft 365 admin center by going to the Settings > Org Settings > Services page, selecting ‘Reports’ and unticking ‘Display concealed user group and site names in all reports’. Showing identifiable user information is a logged event in the Microsoft 365 compliance center audit log.

You are receiving this message because our reporting indicates one or more users in your organization are using or have access to Microsoft 365 usage reports in the admin center.

Learn More:

Microsoft 365 Reports in the Admin Center

https://docs.microsoft.com/microsoft-365/admin/activity-reports/activity-reports?view=o365-worldwide#show-user-details-in-the-reports

https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=93308
N/A

MC Title changes

MC ID MC Title Old Value New Value MC Action required by
MC341572 (Updated) Microsoft Teams: Text Predictions for Teams Mobile (Android) Microsoft Teams: Text Predictions for Teams Mobile (Android) (Updated) Microsoft Teams: Text Predictions for Teams Mobile (Android) N/A
MC362277 (Updated) Display a message to Stream (Classic) end users Display a message to Stream (Classic) end users (Updated) Display a message to Stream (Classic) end users N/A
MC365392 (Updated) Communication Compliance: Reduce detection to investigation time from 24 hours to 1 hour (preview) Communication Compliance: Reduce detection to investigation time from 24 hours to 1 hour (preview) (Updated) Communication Compliance: Reduce detection to investigation time from 24 hours to 1 hour (preview) N/A
MC365786 (Updated) Configuration Change in Name parameter for Exchange Online Configuration Change in Name parameter for Exchange Online (Updated) Configuration Change in Name parameter for Exchange Online 06/30/2022
MC376706 (Updated) Microsoft Project usage data in Microsoft Admin Center Microsoft Project usage data in Microsoft Admin Cente (Updated) Microsoft Project usage data in Microsoft Admin Cente N/A
MC378419 (Updated) Automatic groupings available in Teams for channel posts Automatic groupings available in Teams for channel posts (Updated) Automatic groupings available in Teams for channel posts N/A
MC379026 (Updated) New Yammer as only option for non-admin users New Yammer as only option for non-admin users (Updated) New Yammer as only option for non-admin users N/A
MC379407 (Updated) Exchange Online-Add, edit custom file types in Anti-malware policy Exchange Online-Add, edit custom file types in Anti-malware policy (Updated) Exchange Online-Add, edit custom file types in Anti-malware policy N/A
MC379408 (Updated) Exchange Online-Updates to the file type list in the common attachment filter Exchange Online-Updates to the file type list in the common attachment filte (Updated) Exchange Online-Updates to the file type list in the common attachment filte N/A
MC384329 (Updated) Multitasking Panel for Meetings on iPad Multitasking Panel for Meetings on iPad (Updated) Multitasking Panel for Meetings on iPad N/A
MC384778 (Updated) Microsoft 365 Admin Center: GroupID to be Hidden by Default in Microsoft 365 Active User Reports Microsoft 365 Admin Center: GroupID to be Hidden by Default in Microsoft 365 Active User Reports (Updated) Microsoft 365 Admin Center: GroupID to be Hidden by Default in Microsoft 365 Active User Reports N/A

CW23 New Office 365 Message Center items

MC ID MC Title MC Category MC Workload MC Major Change MC Action required by
MC386412 Flow.microsoft.com is moving to make.powerautomate.com Plan For Change Microsoft Power Automate False N/A
MC387038 Call control with bluetooth headsets and speakerphones Stay Informed Microsoft Teams False N/A
MC387036 Teams Meeting Poll New Question Type - Rating Stay Informed Microsoft Teams, Microsoft Forms False N/A
MC387035 Microsoft Purview: Additional classifiers for Communication Compliance (preview) Stay Informed Microsoft 365 suite False N/A
MC387034 Meeting Chat Bubbles on iOS Stay Informed Microsoft Teams False N/A
MC387229 Microsoft Purview compliance portal: eDiscovery (Premium) supports Teams reactions Stay Informed Microsoft 365 suite False N/A
MC387227 Communication Compliance - Gain context around ML model policy matches (preview) Stay Informed Microsoft 365 suite False N/A
MC387226 Communication Compliance: Expanded optical character recognition support (GA) Stay Informed Microsoft 365 suite False N/A
MC387224 Microsoft Defender for Office 365: Update to Quarantine notification default subject and review button Stay Informed Exchange Online False N/A
MC387220 Meeting Chat Bubbles on Android Stay Informed Microsoft Teams False N/A
MC387165 Ensuring a successful Windows quality update experience  Stay Informed Windows False N/A
MC387231 Update to the Microsoft Cloud Services Subprocessor List Stay Informed Microsoft 365 suite False N/A
MC387684 Upcoming feature release: Teams Button long press to Raise Hand during meeting Stay Informed Microsoft Teams False N/A
MC387683 Capture voice recordings with live speech-to-text in Office Mobile on iOS and Android Stay Informed Microsoft 365 Apps False N/A
MC387682 New opt-in setting for Microsoft Defender for Identity Stay Informed Microsoft 365 Defender False N/A
MC387641 Planner cards now on SharePoint team site activity feed Stay Informed SharePoint Online False N/A
MC387640 Dynamic Caller ID in Calls app for Call Queue Agents Stay Informed Microsoft Teams False N/A
MC387639 Microsoft Purview Information Protection: Maintain protection when creating PDFs (preview) Stay Informed Microsoft 365 suite False N/A
MC388227 Microsoft Secure Score is adding new improvement actions for Defender for Endpoint and Vulnerability Management Stay Informed Microsoft 365 Defender False N/A
MC388226 APP will soon be able to detect Android Enterprise dedicated devices in Azure AD shared mode and AOSP devices Plan For Change Microsoft Intune False N/A
MC387924 May 2022 Windows non-security preview "C" release available for all supported versions of Windows Stay Informed Windows False N/A
MC388234 What’s new in the Microsoft Intune Service Update for May 2022 Stay Informed Microsoft Intune False N/A
MC388232 Microsoft Purview Information Protection: Configure Display Colors for Sensitivity Labels (preview) Stay Informed Microsoft 365 suite False N/A
MC388228 Announcing option to automatically turn on Microsoft Purview Information Protection auto-labeling policy Stay Informed Microsoft 365 suite False N/A
MC388541 Microsoft Project trial for Microsoft 365 users Stay Informed Project for the web False N/A
MC388539 SharePoint: Updated Site Logo Management Stay Informed SharePoint Online False N/A
MC388526 Microsoft Secure Score is adding new improvement actions for Microsoft Defender for Identity Stay Informed Microsoft 365 Defender False N/A

Login to your account

Welcome Back, We Missed You!