Skip to content

Install in Your Tenant

Installing Iristick.Teams in your Microsoft tenant takes one click in a browser. Two service principals must end up in your Microsoft Entra directory before users can sign in and call:

  • Iristick.Teams (9e29744b-7398-4b14-8ba9-4b341b36c0b4) — handles sign-in and Graph API access
  • Azure Communication Services (1fd5118e-2576-4263-8130-9503064c837a) — Microsoft's first-party app that bridges calls into Microsoft Teams

The standard admin-consent URL provisions both in most tenants, but not always. Verify both exist before handing the app to users.

Open the following URL in a browser and sign in with a Global Administrator, Application Administrator, or Cloud Application Administrator account:

https://login.microsoftonline.com/common/adminconsent?client_id=9e29744b-7398-4b14-8ba9-4b341b36c0b4

Review the requested permissions and click Accept.

This action:

  • Creates the Iristick.Teams service principal in your tenant
  • Grants admin consent for the delegated Microsoft Graph and ACS permissions
  • Makes the User app role available for restricting access
  • Usually also creates the Azure Communication Services service principal — but see Step 2.

Once complete, Iristick.Teams appears under Enterprise Applications in the Azure Portal.

Alternative: grant consent by signing in from the app

If Iristick.Teams is already installed on a device, an Application Administrator can grant consent during the sign-in flow:

  1. Open Iristick.Teams on the device
  2. Sign in with an account that has the Application Administrator role (or higher)
  3. Review the requested permissions and click Accept

This achieves the same result as the admin-consent URL.

Step 2: Verify the ACS Service Principal Exists

The Azure Communication Services service principal should be provisioned automatically when you grant consent in Step 1, but some tenants require it to be created explicitly. Always confirm.

In the Azure Portal:

  1. Go to Microsoft Entra ID → Enterprise applications
  2. Set the application type filter to All Applications
  3. Search for Azure Communication Services or its App ID 1fd5118e-2576-4263-8130-9503064c837a

If it appears: you're done. Continue to Step 3.

If it does not appear: provision it manually using one of the methods below.

Open this URL and sign in with an account that has consent rights:

https://login.microsoftonline.com/common/adminconsent?client_id=1fd5118e-2576-4263-8130-9503064c837a

Accept the consent prompt. The ACS service principal will be created in your tenant.

Connect-MgGraph -Scopes "Application.ReadWrite.All"
New-MgServicePrincipal -AppId "1fd5118e-2576-4263-8130-9503064c837a"

az ad sp create --id 1fd5118e-2576-4263-8130-9503064c837a

Re-check Enterprise applications afterward to confirm the service principal now appears.

Step 3: Verify the Iristick.Teams Service Principal Exists

In Enterprise applications, search for Iristick.Teams (it may also appear as RSIQ Teams in some tenants). Open it and check:

  • Permissions → all listed permissions should show Granted for [your tenant]
  • Properties → the app is Enabled for users to sign-in

Next

Verify & Restrict Access — sign in on a test device and optionally limit which users can access the app.

Having issues? See Troubleshooting.