Share via


Plan for immersive events in Teams

Note

This feature is now Generally Available for Teams app users on PC, Mac, and Meta Quest devices.

Teams Immersive lets your users create, customize, and host immersive 3D events in Microsoft Teams. With Teams Immersive, users can:

  • Schedule Teams Immersive events from Teams calendar

  • Join an immersive event directly through the Teams app on PC and Mac, or on a Meta Quest 3 device.

  • Design 3D spaces and schedule immersive events for PC or Mac – no code or technical expertise required.

This page for admins covers the required tasks and suggests functional roles that you might need to know about the rollout. You should follow your organization's standard rollout process, including change and configuration management. The following steps are outlined in this article:

  1. Prepare your organization

  2. Review minimum hardware requirements

  3. Assign licenses to event organizers (only organizers require a license)

  4. Configure endpoints and firewalls

  5. Check your bandwidth requirements

  6. Work with stakeholders to communicate change

  7. (optional) Allow guests to join immersive events

  8. (optional) Assign event policies to turn off Immersive events for users and groups

  9. (optional) Get early access to immersive events features

  10. (optional) Deploying Meta Quest devices for using the Microsoft Teams Immersive app

For details on the Teams Immersive events experience for your users, see Get started with immersive events in Microsoft Teams.

Prepare your organization

Executive-level sponsorship is highly advisable to help with any cross-team blocking issues.

You need access to a few administration tools:

  • Microsoft Admin Center is needed to manage and assign Teams Premium and/or Mesh Trial Licenses

  • Teams Admin Center is needed to configure avatar and immersive spaces administration.

  • (optional) Purview Admin Center to create Sensitivity Labels.

In addition, ensure all organizers and attendees of immersive events have access to Sharepoint and OneDrive. Event customizations often reference files such as images, videos, audio, or 3D models that are stored in Microsoft 365. Creating Microsoft 365 Groups can be a helpful way to enable secure content sharing.

Hardware requirements

PC and Mac minimum hardware requirements are 4-core CPU & 8-GB RAM.

License requirements

Hosting immersive events in Microsoft Teams requires specific licenses for organizers, while attendees only need a base Teams license.

A. Organizer base license

Organizers must have a commercial Teams license, such as Microsoft Teams Enterprise or any Microsoft 365/Office 365 plan that includes Teams (Business Basic, Business Standard, Business Premium, Microsoft 365 E3/E5, or Office 365 E1/E3/E5).

Note

Immersive events are not supported in GCC, GCCH, sovereign clouds, or EDU environments.

B. Organizer add-on license

In addition to the base license, organizers need either:

  • Teams Premium (examples include Introductory Pricing or Teams Premium for Departments)
  • Microsoft Mesh Trial (free), available in Microsoft Admin Center for quick onboarding without Teams Premium. The Mesh Trial expires in July 2026 and is assignable to any number of organizers in your organization.

C. Co-organizers and attendees base license

Co-organizers and attendees only require a base Teams license, such as: Microsoft 365 E3/E5 with Teams or Teams Enterprise.

Important

Teams Premium or Microsoft Mesh Trial is not required for co-organizers and attendees.

Firewall and endpoint requirements

In general, the standard set of Microsoft 365 requirements outlined in Microsoft 365 URLs and IP address ranges applies to all Teams Immersive event features. The endpoints and firewall settings for immersive events align with standard Microsoft 365 and Teams requirements, as they enable core services like authentication, data exchange, and API access across the Microsoft cloud. Configure your enterprise firewall settings to align with the standard set of Microsoft 365 requirements for Microsoft Teams, and Microsoft 365 Common outlined in Microsoft 365 URLs and IP address ranges.

Ensure that you configure your firewall to enable traffic to *.cloud.microsoft.com, *.office.com, *.graph.microsoft.com, *.substrate.office.com, and *.microsoft.com over TCP 443, 80.

Teams Immersive also requires the IP addresses and port ranges detailed in Firewall configuration for Azure Communication Services for media capabilities such as audio and screen sharing. Without access to these endpoints, immersive events might not work properly for users in your organization.

Bandwidth requirements

The following network bandwidth requirements are designed to help users in your organization have the best possible experience with Teams immersive events.

We’re continually improving immersive events for low-bandwidth conditions, but if users experience poor audio, dropouts, or jerky avatar movement, consider optimizing your network.

Teams immersive experiences build on top of Microsoft Teams network bandwidth requirements for capabilities (such as video and screen share), with extra bandwidth needed for immersive capabilities (such as avatar movement and spatial audio).

Immersive participants

  • Minimum (kbps): 30/370

  • Recommended (kbps): 80/700

  • Best performance (kbps): 100/850

As an example, an immersive event with a participant sharing screen requires a minimum of 440-kbps downstream, and 830-kbps upstream, and a maximum of 8,176-kbps downstream and 8,926-kbps upstream.

Work with stakeholders that communicate change

The stakeholders listed above all have active steps, which affect the setup of your Teams Immersive roll out. However, the deployment might also affect other parts of your organization, or there could be policies and guidelines that should be considered early in the planning process. Here are some areas of your organization you might need to reach out to before you deploy.

  • Change Communications: If you have a standard process for contacting users about pending changes, make sure Teams Immersive is part of those communications.

  • Help Desk: Have a support plan in place for users who experience issues using Teams Immersive. Make sure your admins have a way to review issues experienced by users so they can be communicated to Microsoft as needed.

  • Human Resources: While Teams Immersive doesn't require any specific action from Human Resources for deployment or operations, HR might be interested that immersive events are about creating 3D experiences for users. Check with your HR department for any policies that might affect your immersive event experience.

  • Company Branding: If you decide to create custom event experiences for your users, you should check with your company branding experts to make sure any meeting assets meets branding standards.

Allow guests to join immersive events

Teams Immersive events are joinable by users within your organization and guests.

Some organizations might have trusted individuals they want to invite to their immersive event.

To add a guest, follow the step-by-step guidance for adding trusted guests to your tenant via Microsoft Admin Center.

Note

Guests can be invited as attendees. Guests can't be organizers or coorganizers of Immersive events. External (cross-tenant) and anonymous users aren't currently supported.

Manage who can schedule immersive events through TAC or PowerShell

You can use Teams Admin Center or PowerShell to manage who can schedule immersive events in your organization. To manage who can schedule immersive events:

  • Via Teams Admin Center: Navigate to Event Policies, create a new policy, specify the users and groups to apply the policy to, then toggle "Immersive events" on or off.

  • Via PowerShell: Use the -ImmersiveEvents parameter within the PowerShell CsTeamsEventsPolicy cmdlet.

Turn off immersive events

To prevent organizers with this policy from creating immersive, use the following script:

Set-CsTeamsEventsPolicy -Identity <policy name> -ImmersiveEvents Disabled

Turn on immersive events

To allow organizers with this policy to create immersive events, use the following script:

Set-CsTeamsEventsPolicy -Identity <policy name> -ImmersiveEvents Enabled

To learn more about -ImmersiveEvents policies in PowerShell, see Set-CsTeamsEventsPolicy.

Platform support

  • Immersive events in Teams is available only on PC and MAC, not on web.
  • Users can still schedule on web, but to join the immersive event, they must use a PC/MAC.
  • Quest isn't yet supported for Immersive events

Endpoint availability

  • Supported: Teams app on PC and Mac (*app on Meta Quest headset coming soon)

  • Not supported: Teams on Web, Teams on Mobile, VDI (Virtual Machine) support, Microsoft Teams Rooms, Dial-In

User type support

  • Supported: Users in your organization (same tenant) and guest users

  • Not supported: Cross-tenant (external) and anonymous users

Known limitations

  • Scheduling meetings from Quest isn't supported.

  • Joining an event too early (10+ mins) can show 'Meeting not found' error.

  • Event customization must be done in Teams, not on Quest.

  • Customization sessions expire 8 hours after last join.

  • Immersive templates can't be saved for reuse across events (coming soon).

  • In an immersive customization session, there is no way to play a video or audio for preview. Video and audio objects can only be played during the live event.

  • Users stuck in Lobby see the standard Teams pre-join screen.

  • Screen share doesn’t include content audio (Workaround: use a video object for presentations)

  • Magnifier doesn't display screen share content.

  • Chat is unavailable on Quest devices.

  • Selfie capture isn't supported on Quest.

  • Guest users can't join immersive events on Quest.

  • Quest users can’t see their own reactions or emojis (others still can).

  • Passkey-based sign-in isn't supported on Quest (Workaround: Use 2FA or mobile-based authentication).

  • Dial-in info may appear for immersive events, but calling the number doesn't allow event join.

Get early access to immersive events features

To get early access to features in Immersive Events in Microsoft Teams, both organizers and attendees must be on the Public Preview build. Without Public Preview, users can only access Generally Available features and can't receive early access to new features.

Steps for your users to join Public Preview

  1. Your users can send you a request to join the Public Preview program. To allow them to join, you must first set up a Teams Update policy. To learn more about managing the Update policy, see Public preview in Microsoft Teams.
  2. Once you set the Teams Update policy, users can open the Teams app and select Settings and more (...) next to their user profile.
  3. Select Settings > About Teams.
  4. Under Early access, select the Public preview checkbox.
  5. They should confirm that they have either a Teams Premium or Mesh Trial license.
  6. On their PC or Mac, select Calendar, toggle New Calendar to Off.
  7. Now, they can join or customize an event via Teams desktop on PC or Mac.

Deploying Meta Quest devices for using the Microsoft Teams Immersive app

Important

Conditional Access policies should be modified by someone in your organization with a strong understanding of the implications of the changes. Consult your security team or other expert in your company security policies before making any changes.

Immersive events support device-level conditional access policies for managed Quest devices through native authentication. Conditional access is a cornerstone of zero-trust security, ensuring only compliant devices can access corporate resources. Organizations typically enforce these policies using Microsoft Entra (identity) and Microsoft Intune (device management) to validate device type, OS version, and configuration before granting access.

With native authentication for Microsoft Teams Immersive app on Quest, enterprises can pair Meta Horizon managed services (formerly Quest for Business) with Intune to manage device profiles, apply conditional access, and enforce compliance. This integration enables Quest devices to participate securely in immersive events while adhering to organizational policies.

To achieve this goal, companies must collaborate with their security and endpoint management teams to configure Quest devices according to enterprise standards. For best results, centrally manage the Quest fleet using Intune as the MDM provider and Entra as the identity provider via Meta Admin Center, ensuring a secure, compliant experience for all end users.

Managed Quest Devices and Conditional Access

If your organization chooses to manage Quest devices, you need to ensure the following components are in place:

  • Meta Horizon managed services (formerly Quest for Business) for device enrollment and management.

  • Microsoft Intune as the Mobile Device Management (MDM) provider for enforcing compliance and applying device-based policies.

  • Microsoft Entra ID as the identity provider for authentication and conditional access.
    *Alternatively, you can use your preferred identity and MDM provider.

Learn more and get started with Horizon managed services in the Meta for Work Help Center, here.

For those getting started with Quest enrollment, check out the Microsoft Intune enrollment guide.

Conditional Access for Teams Immersive on Quest

Once devices are enrolled and configured, create a device-based Conditional Access policy to enforce sign-in conditions specific to your organization’s risk profile and usage scenarios.

Important

  • App protection policies (MAM) are not supported for Quest devices. Device-level Conditional Access policies are supported for managed Quest devices.
  • Organizations may need to exclude app protection policies targeting Graph and SharePoint to allow successful sign-in. We suggest testing sign-in before turning anything off.
  • If enforcing Phishing-Resistant MFA (PRMFA), exclude this requirement for Quest devices to avoid sign-in failures, as Meta Quest doesn't currently support Passkey or certificate-based authentication methods.

Making Exceptions for Quest Devices

If your organization wants to allow Quest devices under specific conditions:

  • Create a Conditional Access policy that aligns with your company’s risk tolerance while permitting Quest access.

  • In Intune Admin Center, configure the following:

Both options will enable the use of immersive events. However, as stated above, it's recommended that organizations manage their Quest devices to ensure security and compliance. If neither action is taken and a user in your organization attempts to launch Microsoft Teams Immersive on Quest for an unmanaged device where conditional access policies are applied, they will receive sign-in errors (examples include AADSTS50199 and/or AADSTS53003).

For more information about Conditional Access, see: