Overview
Microsoft Teams is a collaboration and communication platform that brings together chat, meetings, file sharing, and app integrations in one workspace. Persona’s integration with Microsoft Teams supports two main use cases:
- Channel alerts: Post a message to a Teams channel when a key event occurs in Persona, for example when an inquiry needs review, a case is created, or a high-risk result comes in.
- Verified meeting access: Verify a person’s identity before they join a high-trust Teams meeting.
Both run from Persona Workflows, which reduces context switching and manual copy-paste for fraud, risk, compliance, and operations teams.
Benefits
Real-Time Alerts: Deliver instant notifications to Teams channels when key events occur in Persona, such as verification failures, flagged reports, or case escalations.
Faster Triage: Route the right context to the right people and channels, reducing time-to-resolution for investigations.
Verified Meeting Access: Give people the meeting link as part of, or after, their Persona verification, so you know who joins your high-trust meetings.
Reduced Manual Work: Eliminate repetitive copy-paste tasks and keep updates and meeting links automatically flowing from Persona into Teams.
Integration Features
Persona’s Microsoft Teams integration covers channel messaging and meeting creation. Key capabilities include:
- Discover Teams and Channels: Identify the right Teams and channels in your organization for targeted message delivery.
- Send Structured Messages: Post alerts with text or HTML formatting, subject lines, and importance flags to ensure critical updates stand out.
- Create Teams Meetings: Create a Teams meeting and get its join link, for a meeting that people join after they verify.
- Automate Workflow Actions: Trigger messages based on Persona events like verification failures, flagged reports, or case escalations.
- Manage Notifications Efficiently: Direct messages to specific channels and stakeholders, keeping information organized and actionable.
Setting up the Microsoft Teams integration
Prerequisites
To set up the Microsoft Teams integration, ensure you have:
- Admin access to your Microsoft Teams account
- Necessary API permissions to access Microsoft Teams credentials
When you connect, Persona requests these delegated Microsoft permissions for the account you sign in with: Team.ReadBasic.All, Channel.ReadBasic.All, ChannelMessage.Send, OnlineMeetings.ReadWrite, User.Read, and offline_access. Some Microsoft tenants require an administrator to grant consent for these permissions before a user can connect. If the sign-in window asks for admin approval, ask your Microsoft administrator to grant admin consent for the Persona app.
Setting up the Microsoft Teams Credentials
- In the Persona Dashboard, navigate to Integrations > Marketplace and click on Microsoft Teams.
- Click on Add Credential at the top of the page.
- Enter a Nickname for Credential and click Continue.
- In the Microsoft sign-in window, log in with your Microsoft account and review the requested permissions.
- Click Accept to grant access and finish connecting the credential.
- (Optional) Click Test on the credential to confirm it’s working.
Using the Microsoft Teams integration in a workflow
- Create a new workflow, or open an existing workflow you’d like to update.
- Add a new Action step > Integrations.
- Select the Microsoft Teams integration and choose your Teams credential.
- Configure the input fields (e.g., Team, Channel, Message content) based on your use case.
- Save and publish the workflow.
Microsoft Teams Operations Overview
Persona can create online meetings, send messages to channels, and retrieve team/channel details using Microsoft Teams’s API. Use the channel steps to alert your team, and use Create Online Meeting to set up meetings that people join after they verify.
See below for a comprehensive list of available Workflow Action steps and possible configurations for the Microsoft Teams integration:
List Teams
Returns a list of Teams in your organization. Use this step to discover the correct Team to target before selecting a channel or sending a message.
Configuration Steps:
- Optionally add:
- Filter: Provide a filter expression (e.g., search by display name).
- Select Properties: Choose specific fields to return (e.g., id, displayName, description).
- Page Size: Limit the number of results per page.
- Skip Token: Use this when continuing from a previous paginated response.
- Include Count: Include a total record count in the response.
List Team Channels
Retrieves channels for a specific Team. This helps you select the exact channel where alerts should be posted (e.g., a standard “risk-alerts” channel or another team’s collaboration channel).
Configuration Steps:
- Provide values for required fields:
- Team ID
- Optionally add:
- Filter: Narrow channels by criteria (e.g., membership type).
- Select Properties: Choose which fields to include in the response.
Send Channel Message Workflow Action Step
Posts a new message to a specified channel. You can send either plain text or HTML content, and optionally include a subject line and importance level to highlight urgent updates. This is ideal for broadcasting Persona case updates, verification results, or risk alerts to the right audience without leaving Persona.
Configuration Steps:
- Provide values for required fields:
- Team ID
- Channel ID
- Message Content
- Content Type: Choose text or HTML
- Content: The message body (e.g., summary, links to the Persona Case)
- Optionally add:
- Subject: Provide a short subject line for the message.
- Importance: Set the importance (normal, high, or urgent) to visually elevate critical alerts.
The step returns the new message, including its Web URL. Use the Web URL to link back to the message in Teams from later steps.
Tips:
- Use HTML to emphasize key details (e.g., bold the case ID or add structured links).
- Target different channels based on severity or event type to improve triage.
Create Online Meeting
Creates a Microsoft Teams meeting and returns a join link that participants can use. Use this step to create a meeting that a person joins after they verify their identity with Persona. See Verify people before they join a meeting.
Configuration Steps:
- Provide values for required fields:
- User ID: The object ID or user principal name (email) of the meeting organizer.
- Subject: The meeting title.
- Start Date Time: The meeting start time in ISO 8601 format, in UTC (e.g., 2026-05-10T15:00:00Z).
- End Date Time: The meeting end time in ISO 8601 format, in UTC.
- Optionally add:
- Allowed Presenters: Choose who can present (Everyone, Organization, Role Is Presenter, or Organizer Only). The default is Everyone.
- Allow Attendee Camera: Let attendees turn on their camera. The default is on.
- Allow Attendee Microphone: Let attendees turn on their microphone. The default is on.
- Allow Meeting Chat: Set meeting chat to Enabled, Disabled, or Limited. The default is Enabled.
- Allow Teamwork Reactions: Let attendees use reactions. The default is on.
- Attendees: List participants by user principal name (email), each with a role (Attendee, Presenter, Producer, or Co-organizer). The default role is Attendee. This sets each person’s role in the meeting. It does not invite them.
This step does not send calendar invites. The meeting is not added to anyone’s calendar, and attendees do not get an email. Share the Join Web URL with them, for example in a Send Channel Message step.
The step returns the meeting details, including the Meeting ID, Join Web URL, Join Meeting ID, start and end times, meeting settings, and participants. Use the Join Web URL in later steps, for example in a channel message, to share the meeting link.
Verify people before they join a meeting
There are two ways to require identity verification before a person joins a Teams meeting.
Redirect to the meeting after verification
The person goes to the meeting when they finish the verification flow.
- In your workflow, add a Create Online Meeting step.
- Set the inquiry’s redirect URL to the Join Web URL that the step returns.
- Send the inquiry link to the person. When they finish the verification flow, Persona sends them to the Teams meeting.
The redirect occurs when the person completes the flow, before Persona makes a pass or fail decision. A person who fails verification can still get to the meeting. If your organization restricts redirect domains, add the Teams meeting domain to your allowed list.
Share the link only after approval
This is the stricter pattern. The person gets the link only if their verification is approved.
- Wait for the verification to be approved in your workflow.
- Add a Create Online Meeting step after the approval.
- Send the Join Web URL to the person, for example by email or through your own system.
The Send Channel Message step posts to a Teams channel, not to a person outside your organization. Use it to tell your team that the meeting is ready.
FAQs
Can I post to private channels?
You can post to any channel that your connected account has permission to access. Enter the Team ID and Channel ID in the step’s input fields. If a channel is missing from the List Team Channels output, or a message fails to post, confirm that your account is a member of the corresponding Team and channel.
How do I find the right Team and Channel IDs?
Add the List Teams and List Team Channels workflow action steps to your workflow. Their output includes the ID of each Team and channel. Enter those IDs in the Team ID and Channel ID input fields of your message step.
Can I format messages?
Yes. Messages support text or HTML. Use HTML to add structured formatting (e.g., headings, bold text, links) so critical information stands out in busy channels.
How do I find the User ID for creating a meeting?
Use the email address (or Microsoft user ID) of the Microsoft account that you connected to Persona. Persona creates meetings as that connected user, so that account is the meeting organizer.
Can I create meetings on behalf of other users?
The integration uses the delegated OnlineMeetings.ReadWrite permission, so Persona creates meetings as the user of the connected Microsoft account. Microsoft requires additional tenant configuration, such as an application access policy, to create meetings for other users. Use the connected account’s user as the organizer, and add other people as attendees.
Plans Explained
Microsoft Teams Integration by plan
| Startup Program | Essential Plan | Growth Plan | Enterprise Plan | |
|---|---|---|---|---|
| Microsoft Teams Integration | Not Available | Not Available | Limited | Available |