Microsoft Roadmap, messagecenter en blogs updates van 20-07-2024

1. Start Windows into Safe Mode or the Windows Recovery Environment.
2. Navigate to the C:\Windows\System32\drivers\CrowdStrike directory
3. Locate the file matching “C-00000291*.sys”, and delete it.
4. Restart the device.
5. Recovery of systems requires a Bitlocker key in some cases.

Introducing four new Microsoft Purview Data Loss Prevention (DLP) Microsoft Exchange (EXO) predicates:

• Message is not labeled: Detects if message body has no label.
• Attachment is not labeled: Detects if there is any attachment without a label.
• Message contains: Detects if the message body contains specified sensitive information types (SITs) or labels. Note that there is no trainable classifiers or non-advanced rule support yet.
• Attachment contains: Detects if an attachment contains specified SITs or labels. Note that there is no trainable classifiers or non-advanced rule support yet.

This message is associated with Microsoft 365 Roadmap ID 377000.

[When this will happen:]

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

[How this will affect your organization:]

You can now create new DLP policies or edit existing policies to include predicates to target specific email components like email body or attachments only.

This feature is available by default.

[What you need to do to prepare:]

For information about how to prepare, visit Create and deploy a data loss prevention policy | Microsoft Learn.

Coming soon to Microsoft Outlook mobile apps: Users will be able to sign in with a QR code (instead of entering a username and password).

This message is associated with Microsoft 365 Roadmap ID 406169.

[When this will happen:]

Public Preview: We will begin rolling out mid-August 2024 and expect to complete by mid-September 2024.

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

[How this will affect your organization:]

In Outlook on the web, your users will be able to go to the Help tab at the top of the screen and select the new Outlook mobile option to get the QR code. Users can scan the QR code with their Outlook Mobile app to sign in without entering their username and password. Outlook will use their identity from Microsoft Entra to securely log them into the mobile app, and users will remain signed in to their mobile app unless manually they sign out.

[What you need to do to prepare:]

This feature will be enabled by default. Admins can disable QR sign in in Microsoft admin center by setting the mailbox policy AccountTransferEnabled to false. This action will prevent the QR code sign in, but users who have already used the QR code will not be signed out from their Outlook mobile app.

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.

Learn more: Use a QR code to sign-in to the Outlook mobile apps – Microsoft 365 admin | Microsoft Learn

Microsoft Defender for Office 365 is retiring four legacy override alerts that are now mostly redundant due to Secure by default. With Secure by default, ZAP (zero-hour auto purge) blocks high confidence phishing emails by default despite the legacy overrides. The four alerts are:

1. Phish not zapped because ZAP is disabled
2. Malware not zapped because ZAP is disabled
3. Phish delivered due to ETR override
4. Phish delivered due to IP allow

As part of the deprecation and rollout,

• These policies will no longer be part of the Alert policies in the Microsoft Defender portal.
• Existing alerts that are already generated will be in the system (part of Alerts) until data retention applies.
• Any features like AIR built on these policies will not function (return no data) but will not result in any crashes or issues to the system.
• Any features like Investigations or post-breach functionalities will not have these alerts as part of the selection, filtering, or processing.

When is the change?

We plan to turn off these alerts starting August 18, 2024 and ending August 30, 2024.

Who is impacted?

1. Phish not zapped because ZAP is disabled: E5/G5 or Microsoft Defender for Office 365 P2 add-on subscription
2. Malware not zapped because ZAP is disabled: E5/G5 or Defender for Office 365 P2 add-on subscription
3. Phish delivered due to ETR override: E1/F1/G1, E3/F3/G3, or E5/G5
4. Phish delivered due to IP allow: E1/F1/G1, E3/F3/G3, or E5/G5

What should I do if I am impacted?

This change will happen automatically by the specified date. No admin action is required. Since these alerts are mostly redundant, we do not expect any impact.

Before this rollout, all presenters added to a Microsoft Teams webinar were displayed on the event page. Coming soon to Teams: webinar organizers will be able to add individuals to the webinar and give them presenter privileges—to join the green room, manage what attendees see, turn their camera on or off, and moderate the event—without including the individuals on the event page as presenters. This feature will allow webinar organizers to support roles like live translators, event moderators, and staff who are not presenting. This message applies to Teams on Windows and the web.

[When this will happen:]

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

[How this will affect your organization:]

To access this new feature, go to the Teams calendar and select the arrow next to New meeting > Webinar > Presenter bios > Select Hide from site in the three-dot menu: 

This feature is on by default and is accessible to all Teams users on Windows and web.

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

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

With the release of Apple iPadOS 17, Microsoft Teams will now support external webcams and cameras in meetings and calls on Apple iPads.  Simply connect your external webcam and camera to your Apple iPad. 

[When this will happen:]

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

[How this will affect your organization:]

To conduct their Teams meeting experience on Apple iPads using external webcams and cameras, users must connect their webcam to their Apple iPad before joining their meeting. If users want to switch to their Apple iPad camera, they must disconnect from their external webcam.

This update 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.

Clipchamp is a simple and robust video editor that enables users to combine video, images, and audio files, with text and effects to create videos worthy of sharing.

Clipchamp can be accessed via the Clipchamp for Windows application or on desktop computers using Microsoft Edge or Google Chrome browsers. It allows for editing and creating videos in OneDrive or SharePoint.

You are receiving this message because Office 365 license holders will gain access to Microsoft Clipchamp capabilities. This update will not impact any other parts of your Office 365 license or Microsoft 365 admin center.

[When this will happen:]

General Availability (Worldwide): Available beginning late August 2024.

[How this will affect your organization:]

Users with corresponding licenses will gain access to Clipchamp.

A new app or service plan, Microsoft Clipchamp, will begin to appear as activated for these license holders in the Microsoft 365 Admin Console.

[What users will see]

Clipchamp will be available from the following locations:

• New Clipchamp Video and Edit in Clipchamp menu in OneDrive and SharePoint document libraries
• Clipchamp for Windows application
• Microsoft365.com/launch/clipchamp start page

Help articles can be found at Clipchamp help and learning (microsoft.com). All articles pertaining to the “for work” version will be updated to also apply for education. 

[What you need to do to prepare:]

When this change takes effect, please make note of the new service plan names for your administrative records and ensure that you update any relevant provisioning documentation, as needed.

The Headspace experience is currently not functioning in Viva Insights. Headspace and all of its content will be removed from Viva Insights. All Headspace entry points and experiences within Viva Insights Home, Virtual Commute, Focus Mode, and Wellbeing Tabs will no longer be accessible and removed effective July 25th, 2024.  

[When will this happen:]

Viva Insights will remove all Headspace content within Viva Insights to users starting July 25th, 2024.  

[How this affects your organization:]

Users within your organization will no longer see Headspace in Viva Insights and will no longer have access as of July 25th.   

Users who rely on the Headspace content can continue to watch our breathing exercises that will continue to be available in app and in experiences such as Virtual Commute and Focus Mode.   

[What you need to do to prepare:]

Headspace overview – For information about the Headspace functionality that will be removed.  

Disable via PowerShell– Admin tasks for the Viva Insights app | Microsoft Learn   

About the Viva Insights app – For information about the Viva Insights app in Teams and on the web.  

Review and assess the impact on your organization and end-users.   

Consider updating your documentation as appropriate to reflect the above changes. 

Coming soon for the Microsoft Lists app: Users will be able to reorder List items using drag and drop.

This message is associated with Microsoft 365 Roadmap ID 380183.

[When this will happen:]

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

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

[How this will affect your organization:]

Before this rollout: Users are not able to drag and drop list items to reorder them.

After this rollout, Users will be able to drag and drop list items.

This feature is on by default and accessible to all Microsoft List app users.

Drag and drop items to reorder your items in Microsoft Lists!

Drag and drop multiple items, too!

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

Learn more: Microsoft Lists App | Microsoft 365

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

We are changing the hardware requirements for Microsoft Edge. Starting in Microsoft Edge version 128, devices that do not have a CPU with SSE3 will no longer be supported or receive updates, including critical security updates.

[When this will happen:]

This change will roll out to Stable channels of Edge no-sooner than the end of August 2024.

[How this will affect your organization:]

Users with devices without SSE3 will no longer receive Microsoft Edge updates once this change is implemented.

Impacted devices will see a banner in Microsoft Edge versions 126 & 127 stating: 

“This computer will soon stop receiving Microsoft Edge updates because its hardware is no longer supported.” 

[What you need to do to prepare:]

Users with devices without SSE3 will need to move to a device with SS3 to continue receiving Microsoft Edge updates. While not recommended, users will have access to Edge version 128 on devices without SSE3. However, they will not receive any updates, including critical security updates.

To learn more about Microsoft Edge requirements, review: Microsoft Edge supported Operating Systems

In February 2024 the retirement of Viva Topics (Changes coming to Topics) was announced. As part of that change, Viva Engage will return to a simplified topics model, called Engage topics, and the integration with Viva Topics will be retired.

The following premium Viva Topics experiences and lightweight topics management experiences will no longer be available in Viva Engage, including:

• Viewing Viva Topics card when hovering on a topic
• Viewing or using AI-discovered Viva Topics
• Links to Viva Topics pages
• Topic management via Viva Topics or lightweight topics management
• Featuring of topics in Answers

Using Engage topics, users will continue to be able to create topics, add topics to posts, follow topics, edit topics they created, and increase the relevance of their feeds by following topics. Topic creators will gain the ability to delete topics they created. Applicable admins will continue to be able to edit topics and will gain the ability to delete topics within Viva Engage.

Organizations using Answers in Viva (Answers in Viva: Introduction) will continue to see additional topic capabilities including bulk topic deletion for admins, AI suggested topics for questions, topics promoted for following, and topic browse experiences. The described topic experiences will be available to Viva Engage tenants that have been migrated to Engage topics.

[When this will happen:]

Rollout will begin August 2024 and will complete for all tenants migrated to use Viva Topics in Viva Engage by April 2025. Tenants using legacy topics in Viva Engage will begin migrations in September 2024 and migrations will continue until all Native mode networks have been completed.

[Why is this change happening?]

As a result of the retirement of Viva Topics, Viva Engage will retire the integration with Viva Topics, but continue to support a simplified topics model to help organize, amplify, route, and recall knowledge posted with topics. To ensure customer data is retained we will migrate customer topics data from Viva Topics into Viva Engage to preserve topics applied to posts and associated Engage topic metadata such as followers, description and creator.

During the transition, we will stop topics migrations to use Viva Topics and Topics lightweight management but continue by-request migrations that enable Viva Engage networks to use Answers in Viva (Technical requirements). Learn more about the migration to Viva Topics (Topics in Viva Engage), the Topics experience (Topics experience in Viva Engage), and the Topics retirement (Changes coming to Topics).

[How this will affect your organization:]

Starting in August 2024, newly created tenants will default to the Engage topics and tenants that have been migrated to use Viva Topics will begin topic migrations to Engage topics. Tenants will be migrated in batches after their Viva Topics license expires or after the Viva Topics retirement date of February 22, 2025, whichever comes first. If your tenant is impacted, notice of topic migration will be shared via message center post approximately one month before topic migration.

Migrations for legacy topics experiences (tenants not yet migrated to Viva Topics) will kick off in September 2024 and continue until all Viva Engage networks in Native mode have migrated to Engage topics.

[What you need to do to prepare:]

Before the migration a tenant admin can get a snapshot of which topics will be migrated by exporting topics in Viva Engage with PowerShell (Export topics created in Viva Engage with PowerShell). No other actions are recommended. 

Coming soon to Microsoft Teams: Copilot in Teams will use the meeting chat (along with the meeting transcript, if enabled) as the data source to answer questions from meeting invitees. For more relevant responses, Copilot will be able to access the chat data for 24 hours before a meeting, during a meeting, and 24 hours after a meeting. The new prompt Highlights from meeting chat will indicate that Copilot can now answer questions using both chat and transcript data. A Microsoft Copilot for Microsoft 365 license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 383019.

[When this will happen:]

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

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

[How this will affect your organization:]

Before this rollout: Copilot in Teams used only the meeting transcript (if enabled)

After this rollout: When your organization’s users pose questions for Copilot in Teams meetings, the responses will include information from the meeting chat.

Copilot in Teams is on by default and accessible to all Copilot for Microsoft 365 licensed users.

The Highlights from meeting chat prompt in Copilot in Teams:

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

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

To learn more about Microsoft’s own review of this product with its works councils, please consider reading: https://aka.ms/Copilot/MSWorksCouncilsArticle