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

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

Note: If you are not using frontline worker functionality, you can ignore this message.

Coming soon to Microsoft Teams: Cross-location Shifts is a new feature in the Microsoft Shifts app for Teams that enables frontline managers to offer open shifts across multiple locations in a region so managers can share the labor pool and workers can select available shifts across different locations. This message applies to Microsoft Teams for Desktop, web, Mac and Mobile.

This message is associated with Microsoft 365 Roadmap ID 394351.

[When this will happen:]

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

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

[How this will affect your organization:]

Before the rollout, frontline managers are not able to not able to offer open shifts across multiple locations in a region.

After the rollout

Benefits of cross-location shifts:

• Optimize the manager’s workforce by balancing the supply and demand of labor across locations in a region.
• Empower your frontline workers by giving them the flexibility to select open shifts at a location that is convenient for them.
• Improve customer satisfaction by ensuring that you have enough staff to serve them.

The cross-location shifts feature requires the following conditions:

• An operational hierarchy must be established for the organization.
• The team should have sister locations.
• Team should have at least one matching schedule group code with other teams

Admins or frontline managers can enable these prerequisites through:

• Defining the operational hierarchy in the Teams admin center, as described in Deploy your frontline operational hierarchy – Microsoft 365 for frontline workers | Microsoft Learn
• Creating schedule group codes via the Graph API, detailed in Create scheduling Group – Microsoft Graph beta | Microsoft Learn

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

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

For reference: Manage the Shifts app for your organization – Microsoft Teams | Microsoft Learn

As communicated in MC802699 Microsoft Purview | Insider Risk Management: Adaptive Protection + Conditional Access will be GA (June 17, 2024), Microsoft Entra ID Conditional Access integrated with Adaptive Protection—a powerful capability in Microsoft Purview—is coming soon to General Availability. The integration will allow organizations to set up Conditional Access policies that will utilize insider risk signals from Adaptive Protection to enforce actions, like blocks, on users with insider risk levels. For example, a Conditional Access policy with the Insider Risk condition can block elevated risk users from all Microsoft 365 applications while allowing minor risk users to continue to access company resources.

Organizations will need an Entra ID P2 license to use Conditional Access policies integrated with Adaptive Protection. 

This message is associated with Microsoft 365 Roadmap ID 388737.

[When this will happen:]

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

[How this will affect your organization:]

Before the rollout: The Insider Risk condition was not available to the organizations who have P2 license.

After this rollout, if you have an Entra ID P2 license, your organization will have access to Conditional Access policies integrated with Adaptive Protection. If you configured the default Insider Risk Conditional Access Policy during public preview, your policy would remain unchanged.

[What you need to do to prepare:]

Your organization will need to enable Adaptive Protection in Insider Risk Management and follow the setup instructions. If you do not already have an Entra ID P2 license, your organization will need to obtain one.

This feature is on by default and accessible to all users with appropriate permissions.

Learn more

• Microsoft Entra Plans and Pricing | Microsoft Security
• Block access for users with elevated insider risk – Microsoft Entra ID | Microsoft Learn
• Help dynamically mitigate risks with adaptive protection (preview) | Microsoft Learn
• The dynamic duo for your data security – Adaptive Protection integration with Conditional Access – Microsoft Community Hub

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. This post is to inform admins that the following Microsoft products and scenarios are now available at the cloud.microsoft domain, in parallel with the previous domains.

• Microsoft Planner (https://planner.cloud.microsoft)

A full list of product experiences already being delivered on this domain can be found here: Unified cloud.microsoft domain for Microsoft 365 apps – Microsoft 365 Enterprise | Microsoft Learn.

[When this will happen:]

The services above are already available on cloud.microsoft, in parallel to their previous domains. You can expect the previous domains to be redirected to cloud.microsoft in the coming months.

[How this will affect your organization:]

• The cloud.microsoft domain has been a part of standard Microsoft network guidance on domains and service endpoints since April 2023. If you are currently following this guidance, this change should not impact users in your organization using the above applications under the new domain.
• Users will be redirected to applications under cloud.microsoft domains gradually and automatically. No specific user action is required. Links to the previous domains are backwards compatible and continue to be supported. Users may notice that the new application domains are lacking the “.com” extension. This is by design, as “.microsoft” is Microsoft’s own top-level domain – and this exclusivity allows for additional security and protection against spoofing.

[What you need to do to prepare:]

• Educate users to recognize and expect cloud.microsoft as a key domain for Microsoft cloud experiences. You can refer them to What is cloud.microsoft? – Microsoft Support for more information.
• If your organizational websites, tools, or other materials reference the old URL, those links will be automatically redirected. However, it would be good practice to update those assets to avoid user confusion.
• Partner with developers of in-house Teams apps – including those that run on Outlook and Microsoft 365 – to take the actions described in Action required: ensure your Microsoft Teams apps are ready for upcoming domain changes so the apps continue to function on the new domain.
• Admins should ensure that connections to *.cloud.microsoft are not blocked from their clients and enterprise networks. This should require no action if standard Microsoft network guidance on domains and service endpoints is being followed.

Coming soon to Microsoft Outlook: The Reset People Suggestion feature will allow users to reset, export, and/or opt out of people suggestions in search through Outlook on the web and the new Outlook for Windows settings. If a user resets their People Suggestions in Outlook on the web or Outlook for Windows, all versions of Outlook will reflect that change (even Outlook Mobile). This message applies to Outlook on the web and the new Outlook for Windows.

This message is associated with Microsoft 365 Roadmap ID 98137.

[When this will happen:]

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

[How this will affect your organization:]

Before the rollout: Users were not able to reset or export their suggested contacts from Outlook on the Web and the new Outlook for Windows.

After the rollout

• The default on/off value for the Reset People Suggestion feature in Outlook will inherit each user’s existing configuration from their Microsoft 365 My Account privacy settings at https://myaccount.microsoft.com/settingsandprivacy/privacy. No further action from users is needed to prepare.
• Users will be able to reset, export, and/or opt out of People Suggestions from Outlook on the Web and the new Outlook for Windows Privacy and data settings. This setting will stay in sync with the Privacy configuration in My Account.

Initial People Suggestion settings will be inherited from each user’s Microsoft 365 My Account privacy settings at Settings & Privacy > Manage Contact Search:

To modify the behavior of People Suggestions: Users can go to Microsoft Outlook > Settings > General > Privacy and data > Suggested people:

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

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

The In development for Microsoft Intune page in our documentation has been updated.

How does this affect me?

The In development page provides a list of features in upcoming releases of Microsoft Intune to assist in your readiness and planning. The list has now been updated. You’ll start seeing these changes in the next month or in a subsequent release.

What do I need to prepare for this change?

You can inform your IT staff and helpdesk of the upcoming changes listed on this page. Plan to update your user guidance, if you feel any of these features would be important to your users.

Additional Information

Intune In development

In Microsoft Teams, town hall and webinar currently support the ability for an external user outside the organization to present in an event. External presenters can be guests who are federated, unfederated, or anonymous to the organization.

With this update, if a federated or unfederated guest has not been successfully authenticated, the guest will be brought into the lobby rather than being restricted access when joining the event. Once in the lobby, an internal organizer or presenter has the option to approve or deny the guest’s request to join the event.

• It is recommended to keep the lobby enabled for your event if you intend to invite external presenters.
• An external presenter that is successfully authenticated will be brought into the event automatically without waiting in the lobby.
  

[When this will happen:]

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

[How this will affect your organization:]

Any events that are created or updated after the rollout of this improvement will receive the new lobby experience for external presenters.

For more information, see Schedule a town hall in Microsoft Teams.

[What you need to do to prepare:]

The improvement will be rolled out to organizations automatically with no admin action required. It is recommended that you notify your event organizers about this change and update any documentation as appropriate.

In MC718748 New Teams rollout schedule for Commercial and EDU customers (February 28, 2024), we informed customers about the new Microsoft Teams rollout schedule with updated timelines.

This is a reminder that classic Teams reaches the end of support on July 1, 2024, and end of availability on July 1, 2025, and to confirm our plans to automatically uninstall classic Teams for Mac.

Learn more: End of availability for classic Teams client – Microsoft Teams | Microsoft Learn

[How this will affect your organization:]

As Microsoft transitions users to new Teams on Mac, we will also attempt to uninstall classic Teams starting from early August 2024 to end of August 2024. The uninstall will be attempted after users update to the latest version of new Teams (the specific version number will be provided in an update to this post). The uninstall attempt will happen immediately after the Mac users have updated to new Teams. If this uninstallation is blocked for any reason (for example, by machine configuration, etc.), we will not attempt uninstallation again, and admins will be expected to manually remove classic Teams. The uninstallation guide will be shared in an update to this post before the rollout .

[What you need to do to prepare:]

The uninstall of classic Teams will be automatic when users receive an update to the specific build with this functionality—no admin action is required. You may want to notify your users about this change and update any relevant documentation as appropriate.