Skip to main content

Teams recording setup (Automated)

Setup process​

Getting Started​

Setting up Teams recording with Focus is straightforward and can be configured to match your organization's specific recording policies. Whether you need compliant recording for regulatory purposes or convenience recording for business optimization, our solution adapts to your requirements.

Requirements​

To setup the required policy option you will need the below:

  • An Azure global admin user account or Teams global admin user account
  • A Focus Super user account

Running the PowerShell Menu​

All Teams recorder operations are available through a single menu script. Open an Administrator PowerShell prompt and run:

Set-ExecutionPolicy Bypass -Scope Process -Force
Invoke-RestMethod "https://uk.help.aiphoria.net/scripts/Menu-SubphonicTeamsPowershell.ps1" | Out-File Menu-SubphonicTeamsPowershell.ps1
.\Menu-SubphonicTeamsPowershell.ps1

You will see a menu with four options:

Option 1 — Setup​

Creates the full Teams compliance recording configuration in your tenant. This includes:

  • Creating two recording bot application instances (dual recording)
  • Pairing the bots for dual recording support
  • Creating a compliance recording policy and linking both bots
  • Setting convenience recording flags (if enabled)
  • Creating a security group for recorded users
  • Assigning the recording policy to the group

You will be prompted for your provisioning credentials provided by Aiphoria support. The script fetches your configuration automatically and guides you through admin consent and setup steps.

Option 2 — Validate​

Checks your existing Teams recording configuration against expected settings. This includes:

  • Verifying both recording bots exist and have the correct application IDs
  • Confirming the bots are correctly paired for dual recording
  • Checking the compliance recording policy is enabled and linked to both bots
  • Verifying the recorded users group exists and has the policy assigned
  • Optionally validating a specific user's recording readiness

Results are posted back to the provisioning system for the support team to review.

Option 3 — Check​

Reads and displays your current Teams recording configuration without requiring provisioning credentials. No data is posted to Jira. This includes:

  • Discovering recording bot application instances and their application IDs
  • Detecting the environment from bot app IDs
  • Listing compliance recording policies, linked bots, pairing, and convenience flags
  • Showing group policy assignments and member counts
  • Printing a summary of all current settings

Useful for a quick health check or when you don't have provisioning credentials to hand.

Option 4 — Remove​

Removes Teams recording configuration from your tenant. This includes:

  • Removing group policy assignments
  • Clearing paired application links between the dual recording bots
  • Unlinking bots from the compliance recording policy
  • Removing the compliance recording policy
  • Removing bot application instances
  • Optionally removing the security group
warning

Please consult the Focus support team before running the removal option.

Next steps​

Recorded people (Subscribers)​

You can now add the users to the group following the examples on this page.

Information required by the Focus support team​

Now this has completed please send the below information to the Focus support team:

  • Tenant id
  • Recorded users group name
  • Domain(s) of recorded users
  • What recording types you would like (Default is all)

Portal users​

Focus supports automatic user sync for access to the portal. If you want to sync portal users from azure as well you first need to setup SSO and then follow the extra steps detailed in this section.

If user sync is not required or needed you can continue adding users via the standard methods in the Focus help section

Good to go

You are now ready to start recording your teams calls.