Skip to content

IT Admin Troubleshooting

Common issues IT administrators encounter when setting up Iristick.Teams, with error-specific solutions.

"AADSTS700016: Application not found in the directory"

Cause: The service principal hasn't been created in your tenant.

Fix: Complete the Grant Admin Consent step.

Verify: In the Azure Portal, go to Enterprise applications and search for "Iristick.Teams" or "RSIQ Teams". If it doesn't appear, the service principal is missing.

"Need admin approval" when signing in

Cause: The service principal exists, but admin consent hasn't been granted for the required permissions.

Fix: Use the admin consent URL.

Verify: Go to Enterprise applications > Iristick.Teams > Permissions. All permissions should show "Granted for [your tenant]".

Sign-in fails with no clear error

Cause: Could be various issues — expired credentials, conditional access policies, app role assignment, or account problems.

How to diagnose:

  1. Go to the Azure Portal > Microsoft Entra ID > Users
  2. Select the affected user
  3. Open Sign-in logs
  4. Filter for application RSIQ Teams
  5. The Failure reason column will show the specific error

See also: Conditional access blocking sign-in and "Not a member of a group that has access".

No meetings appear after successful sign-in

Cause: The meeting invitations came from an account without the right license tier, or the meetings are not scheduled for today.

Fix:

  • Ensure the meeting organizer has a Business Basic or higher license
  • Create a new meeting scheduled for today — only today's meetings are shown in the app
  • Check that the affected user was actually invited to the meeting

App stuck on loading screen after admin approved

Cause: The service principal exists, but permissions were not fully consented.

Fix: Go to Enterprise applications > Iristick.Teams > Permissions > click Grant admin consent for [your tenant].

Conditional access blocking sign-in

Cause: A conditional access policy in your tenant is blocking Iristick.Teams. Common triggers include policies that require compliant devices, specific locations, or MFA flows that the app cannot complete.

How to diagnose: Check the sign-in logs (Microsoft Entra ID > Users > [affected user] > Sign-in logs, filter for RSIQ Teams). The failure reason will reference a conditional access policy by name.

Fix: Review the policy identified in the logs and either:

  • Add Iristick.Teams as an excluded application in the policy, or
  • Adjust the policy conditions so they don't block the app

"Not a member of a group that has access"

Cause: Assignment required is enabled on the Iristick.Teams enterprise application, but the user has not been assigned to the User app role.

Fix:

  1. Go to the Azure Portal > Microsoft Entra ID > Enterprise applications
  2. Open Iristick.Teams
  3. Go to Users and groups
  4. Click Add user/group and assign the user or group to the User role

Once assigned, the user can sign in.