> ## Documentation Index
> Fetch the complete documentation index at: https://docs.truu.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Teams

> Let help desk agents send verifications from a Teams chat, and let employees verify themselves by typing verify me. Create an Azure Bot, connect it to TruU IDV, choose agents and use cases, and install the Teams app.

This page is for the Microsoft 365 administrator setting up verification in Teams. When you finish, agents in your help desk group can type `verify` and a name in a chat with the TruU bot and watch the request update live, and, if you turn it on, employees can type `verify me` to verify themselves.

This connector **starts** verifications.

## How it works for agents

1. An agent messages the bot in a 1:1 chat, or @mentions it in a channel: `verify jamie@contoso.com`.
2. The bot finds the person in your directory and shows a card with their name and UPN, a **use case** choice and a delivery choice (**Email** or **SMS**). SMS shows "number on file", never the digits.
3. The agent chooses **Send verification link**. The employee gets the link and verifies on their phone.
4. The card updates in place: link sent, opened, then **Verified**, **Failed** (also shown for a declined verification), **Needs review**, **Cancelled** or **Expired**. After a verification passes, it also shows any after-success action (for example "TAP issued"), never the code itself.

Only direct members of the Entra group you choose can send verifications. Anyone else gets "You're not in the group allowed to start verifications."

## How it works for employees

With **Self-service** turned on, employees can verify themselves, for example after getting a new phone:

1. The employee messages the bot directly (not in a channel) and types `verify me`, or taps **Verify me** on the welcome card.
2. If more than one use case is allowed for self-service, they pick what it's for, then choose **Start verification**.
3. The bot replies in the chat with their personal verification link. Nothing is sent by email or text.
4. They complete the verification in their browser, and the use case's after-success action runs, such as issuing a Temporary Access Pass or resetting PingOne MFA.

![Teams chat with the TruU Verify bot: the employee typed verify me, and the bot replied with a Verify it's you card listing use cases to choose from and a Start verification button](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/teams-verify-me.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=6b3ac57babc165bc80280f22d508e2f8)

An employee types verify me, picks what it's for, and starts. The link comes back in the chat.

Who the employee is comes from Microsoft's signed Teams identity (their Entra object ID), never from anything they type, so nobody can start a verification for someone else this way. Each person can start 3 self-service verifications per 15 minutes.

## Before you start

* A connected **Microsoft Entra ID** directory. Agents are checked against an Entra group, so this connector needs Entra. See [Connect Microsoft Entra ID](https://docs.truu.ai/idv/connect/directory/entra-id.md).
* An Azure subscription where you can create an **Azure Bot** resource.
* A Teams administrator who can upload a custom app in the Teams admin center.
* An Entra group containing the agents who may send verifications.
* An **Owner** or **Admin** seat in TruU IDV.

## Set it up

Open **Settings → Connectors → Microsoft Teams**.

![Microsoft Teams connector page with the messaging endpoint, Bot App ID, Directory tenant ID, Client secret, the agent group and use case choices, and a setup checklist](https://mintcdn.com/truu-2/ggexkQvmOZdl3yHs/images/idv/settings-teams-light.png?fit=max\&auto=format\&n=ggexkQvmOZdl3yHs\&q=85\&s=32cb29a71a1a681cc22b7386b9e96572)

**1. Create an Azure Bot**

In the Azure portal, create an **Azure Bot** resource. Choose **Single Tenant** as the app type, and let Azure create a new Microsoft App ID (app registration) for it.

**2. Point the bot at TruU**

In the bot's **Configuration**, paste the **Messaging endpoint** shown on the TruU page (use **Copy**), and save.

**3. Add the Microsoft Teams channel**

In the bot's **Channels**, add **Microsoft Teams** and accept the terms.

**4. Create a client secret**

Open the bot's app registration (**Configuration → Manage Password**) and create a client secret. Copy its value (shown once).

**5. Enter the bot's credentials in TruU**

Enter the **Bot App ID** (the Microsoft App ID), your **Directory (tenant) ID** and the **Client secret**. The secret is stored encrypted and never shown again.

**6. Choose agents and use cases**

Under **Help desk agents**, choose the Entra group in **Who can send verifications**, and tick the **Use cases** agents may pick (at least one; **Helpdesk** is the usual choice). Then choose **Connect Teams**.

**7. Turn on self-service (optional)**

Once connected, turn on **Self-service** ("Employees type verify me to verify themselves") and tick the **Use cases** employees may start, for example **Credential reset**. Self-service is open to everyone in your directory.

**8. Install the Teams app**

Download the TruU app package from the connector page and upload it in the Teams admin center under **Teams apps → Manage apps → Upload new app**. Make it available to your agents in the Teams admin center. If self-service is on, also add the app to a Teams setup policy for employees so they can find the bot.

## Test it

As a member of the agent group, open a chat with the TruU bot in Teams and type `verify` followed by your own email. Send the link to yourself, complete the verification on your phone, and watch the card update to **Verified**. If self-service is on, type `verify me` in a direct chat and complete the link it returns.

## Troubleshooting

| Symptom | Cause | Fix |
| - | - | - |
| The bot doesn't reply | The messaging endpoint isn't saved on the Azure Bot, or the Teams channel isn't added | Check the bot's **Configuration** and **Channels** |
| "You're not in the group allowed to start verifications" | The agent isn't a direct member of the chosen group (nested groups don't count) | Add the agent to the group directly |
| "No one matches" | The person isn't in the connected directory, or the name is ambiguous | Use their email address |
| A use case isn't offered on the card | It isn't ticked on the connector | Tick it under **Use cases** |
| The card stops updating | A status update was missed | Use **Refresh** on the card |
| The app isn't visible to agents | The app wasn't made available in Teams | Check the app's availability in the Teams admin center |
| "Self-service verification is turned off for your organization" | Self-service is off, or no use case is ticked for it | Turn on **Self-service** and tick at least one use case |
| "Message me directly to verify yourself" | The employee typed `verify me` in a channel | Use a 1:1 chat with the bot |
| "You've started 3 verifications in the last 15 minutes" | Self-service rate limit | Wait the time shown |

## Related

* [Help desk verification](https://docs.truu.ai/idv/use-cases/help-desk.md)
* [ServiceNow](https://docs.truu.ai/idv/connect/servicenow.md)
* [How use cases work](https://docs.truu.ai/idv/use-cases/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.