Skip to main content

Microsoft Teams

Connecting Four/Four to Microsoft Teams

Written by Chris Lloyd
Updated over a week ago

Overview

Customers who have pre-existing recordings made in Teams can import these into Four/Four for analysis. Four/Four will review the calendars of team members who are users in Four/Four, find recorded meetings with participants outside your company and import them into the catalogue.

This document describes the process to give Four/Four access to retrieve these recordings.

If you need automated recordings across multiple platforms for your enterprise you may be interested in the Four/Four "Notetaker". Get in touch to find out more.

How to set up

Four/Four uses the Microsoft Graph to access meeting transcripts and attendance data on behalf of users.

There are two parts to this process

  1. Grant access using the 'Connect' button in the Four/Four connections interface.

  2. Configure an application access policy in Teams using PowerShell.

Prerequisites

  • You must be a Teams administrator in your Microsoft 365 tenant.

  • Install the Microsoft Teams PowerShell module if you haven't already, or use the embedded terminal in the Azure portal.

Creating the Application Access Policy

1. Connect to Microsoft Teams PowerShell

Connect-MicrosoftTeams 

2. Create the policy

New-CsApplicationAccessPolicy -Identity FourFour -AppIds "d4a8379f-7ee7-4c71-a02b-931b36dbe0fc" 

This creates a policy called "FourFour" that authorises the Four/Four application to access Teams meeting data. The provided App ID matches the 'Four/Four for Teams' application.

3. Grant the policy globally

Grant-CsApplicationAccessPolicy -PolicyName FourFour -Global

This applies the policy to all users in your tenant, allowing Four/Four to access meeting transcripts and attendance reports for any user.

Note: Changes to application access policies can take up to 30 minutes to take effect.

Verification

After waiting up to 30 minutes, go to Connections in Four/Four and check the Microsoft Teams status. The connection status should change from "Authentication failed" to "Connected".

Reference

For more detail on application access policies, see Microsoft's documentation: Configure application access policy.

Did this answer your question?