Microsoft Roadmap, messagecenter en blogs updates van 12-05-2024

Viva Connections will be directly available in the browser, offering all the same functionalities that exist in Microsoft Teams. This integration surfaces directly in the browser, providing a consistent experience with other Viva Modules. 

This message is associated with Microsoft 365 Roadmap ID 394276

[When this will happen:]

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

General Availability (Worldwide, GCC, GCCHigh, DoD): We will begin rolling out late May 2024 and expect to complete by mid-June 2024.

[How this will affect your organization:]

All the functionalities that exist in Viva Connections in Teams are now also available directly in the browser, providing a consistent experience with other Viva modules. The web experience offers an additional entry point for Viva Connections, catering specifically to customers who do not rely on Teams.

Figure 1:

[What you need to do to prepare:]

No action is required to use Viva Connections on the web. It is recommended that you share more information about this release with your employees so that they can use Viva Connections more effectively.

Additional Information: 

• Overview: Viva Connections | Microsoft Learn

With this new feature, end users can delete non-empty document library folders containing many files on a site managed by a Retention policy. Additionally, folders covered under a Retention policy that have been deleted don’t reappear for users who sync a document library offline using Microsoft OneDrive for Business.

This message is associated with Microsoft 365 Roadmap ID 394689

[When this will happen:]

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

[How this will affect your organization:]

This new feature ensures that folders can be deleted as intended and folders remain deleted post-synchronization with OneDrive for Business. This feature is available by default.

[What you need to do to prepare:]

Get started with Data Lifecycle Management in the Microsoft Purview compliance portal.

We are introducing a user setting to prevent automatic transition to Do Not Disturb (DND) while presenting in a Microsoft Teams call on web.

This message is associated with Microsoft 365 Roadmap ID 393228

[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 and GCC): We will begin rolling out mid-June 2024 and expect to complete by early July 2024.

[How this will affect your organization:]

Traditionally, when a user is engaged in screen sharing, Microsoft Teams automatically switches their presence to DND during a call or meeting. While in DND mode, users do not receive notifications of calls, meetings, or chats, except from priority contacts. This automatic presence transition is aimed to help users concentrate on their tasks without interruptions. Based on customer feedback, we are now introducing this new feature for increased flexibility while working to receive notifications and messages while in presenting mode.

The setting will be available by default. Users must toggle the DND setting off to enable this feature.

 [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.

Microsoft Purview: We are excited to announce upcoming enhancements to Microsoft Purview Data Loss Prevention (DLP). With the forthcoming update, the capability to scan, classify, and protect sensitive content on Windows endpoint devices will be significantly expanded. The number of supported file types will increase from approximately 40 to over 100, aligning endpoint coverage with other platforms like Exchange, SharePoint, and OneDrive. Additionally, this update will introduce several key enhancements, including:

• Detection of labels from protected files (pfiles).
• Identification of sensitive content within file metadata.
• Recognition of sensitive information in PDF form fields.
• Detection of sensitive information in files embedded inside office files (for example, a .txt file inside .pptx file)

This message is associated with Microsoft 365 Roadmap ID 171586

[When this will happen:]

Public Preview: We will begin rolling out late June 2024 and expect to complete by early October 2024.

General Availability Worldwide: We will begin rolling out early October 2024 and expect to complete by late October 2024.

[How this will affect your organization:]

The upcoming update will enhance DLP’s content scanning on Windows devices. No changes to existing policies are required.

Summary of enhancements:

1. Enhanced file type coverage

The file type coverage to scan, classify, and protect sensitive content on Windows Endpoint devices will increase from 40 file types to over 100.

This means that sensitive content in additional file types like BZ2, EML etc. will also start getting scanned and protected using DLP policies.

2. Detect label in PFILE

The DLP condition “content contains sensitivity label” now has the capability to detect labels from protected files (pfiles). This means that it can now read labels not just from Office and PDF files, but all other files where MIP label with protection can be applied via applications like AIP client, Secude etc. which converts the file into “pfile”.

Picture 1:

A txt file converted to .ptxt (PFile) after applying a label. This label can now be detected with this preview.

3. Scanning metadata

Ability to detect sensitive content in file metadata like custom properties in Office and PDF files.

Picture 2:

4. Scanning content embedded in Microsoft 365 office files

If a file is embedded inside an office file (Microsoft Word/Excel/PowerPoint), the content of the embedded file is also scanned. For example, if a DOCX file containing credit card numbers is inserted into an XLSX file, the content of both XLSX and the embedded DOCX files will be scanned, and credit card numbers will be detected.

Picture 3:

5. Better scanning with PDF files

· Ability to scan and detect sensitive content in PDF forms.

· Ability to scan and detect sensitive content in permission protected PDF files. Permission protected PDF files are ones which do not require any password to open the file and read the content but require a password to edit/copy the content.

Picture 4:

[What you need to do to prepare:]

You do not need do any changes to your existing policies. Your existing policies will seamlessly start scanning additional content as detailed above.

Additional Resources

• Learn about Endpoint data loss prevention | Microsoft Learn

Coming soon for Teams Phone Mobile (TPM). A new Call my phone feature will allow TPM users (iOS, Android) to transfer an active call from the Teams app to their cell phone dialer on their SIM-enabled device, with no interruption to the call. Teams will use the user’s Audio Conferencing Subscription service to connect with the user’s cell phone dialer. This rollout will apply to calls to one person (and will not apply to group calls).

This message is associated with Microsoft 365 Roadmap ID 385349.

[When this will happen:]

Public Preview: We will begin rolling out early June 2024 and expect to complete by late June 2024.

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

[How this will affect your organization:]

After rollout, users will need to update to the latest Teams Phone app.

The Call my phone feature in iOS:

[What you need to do to prepare:]

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