Communications Connector with Teams: Troubleshooting guide

This guide helps you find and fix application access policy issues that can stop Aptem's communications connector with Teams working, for example when Aptem can't access meeting transcripts.

In this article:

  1. Verify the application
  2. Prerequisites
  3. Step 1: List existing application access policies
  4. Step 2: Confirm the Aptem app ID is in a policy
  5. Step 3: Check which policy is applied to a user
  6. Step 4: Check whether the user's policy includes the Aptem app
  7. Step 5: Check group-based policy assignments and ranking (if applicable)
  8. Step 6: Check for direct (per-user) policy overrides
  9. Related articles

Verify the application

To confirm the Aptem Teams application exists in your Microsoft tenant:

  1. In the Azure Portal, go to Microsoft Entra ID.
  2. Select Enterprise Applications.
  3. Search for Aptem - MS Teams - Prod.
  4. Select the application to see its details.
  5. Copy the Application (Client) ID. You'll need it later.

If the application isn't there: enable the Microsoft Teams connector in Aptem again, and complete the steps in Configuring the communications connector with Microsoft Teams. Then come back to this guide and continue with the steps below.

Prerequisites

Before you run the commands in this guide:

  • Install or update the Microsoft Teams PowerShell module.
  • Connect to your Microsoft tenant in PowerShell:
Connect-MicrosoftTeams

Sign in with an account that has enough admin permissions.

Step 1: List existing application access policies

To see which application access policies exist in your tenant, run:

Get-CsApplicationAccessPolicy

What to look for

  • One or more policies should be listed.
  • Each policy includes:
    • Identity: the policy name
    • AppIds: one or more application IDs the policy allows.

If no policies are listed: no application access policy has been created yet. Create one that includes the Aptem Teams application ID. See Setting up an access policy for Microsoft Teams.

Once you've created the policy, come back to this guide and continue from Step 3.

Step 2: Confirm the Aptem app ID is in a policy

Find the application access policy that should allow the Aptem Teams application.

If you know the policy name:

Get-CsApplicationAccessPolicy -Identity "<PolicyName>"

If you don't know which policy to use, list all policies and check their AppIds:

Get-CsApplicationAccessPolicy | Select-Object Identity, AppIds

What to look for

  • The Aptem application ID (GUID) must be in the AppIds list of at least one policy.

If the Aptem app ID isn't in any policy: add it to an existing policy, or create a new policy that includes it:

Set-CsApplicationAccessPolicy -Identity "<PolicyName>" -AppIds {ENTER APP ID HERE}

Important: each user can have only one effective application access policy. The policy applied to the user must include every application that user is allowed to access, including Aptem.

Step 3: Check which policy is applied to a user

The Aptem integration works in the context of the meeting organiser, so check the application access policy applied to the user who organised the meeting.

Run:

Get-CsUserPolicyAssignment -Identity <organiserUPN>

Replace <organiserUPN> with the organiser's sign-in name, for example name@yourorganisation.co.uk.

What to look for

  • An entry where PolicyType = ApplicationAccessPolicy.
  • Note the PolicyName. This is the effective policy for that user.

If no ApplicationAccessPolicy is listed: the user doesn't have an application access policy. Aptem can't access their Teams content, such as transcripts, until one is applied.

Step 4: Check whether the user's policy includes the Aptem app

Using the policy name from Step 3, check the policy:

Get-CsApplicationAccessPolicy -Identity "<PolicyName>" | Select-Object Identity, AppIds

What to look for

  • Confirm the Aptem application ID is in the AppIds list.

If the Aptem app ID is missing, the policy exists but doesn't allow Aptem. Either:

  • add the Aptem app ID to this policy, or
  • assign the user to a different policy that already includes it.

If the Aptem app ID is there, continue to Step 5.

Step 5: Check group-based policy assignments and ranking (if applicable)

If application access policies are assigned to groups, run:

Get-CsGroupPolicyAssignment -PolicyType ApplicationAccessPolicy

What to look for

  • Which groups have an application access policy assigned.
  • The PolicyName and Rank for each group. A lower rank number has higher priority, so rank 1 takes precedence over rank 2.

Check that:

  • the meeting organiser is in a group with a policy that includes the Aptem app ID
  • if the user is in more than one group, the effective policy is the one from the group with the highest priority (lowest rank).

If a higher-priority group policy doesn't include the Aptem app ID, it blocks access, even if a lower-priority policy allows Aptem.

Step 6: Check for direct (per-user) policy overrides

A policy assigned directly to a user always takes precedence over group-based assignments.

From Step 3, if the user has a per-user ApplicationAccessPolicy that doesn't include the Aptem app ID, and you expected them to get a policy from a group, the per-user assignment is overriding the group policy.

To fix this, either:

  • update the per-user policy to include the Aptem app ID, or
  • remove the per-user assignment so the group-based policy takes effect.
Was this article helpful?
0 out of 0 found this helpful