2024 CW 09 Microsoft 365 Message Center changes

Figure 2: Review admin Override reason:

Figure 3: Undo Block sender:

Figure 4: Allow sender in Quarantine policy:

Figure 5: Block sender action eliminated from default Quarantine policies:

Figure 6: How to include or exclude messages from blocked sender in Quarantine notification:

Figure 7: Quarantined messages from blocked senders are excluded from Quarantine view by default

Figure 2: Review admin Override reason:

Figure 3: Undo Block sender:

Figure 4: Allow sender in Quarantine policy:

Figure 5: Block sender action eliminated from default Quarantine policies:

Figure 6: How to include or exclude messages from blocked sender in Quarantine notification:

Figure 7: Quarantined messages from blocked senders are excluded from Quarantine view by default

We urge you to switch to this new EAC experience as soon as you can, as the old EAC experience will be deprecated mid-2024.

We urge you to switch to this new EAC experience as soon as you can, as the old EAC experience will be retired mid-2024.

To ensure that these notifications successfully reach you, an email will now be sent automatically each time a new issue is posted.

If you do not want to receive these email notifications, you can adjust your email preferences by clicking the "Customize" button on the service health page.

This message is associated with Microsoft 365 Roadmap ID 103631

[When this will happen:]

Targeted Release: We will begin rolling out late July (previously mid-June) and expect to complete by mid-August.

Worldwide: We will begin rolling out early August (previously early July) and expect to complete by late April 2024 (previously mid-February).

To ensure that these notifications successfully reach you, an email will now be sent automatically each time a new issue is posted.

If you do not want to receive these email notifications, you can adjust your email preferences by clicking the "Customize" button on the service health page.

This message is associated with Microsoft 365 Roadmap ID 103631

[When this will happen:]

Targeted Release: We will begin rolling out late July (previously mid-June) and expect to complete by mid-August.

Worldwide: We will begin rolling out early August (previously early July) and expect to complete by late March 2024 (previously mid-February).

Note: These rollout timelines apply to customers in the following markets: United States, Canada, UK, Australia, New Zealand, South Africa, India, and Singapore. When the work is completed to send these emails in languages other than English, the list of countries will be expanded.

This message is associated with Microsoft 365 Roadmap ID 122550

[When this will happen:]

Targeted release: We will begin rolling this out in mid-October 2023 and expect to complete rollout by late October 2023 (now completed)

Standard release: We will begin rolling this out in mid-November 2023 and expect to complete rollout by late November 2023.

GCC: We will begin rolling this out in mid- November 2023 and expect to complete rollout by late November 2023.

GCC-H: We will begin rolling this out in early December 2023 and complete rollout by mid-February 2024 (previously late January).

DoD: We will begin rolling this out in early December 2023 and complete rollout by mid-February 2024 (previously late January).

This message is associated with Microsoft 365 Roadmap ID 122550

[When this will happen:]

Targeted release: We will begin rolling this out in mid-October 2023 and expect to complete rollout by late October 2023 (now completed)

Standard release: We will begin rolling this out in mid-November 2023 and expect to complete rollout by late November 2023.

GCC: We will begin rolling this out in mid- November 2023 and expect to complete rollout by late November 2023.

GCC-H: We will begin rolling this out in early December 2023 and complete rollout by mid-March 2024 (previously mid-February).

DoD: We will begin rolling this out in early December 2023 and complete rollout by mid-March 2024 (previously late mid-February).

This message is associated with Microsoft 365 Roadmap ID 124909

[When this will happen:]

We will begin rolling out in mid-July 2023 (previously late June) and expect to complete rollout by mid-February 2024 (previously mid-December).

This message is associated with Microsoft 365 Roadmap ID 124909

[When this will happen:]

We will begin rolling out in mid-July 2023 (previously late June) and expect to complete rollout by late July 2024 (previously mid-February).

[When this will happen:]

TAP will begin in Q2 of calendar 2024.

Eligible Microsoft Teams Android devices will initially receive a manual firmware update in Teams Admin Center so IT admins can manually verify the migration on select devices.

Eventually, the firmware update for migration will be scheduled as an automatic firmware update in Teams Admin Center. This automatic firmware update can be deferred for up to 90 days from first availability.

[When this will happen:]

A Preview program for select Microsoft Teams Android devices is targeted for Q2 of calendar year 2024. General release of the firmware update with the Android AOSP management stack will happen later in Q3 of calendar year 2024 for all eligible Microsoft Teams Android devices.

Eligible Microsoft Teams Android devices will initially receive a manual firmware update in Teams Admin Center so IT admins can manually verify the migration on their own schedule on select devices of their choosing.

Eventually, the firmware update for migration will be scheduled as an automatic firmware update in Teams Admin Center. This automatic firmware update can be deferred for up to 90 days from first availability based upon the admin configured stages in Teams Admin Center.

This message is associated with Microsoft 365 Roadmap ID 117587

[When this will happen:]

Preview: Rollout will begin in early January 2024 (previously mid-December) and is expected to be complete by late February 2024 (previously mid-December).

Standard: Rollout will begin in late February 2024 (previously mid-January) and is expected to complete by early March 2024 (previously late January).

This message is associated with Microsoft 365 Roadmap ID 117587

[When this will happen:]

Preview: Rollout will begin in early January 2024 (previously mid-December) and is expected to be complete by late February 2024 (previously mid-December).

Worldwide: Rollout will begin in late March 2024 (previously late February) and is expected to complete by mid-April 2024 (previously early March).

This message is associated with Microsoft 365 Roadmap ID 163598

[When this will happen:]

Rollout will begin in late October 2023 and is expected to be complete by mid-February 2024 (previously early November).

This message is associated with Microsoft 365 Roadmap ID 163598

[When this will happen:]

Rollout will begin in late October 2023 and is expected to be complete by mid-March 2024 (previously mid-February).

Changes to our web domain are currently not anticipated to impact our APIs. Should there be any changes in the future we will notify you.

This message is associated with Microsoft Roadmap ID 180352

[When this will happen:]

Web domain change: Rollout will begin in late March 2024 (previously early January) and is expected to be complete by early April 2024 (previously early February).

Email domain change: The email sender domain will not start in January 2024 as previously announced. We will send a new notice via message center with 30-days' notice before we start changing the email sender domain later in 2024.

Changes to our web domain are currently not anticipated to impact our APIs. Should there be any changes in the future we will notify you.

This message is associated with Microsoft Roadmap ID 180352

[When this will happen:]

Web domain change: Rollout will begin in late June 2024 (previously late March) and is expected to be complete by mid-July 2024 (previously early April).

Email domain change: The email sender domain will not start in January 2024 as previously announced. We will send a new notice via message center with 30-days' notice before we start changing the email sender domain later in 2024.

This message is associated with Microsoft 365 Roadmap ID 169881.

[When this will happen:]

Standard Release: We will begin rolling out mid-November and expect to complete it by mid-February 2024 (previously late January).

This message is associated with Microsoft 365 Roadmap ID 169881.

[When this will happen:]

We will begin rolling out mid-November and expect to complete it by mid-March 2024 (previously mid-February).

This message is associated with Microsoft 365 Roadmap ID 167211

[When this will happen:]

Targeted Release: We will begin rolling out mid-November and expect to complete by late November.

Worldwide: We will begin rolling out early December and expect to complete by mid-December.

GCC: We will begin rolling out early January and expect to complete by mid-January.

GCC High: We will begin rolling out mid-January and expect to complete by late January.

DoD: We will begin rolling out early February and expect to complete by mid-March 2024 (previously mid-February).

To make sure Microsoft Teams provides the best workflow experience for our users we are making it easier to configure workflows for chats. From the list of chats users will be able to go into the overflow menu for a specific chat (...) and select "Workflows". Here they will see a list of workflow templates specific to chats within Teams. Users can then configure these templates to their needs and deploy them to the chat.

This message is associated with Microsoft 365 Roadmap ID 180364

[When this will happen:]

Standard Release: We will begin rolling out mid-November and expect to complete by mid-February 2024 (previously late January).

To make sure Microsoft Teams provides the best workflow experience for our users we are making it easier to configure workflows for chats. From the list of chats users will be able to go into the overflow menu for a specific chat (...) and select "Workflows". Here they will see a list of workflow templates specific to chats within Teams. Users can then configure these templates to their needs and deploy them to the chat.

This message is associated with Microsoft 365 Roadmap ID 180364

[When this will happen:]

We will begin rolling out mid-November and expect to complete by mid-March 2024 (previously mid-February).

Currently, our team and channel creation processes have several steps and are focused on letting users create team at the top level, with channel creation as an option for each team.

We are making the team create experience simpler by default, but still giving users the advanced options of creating a team from a template or group and choosing the privacy/ sensitivity of the team if they want. To help users create channels within these teams, we are putting "create channel" option at the top. They will be able to host the channel into a default team or a team they select.

Users can now create the right collab space by choosing between team or channel. Overall, users can now set up the right teams or channels from the + button, without having to go to different places or follow multiple steps.

This change is associated with Microsoft 365 Roadmap ID: 163363 and 163364

[When this will happen:]

Preview: We will begin rolling out mid-November 2023.

Targeted Release: We will begin rolling out mid-January 2024.

Standard Release: We will begin rolling out early February 2024 and expect to complete by late February 2024.

Currently, our team and channel creation processes have several steps and are focused on letting users create team at the top level, with channel creation as an option for each team.

We are making the team create experience simpler by default, but still giving users the advanced options of creating a team from a template or group and choosing the privacy/ sensitivity of the team if they want. To help users create channels within these teams, we are putting "create channel" option at the top. They will be able to host the channel into a default team or a team they select.

Users can now create the right collab space by choosing between team or channel. Overall, users can now set up the right teams or channels from the + button, without having to go to different places or follow multiple steps.

This change is associated with Microsoft 365 Roadmap ID: 163363 and 163364

[When this will happen:]

Preview: We will begin rolling out mid-November 2023.

Targeted Release: We will begin rolling out mid-January 2024.

Worldwide: We will begin rolling out early February 2024 and expect to complete by late March 2024 (previously late February).

This message is associated with Microsoft 365 Roadmap ID 181621

[When this will happen:]

Standard Release: We will begin rolling out early December and expect to complete by mid-February 2024 (previously late January).

This message is associated with Microsoft 365 Roadmap ID 181621

[When this will happen:]

We will begin rolling out early December and expect to complete by mid-March 2024 (previously mid-February).

This message is associated with Microsoft 365 Roadmap ID 181794

The Remove functionality can be found under the ellipsis menu in the activity feed:

After an activity feed item is removed, the user is informed through a toast notification:

[When this will happen:]

Targeted Release: We will begin rolling out mid-December 2023 and expect to complete by mid-February 2024 (previously late January).

Standard Release: We will begin rolling out mid-February 2024 and expect to complete by late February 2024.

This message is associated with Microsoft 365 Roadmap ID 181794

The Remove functionality can be found under the ellipsis menu in the activity feed:

After an activity feed item is removed, the user is informed through a toast notification:

[When this will happen:]

Targeted Release: We will begin rolling out mid-December 2023 and expect to complete by mid-February 2024 (previously late January).

Worldwide, GCC, GCC High & DoD: We will begin rolling out mid-February 2024 and expect to complete by mid-March 2024 (previously late February).

The mobile experience for the Tasks app in Teams will soon be updated to make it easier to filter to a specific bucket or set of buckets so that you can focus on the tasks in your area. We expect this simple user experience change to provide greater focus and greater productivity, while maintaining the familiar look and feel throughout the Tasks app.

Note: This change is specific to the Tasks by Planner and To Do app in Teams mobile.

This message is associated with Microsoft 365 Roadmap ID 135561

[When this will happen:]

We will begin rollout in early December 2023 and complete by mid-February 2024 (previously late December).

The mobile experience for the Tasks app in Teams will soon be updated to make it easier to filter to a specific bucket or set of buckets so that you can focus on the tasks in your area. We expect this simple user experience change to provide greater focus and greater productivity, while maintaining the familiar look and feel throughout the Tasks app.

Note: This change is specific to the Tasks by Planner and To Do app in Teams mobile.

This message is associated with Microsoft 365 Roadmap ID 135561

[When this will happen:]

We will begin rollout in early December 2023 and complete by mid-March 2024 (previously mid-February).

Frontline workers often balance various personal commitments and specific work-time preferences. Through shifts, FLWs can establish availability preferences for calendar dates alongside recurring days. This feature streamlines shift assignments for frontline managers, who can seamlessly assign shifts by reviewing these availability preferences within the Shifts app.

This message is associated with Microsoft 365 Roadmap ID: 156952

[When this will happen:]

Standard Release: We will begin rolling out mid-January 2024 and expect to complete by mid-February 2024 (previously late January).

Frontline workers often balance various personal commitments and specific work-time preferences. Through shifts, FLWs can establish availability preferences for calendar dates alongside recurring days. This feature streamlines shift assignments for frontline managers, who can seamlessly assign shifts by reviewing these availability preferences within the Shifts app.

This message is associated with Microsoft 365 Roadmap ID: 156952

[When this will happen:]

Worldwide & GCC: We will begin rolling out mid-January 2024 and expect to complete by mid-March 2024 (previously mid-February).

IntelliFrame experiences availability on new Teams app for Desktop,

Expanding recognition support to cover scenarios such as meeting invite forwarding and Teams meeting nudge among others (Please See below for details)

IntelliFrame experiences from Edge cameras like Yealink Smartvision 60 are currently available on Teams Desktop platform. With this update, we want to announce the availability of IntelliFrame on New Teams app.

Recognition expansion: This update applies to both existing and new Teams desktop app. Previously recognition was only supported when an organizer invited the meeting room with Intelligent camera connected. With this update, we are able to support the following scenarios.

Meeting forward (both one time and recurring meetings)

Teams nudge (using Roster>add participant)

Join by meeting ID (Using MTR to join a meeting by ID)

Also, under "Recognition" feature, we heard our users and renamed unrecognized users from "Guest" to "Participant". Moving forward, with this update anyone who is unrecognized will see their name label as "Participant."

This message is associated with Microsoft 365 Roadmap ID 161427

[When this will happen:]

Targeted Release: We will begin rolling out early January 2024 and expect to complete by mid-January 2024.

Standard Release: We will begin rolling out mid-January 2024 and expect to complete by mid-February 2024 (previously late January).

IntelliFrame experiences availability on new Teams app for Desktop,

Expanding recognition support to cover scenarios such as meeting invite forwarding and Teams meeting nudge among others (Please See below for details)

IntelliFrame experiences from Edge cameras like Yealink Smartvision 60 are currently available on Teams Desktop platform. With this update, we want to announce the availability of IntelliFrame on New Teams app.

Recognition expansion: This update applies to both existing and new Teams desktop app. Previously recognition was only supported when an organizer invited the meeting room with Intelligent camera connected. With this update, we are able to support the following scenarios.

Meeting forward (both one time and recurring meetings)

Teams nudge (using Roster>add participant)

Join by meeting ID (Using MTR to join a meeting by ID)

Also, under "Recognition" feature, we heard our users and renamed unrecognized users from "Guest" to "Participant". Moving forward, with this update anyone who is unrecognized will see their name label as "Participant."

This message is associated with Microsoft 365 Roadmap ID 161427

[When this will happen:]

Targeted Release: We will begin rolling out early January 2024 and expect to complete by mid-January 2024.

Worldwide & GCC: We will begin rolling out mid-January 2024 and expect to complete by mid-March 2024 (previously mid-February).

Archiving channels will be available for Teams users. You, as a channel owner or administrator can archive a channel you own. By archiving the channel, it will not be available in your and channel members teams and channels list anymore and no more actions will be allowed on the channel like messaging, reacting, commenting, editing etc. In case, you want, you can unarchive the channel as well, by going to manage teams > channels. Team members can hoist the channel in their left rail even after archival.

This message is associated with Microsoft 365 Roadmap ID 123769

[When this will happen:]

Targeted Release: We will begin rolling out early February 2024 (previously early January) and expect to complete by mid-February 2024 (previously early January).

Standard Release: We will begin rolling out late February 2024 (previously mid-February) and expect to complete by mid-March 2024 (previously late February).

Archiving channels will be available for Teams users. You, as a channel owner or administrator can archive a channel you own. By archiving the channel, it will not be available in your and channel members teams and channels list anymore and no more actions will be allowed on the channel like messaging, reacting, commenting, editing etc. In case, you want, you can unarchive the channel as well, by going to manage teams > channels. Team members can hoist the channel in their left rail even after archival.

This message is associated with Microsoft 365 Roadmap ID 123769

[When this will happen:]

Targeted Release: We will begin rolling out late February 2024 (previously early February) and expect to complete by mid-March 2024 (previously mid-February).

Worldwide: We will begin rolling out mid-March 2024 (previously mid-February) and expect to complete by early April 2024 (previously late February).

Soon, admins can provide intent when submitting messages (email and Microsoft Teams), email attachments, or URLs to Microsoft.

Admins can convey whether they are submitting for a second opinion from Microsoft or they are submitting because a true malicious message was missed by Microsoft. With this change, Microsoft analysis of admin submitted messages (email and Microsoft Teams), URLs, and email attachments will be further streamlined and will result in more accurate analysis.

This message is associated with Microsoft 365 Roadmap ID 183907

[When this will happen:]

This change will start rolling out in mid-February 2024 (previously mid-December) and should be complete by late February 2024 (previously mid-January).

Soon, admins can provide intent when submitting messages (email and Microsoft Teams), email attachments, or URLs to Microsoft.

Admins can convey whether they are submitting for a second opinion from Microsoft or they are submitting because a true malicious message was missed by Microsoft. With this change, Microsoft analysis of admin submitted messages (email and Microsoft Teams), URLs, and email attachments will be further streamlined and will result in more accurate analysis.

This message is associated with Microsoft 365 Roadmap ID 183907

[When this will happen:]

This change will start rolling out in mid-February 2024 (previously mid-December) and should be complete by late March 2024 (previously late February).

For users to collaborate effectively, they need to set-up the right collaboration space. Channels being the main hub of collaboration, we made it easier for users to create channels. With the channel creation option elevated to the top, users can now create the appropriate collab space by picking between team or channel. They will be able to host the channel into a team of their choosing.

This message is associated with Microsoft 365 Roadmap ID: 163363

[When this will happen:]

Targeted Release: We will begin rolling out early January 2024 and expect to complete by mid-January 2024.

Standard Release: We will begin rolling out mid-February 2024 and expect to complete by late February 2024.

For users to collaborate effectively, they need to set-up the right collaboration space. Channels being the main hub of collaboration, we made it easier for users to create channels. With the channel creation option elevated to the top, users can now create the appropriate collab space by picking between team or channel. They will be able to host the channel into a team of their choosing.

This message is associated with Microsoft 365 Roadmap ID: 163363

[When this will happen:]

Targeted Release: We will begin rolling out early January 2024 and expect to complete by mid-January 2024.

Worldwide, GCC, GCC High and DoD: We will begin rolling out mid-February 2024 and expect to complete by late March 2024 (previously late February).

This message is associated with Microsoft 365 Roadmap ID 98328

[When this will happen:]

Standard Release: We will begin rolling out late January 2024 and expect to complete by mid-February 2024.

This message is associated with Microsoft 365 Roadmap ID 98328

[When this will happen:]

Standard Release: We will begin rolling out late January 2024 and expect to complete by mid-March 2024 (previously mid-February).

Targeted Release: We will begin rolling out by mid-January 2024 and expect to complete by late January 2024.

Standard Release: We will begin rolling out early February 2024 and expect to complete by mid-February 2024.

This message is associated with Microsoft 365 Roadmap ID 186571

[When this will happen:]

Targeted Release: We will begin rolling out by mid-January 2024 and expect to complete by late January 2024.

Worldwide, GCC, GCC High and DoD: We will begin rolling out early February 2024 and expect to complete by mid-March 2024 (previously mid-February).

Users can access this feature in 3 ways:

During a meeting, you can access the audio flyout and video flyout by clicking the split button with a downward arrow right next to 'camera' and 'microphone' in the meeting toolbar.

From both the audio and video flyouts, you can access audio settings and video settings, which open as panels on the right side of the calling window. You can access these settings by clicking 'more video options' and 'more audio options' at the bottom of the flyout to open the side panel.

Users can also access 'audio settings' and 'video effects and settings' by clicking the 'more' menu in the meeting toolbar:

Audio settings: “More” menu > Audio settings

Video effects and settings: “More” menu > “Video effects and settings”

This message is associated with Microsoft 365 Roadmap ID 187098

[When this will happen:]

Targeted Release: We will begin rolling out late January 2024 and expect to complete by mid-February 2024.

Standard Release: We will begin rolling out mid-February 2024 and expect to complete by late February 2024.

Users can access this feature in 3 ways:

During a meeting, you can access the audio flyout and video flyout by clicking the split button with a downward arrow right next to 'camera' and 'microphone' in the meeting toolbar.

From both the audio and video flyouts, you can access audio settings and video settings, which open as panels on the right side of the calling window. You can access these settings by clicking 'more video options' and 'more audio options' at the bottom of the flyout to open the side panel.

Users can also access 'audio settings' and 'video effects and settings' by clicking the 'more' menu in the meeting toolbar:

Audio settings: “More” menu > Audio settings

Video effects and settings: “More” menu > “Video effects and settings”

This message is associated with Microsoft 365 Roadmap ID 187098

[When this will happen:]

Targeted Release: We will begin rolling out late January 2024 and expect to complete by mid-February 2024.

Worldwide, GCC, GCC High & DoD: We will begin rolling out mid-February 2024 and expect to complete by mid-March 2024 (previously late February).

We are now removing any possibility of having 1:1 chat (between users from different MTO tenants) split across multiple threads. As part of this, users will no longer be able to send new messages in existing chat threads which use B2B identities of either party and they will be directed to the right single-thread.

Users will now see a richer profile for users from other MTO tenants - this includes information like profile picture, contact information, and org chart.

Users will now be able to perform a name-based search for users from other MTO tenants while adding them to a Shared channel.

Users from MTO tenants and conversations involving them will no longer be labeled as "External."

MTO group admins can now configure an optional label for each tenant that will be displayed alongside user's display name.

This message is associated with Microsoft 365 Roadmap ID 375631

[When this will happen:]

Targeted Release: We will begin rolling out mid-January 2024 and expect to complete by mid-February 2024.

Standard release is dependent on release of Microsoft Admin Center, and we will update this release schedule as appropriate.

We are now removing any possibility of having 1:1 chat (between users from different MTO tenants) split across multiple threads. As part of this, users will no longer be able to send new messages in existing chat threads which use B2B identities of either party and they will be directed to the right single-thread.

Users will now see a richer profile for users from other MTO tenants - this includes information like profile picture, contact information, and org chart.

Users will now be able to perform a name-based search for users from other MTO tenants while adding them to a Shared channel.

Users from MTO tenants and conversations involving them will no longer be labeled as "External."

MTO group admins can now configure an optional label for each tenant that will be displayed alongside user's display name.

This message is associated with Microsoft 365 Roadmap ID 375631

[When this will happen:]

Targeted Release: We will begin rolling out mid-January 2024 and expect to complete by mid-March 2024 (previously mid-February).

Worldwide, GCC, GCC High and DoD: dependent on release of Microsoft Admin Center, and we will update this release schedule as appropriate.

[When this will happen:]

Targeted Release: We will begin rolling out mid-January 2024 and expect to complete by late January 2024.

Standard Release: We will begin rolling out early February 2024 and expect to complete by mid-February 2024.

[When this will happen:]

Targeted Release: We will begin rolling out mid-January 2024 and expect to complete by late January 2024.

Worldwide, GCC, GCC High & DoD: We will begin rolling out early February 2024 and expect to complete by mid-March 2024 (previously mid-February).

Search external users by name and establish 1:1 or group chats with them.

View a company curated profile that includes information like a user's location, job role, or business unit and even assign an organization manager for these external partners.

In addition to these end user improvements, IT admins can continue to use all compliance and security features available with Teams Connect chat along with enhancements like restricting external chat to the list of users added via phone numbers.

This message is associated with Microsoft 365 Roadmap ID 119789

[When this will happen:]

Targeted Release: We will begin rolling out in early February 2024 and expect to complete by mid-February 2024.

Standard Release: We will begin rolling out mid-February 2024 and expect to complete by late February 2024.

Search external users by name and establish 1:1 or group chats with them.

View a company curated profile that includes information like a user's location, job role, or business unit and even assign an organization manager for these external partners.

In addition to these end user improvements, IT admins can continue to use all compliance and security features available with Teams Connect chat along with enhancements like restricting external chat to the list of users added via phone numbers.

This message is associated with Microsoft 365 Roadmap ID 119789

[When this will happen:]

Targeted Release: We will begin rolling out in early February 2024 and expect to complete by mid-February 2024.

Worldwide: We will begin rolling out mid-February 2024 and expect to complete by mid-March 2024 (previously late February).

This message is associated with Microsoft 365 Roadmap ID 373555

[When this will happen:]

Targeted Release: We will begin rolling out mid-February 2024 and expect to complete by late February 2024.

Standard Release: We will begin rolling out late February 2024 and expect to complete by late March 2024.

This message is associated with Microsoft 365 Roadmap ID 373555

[When this will happen:]

Targeted Release: We will begin rolling out late February 2024 (previously mid-February) and expect to complete by early March 2024 (previously late February).

Worldwide, GCC, GCC High & DoD: We will begin rolling out early March 2024 (previously late February) and expect to complete by early April 2024 (previously late March).

To control your call mic from the taskbar, do the following:

Select the mic icon on your taskbar or press Windows logo key + Alt + K to mute or unmute your microphone while using a calling app.

-OR- Click the volume icon in the hardware indicator for volume in Windows taskbar.

This message is associated with Microsoft 365 Roadmap ID 191528

[When this will happen:]

Targeted release: We will begin rolling out mid-March 2024 (previously mid-February) and expect to complete by late March 2024 (previously late February).

Standard Release: We will begin rolling out early April 2024 (previously early March) and expect to complete by late April 2024 (previously mid-April).

To control your call mic from the taskbar, do the following:

Select the mic icon on your taskbar or press Windows logo key + Alt + K to mute or unmute your microphone while using a calling app.

-OR- Click the volume icon in the hardware indicator for volume in Windows taskbar.

This message is associated with Microsoft 365 Roadmap ID 191528

[When this will happen:]

Targeted release: We will begin rolling out mid-April 2024 (previously mid-March) and expect to complete by late April 2024 (previously late March).

Worldwide, GCC, GCC High & DoD: We will begin rolling out early May 2024 (previously early April) and expect to complete by late May 2024 (previously late April).

This message is associated with Microsoft 365 Roadmap ID 376853

[When this will happen:]

Targeted Release: We will begin rolling out mid-March 2024 (previously mid-February) and expect to complete by late March 2024 (previously late February).

Standard Release and GCC: We will begin rolling out late March 2024 (previously late February) and expect to complete by late April 2024 (previously early March).

This message is associated with Microsoft 365 Roadmap ID 376853

[When this will happen:]

Targeted Release: We will begin rolling out mid-March 2024 (previously mid-February) and expect to complete by early April 2024 (previously late February).

Worldwide and GCC: We will begin rolling out early April 2024 (previously late February) and expect to complete by early May 2024 (previously early March).

This message is associated with Microsoft 365 Roadmap ID 380185.

[When this will happen:]

Standard Release, GCC, and GCC High: We will begin rolling out mid-Feb 2024 and expect to complete by mid-March 2024.

DoD: We will begin rolling out mid-March 2024 and expect to complete by mid-April 2024.

This message is associated with Microsoft 365 Roadmap ID 380185.

[When this will happen:]

Standard Release, GCC, and GCC High: We will begin rolling out late March 2024 (previously mid-February) and expect to complete by late April 2024 (previously mid-March).

DoD: We will begin rolling out late April 2024 (previously mid-March) and expect to complete by mid-May 2024 (previously mid-April).

This message is associated with Microsoft 365 Roadmap ID 380186.

[When this will happen:]

Standard Release: We will begin rolling out mid-February 2024 and expect to complete by mid-March 2024.

This message is associated with Microsoft 365 Roadmap ID 380186.

[When this will happen:]

Worldwide: We will begin rolling out late March 2024 (previously mid-February) and expect to complete by late April 2024 (previously mid-March).

Your frontline can quickly and easily reach the right groups of people. Because the tags are automatically created based on your mapped attribute values, team owners do not have to manually create and assign tags or manage them locally.

This message is associated with Microsoft 365 Roadmap ID 365845

[When this will happen:]

Targeted release: We will begin rolling out mid-February 2024 and expect to complete by late February 2024.

Standard Release: We will begin rolling out late February 2024 and expect to complete by late March 2024.

Your frontline can quickly and easily reach the right groups of people. Because the tags are automatically created based on your mapped attribute values, team owners do not have to manually create and assign tags or manage them locally.

This message is associated with Microsoft 365 Roadmap ID 365845

[When this will happen:]

Targeted release: We will begin rolling out late February 2024 (previously mid-February) and expect to complete by early March 2024 (previously late February).

Worldwide: We will begin rolling out early March 2024 (previously late February) and expect to complete by late April 2024 (previously late March).

A new PowerShell command, "DelayDenyAddAndCustomizePagesEnforcement", has been introduced. This command is available in the SharePoint Online Management Shell version 16.0.24524.12000, or above which allows delay of the change to custom script set on the Tenant until May 2024.

* False (default) - for site collections where administrators enabled the ability to add custom script, SharePoint will revoke that ability within 24 hours from the last time this setting was changed.

* True - All changes performed by administrators to custom script settings are preserved. When the value is set to true, a banner shows in the active sites list of the SharePoint admin center informing that changes to custom scripts are permanent.

Set-SPOTenant DelayDenyAddAndCustomizePagesEnforcement $True

Please be aware that the new PowerShell command will only be accessible until May 2024. Post that period, on SharePoint sites if administrators wish to continue using features that are only available when unmanaged custom scripts are permitted to run, they will need to re-enable the running of custom scripts every 24 hours. This option does not impact existing custom scripts.

The NoScriptSite setting will be configured to True for all existing SharePoint sites and OneDrive sites except for below mentioned sites templates.

BLANKINTERNETCONTAINER#0 = Classic Publishing Portal site

CMSPUBLISHING#0 = Publishing Site

BLANKINTERNET#0 = Publishing Site

GROUP#0 = Team site

APPCATALOG#0 = App Catalog

CSPCONTAINER#0 = CSP Container

The execution of existing scripts in OneDrive and SharePoint sites will remain unaffected.

There will not be an option to enable custom script on OneDrive sites once the delay set using DelayDenyAddAndCustomizePagesEnforcement ends in May 2024.

Customers will retain the ability to permit the execution of custom scripts on specific SharePoint sites using the Set-SPOSite <SiteURL> -DenyAddAndCustomizePages PowerShell command or from the Active sites page in the SharePoint Admin Center.

Any modifications made to a site will be automatically reverted to False status within 24 hours, unless the new PowerShell command “DelayDenyAddAndCustomizePagesEnforcement” is used prior to May 2024. After May, the 24 hour reversion will occur regardless of this setting.

[When this will happen:]

The Custom Script setting from SharePoint admin center will be removed in March 2024.

The new PowerShell command will be available in March 2024.

A new PowerShell command, "DelayDenyAddAndCustomizePagesEnforcement", has been introduced. This command is available in the SharePoint Online Management Shell version 16.0.24524.12000, or above which allows delay of the change to custom script set on the Tenant until May 2024.

Note: that while this cmdlet is available in the latest management shell , running the cmdlet will result in an error (The requested operation is part of an experimental feature that is not supported in the current environment) until March when the settings are shipped.

* False (default) - for site collections where administrators enabled the ability to add custom script, SharePoint will revoke that ability within 24 hours from the last time this setting was changed.

* True - All changes performed by administrators to custom script settings are preserved. When the value is set to true, a banner shows in the active sites list of the SharePoint admin center informing that changes to custom scripts are permanent.

Set-SPOTenant DelayDenyAddAndCustomizePagesEnforcement $True

Please be aware that the new PowerShell command will only be accessible until May 2024. Post that period, on SharePoint sites if administrators wish to continue using features that are only available when unmanaged custom scripts are permitted to run, they will need to re-enable the running of custom scripts every 24 hours. This option does not impact existing custom scripts.

The NoScriptSite setting will be configured to True for all existing SharePoint sites and OneDrive sites except for below mentioned sites templates.

BLANKINTERNETCONTAINER#0 = Classic Publishing Portal site

CMSPUBLISHING#0 = Publishing Site

BLANKINTERNET#0 = Publishing Site

GROUP#0 = Team site

APPCATALOG#0 = App Catalog

CSPCONTAINER#0 = CSP Container

The execution of existing scripts in OneDrive and SharePoint sites will remain unaffected.

There will not be an option to enable custom script on OneDrive sites once the delay set using DelayDenyAddAndCustomizePagesEnforcement ends in May 2024.

Customers will retain the ability to permit the execution of custom scripts on specific SharePoint sites using the Set-SPOSite <SiteURL> -DenyAddAndCustomizePages PowerShell command or from the Active sites page in the SharePoint Admin Center.

Any modifications made to a site will be automatically reverted to False status within 24 hours, unless the new PowerShell command “DelayDenyAddAndCustomizePagesEnforcement” is used prior to May 2024. After May, the 24 hour reversion will occur regardless of this setting.

[When this will happen:]

The Custom Script setting from SharePoint admin center will be removed in March 2024.

The new PowerShell command will be available in March 2024.

Standard Release: We will begin rolling out late February 2024 and expect to complete by early March 2024.

[When this will happen:]

Standard Release: We will begin rolling out late February 2024 and expect to complete by early March 2024.

Standard Release (if applicable): We will begin rolling out mid-March 2024 and expect to complete by mid-April 2024.

We will communicate via Message center when we are ready to proceed.

OrganizationalBrandingOnWorkProfileUIEnabled

OrganizationLogoOverlayOnAppIconEnabled

This message is associated with Microsoft 365 Roadmap ID 383013

[When this will happen:]

Worldwide: We will begin rolling out no sooner than late March 2024 with Microsoft Edge version 123. Rollout is expected to complete by the end of March 2024.

OrganizationalBrandingOnWorkProfileUIEnabled

OrganizationLogoOverlayOnAppIconEnabled

This message is associated with Microsoft 365 Roadmap ID 383013

[When this will happen:]

Worldwide: We will begin rolling out no sooner than late March 2024 with Microsoft Edge version 123. Rollout is expected to complete by the end of March 2024.

(Microsoft Admin Center for Viva Connections highlighting where admins can find site URL.)

https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=176677

(Microsoft Admin Center for Viva Connections highlighting where admins can find site URL.)

Resources:

What's new with Viva Connections: Resources update!

Overview: Viva Connections | Microsoft Learn

Customize and edit the Viva Connections home experience | Microsoft Learn

https://learn.microsoft.com/viva/connections/edit-viva-home

https://learn.microsoft.com/viva/connections/viva-connections-overview

https://techcommunity.microsoft.com/t5/viva-connections-blog/what-s-new-with-viva-connections-resources-update/ba-p/3969373

https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=176677