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

Updated September 17, 2024: We have updated the images below. Thank you for your patience.

We’re making a change to the shared folder experience in Microsoft OneDrive. Currently, when a user opens a shared folder in OneDrive, they are taken to a view of that folder within the sharer’s OneDrive. In the new experience, opening a shared folder will take the user to the shared folder within the People view of their own OneDrive. This view, organized by people, shows and allows access to all the files and folders that have been shared with the user.

This message is associated with Microsoft 365 Roadmap ID 395378.

[When this will happen:]

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

[How this will affect your organization:]

With this feature update, opening a shared folder will take the user to the shared folder within the People view of their own OneDrive, as follows.

[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 September 17, 2024: We have updated the timing of this change and provided additional information to prepare for the change. Thank you for your patience.

Starting October 16, 2024, we’re gradually enabling IPv6 for all customer Accepted Domains that use Exchange Online for inbound mail. Microsoft is modernizing Exchange Online so our customers can easily meet their local regulations as well as benefit from the enhanced security and performance offered by IPv6.

More information on IPv6 support for Microsoft 365 services can be found at: IPv6 support in Microsoft 365 services

[When this will happen:]

October 16, 2024 (previously October 1, 2024)

[How this will affect your organization:]

After we enable IPv6 for your Accepted Domains, when someone tries to send an email to one of your users and queries the MX record for the domain, they will receive both IPv4 and IPv6 addresses (AAAA records) in response to their MX record query.

[What you need to do to prepare:]

To take advantage of IPv6 connectivity, please make sure that you and your partner’s update network allow-lists to allow Exchange Online IPv6 endpoints in the same way it allow-lists IPv4.

The Exchange Online IPv6 endpoints can be found here: Microsoft 365 URLs and IP address ranges.

To opt a domain out of inbound IPv6 so traffic flowing to the domain remains IPv4-only, please use Disable-IPv6ForAcceptedDomain -Domain for each domain you want to opt out of IPv6 (Disable-IPv6ForAcceptedDomain (ExchangePowerShell) | Microsoft Learn).

IPv6 enablement may impact the source IP type used by Senders when connecting to Exchange Online, as the source and destination IP versions must match. For any IP Address-based Inbound connectors in Exchange Online that are referencing IPv4 addresses, you need to either:

• Keep the sending server as IPv4.
  • Coordinate with the Sender so the Sender keeps connecting to your domain(s) via IPv4 or Opt your domain(s) out of IPv6
• Change the IP based connector to certificate domain based connector.
  • This applies to both OnPremises type (From: Your organization’s email server, To: Office 365) and Partner Type connectors (From: Partner organization, To: Office 365).

You can manage IPv6 for your Exchange Online Accepted Domains using the commands Enable-IPv6ForAcceptedDomain or Disable-IPv6ForAcceptedDomain.

Currently, you can check the status of your Accepted Domains with the Get-IPv6StatusForAcceptedDomain command. While some customers have already enabled IPv6, most will see it as disabled until October 16th.

After October 16, once IPv6 is enabled for your tenant, if you haven’t explicitly set the IPv6 status for your Accepted Domains, the Get-IPv6StatusForAcceptedDomain command will reflect the new default behavior (enabled).

IMPORTANT: To ensure your preferred settings are applied, please use the Enable-IPv6StatusForAcceptedDomain or Disable-IPv6StatusForAcceptedDomain commands before October 16th, after which IPv6 will be enabled by default if you haven’t explicitly set it.

Updated September 16, 2024: Based on customer feedback, we have determined we will not be moving forward with the domain change as originally communicated. Users will not see a new URL and will continue to see outlook.office365.com/Encryption as they do today. Thank you for your feedback.

We will be proceeding with the minor design updates on the portal (fonts, colors, controls and more). These changes are to align with Purview branding and should not disrupt users.

[When this will happen:]

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

[How this affects your organization:]

Users will see minor design changes within the UI.

[What you need to do to prepare:]

You may consider updating training and documentation as appropriate.

—Summary of original message—

The Microsoft Purview Message Encryption portal provides access to encrypted messages sent from your organization’s users to external recipients. The cloud.microsoft domain was provisioned in early 2023 to provide a unified, trusted, and dedicated DNS domain space to host Microsoft’s first-party authenticated SaaS products and experiences. With this rollout, selected Microsoft products and scenarios will transition to a similar static.microsoft domain, in parallel with the previous domains. As part of this transition, the design of the portal (fonts, colors, controls, and more) will be adjusted to align with Purview branding and domain change.

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

Before this rollout, Microsoft Viva Engage users go to different locations in the application for different creation types such as a post, a community, and more.

After this rollout, a Viva Engage user will be able to create the different types of content they are licensed for with one Create new button. This new button eases the process of creation and helps users quickly discover the various creation options they are licensed to use. This feature is available in Viva Engage for Windows desktop, Viva Engage for the web, as well as the Viva Engage app in Microsoft Outlook for Windows desktop and iOS/Android and Microsoft Teams for Windows desktop and iOS/Android.

This message is associated with Microsoft 365 Roadmap ID 416449.

[When this will happen:]

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

[How this will affect your organization:]

The new Create new button is in the top left area of the Engage app (below the user’s own profile) and is always visible as the user visits different pages in the application. Users will be able to create only those content types they were licensed to create before the rollout.

With the Create new button, a user with all permissions and a Viva Engage premium license would be able to create a new:

• Post (discussion, question, praise, poll, article)
• Community
• Event
• Campaign

Other users will see a reduced set of creation options based on their existing license and permissions.

The Create new button in the left menu under the profile of a user who is licensed to create all content types (shown in the drop-down menu):

The Create new button for a user who is only licensed to create posts. This button has no drop-down menu.

This feature is 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.

Learn more about the nuances of licensing and permissions for Viva Engage and for each content type:

• Set up Viva Engage | Microsoft Learn
• Posts: Write and schedule posts, articles, and announcements in Viva Engage – Microsoft Support
• Communities: Create a community in Viva Engage – Microsoft Support
• Campaigns: Set up official campaigns in Viva Engage | Microsoft Learn
• Events: Organize a Viva Engage live event | Microsoft Learn

Coming soon to Microsoft Viva Insights: To enhance reliability and performance, we are transitioning to a more agile, high-performing API. This change will ensure a more consistent and robust user experience. Users will retain access to all reports but will see some design and content changes.

[When this will happen:]

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

[How this will affect your organization:]

These changes will apply to both default report pages and metric reports:

• The New hire onboarding report focuses on a specific group in the organization (new hires). It will adhere to current standards by displaying data only when the number of new hires meets the minimum group size requirement.
• Specific rounding rules are applied to time-based metrics to make trends more meaningful and significant. For durations under 1 hour, rounding is to the nearest 15 minutes. For durations over 1 hour, rounding is to the nearest 30 minutes.

Change to metric reports only:

• Metric reports will be enhanced to provide a four-week average, aligning with default report time frames. As a result, peer benchmarks, Last week’s snapshot, Inspiration library articles, and Recommended actions will no longer be accessible in the metric reports.
• The home page cards for metric reports will be updated to compare metrics to the previous week instead of peer organizations.

Updated metric reports:

This change will be on by default.

[What you need to do to prepare:]

Review and assess the impact on your organization. We have updated the documentation: Use Leader reports to uncover key business outcomes | Microsoft Learn

Also, you may want to notify your users about this change and update any relevant documentation.

Coming soon to Microsoft Viva: Pulse admins will be able to copy and share links to Pulse templates from the template management page or from the template. For example, as a Pulse admin, I can copy a link for a template I’ve created and share it to all users in my company so they can also use or edit a template to create and send a Pulse.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout, it is not possible for Pulse admins to copy and share a link to a Pulse template. Users must discover templates for themselves in the Pulse app. If they can find a template created by a Pulse admin, they can use the template.

After this rollout, Pulse admins can copy template links from the Template management section on the Customize templates and questions page or from the template and share it to all users. Users who open a shared template link will go to the customization page for that template.

This feature is 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.

Review and assess the impact on your organization. Share this communication with all Viva pulse admins in your organization.

Learn more: Manage available surveys and questions | Microsoft Learn (will be updated before rollout)

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 late October 2024.

[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

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)

In Microsoft Outlook, customers can select portions of text in an email and use Microsoft Copilot for Microsoft 365 to rewrite it. Using Copilot for Microsoft 365, users can give detailed instructions on how to rewrite a selection of text and find quick options to modify tone and length.  

This message is associated with Microsoft 365 Roadmap ID 392327.

[When this will happen:]

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

[How this will affect your organization:]

After composing a message, users will now have the ability to select a portion of text and get help from Copilot for Microsoft 365 to rewrite it, instead of rewriting the entire email.

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.

With voice isolation in Microsoft Teams, you can enjoy clear and uninterrupted calls or meetings, no matter where you are. Voice isolation is an AI-based advanced noise suppression feature that eliminates unwanted background noise, including other human voices. The technology recognizes your voice profile and ensures only your voice is transmitted. Voice isolation can be enabled for calls and meetings. With this rollout, voice isolation will be available on Teams for macOS desktops.

This message is associated with Microsoft 365 Roadmap ID 412359.

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

[How this will affect your organization:]

Before this rollout, Teams users on macOS desktops are not able to access the Teams voice isolation feature.

After this rollout, to use this feature, admins must enable the enrollUserOverride policy and the Voice isolation feature policy in the Teams admin center. Users will need to enroll their voice profile in Teams Settings on the Recognition tab to enable the voice isolation feature to have better audio input quality.

To disable this feature for your organization, use Microsoft PowerShell: Set-CsTeamsMeetingPolicy

This feature is on by default and available for admins to enable it.

[What you need to do to prepare:]

Make sure to enable the enrollUserOverride policy for Voice and Face profile enrollment. Users can begin enrolling their Recognition profile now so they can use the voice isolation on macOS as soon as it is rolled out to your tenant.

These support articles and resources will help address any questions you or your users may have about the rollout:

• Voice isolation in Microsoft Teams calls and meetings – Microsoft Support
• Manage voice isolation for your users’ Microsoft Teams calls and meetings

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 training and documentation as appropriate.