MC855701: Microsoft Teams: Updated network setup requirements for immersive spaces

Announcement IDMC855701Published Date08-08-2024
ServiceGeneralLast Updated08-08-2024
CategoryStay informedExpiration Date12-27-2024
Roadmap IDAction Required by Date
TagsAdmin impact, Feature update, User impact


Summary
                Microsoft Teams is updating to a unified backend infrastructure for immersive spaces, simplifying network setup. Rollouts begin mid-August 2024, with full availability by late September 2024. Organizations will need fewer endpoint and firewall configurations, and users won't need to consent to Mesh's terms for spatial audio. No admin action is required before the rollout.


More Information

Coming soon to Microsoft Teams: We are starting to transition immersive spaces in Teams to the same backend infrastructure as the rest of Microsoft Teams for spatial audio. Once complete, this rollout will simplify network setup requirements needed to roll out immersive spaces with the Microsoft Mesh app in Teams to your organization.

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

How this will affect your organization:

Before the rollout

Immersive spaces in Teams require endpoint and firewall requirements outlined in Endpoints and Firewall Ports for immersive spaces in Teams.

During the rollout

  • You may find that you don't need to configure the endpoint and firewall requirements outlined in Endpoints and Firewall Ports for immersive spaces in Teams.
  • We recommend supporting the full set of endpoint and firewall requirements for immersive spaces to prevent an interruption in service during rollout.

After the rollout

  • 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, as documented in Firewall configuration for Azure Communication Services.
  • As part of this, you will no longer need to allow traffic to IP addresses in the "AzureCloud" service tag over the protocols and ports, as outlined in the immersive spaces 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 immersive spaces in Teams.

This feature is on by default and accessible to all Mesh users.

Immersive spaces in Teams

Switching to Immersive space (3D) view during a meeting from the View menu in Teams:

Switching to Immersive space

An example of an immersive space in Teams:

immersive space 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.

After the rollout is completed late September, you can optionally take action to simplify your network setup for using Mesh in your organization.

Previous Post Next Post