Microsoft Roadmap, messagecenter en blogs updates van 09-11-2024

Updated November 7, 2024: We have updated the rollout timeline below. Thank you for your patience.

Soon, on Windows and macOS devices running the OneDrive sync app, we will enable a new feature called “Offline mode” that will allow you to continue working with the OneDrive web app in your browser, OneDrive PWA (Progressive Web App) or Microsoft Teams even when you are offline. This feature will be on by default and will give your users the ability to view, rename, move, copy their files, and create new folders when offline. Users will be able to open their files that are available offline on users’ device in a native app directly from inside OneDrive on the web. All of the metadata changes users make offline to their files in the browser will be automatically synced back to OneDrive when Internet connection is restored, and users can resolve conflicts, if there are any. As an administrator, you’ll be able to control various aspects of Offline mode using the Group Policies outlined in here.

When this feature becomes enabled for users in your organization and the user then visits OneDrive for web, Offline mode will be set up for the first time. A copy of user’s file metadata that powers OneDrive for web is securely stored locally on user’s device. These data on user’s device are only available and accessible by that user. If someone else were to sign in on your device, these local data on the device wouldn’t be available to them.

A secure local web server on user’s device will handle the operations that users perform on their files in OneDrive for web, such as viewing, sorting, renaming, moving, and copying where traditionally these operations would need to be handled by the OneDrive cloud service. This allows to eliminate network as the bottleneck when loading and working with OneDrive for web resulting in fast and smooth interactions with users’ files like loading your files and folders, sorting, renaming, moving, renaming, and more. And all of these operations will continue to work even when users are offline, lose internet connection, or run into a service disruption.

• OneDrive Offline mode lets you work on OneDrive when offline in the browser, OneDrive PWA (Progressive Web App) and in Microsoft Teams, improves performance on all kinds of networks, and helps alleviate throttling related to working with large file collections.
• OneDrive Offline mode is currently supported on Windows devices (Windows 10 or later) and macOS devices (macOS 12 Monterey or later) that have the OneDrive sync app installed and on Chromium-based browsers (Microsoft Edge, Google Chrome)
  
• Offline mode will be on by default for user’s OneDrive on the web and both users and administrators will have the option to disable Offline mode for their OneDrive.
  
• Offline mode is a per-device setting (configured separately for every device users use to access OneDrive on the web.
  
• The data is securely stored in a local database under the user’s profile directory and requests are handled through a secure localhost HTTP server. Offline mode is powered by a separate background process (Microsoft.SharePoint.exe).
  
• When Offline mode is on, users will see a new icon in the top navigation bar in OneDrive on the web.
  

This message is associated with Microsoft 365 Roadmap ID 168618

[When this will happen:]

Worldwide: We will begin gradually rolling out in late February 2024 (previously mid-February) and expect to complete in late November 2024 (previously late October).

[How this will affect your organization]

When this feature becomes enabled for users in your organization and the user then visits OneDrive for web, Offline mode will be set up for the first time. A copy of user’s file metadata that powers OneDrive for web will be downloaded and securely stored locally on user’s device. The actual contents of users’ files will not be downloaded. After Offline mode is set up, only changes to users’ file metadata will result in upload or download activity over the network. Users can continue working with OneDrive on the web as before and they can choose to turn off Offline mode if they desire to do so. As an administrator, you’ll be able to control various aspects of Offline mode using the Group Policies.

[What you need to do to prepare]

Evaluate the new functionality and available controls as outlined in the help article, prepare your users on how to take advantage of this new functionality. Leverage the group policies provided to control how this feature gets enabled in your organization.

More information:

• Help article.
• Admin controls.
  
  

Updated November 7, 2024: We have updated the rollout timeline below. Thank you for your patience.

Coming soon to general availability, Microsoft Purview Communication Compliance will release a feature that empowers users to report policy-violating posts and comments in Viva Engage:

This message is associated with Microsoft 365 Roadmap ID 144596

[When this will happen:]

Rollout will begin in mid-December 2023 and is expected to be complete by late June 2025 (previously late October). 

[How this will affect your organization:]

Microsoft Viva Engage users are empowered to report inappropriate or concerning posts and comments violating customers’ organizational policies within Viva Engage Team conversations. These reported posts are then submitted to a Communication Compliance policy for customers’ designated investigators with the appropriate role-based access control permissions to review and take action if deemed necessary.

[What you need to do to prepare:]

Microsoft Purview Communication Compliance provides the tools to help organizations detect business conduct and regulatory compliance violations (e.g. SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to help ensure user-level privacy. 

To use this feature, please enable Viva Engage conversation reporting. Reported conversations will automatically route to Communication Compliance if a supported license is present in the tenant.

You can access the Communication Compliance solution in the   Microsoft Purview compliance portal.

Learn more:

• Learn about Communication Compliance.
• Create and manage communication compliance policies | Microsoft Learn
• Report a Viva Engage conversation | Microsoft Learn

Updated November 6, 2024: We have updated the rollout timeline below. Thank you for your patience.

Updated May 17, 2024: We have updated the content below to clarify the experience for EDU and FLW licensed users. Thank you for your patience.

Coming soon in Microsoft Teams: A new way to join teams and channels. This message applies to new Teams for the web and Teams for desktop. It does not apply to Teams for iOS or Android.

This message is associated with Microsoft 365 Roadmap ID 381734.

[When this will happen:]

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

General Availability (Worldwide): We will begin rolling out mid-September (previously mid-July) 2024 and expect to complete by late September (previously late July) 2024.

General Availability (GCC): We will begin rolling out late September (previously late July) 2024 and expect to complete by early October (previously late July) 2024.

General Availability (GCC High, DoD): We will begin rolling out early October (previously early August) 2024 and expect to complete by late November (previously late October) 2024.

[How this will affect your organization:]

Before this rollout, a team owner could mark a standard channel as Show for members while creating the channel or later from the team management page. These channels appeared automatically in the teams and channels list on the left side of the screen for all team members.

After this rollout:

• A team owner will be able to recommend channels for team members to join. This functionality replaces Show for members.
• When joining a new team, team members will see only the General channel. On the team onboarding page, additional channels may be tagged as Recommended by the team owner. Members can review channel details and opt into channels of interest. This rollout is designed to help team members join the most relevant channels, for a more streamlined experience in Teams.

The view from the Activity stream: A team owner adds a user to team (called Cross team collaboration) and recommends specific channels (Feature crew, General) for the user to show in the teams and channels list:

The view from the teams and channels list: General is the only channel shown when a team owner adds a user to team (called Cross team collaboration) and recommends additional channels (Feature crew, General) for the user to show in the teams and channels list:

Note: Users with EDU and FLW licenses will continue to see “owner recommended” channels in their teams and channels list automatically.  

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate.

We will update this comm before rollout with revised documentation.

Updated November 6, 2024: We have updated the rollout timeline below. Thank you for your patience.

In Microsoft Teams, users will be able to add their own custom emojis and reactions by uploading an image or GIF file, and their emojis and reactions will be accessible to all users in the tenant alongside the standard Teams emojis and reactions. Up to 5,000 custom emojis can be added per tenant.

This message is associated with Microsoft 365 Roadmap ID 80659.

[When this will happen:]

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

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

GCC: We will begin rolling out late September 2024 (previously mid-July) and expect to complete by early October 2024 (previously late July).

GCC High: We will begin rolling out early October 2024 (previously early August) and expect to complete by mid-October 2024 (previously late August).

DoD: We will begin rolling out mid-October 2024 (previously early August) and expect to complete by late January 2025 (previously late October).

[How this will affect your organization:]

This new custom emojis and reactions feature will be turned on by default. Users in the tenant will be able to upload emojis that are visible to the whole tenant. You can pre-emptively turn this feature off or restrict users who can create new emojis via the Teams Admin Center controls described below.

How do I use this feature?

Custom emojis and reactions will be found in the emoji and reaction menus in the Custom category. Users with upload abilities can add new content through the plus (+) button. Users with delete abilities can right-click any custom emoji to delete. Please note that deleted emojis may take up to 24 hours to reflect for all users in the tenant. Deleted emojis may take up to 24 hours to reflect for other users.

How do I manage this feature?

This feature can be managed through the Teams Admin Center. Admins will have access to the following controls:

• Turn the feature on/off for the whole tenant via the Messaging Settings page (on by default).
• Set which users can create new emojis via the Messaging Policy groups (on for all users by default).
• Set which users can delete emojis via the Messaging Policy groups (off for all users except admins by default).

The Teams Admin Center controls will be made available in early June. We recommend adjusting your settings as needed prior to the Targeted and Worldwide Releases in late June 2024 to ensure that they are in place when the feature rolls out.

[What you need to do to prepare:]

This feature is on by default. If you would like to turn the feature off, please use the provided setting in the Messaging Settings page:

Messaging Settings

This feature allows all users to create new emojis by default and only allows admins to delete emojis by default. If you would like to adjust emoji creation and deletion permissions, please make the appropriate changes through the Messaging Policy groups:

Emoji Creation Setting (enabled for all users by default)

Emoji Deletion Setting (only enabled for admins by default)

Additional feature capabilities:

View custom emojis in the emoji menu

Press the plus (+) menu to select an image to upload

Set a name for your emoji

Right-click on an emoji to delete or to see the creator

Updated November 7, 2024: We have updated the rollout timeline below. Thank you for your patience.

In Microsoft Teams, a new feature enhances the meeting view that is shown to attendees while the main meeting window is minimized.

When participants in a meeting minimize the main meeting window, they can multitask without losing sight of the meeting or missing important information by monitoring activity in a smaller meeting view window.

This view switcher feature update allows users to expand the default active speaker view of the meeting to an extended large gallery view. This view allows users to see up to 4 meeting participants, including reactions, raised hands, and a Me Video tile.

This expanded view can be toggled via a new UI control.

This message is associated with Microsoft 365 Roadmap ID 398449

[When this will happen:]

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

General Availability (Worldwide, GCC, GCC High, and DoD): We will begin rolling out mid-August 2024 (previously mid-July) and expect to complete by late November 2024 (previously late October).

[How this will affect your organization:]

When multitasking with the main meeting window minimized, meeting participants will now be able to better keep track of the meeting activity by using an extended meeting view window. 

[What you need to do to prepare:]

This feature is available by default. No action is needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.

Updated November 7, 2024: We have updated the rollout timeline below. Thank you for your patience.

To help increase productivity while working online, web links from Azure Active Directory (AAD) accounts and Microsoft (MSA) accounts in the new Outlook for Windows app will open in Microsoft Edge in a single view showing the opened link side-by-side with the email it came from.

We’re adding this to the new Outlook for windows to have a consistent experience across our applications. If you have previously managed this change for the classic Outlook for Windows (MC545904, MC548092, MC541626) or for Teams (MC669480), your configuration will also apply to the new Outlook for Windows. If you wish to maintain this configuration across all three apps, no action is required.

Note: This does not change the default browser setting in Windows.

[When will this affect your organization:]

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

[How this will affect your organization:]

Web links from emails in the new Outlook for Windows app will open side-by-side with the email in Microsoft Edge so users can easily reference the link and email without switching back and forth between apps. Links will open in Microsoft Edge even if it is not the system default browser in Windows.

• Only links set to open via a web browser are affected. Links that are set to open in a client app or within Outlook itself will continue to do so.
• This initial release to the new Outlook for Windows application will only enable links reading pane’s message body content
• User experiences will vary by policy configuration; please see the next section.
• Web links from all accounts in the Outlook for Windows app will open in Microsoft Edge.

[What you need to do to prepare:]

To manage this change, you will need to configure the Choose which browser opens web links policy, which is available today, using the Cloud Policy service for Microsoft 365 (formerly the Office Cloud Policy Service) and Administrative Templates for Microsoft 365 Apps.

• To open web links from the Outlook for Windows app using the system default browser (current default behavior): Enable the policy and select System default browser from the policy options.
  • Users will not be able to disable or change this setting.
• To open web links from the Outlook for Windows app using Microsoft Edge (future default behavior): Enable the policy and select Microsoft Edge from the policy options.
  • Users will not be able to disable or change this setting.
  • Users will receive a notification of this change on the first occurrence.
• To allow users to manage the change: Disable the policy or leave the policy unconfigured. Please note that the future default behavior for web links will be to open in Microsoft Edge.
  • Users will see a notification informing them of this change on the first occurrence. This notification provides users with the option to accept the change/learn more, or to disable the change.
  • The user’s selection will also apply to the experience in the classic Outlook for Windows and Teams.
  • Users may manage this setting at any time in the new Outlook for Windows app via Settings > General > Files and links > Open hyperlinks from Outlook in.
  • If there is an existing user preference set in the classic Outlook for Windows, the new Outlook for Windows will respect it. If the user only sets a preference to use the system default browser in Teams, the new Outlook for Windows will open the links in Microsoft Edge informing them of this change on the first occurrence and users can accept the change/learn more, or to disable the change.

If your organization uses a Microsoft 365 for business plan, your users will need to manage this change individually through the Outlook settings menu: Settings > General > Files and links > Open hyperlinks from Outlook in.

Example of the user notification experience

Read more about how we’re improving the experience between Microsoft 365 and Microsoft Edge with this feature in: Web links from Outlook and Teams open in Microsoft Edge in side-by-side view – Outlook | Microsoft Learn.

Updated November 6, 2024: We have updated the rollout timeline below. Thank you for your patience.

The Resources section on Microsoft Viva Connections mobile will show content from the recently revamped Resources section on Viva Connections desktop. The Resources section in Viva Connections is comprised of navigational links. If these links are created via in-app editing in Viva Connections, they will propagate to the Resources section in mobile as well. If no links have been added via in-app editing and Global Navigation is configured on the Home site, the Resources section on mobile will continue to show the navigational links from Global Navigation.

This message is associated with Microsoft 365 Roadmap ID 388369

[When this will happen:] 

General Availability (Worldwide): We will begin rolling out late August 2024 (previously mid-July) and expect to complete by mid-December 2024 (previously mid-November).

[How this will affect your organization:]

Navigational links created via in-app editing in the Viva Connections Resources section will now be consistent across endpoints.

For more information, visit Viva Connections resources.

This feature is available by default. 

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Updated November 6, 2024: We have updated the rollout timeline below. Thank you for your patience.

Note: Users with EDU licenses assigned will not receive this change.

Coming soon: Microsoft Teams will automatically detect and hide inactive channels you have not interacted with recently. You can review the list of channels and unhide some or all of them. You can opt out of automatic hiding from Teams Settings or initiate the hiding process on demand. This message applies to Microsoft Teams for Desktop, web, and Mac.

This message is associated with Microsoft 365 Roadmap ID 325780.

[When this will happen:]

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

General Availability (Worldwide): We will begin rolling out mid-August 2024 and expect to complete by mid-September 2024.

General Availability (GCC): We will begin rolling out late September 2024 and expect to complete by early October 2024.

General Availability (GCC High): We will begin rolling out early October 2024 and expect to complete by mid-October 2024.

General Availability (DoD): We will begin rolling out late October 2024 and expect to complete by late November 2024 (previously late October).

[How this will affect your organization:]

Before this rollout: Users had to manually hide inactive channels.

After this rollout: Teams will hide channels that have been inactive and notify the user with the message, “We’re hiding some inactive channels for you.” The user can select View changes to see the details (second screenshot):

The user can keep the channels hidden or show them again:

To initiate or stop channel hiding, go to Teams > Settings > Chats and channels > Hide inactive channels:

This feature is on by default and all Teams users on the affected platforms will have access to it.

[What you need to do to prepare:]

Admins need to be aware of this feature, but no additional action is needed. This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate.

Updated November 7, 2024: We have updated the images and rollout timeline below. Thank you for your patience.

As communicated in MC816207 Microsoft Forms now supports live data sync to Microsoft Excel with more functionality (July 2024), Microsoft Forms is introducing a new data sync solution with higher reliability to sync Forms response data to Microsoft Excel for the web. Before this rollout. Forms supported an older version of live data sync to Excel. The older version of live data sync will be replaced by the newer solution on January 13, 2025. This message describes the support that we will provide for migrating from the older solution to the newer solution. 

This message is associated with Microsoft 365Roadmap ID 410988.

[When this will happen:]

General Availability (Worldwide): Support for migrating the older data sync to the new solution will begin rolling out in late October 2024 (previously early October), and we expect to complete by late November 2024 (previously early October). 

[How this will affect your organization:]

Users who rely on the older version to sync data from Forms to Excel will need to manually update the data sync to the new solution before January 13, 2025 (previously October 20, 2024). After this date, existing Excel files with the older data sync will be retained but will no longer receive automatic data updates from Forms.

The older version of the data sync exists in two types of Forms:  

• Forms created from Microsoft OneDrive and Excel for the web
• Group forms created with SharePoint Online, Microsoft Teams, and Microsoft 365 Groups.

For these two types of Forms, we will provide this support to migrate to the new solution:

• Users who own Forms with the older version of the data sync will get notifications through email, Forms, and Excel for the web.
• In Forms, users will be able to recreate the data sync with the new solution. The data sync will be created to the same table in the existing workbook as the older data sync. The new worksheet will be connected to the latest data from Forms.
• After the older solution is retired, the user can still recreate a new data sync to the Excel workbook.

For workflows that connect to Excel data from Forms responses (such as Power Automate workflows), users will need to update the workflow to the Forms connector for new response updates. Learn more: Create an automated workflow for Microsoft Forms – Microsoft Support

Note: The new data sync can only be triggered in Excel for the web. If users want to receive new Forms response data in the Excel desktop app, open the file in Excel for the web, and then wait for the desktop app file to sync from the web file. (Support for other versions of Excel is in progress.)

The new data sync solution will be on by default and available to all Forms and Excel for the web customers. 

Notification in Forms to update workbook to continue syncing with Forms:

Notification in Excel for the web to update the data sync to new solution:

Excel workbook is successfully updated to new solution:

[What you need to do to prepare:]

• Send a notification to impacted users and groups to migrate their data syncs to new solution.
• Share the migration solution if users report they cannot get Forms data updated in Excel.
• Learn more: Introducing Forms data sync to Excel – Microsoft Community Hub

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation.

Before rollout, we will update this post with revised documentation.


Updated November 7, 2024: We have updated the rollout timeline below. Thank you for your patience.

Starting in early September 2024, customers will see a new setting in the Microsoft Viva Engage admin center to mute users across their networks. Muting a user removes new posts from that user from the Home feed, Storylines feed, and all email digests.

This message is associated with Microsoft 365 Roadmap ID 396168.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out early September 2024 and expect to complete by mid-November 2024 (previously late October).

[How this will affect your organization:]

Network, Engage, and Global admins will be able to add or remove a user from mute for network status. The feature can be found in the Engage admin center under the Governance and Compliance tab. All admin activity related to muting users for the network is captured in the user audit log for Engage.

While muted, new ThreadStarters from a user cannot show in discovery surfaces, including the Home feed, Storylines feed, and email digests. Comments and replies from a muted user can show in discovery surfaces.

Muting a user does not affect visibility of ThreadStarters, comments, or replies in community feeds. Users and their content remain visible through search.

Muted users will not see any indication they’ve been muted. Admins can only see who is muted within the admin center. Users do not receive a notification when added or removed from mute status. Customers own all internal communication around the use of the feature.

Admins can mute any user in their network, including guest users. Muting applies per user per network. Up to 1,000 users can be muted simultaneously per network.

This new feature is available by default.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Please review the available documentation on Microsoft Support and Microsoft Learn, which will be available publicly after general availability rollout begins in September 2024: Reduce visibility of a user’s posts in Viva Engage (Private Preview) | Microsoft Learn

Updated November 6, 2024: We have updated the content. Thank you for your patience.

Starting February 3 (previously December 1), we’re going to start gradually dropping messages that have multiple From addresses (also known as P2 From headers) without a Sender header from being sent via Exchange Online.

If we see significant traffic exhibiting multiple From addresses (P2 From headers) without a Sender header in your tenant in the month of September, we will send you a Message Center Post by October 15th alerting you and providing some sample message IDs.

We are doing this to comply with RFC 5322 (https://www.rfc-editor.org/rfc/rfc5322#section-3.6.2) which mandates the Sender header to be present and contain a single address if the From header has more than one address. Noncompliance with this could be exploited by attackers, allowing them to impersonate a sender address by misleading the client into using the From header to determine the sender instead of the Sender header.

[When this will happen:]

February 3, 2025 (previously December 1st)

We are delaying the rollout start date from December to February 3rd 2025 in order to provide more time to customers for investigating messages exhibiting multiple P2 From Addresses without a Sender Address.

Most of the traffic exhibiting multiple P2 From Addresses without a Sender Address will be inbound spam destined for your tenant sent by malicious spammers on the internet.

Some customers are sending legitimate emails with this malformed header configuration. On October 15, we sent a targeted MC post to customers showing high volumes of messages exhibiting multiple P2 From Addresses without a Sender Address as they may be impacted by this change.

For investigating if you will be impacted by this change, focus your investigation on messages sent using On Premises Inbound Connectors to Exchange Online. Authenticated mail submission is not impacted because submitting messages like this using those submissions are not allowed (Graph, Outlook clients, SMTP AUTH Client Submission).

[How this affects your organization:]

If email clients including devices and applications that you use to send messages, do so using multiple From addresses but without a Sender address header after December 1st, you will get an NDR error code 550 5.1.20 “Multiple From addresses are not allowed without Sender address’”.

[What you can do to prepare:]

When this change is in effect, if you need to send a message that has more than one email address in the From field, make sure that you have a single email address in the Sender header.

If you expect this change to cause any issues for your organization, please share that feedback.

Updated November 6, 2024: We have updated the content. Thank you for your patience.

Coming soon to Microsoft SharePoint and Lists in Microsoft Teams: An updated Microsoft Lists. This rollout introduces new features to users, including the ability to add ratings to any list, drag and/or paste images directly into a list, see who is collaborating with you in real time, switch views by clicking tabs, and more.

This is an update to MC600726: (Updated) Microsoft Lists User Experience Update (updated October 2023) and MC709979 (Updated) Microsoft SharePoint: Updated Lists in Team Sites, Lists progressive web app (PWA), and Teams (January 2024).

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late September 2024 and expect to complete by mid-November 2024 (previously late October).

[How this will affect your organization:]

Before this rollout, Lists do not have features like visible real time collaborators, easy access to views via tabs, and applied filters at the top of a list. Note: Some features described in the May 2023 blog Microsoft Lists: Easier, Better, Faster, Stronger – Microsoft Community Hub, such as new forms to collect information easily, have started to roll out or have fully rolled out.

After this rollout, users in active tenants will see the remaining Lists feature updates described in the May 2023 blog when browsing lists on SharePoint sites, the Lists progressive web app (PWA), the Lists app on the web, and the Lists app in Teams. All Lists in SharePoint sites will retain the SharePoint site’s theme and navigation.

Existing lists configured with these features will be updated after this rollout:

• SharePoint Framework (SPFx) command extensions
• Power Apps forms
• Approvals

Note: Extensions that depend directly on DOM (Document Object Model) structure or CSS (cascading style sheets) are not supported and may break. We recommend using Microsoft SharePoint Framework, which provides a rich API to customize the SharePoint experience. 

These Lists components are not included in the new rollout:

• SharePoint Framework (SPFx) field customizers
• The Playlist template integrated with Microsoft Stream

All new and updated List features are on by default.

[What you need to do to prepare:]

No admin action is needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.

Learn more

• Microsoft Lists: Easier, Better, Faster, Stronger – Microsoft Community Hub (May 2023)
• Introducing Drag and Drop to Reorder Items in Microsoft Lists – Microsoft Community Hub (August 2024)
• Collect information like a pro New Microsoft Lists forms experience in Microsoft 365 (March 2024)

Updated November 7, 2024: We have updated the rollout timeline below. Thank you for your patience.

We’re rolling out new and improved DLP Policy tips in New Outlook to support top DLP predicates & exceptions, all advanced classifiers, and override capabilities.

* Features mentioned above are enabled based on Licenses. Please review license requirements here.

The number of supported conditions has been updated:

• E3 and equivalent licenses: DLP Policy tips on New Outlook for Windows will support following DLP conditions (and corresponding exceptions):
  • Content contains OOB/custom sensitive information types
  • Content is shared from Microsoft 365
• E5 and equivalent licenses: In addition to the above, DLP Policy tips on New Outlook for Windows will now support a richer set of DLP conditions (and corresponding exceptions), including the following:
  • Content contains Sensitivity label
  • Sender is
  • Sender domain is
  • Sender is member of
  • Recipient is
  • Recipient domain is
  • Recipient is a member of
  • Subject contains words

Additionally, DLP Policy tips now support advanced classifiers like Trainable classifiers, Exact data match (EDM), and Named Entities, as well as an override feature that gives end users the ability to quickly and easily modify or override policies (if allowed in the DLP rule configuration), ensuring that the sensitive data is always protected, while still allowing end users to work efficiently.

For more details, admins can refer documentation here.

Please note that any existing conditions outside this updated list, which may currently trigger Policy Tips in New Outlook, will stop working after October 18th, 2024.

[When this will happen:]

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

[How this will affect your organization:]

If you are not using New Outlook this shall not impact you.

If you do not configure the Data Loss Prevention policies to enable policy tips for emails with sensitivity labels, this will not impact you.

If your organization is currently using Data loss prevention policies to enable policy tips and Oversharing pop-up, you will soon see them in New outlook with enhanced experience.

[What you need to do to prepare:]

At this time, there is no action required from you.

You can access Data Loss Prevention in the Microsoft Purview compliance portal. You can create new DLP policies or leverage the existing ones to use DLP Policy tips as an additional layer of security for sensitive data.

Learn more:

• Learn about data loss prevention
• Learn about New Outlook

You are receiving this message because our reporting indicates you may be using new Microsoft Outlook for Windows in your organization.

Coming soon for new Outlook for Windows: an updated People Hub with a modern contact management experience that will retrieve and display high-quality, complete, coherent, and up-to-date information about the people that matter the most to you.

This message is associated with Microsoft 365 Roadmap ID 413114.

[When this will happen:]

Targeted Release: We will begin rolling out mid-January 2025 and expect to complete by end of January 2025.

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

[How this will affect your organization:]

Before this rollout: The People Hub can contain multiple entries for the same contact and organizational profile information may not be included.

After this rollout: The People Hub will contain a unified view of a person with profile enriched contacts and auto-hidden duplicates. To access the People Hub, select the People icon from the left side of the new Outlook for Windows.

As part of the new contact management experience, your contacts will automatically be enriched with profile information from your organization’s directory and other sources. We have updated the profile card with a new Manage sources feature where a user can manage links to the contact sources:

After a user selects Manage sources, the user can manually Unlink contact sources, Edit contact sources that are not from their organization, and manage sources.

Also, to improve the contact management experience, contacts that are exact duplicates will be automatically hidden.

These changes will be on by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation.

After the feature is rolled out, please ensure that you are using new Outlook for Windows to get access to the updated People Hub.

Learn more: Add, find, edit, or delete a contact in Outlook – Microsoft Support (will be updated when rollout begins)

#newoutlookforwindows

• Suggested meeting time slots based on the email conversations.
• Copilot responses in localized languages to respect language nuances.

When an external network participant is invited to join a Microsoft Viva Engage external network, they receive an invitation email with an option to accept. Before this configuration change, all invited external users receive community conversations and emails, even if their invitation is in a pending or inactive state, allowing them to receive updates without completing registration. An E5 license is required to use this feature.

After this change, pending or inactive users will no longer receive community conversations or emails unless they accept the invitation and complete the registration process. This change prioritizes active engagement, ensuring only registered users access conversation updates and reducing the volume of emails sent to non-registered users. External users who have activated their accounts will receive conversations and community emails.

We will begin rolling out this change early December 2024 and expected to complete by early January 2025. Extensions will not be provided for this configuration change.

[How this will affect your organization:]

For organizations that frequently post in the Viva Engage external network expecting external recipients to engage via email without registering, this adjustment may impact their communication flow. However, we expect this effect to be minimal for most customers.

Pending users will need to actively accept their invitation by selecting the link in the invitation email or manually entering the URL in their browser to complete registration. After the user registers, they will begin to receive community conversations and emails.

An example of an invitation to join a Viva Engage external network:

[What you need to do to prepare:]

This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change and update relevant documentation.