# Authenticated Calls with Microsoft Teams

## Requirements

To enable authenticated calls with Microsoft Teams, the following prerequisites must be met.

{% stepper %}
{% step %}

### Azure Communication Services service principal

Microsoft Teams interoperability for third party applications relies on **Azure Communication Services (ACS)**.

To allow authenticated calls, the Microsoft tenant must contain the **Azure Communication Services service principal**. This component allows applications to authenticate Teams identities and join meetings through the Microsoft communication APIs.

#### 🔍︎ Check if the Azure Communication Services service principal is installed

An administrator can verify whether the ACS service principal already exists in the tenant.

1. Sign in to the [Azure portal](https://portal.azure.com/)
2. Go to Microsoft Entra ID > Enterprise Applications > **All Applications**

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FiBdqVUpQpQSLQNL4Bkj2%2Fenterprise-apps.webp?alt=media&#x26;token=bb4655ed-312c-4e3f-b80f-c39eb9fc2b96" alt=""><figcaption></figcaption></figure>

3. Clear any filters that may be applied

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FthP8jIMRChLM9OkDfxcK%2Facs1.webp?alt=media&#x26;token=dea14368-16f9-4bc0-a85c-7b478420e19e" alt=""><figcaption></figcaption></figure>

4. In the search field, search for "Azure Communication Services"

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Ftmr6Jis6Cy04UGEJogGw%2Facs2.webp?alt=media&#x26;token=f8fede73-4490-4fb1-922a-0328f5b9a04b" alt=""><figcaption></figcaption></figure>

If the application appears in the list, the **ACS service principal is already installed** and no further action is required.

If the application does not appear in the list, follow the next steps to **proceed with the installation**.

#### ✅ Installing the Azure Communication Services service principal

If the ACS service principal is not present in the tenant, it must be created by an administrator.

#### Step 1. Open PowerShell

Open the Azure Portal and start a PowerShell session with administrative privileges.

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FFPJTNBUlRoeyfsMvL3GZ%2Facs3.webp?alt=media&#x26;token=5695d528-c11f-481e-a197-1b63d9360e4c" alt=""><figcaption></figcaption></figure>

#### Step 2. Install the Azure AD module (if not already installed)

```
Install-Module AzureAD
```

#### Step 3. Connect to the Microsoft tenant

Replace `TENANT_ID` with your tenant ID. Find your tenant ID [here](https://entra.microsoft.com/#view/Microsoft_AAD_IAM/TenantOverview.ReactView).

```
Connect-AzureAD -TenantId "TENANT_ID"
```

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2Fm6Ie4WRLi8mEVEm3FQ9B%2Facs6.webp?alt=media&#x26;token=8ce6fdfb-8794-4145-b31b-00bf4e60fd4b" alt=""><figcaption></figcaption></figure>

A Microsoft authentication window will appear where the administrator must sign in.

#### Step 4. Create the Azure Communication Services service principal

Run the following command:

```
New-AzureADServicePrincipal -AppId "1fd5118e-2576-4263-8130-9503064c837a"
```

This registers the **Azure Communication Services service principal** in the tenant and enables authenticated Teams calls for supported applications.
{% endstep %}

{% step %}

### Microsoft Teams license

An account with an active Microsoft Teams license is required in order to authenticate and join Teams meetings. The specific license type depends on the organization’s Microsoft 365 subscription.
{% endstep %}
{% endstepper %}

## Setup scenarios

<figure><img src="https://2978719120-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M2FbpP2hYI1Myy7hMs_%2Fuploads%2FCk4wWPbJcS629kuSIIgo%2Fmago-authenticated-calls.jpg?alt=media&#x26;token=7fd9214c-f8b1-483d-a274-54c028a135c4" alt=""><figcaption></figcaption></figure>

## When authentication is not configured

If authentication is not enabled, Mago can still join meetings as a guest participant.

In this scenario:

• the system may enter the meeting lobby\
• the participant appears as a generic device name\
• some meeting features may behave differently depending on the host organization’s policies