MC878427: Restricted Content Discoverability for SharePoint Sites

Announcement ID	MC807460		Published Date	07-01-2024
Service	microsoftteams		Last Updated	07-26-2024
Category	Stay informed		Expiration Date	09-30-2024
Roadmap ID			Action Required by Date
Tags	Admin impact, Feature update

Summary
Microsoft Mesh is transitioning to use Microsoft Teams' backend for spatial audio, promising improved audio quality and simpler network setup requirements for users with Mesh app versions 5.2407+. The rollout, starting now, is expected to complete by late July 2024. No admin action is required before the rollout.

More Information

We are starting to transition the Microsoft Mesh app for PCs and Meta Quest headsets to use the same backend infrastructure as Microsoft Teams for spatial audio. This rollout will provide improved audio quality and simplified network requirements. This message applies to users with Mesh app versions 5.2407+. When this will happen: General Availability (Worldwide): We have started the rollout and expect to complete by late July 2024. How this will affect your organization: Before the rollout Multi-room events hosted in the Mesh app require endpoint and firewall requirements. During the rollout You may find that you don't need to configure the endpoint and firewall requirements. We recommend supporting the full set of endpoint and firewall requirements for multi-room events to prevent an interruption in service during rollout. After the rollout Users should observe improved audio quality when using the Mesh app, and there will be simplified network requirements to get started with the Mesh app on PC and Meta Quest headsets. The network setup requirements will be simplified to the endpoints and ports needed for Microsoft Teams, as documented in Microsoft 365 URL and IP address ranges, as well as those for Azure Communication Services. Admins will no longer need to allow traffic to all IP addresses in the "AzureCloud" service tag over the protocols and ports outlined in Mesh setup docs for admins. Users in your organization will no longer need to consent to the terms needed to use Mesh's current infrastructure for spatial audio to use the Mesh app on PC and Meta Quest headsets. Please note that if your organization hosts custom content as part of using Mesh (for example, for cloud scripting, web slates, or other media), you will still need to continue allowing access to those resources, as outlined in Mesh setup docs for admins. Also note that Immersive spaces in Teams will continue to require the "AzureCloud" service tag over associated protocols and ports until its respective infrastructure transition is completed in upcoming months. This feature is on by default and accessible to all Mesh users. The Microsoft Mesh app on PCs: 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. After the rollout is completed at the end of July, you can optionally take action to simplify your network setup for using Mesh in your organization.