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

Updated September 24, 2024: We have updated the rollout timelines below. Thank you for your patience.

Microsoft Teams users will soon be able to control how they get notified in meeting chats through RSVP to their meetings. When they decline a meeting, they will not receive notifications or see the chats in chat list; when they accept a meeting, they will receive notification for all new messages. This release of Microsoft Teams Meeting ID will be rolling out across Microsoft Teams Desktop, Mobile and Web and will provide an additional way for users to control their chat list by selecting which meetings they want to receive message updates from.

This message is associated with Microsoft 365 Roadmap ID 161739

[When this will happen:]

Targeted Release will begin rolling out early November 2024 (previously mid-October) and expect to complete by mid-November 2024 (previously late October). 

Worldwide will begin rolling out early December 2024 (previously late October) and expect to complete by mid-December 2024 (previously early November). 

GCC will begin rolling out January 2025 (previously early November) and expect to complete by mid-January 2025 (previously mid-November). 

GCC High will begin rolling out mid-January 2025 (previously mid-November) and expect to complete by January 2025 (previously late November). 

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

[How this will affect your organization:]

You will not receive notifications or see chats from meetings you declined. You will be able to set how you want to be notified for meetings you RSVP with Accept or Tentative from Microsoft Teams settings.

[What you need to do to prepare:]

You might want to notify your users about this new capability to control meeting chat notifications by RSVP to meetings. 

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

Introducing two new Data Loss Prevention (DLP) Microsoft Exchange support predicates for DLP Policy tips and Oversharing popups features for Microsoft 365 E5 Compliance users: Message contains and Attachment contains. Unlike the broader Content contains DLP predicate that evaluated the entire email envelope, these new predicates are tailored for client-side evaluation of specific email components only (email body or attachments) and show DLP Policy tips and Oversharing popups accordingly in Microsoft Outlook Win32.

This message is associated with Microsoft 365 Roadmap ID 376999

[When this will happen:]

Public Preview: We will begin rolling out mid-April 2024 and expect to complete by late May 2024.

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

[How this will affect your organization:]

You can now create new DLP Policies or edit existing policies to include Policy tip and Oversharing popup features support for these new focused Message contains and Attachment contains predicates.

For more information, the following resources are available:

• Create and deploy a data loss prevention policy | Microsoft Learn
• Data loss prevention policy tip reference for Outlook for Microsoft 365 | Microsoft Learn
• Get started with oversharing pop ups | Microsoft Learn

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required.

Updated September 25, 2024: We have updated the content. Thank you for your patience.

Video files tend to be very large and consume lots of space against your Microsoft OneDrive and Microsoft SharePoint storage quotas. Currently, when you make metadata changes such as title, description, transcripts, chapters, interactivity, thumbnails, media settings, etc. to files in Microsoft Stream, each of those changes cause new versions to be created. Each of these versions in Microsoft OneDrive and Microsoft SharePoint count the full file size towards consumed storage quota. Thus, for large video and audio files, these versions cause your storage consumption to quickly increase.

To prevent this, we are changing how Microsoft Stream handles versioning. Any changes made specifically to chapters and transcripts of files from Stream will stop making versions, thus preventing storage from increasing as rapidly as it has in the past.  

This message is associated with Microsoft 365 Roadmap ID 395380

[When this will happen:]

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

[How this will affect your organization:]

Changes to video and audio files from Stream will no longer take version snapshots. This means that any metadata changes in chapters and/or transcripts made through Stream cannot be reverted to previous versions.  

The following actions will no longer create a version in the file’s version history:

• Adding or editing chapters, and transcripts
• Toggling transcript media settings  

The following actions will still create a version in the file’s version history:

• Editing title or description from within Stream
• Adding audio tracks.
• Editing column metadata in SharePoint document library for a video file.
• Editing title or description from outside of Stream.
• Replacing the file with a new different version of the file.
• Other operations outside of the Stream app.
• Toggling media settings (show/hide about video, chapters, interactivity, comments, analytics, etc.).  This change will happen by default, and there will not be a way to revert to the previous behavior where everything changed in Stream created versions.

This change will happen by default, and there will not be a way to revert to the previous behavior where chapters and transcripts changed in Stream created versions.

This change will only stop new versions from being taken from Stream. To clean up existing versions of files or versions taken outside of Stream, the SharePoint team has a separate capability and new settings coming that will help clean up low value versions (see Roadmap ID 145802). Admins must complete this action for each site, and it will take approximately 30 days before the new version of the site is in effect. 

For more information, visit Versioning in Stream – Microsoft Support.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. This change will happen by default, and there are no settings to control it. You may want to notify your users about this change and update any relevant documentation as appropriate.

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

Currently, when you share a link with view-only permissions in Microsoft 365 apps, clicking on Copy link defaults to an “Only people with existing access” link that does not always target your intended people.

With this new feature, when you share a link with view-only permissions with other people, those people will now be able to copy that same link directly from the Share dialog when they attempt to share. If your only option to share with others is Only people with existing access, you will be able to send a request to the owner to share this file with specific people directly in the sharing control. The owner of the file will then receive a request and will be able to approve or reject the request.

[When this will happen:]

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

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

[How this will affect your organization:]

With this new feature, anyone who accesses a Microsoft 365 apps file with view-only permissions will see this new experience. 

Learn more: Sharing files, folders, and list items – Microsoft Support (content within will be updated before rollout begins).

[What you need to do to prepare:]

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

Updated 9/25/2024: The content for this release has been updated. Thank you for your patience.

In Microsoft Clipchamp, the Brand kit feature enables users to create and share brand asset collections including colors, fonts and logos to use when creating videos. With this rollout, users with these subscriptions will have Brand kit as a standard feature in Clipchamp:

• Microsoft 365 E3 and E5
• Microsoft 365 Business Premium and Business Standard
• Microsoft 365 A3 and A5

This message is associated with Microsoft 365 Roadmap ID 398992.

This message applies to Clipchamp for Windows and for the web.

[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 late July 2024 and expect to complete by late August 2024.

[How this will affect your organization:]

You are receiving this message because users in your tenants have licenses which enable access to these capabilities. This update will not impact any other parts of your Microsoft 365 license or Microsoft 365 admin center.

Before this rollout: Users with the subscriptions in this message had no access to Brand kit in Clipchamp and manually managed brand assets when creating videos.

After this rollout, your users can expect these changes in Clipchamp:

• Creation, sharing and manual usage of personal Brand kits is available via all work and education accounts.
• Brand kit now supports elements beyond colors, fonts and logos including up to 300 each of: videos, music, sound effects, images, backgrounds, and stickers. All assets are stored on OneDrive or SharePoint.
• Organization “official” Brand kits can be surfaced to all users opening Clipchamp across a tenant by placing the Brand kit in Organization Asset Library (OAL) – anticipated to be finalized by end of October. 

What users will see

• In Clipchamp, Brand kits can be created, used, or opened by anyone if the creator generates a link to share with them.
• User-created Brand kits can be stored in OneDrive or SharePoint.
• Up to 300 of these brand elements can be stored with the Brand kit: videos, sound effects, music, images, backgrounds, and stickers.

The default state of this feature is on and all users with the specified licenses can access it.

Clipchamp video editor with the Brand kit menu expanded to show example brand kits for Tailspin Toys and Microsoft. Select the Brand kit button from the left side of the screen:

[What you need to do to prepare:]

When this change takes effect, please make note of the new feature in Clipchamp for your administrative records and ensure that you update any relevant provisioning documentation, as 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.

Learn more: How to use brand kit in Clipchamp – Microsoft Support

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

Copilot in Microsoft SharePoint’s Rich Text Editor makes it easy to author content in SharePoint pages and posts. Copilot in SharePoint’s Rich Text editor is available as part of the Text webpart for any user with a Copilot Microsoft 365 license.

This message is associated with Microsoft 365 Roadmap ID 124840.

[When this will happen:]

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

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

[How this will affect your organization:]

Before the rollout: The Copilot button did not appear in the SharePoint’s Rich Text editor.

After the rollout: Users who have been assigned a Microsoft 365 Copilot license will find a Copilot option in SharePoint’s Rich Text Editor when editing page content. Copilot in SharePoint combines the power of Large Language Models (LLMs), the user’s data in the Microsoft Graph, and best practices to create engaging web content. Copilot in SharePoint can help users draft content when creating new pages, adjust the tone, condense content, and expand meeting bullets into structured text—all within Microsoft’s existing commitments to data security and privacy in the enterprise.

The Copilot menu option in the Rich Text Editor for the Text webpart:

Copilot after rewriting the contents of a SharePoint Text webpart:

This feature is bundled as part of Microsoft Copilot for Microsoft 365 and always on for licensed users. It can be disabled if the customer deselects the Microsoft M365 Copilot for SharePoint service plan from the Microsoft 365 admin center.

[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 post with new Support articles before rollout begins.

To learn more about Microsoft’s own review of this product with its works councils, please consider reading: Deploying Copilot for Microsoft 365 and AI at Microsoft with our works councils.

Update 9/24/2024: This change has been postponed. Stay tuned to the blog for updates: Important changes to the Windows enrollment experience coming soon.

Expected in the upcoming October Windows update, the Windows enrollment experience for managed devices will be updated to automatically enable quality updates during the out-of-box experience (OOBE). This change ensures that devices are fully patched and ready to use as soon as they are enrolled. For more information, review the blog: Important changes to the Windows enrollment experience coming soon

[How this will affect your organization:]

For new enrollments, all Windows 11, version 22H2 and higher devices will automatically download and install quality updates during OOBE. This applies to all enrolled Windows devices, regardless of whether they are pre-registered with Windows Autopilot or not. The updates will be applied before the user reaches the desktop, ensuring that the device is fully patched before logging in. Note: Device setup may require additional time due to quality update installation during OOBE.

[What you need to do to prepare:]

Plan accordingly for additional device set up time. If you are using Temporary Access Passwords, we recommend extending the validity period during enrollment to prevent the passcode from expiring. For more information, review the blog: Important changes to the Windows enrollment experience coming soon

SharePoint Embedded Administrators will be able to grant guest applications permission to SharePoint Embedded applications within their tenant using cmdlets in SharePoint Online Management Shell. A guest application is defined as any application within the enterprise applications of the owning tenant.

1. Get-SPOApplication includes changes to view guest application permissions
2. Set-SPOApplicationPermission includes changes to manage guest application permission management

[When this will happen:]

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

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

Current SharePoint admins will need to download the latest version of SharePoint PowerShell to access changes to guest application permission management cmdlet changes

[How this will affect your organization:]

SharePoint admins will now be able to grant guest applications within their tenant permissions to access SharePoint Embedded applications.

[What you need to do to prepare:]

Current tenant admins will need to download the latest version of SharePoint PowerShell to access changes to guest application permission management.

This message is for customers who have tenants in the EU, but their Q&A data currently resides in the US data boundary. Q&A is an experience in Teams, powered by Viva Engage, that allows presenters to take questions from meeting attendees and answer them in real time.

Starting late October 2024, organizations based in the European Union (EU) with existing Teams Q&A enabled tenants that

• Onboarded to Viva Engage prior to 2019, or
• Onboarded to Teams Q&A without a prior Viva Engage network

will be relocated from datacenters in the US to the datacenters in the EU.

To be considered a tenant in the EU Data Boundary: The tenant must have default geography in an EU country or select a country from among the EU countries as their residence during free trial sign-up. 

[When this will happen:]

Q&A data relocation for impacted customers starting in late October 2024.

We will send out another notification informing you of the specific date and time at which migration will occur for your tenant so you can plan accordingly.

[How this will affect your organization:]

The Q&A feature on Teams will be in read-only mode while the data is relocated. All other Teams features will remain unaffected.

The relocation process will move your Q&A data from the US to the EU boundary in the backend. During of the migration process, users will

• Be able to view the Q&A from prior meetings, but not be able to edit or react
• Not be able to access the Q&A feature during live meetings
• Not be able to create new Teams meetings with Q&A enabled.

The read-only mode is expected to last for about 4 hours, after which, Q&A feature will be reinstated.

To minimize impact, we will be running the relocations during off hours over the weekends. You will be notified of the exact date and time for your data’s relocation, two weeks before the relocation activity begins.

[What you need to do to prepare:]

We will be relocating Teams Q&A content in batches over the next several months and will notify you in a separate message regarding the exact date and time that your Teams Q&A data relocation will occur. Please inform your users that there is a planned maintenance that will keep the Q&A experience in read-only mode for a few hours.