This article provides end-to-end instructions for deploying imper.ai for Microsoft Teams.
It covers the complete deployment lifecycle, including:
Reviewing required Microsoft Entra permissions
Connecting Microsoft Teams as a communication channel
Protecting Teams meetings by adding users
Deploying the imper.ai Microsoft Teams app (recommended)
(Optional) Configuring a custom meeting URL
Validating the deployment
Follow the steps in the order listed to ensure successful protection of Microsoft Teams meetings.
Prerequisites
Before connecting imper.ai to Microsoft Teams, administrators must ensure that all prerequisites are met and that deployment steps are completed in the correct order.
The Microsoft Teams integration relies on Microsoft Entra ID, Microsoft Graph, and Teams-specific permissions. Completing steps out of sequence may result in failed connections, incomplete monitoring, or missing verification signals.
Before you begin, ensure that:
You have Global Administrator or Application Administrator privileges in Microsoft Entra ID
Required Microsoft Graph permissions have been reviewed and approved
You have Admin access to the imper.ai Admin Console
Microsoft Teams is enabled for your organization
Microsoft Teams apps are allowed in your tenant
Outbound connectivity to Microsoft APIs is allowed
You have reviewed internal security and compliance requirements for third-party integrations
Some steps require Global Administrator or Application Administrator roles in Microsoft Entra ID.
Integration Components
The Microsoft Teams deployment consists of several dependent components that work together to enable meeting protection:
Microsoft Entra ID (Identity Provider)
Provides identity, user, and directory context used for verification and correlation.
Microsoft Teams Communication Channel
Enables imper.ai to monitor Teams meetings using Microsoft Graph APIs and event subscriptions.
imper.ai Microsoft Teams App (recommended)
Provides protected users with in-meeting visibility and security indicators.
Backend meeting protection functions without the app, but deploying it is recommended for real-time awareness.
Each component is configured separately and activated in sequence as part of the deployment process.
What Not to Do
Review the following constraints before proceeding with deployment.
Do not attempt to connect Teams before approving Entra permissions
Do not deploy the Teams app before completing backend integration
Do not mix end-user steps into admin onboarding
Do not assume the Teams app replaces backend monitoring
Deployment Procedure
Step 1: Open the Integrations Page
Log in to the imper.ai console.
Navigate to Admin Console > Integrations.
Step 2: Connect Microsoft Teams (communication channel)
This step establishes backend connectivity and enables imper.ai to monitor Teams meetings.
Log in to the imper.ai Admin Console using administrator credentials or SSO.
Navigate to Settings > Integrations.
Locate Microsoft Teams and click Connect.
The Microsoft Teams connection dialog opens.
Click Authorize with Microsoft.
Sign in using an account with Global Administrator or Application Administrator privileges.
Review the requested permissions.
Click Accept to grant tenant-level consent.
Verification and Status
After authorization:
You are redirected back to the imper.ai console
imper.ai completes backend validation
Microsoft Teams appears as Connected on the Integrations page
Once connected:
Microsoft Teams meetings are monitored automatically
Participant identity and meeting context are evaluated in real time
Verification and risk analysis are applied according to your organization’s policies
No end-user action is required at this stage.
Step 3: Protect Microsoft Teams Meetings
After connecting Microsoft Teams, you must explicitly add users to be protected.
Only meetings created by protected users are wrapped and monitored by imper.ai.
Enable Teams Protection
In the imper.ai Admin Console, navigate to Settings > Integrations.
Locate Microsoft Teams under Communication Channel Integrations.
Open the Microsoft Teams integration settings.
Add individual users to be protected.
Save your changes.
Protection is applied at the user level only.
Verification and Status
Once users are added:
imper.ai wraps Microsoft Teams meeting links created by protected users with a secure verification link
imper.ai begins monitoring those Teams meetings automatically
No additional configuration is required to activate protection
What Happens During a Microsoft Teams Meeting
For meetings created by protected users:
A participant clicks the wrapped Microsoft Teams meeting link.
imper.ai intercepts the link and initiates verification.
Identity and contextual signals are evaluated in real time.
After verification, the participant is redirected to the Teams meeting.
Verification results and meeting activity are available in the imper.ai console.
Step 4: Deploy the imper.ai Microsoft Teams app (recommended)
The imper.ai Microsoft Teams app provides protected users with in-meeting visibility and security indicators.
Backend meeting protection works without the app, but deploying it is recommended for real-time, in-meeting awareness.
What the Teams App Provides
When deployed, protected users can:
View real-time verification indicators during meetings
Receive alerts about unverified or high-risk participants
Access imper.ai security context without leaving the meeting
The app does not replace backend monitoring or verification logic.
Deploy the App
Sign in to the Microsoft Teams Admin Center.
Navigate to Teams apps > Manage apps.
Search for imper.ai.
Open the imper.ai app details page.
If the app is blocked:
Set the app status to Allowed.
Save your changes.
Assign the App
Go to Teams apps > Setup policies.
Select an existing policy or create a new one.
Under Installed apps, add imper.ai.
Assign the policy to:
All users
Specific users
Specific groups
Save the policy.
Post-Deployment Behavior
The imper.ai app loads automatically during Teams meetings
Protected users see imper.ai indicators inside the meeting UI
No manual configuration is required by end users
Users may need to restart Teams for the app to appear initially
Managing or Removing the App
Administrators can manage or remove the app at any time from:
Microsoft Teams Admin Center > Teams apps
Removing the app:
Disables in-meeting visibility
Does not disable backend Teams meeting protection
Step 5: (Optional) Configure a custom meeting URL
Navigate to Meeting Protection > Custom URLs in the imper.ai console.
Configure a branded meeting URL for Teams meetings.
Save the configuration.
This step can be completed at any time after the Teams integration is connected.
➡ See Setting Up a Custom Meeting URL (Teams)
Step 6: Validate the Deployment
Create a test Microsoft Teams meeting.
Confirm that the meeting link is wrapped by imper.ai.
Verify participant verification and monitoring behavior.
Check integration status and logs in the imper.ai console.