Skip to main content

Microsoft Teams Identity Join

To enable a Mersive Pod to join Microsoft Teams meetings as an authenticated, named participant, your organization must complete a one-time setup in your Microsoft 365 and Azure environment.

During setup, your IT administrator will:

  • Either create a dedicated Microsoft Teams room or equipment resource account if the Mersive Pod is to be shared, or the Mersive Pod may be assigned to a dedicated user account.

  • Assign a Teams Room Basic license to the resource account.

  • Create and manage the Azure Communications Service resource used for Teams meeting participation and billing.

  • Grant the Mersive Teams Connector permission to use that resource on behalf of your organization.

Important

The Mersive Teams Connector is a managed Mersive application. Your IT administrator only needs to configure the required resources and permissions within your organization’s tenant.

Requirements

All setup steps are required. No fallback or alternative connection method exists. If any required component is missing or incorrectly configured:

  • The Mersive Pod cannot join Microsoft Teams meetings.

  • Join requests will be rejected immediately.

  • A specific error message will be displayed to help identify and resolve the issue.

For troubleshooting guidance, refer to the Troubleshooting section later in this document.

Before You Begin

Ensure the following requirements are in place before starting the setup process:

  • A valid Microsoft 365 or Microsoft Entra ID (work or school) tenant.

    • Personal Microsoft accounts are not supported.

  • One of the following administrative roles in your tenant to complete the Azure and application-authorization steps during setup:

    • Global Administrator

    • Application Administrator

    • Cloud Application Administrator

    These permissions are required to complete the Azure and application-authorization steps during setup.

  • An eligible Microsoft Teams license assigned to the room account used by the Mersive Pod. Supported licenses include:

    Note

    Consumer subscriptions, such as Microsoft 365 Family, are not supported.

  • Microsoft 365 Business Basic

  • For Resource Accounts:

    • Microsoft Teams Room Basic

    • Microsoft Teams Room Pro

  • For User Accounts:

    • Microsoft 365 Business Basic, Standard, or Premium

    • Microsoft 365 E3 or E5

    • Other Teams-enabled Microsoft 365 plans

Note

Consumer subscriptions, such as Microsoft 365 Family, are not supported.

Having these prerequisites in place before you begin will help ensure a smooth setup experience and prevent authentication or meeting-join issues later.

Get Started

  1. Create or Use an Existing Room Resource or User Account

    Create or use an existing dedicated room or equipment resource account that the shared Mersive Pod will use when joining meetings. Create or use an existing user account that the assigned Mersive Pod will use when joining meetings.

    1. Sign in to the Microsoft 365 Admin Center: admin.microsoft.com

    2. Create an account:

      • For a shared Mersive Pod: Navigate to Resources > Rooms > Equipment > Add resource > Resource Type = Room or Equipment.

      • For an assigned Mersive Pod: Navigate to Users > Add User

    3. Enter a recognizable name and email address, such as Room 1: room1@yourtenant.onmicrosoft.com.

    4. Assign an eligible Microsoft Teams license to the account.

    5. Create a password and save it securely. You will need these credentials later when connecting the room account.

    6. Complete the setup and verify that the account appears in Active users with the assigned license.

      Note

      Use a clear naming convention so you can easily identify the account's purpose in your Microsoft 365 environment.

  2. Add the Azure Communication Services Application to Your Tenant

    To enable Teams meeting participation, Microsoft's Azure Communication Services (ACS) application must be available in your tenant.

    1. Install and connect to the Microsoft Graph PowerShell module using an account with the required administrator permissions.

    2. Run the following commands:

      ### Preparation ### 
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser 
Install-Module PowerShellGet-Scope CurrentUser -Force 
Install-Module Microsoft.Graph.Applications -Scope CurrentUser -Repository PSGallery -Force   

### Connect ### 
Connect-MgGraph -Scopes "Application.ReadWrite.All" -NoWelcome   

### See if principal is there already ### 
Get-MgServicePrincipal -Filter "appId eq '1fd5118e-2576-4263-8130-9503064c837a'"   

### IF not, add it ### 
New-MgServicePrincipal -AppId
"1fd5118e-2576-4263-8130-9503064c837a"

    3. Sign in with your administrator account when prompted.

    Note

    This is a one-time setup per Microsoft 365 tenant. If the service principal already exists, an error indicating that it is already present can be safely ignored.

  3. Create an Azure Communication Services Resource

    Meeting participation is billed to your organization's Azure subscription, so you must create or designate an Azure Communication Services resource.

    1. Sign in to the Azure Portal.

    2. Search for Communication Services and select Create.

      If your organization already has a dedicated ACS resource for this purpose, you can use the existing resource instead.

    3. Specify the resource group, resource name, and region.

    4. Select Review + Create, then Create.

    5. After deployment is complete, open the resource and navigate to Settings > Keys

    6. Copy the full Connection string value.

      Important

      Copy the entire connection string, including both the endpoint and access key. The value should look similar to:

      endpoint=https://your-resource.communication.azure.com/;accesskey=xxxxxxxxxxxxxxxx

      Do not copy only the endpoint URL or only the access key.

  4. Configure the Microsoft Teams Integration in the Mersive Portal

    1. In the Mersive portal, navigate to the Microsoft Teams Integration page.

    2. Paste the Azure Communication Services connection string from Step 3 into the ACS Connection String field.

    3. Select Apply.

    4. Select Sign in with Microsoft and sign in with your Microsoft 365 administrator account.

    5. Review and approve the requested permissions.

      During this step, your organization grants the Mersive Teams Connector permission to access the Teams functionality required for meeting participation.

      Note

      You are granting consent to a Mersive-managed application. You don't need to register an application or configure anything in your Microsoft Entra ID tenant.

    6. Once you grant consent, the Sign in with Microsoft option is replaced with a Disconnect option.

  5. Connect the Room Account

    After you configure the integration, connect the room account created in Step 1.

    1. On the Microsoft Teams Integration page, locate Conference-Join Room Account.

    2. Select Connect Room Account.

    3. When prompted to sign in, use the room account credentials created in Step 1, not your administrator account.

    4. Review and accept the consent prompt. When authentication is complete, the dialog closes automatically.

    5. The integration page displays the connected room account and provides a Sign Out option.

Depending on your organization’s consent and permissions configuration or use of Microsoft Security Defaults, users will initially be required to have Global Administrator approval for the permissions used by the Mersive Teams Connector app registration. The delegated permissions are:

  • User.Read

  • profile

  • openid

  • offline_access

  • Calendars.Read

  • Teams.ManageCalls

  • Teams.ManageChats

Optionally, you may grant Admin consent for the Mersive Teams Connector app’s permissions once registered, or you may choose to adjust your organization’s “Consent and permissions” configuration. Please ensure the suggested changes fit your organization’s needs.

Example:

  1. Log in to the Microsoft Entra portal.

  2. Select “Enterprise apps” from the left menu pane.

  3. Select “Consent and permissions” from the left menu of the Enterprise apps pane.

    1. a. Select “Allow user consent for apps from verified publishers, for selected permissions”.

  4. Select “Permission classifications” from the left menu of the Consent and permissions pane.

  5. Add the delegated permissions used by the Mersive Teams Connector.

The Mersive Teams Connector uses industry-standard, low-risk permissions. Microsoft Security Defaults do not include the Azure Communication Services Teams permissions, which will prompt users to request approval or otherwise require a Global Administrator to approve the connection. The example instructions provide a path to allow end-users to accept without requiring Global Administrator approval, depending on your organization’s security requirements.

The Mersive Pod is now configured to join Microsoft Teams meetings as the connected room account. In most cases, no additional action is required after setup. Authentication is refreshed automatically in the background, and you only need to reconnect the account if:

  • Someone manually signs out of the room account.

  • The room account password has been changed.

  • The account remains inactive long enough for its authentication token to expire.

In this section: