Overview
When you use the communications connector with Microsoft Teams, Microsoft requires that an application access policy is in place. This policy determines which applications can access Teams meeting artifacts (such as transcripts).
Because each user can only have one effective access policy at a time, it’s important to plan carefully. Below we explain the two scenarios you might face.
Scenario 1: No existing access policies
If you have not set up any access policies before, the process is straightforward:
- Create a new policy that includes the communications connector with Microsoft Teams.
- Assign that policy to the user accounts (or groups of users) who will be organising Microsoft Teams meetings where Aptem requires access.
Scenario 2: Existing access policies
If you already use access policies for other apps:
- If the Aptem app needs the same level of permissions as your existing app(s):
Add the Aptem app’s ID to the existing policy. Users who are already covered by that policy will then automatically allow Aptem as well. - If the Aptem app needs different permissions from your existing apps:
It is not possible to assign two different policies to the same user (one per app). Only one policy can be effective for each user. In this case, you must decide whether to: - Combine all required apps (including Aptem) into one single policy that grants the union of permissions, or
- Split users into separate groups, ensuring that each group only needs one policy with the appropriate set of permissions.