Skip to main content

Documentation Index

Fetch the complete documentation index at: https://relevanceai-changelog-migration.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

With Relevance AI’s Microsoft Teams integration, you can connect your Teams workspace to your AI agents, enabling them to monitor channels, respond to messages, and automate communication workflows directly within Teams. Relevance AI uses a unified Microsoft authentication that works across Teams, Outlook, SharePoint, and OneDrive — connecting one account gives you access to all services. See the Outlook integration and SharePoint knowledge source pages for details on those services.

Prerequisites

Before setting up the Microsoft Teams integration, ensure you have:

Relevance AI account

An active project in Relevance AI

Microsoft Teams access

Desktop or web app within your organization

Sufficient permissions

Enterprise organizations may require admin consent from a Global Administrator or Teams Administrator (see Admin consent & permissions)

A Teams channel or chat

At least one channel or chat where you want your agent to operate

Setup overview

Setting up Microsoft Teams requires two separate steps. Both are required — completing only one is not enough.

1. Connect your Microsoft account

Authenticate via OAuth in Relevance AI to grant access to Microsoft services.

2. Install the Relevance AI app in Teams

Add the app from the Teams app store to the channels and chats where your agent should operate.

Step 1 - Connect the integration

1

Open the Integrations page

In the Relevance AI dashboard, click Integrations & API Keys in the sidebar.
2

Find the Microsoft integration

Locate Microsoft (Teams, Outlook, SharePoint, OneDrive) in the list of available integrations.
3

Add the integration

Click Add Integration. A pop-up window will open for Microsoft sign-in.
If a pop-up window doesn’t appear, check your browser’s pop-up blocker settings and allow pop-ups from Relevance AI.
4

Sign in to your Microsoft account

Enter your Microsoft credentials in the pop-up window and sign in.
The Microsoft account you sign in with determines which Teams, channels, and chats are visible to the integration. Use the account that has access to the channels your agent needs to operate in.
5

Grant permissions

Review the requested permissions and click Accept. These permissions allow Relevance AI to read and send messages, access channel and team information, and maintain a persistent connection.
If you see a “Need admin approval” message, your organization’s Azure AD / Entra ID tenant restricts third-party app consent. See Admin consent & permissions for next steps.
For a full list of requested scopes, see the Permissions reference.
6

Confirm the connection

Once complete, you’ll see a green Connected status indicator next to the Microsoft integration in Relevance AI.

Step 2 - Install the Relevance AI app in Microsoft Teams

After connecting your Microsoft account, you need to install the Relevance AI app in Teams so your agents can interact with channels and chats.
The Relevance AI app must be added to every channel and group chat where you want your agent to respond. Triggers and tool steps will not work in channels or chats where the app has not been added.
1

Open the Teams app store

In Microsoft Teams, click on Apps in the left sidebar.
2

Search for the Relevance AI app

Type Relevance AI in the search bar and locate the app in the results.
If you don’t see the Relevance AI app, your organization may restrict third-party app installations. See Admin consent & permissions for how to request approval.
3

Install the app

Click Add or Install to add the Relevance AI app to your Teams workspace.
4

Add the app to specific channels and chats

After installing, add the app to each channel or group chat where you want your agent to operate.
  1. Navigate to the channel where you want your agent to work
  2. Click the + icon at the top of the channel to add a tab or app
  3. Search for Relevance AI in the app picker
  4. Select the app and click Save
5

Verify the app is active

Confirm the Relevance AI app appears in the channel’s app list and that the channel shows up in the trigger setup dropdown in Relevance AI.

Triggers

Trigger conversation in Teams
Triggers let your agents respond to Teams messages automatically, so your team can get answers, run workflows, and escalate issues without leaving their existing conversations. Instead of switching to a separate tool, users interact with agents right where they already communicate. The Relevance AI app is available on the Microsoft Teams marketplace. Users can @mention or message the app in channels, group chats, or direct messages to trigger agents and have two-way conversations directly in Teams. The same trigger setup also works for workforces.
Teams triggers activate only on new messages. They do not trigger on new chat creation, group creation, or webhooks.

Setting up a trigger

Before setting up a trigger, confirm that you have completed both Step 1: Connect the integration and Step 2: Install the Relevance AI app.
1

Open your agent's settings

Navigate to your agent in Relevance AI and go to the Triggers section.
2

Add a Microsoft Teams trigger

Click Add Trigger and select Microsoft Teams from the list.
3

Select the Team and channel

Choose the Microsoft account you connected, then select the Team and specific channel or chat you want to monitor.
Only channels where the authenticated user is a member and the Relevance AI app has been added will appear in the dropdown.
4

Configure trigger conditions (optional)

Set up keyword matching to filter which messages activate your agent. Leave the keyword field empty to trigger on all messages, or enter specific keywords separated by commas. The trigger checks whether any of the keywords appear anywhere in the message text (case-insensitive).
5

Write agent instructions

In the Core Instructions section, write a prompt that guides how your agent should respond — including its role, tone, and when to respond.
Set tool permissions to “approval mode” initially so your agent asks before sending messages. Switch to autopilot once you’re confident.

How triggered conversations work

Once a trigger fires, the agent responds directly inside Teams with the following capabilities:

Threaded conversations

Agent replies are threaded in the channel. Conversation threads stay active for 30 minutes.

Adaptive Cards

Responses are delivered as Microsoft Adaptive Cards — rich, interactive messages inside Teams.

Typing indicator

Teams displays a typing indicator while the agent is processing a response.

File and image attachments

Agents can receive and process inline images, pasted screenshots, and uploaded files (PDFs, documents, images) from Teams conversations.

Proactive messages

Agents can send direct messages to users without the user initiating first.

Workforce triggers

Teams messages can trigger an entire workforce, not just an individual agent.
Messages that contain only attachments with no text will show a “[N attachments]” indicator to the agent.

Tool steps for Microsoft Teams

The Microsoft Teams integration provides actions your agents can use as tool steps in their workflows.

Send Channel Message

Post a message to a specific Teams channel

Send Chat Message

Send a direct message in Teams

Create Channel

Create a new channel in a Team

List Teams

Get all teams the authenticated user belongs to

List Channels

Get all channels in a Team

Retrieve Chat Messages

Fetch messages from a specific chat conversation

Search Messages

Search for messages across Teams channels and chats

List Shifts

Retrieve shift information from Teams

Microsoft API Call

Make custom calls to Microsoft Graph API
Most Microsoft Teams tool steps are currently in beta. Please report any issues to our support team.

Agent alerts

Agent notification configuration
You can receive notifications in Microsoft Teams when your agents enter specific statuses or encounter tool errors. This helps you monitor agent activity and respond quickly when issues occur.
Agent notifications are currently in beta and may not be available for all accounts.

Setting up Teams notifications

1

Open the escalations panel

Navigate to your agent and click the Build tab, then click Escalations in the left sidebar.
2

Add an agent notification

Under “Agent Notifications”, click Add agent notification.
3

Configure notification settings

Select Microsoft Teams as the platform, then choose the notification trigger: Agent enters status (select specific task statuses such as “Running”, “Completed”, or “Failed”) or Tool errors (any tool) to get notified when any tool encounters an error. Select a Microsoft Teams account and the channel where you want to receive notifications. If no accounts appear, complete the connection steps first.
4

Publish changes

Click Publish changes to save your notification configuration.
Test the notification by running your agent — you should receive a notification in your selected Teams channel based on your configured triggers.

What you’ll receive

When a notification is triggered, you’ll receive a message in your Teams channel containing:

Agent status and context

Agent name, status, and task details

Direct link

Link to view the full task in Relevance AI

Error details

For tool errors: which tool failed and why
Enterprise organizations often require administrator approval before users can connect third-party applications or install apps in Microsoft Teams. Microsoft Azure AD (Entra ID) allows tenant administrators to restrict whether users can grant consent to third-party apps on their own. When this restriction is active, individual users will see a “Need admin approval” screen during the OAuth flow instead of the standard consent prompt. This is a tenant-level policy — it is not specific to Relevance AI. If you see “Need admin approval” or “This app requires admin approval”, follow the steps below.
If you see an admin approval message when connecting your Microsoft account:
1

Copy the consent URL

Copy the consent URL that appears in the Microsoft login window. This URL contains the specific permissions Relevance AI is requesting.
2

Forward the URL to your administrator

Send the URL to your Microsoft 365 Global Administrator or Application Administrator with a request to grant consent. Include a brief explanation of what Relevance AI is and how it will be used.
3

Wait for admin approval

Your administrator will open the URL, review the requested permissions, and click Accept to grant consent on behalf of the organization.
4

Retry the connection

Return to Relevance AI and retry the Microsoft integration connection. The consent prompt should no longer appear.

Permissions reference

The following OAuth scopes are requested when you connect your Microsoft account. These permissions allow Relevance AI to read and send messages, access team and channel metadata, and maintain persistent access.
ScopeDescription
offline_accessMaintains access without requiring frequent re-authentication
Chat.CreateCreate new chats
Chat.ReadWriteRead and write to chats the user has access to
ChatMessage.ReadRead chat messages
ChatMessage.SendSend chat messages
ChannelMessage.Read.AllRead messages in channels the user has access to
ChannelMessage.SendSend messages to channels
Channel.ReadBasic.AllRead basic channel information (name, description, ID)
Team.ReadBasic.AllRead basic team information (name, description, ID)
User.ReadRead the signed-in user’s profile
User.Read.AllList users in the organization (used for trigger user filters)
These permissions may evolve as new features are added to the integration. Any changes will be reflected in the OAuth consent prompt.

Troubleshooting

This error means your Azure AD / Entra ID tenant has not granted consent for Relevance AI. Ask your Microsoft 365 Global Administrator to grant admin consent using the steps in Admin consent & permissions. Once consent is granted, retry the connection from the Integrations page.
If the Relevance AI app does not appear in the Teams app store, your organization likely restricts third-party app installations. Ask your IT administrator to allow the app in the Microsoft Teams Admin Center under Teams apps > Manage apps. See Admin consent & permissions for detailed steps.
Some Teams features are controlled by feature flags and may not be enabled for all accounts. If you don’t see Microsoft Teams as a trigger option in your agent or workforce settings, contact our support team to check whether the feature needs to be enabled for your account.
Verify that the Relevance AI app has been added to the specific channel or chat being monitored (not just installed in Teams), and that the Microsoft account used for the trigger is a member of the channel. Confirm the trigger is enabled and published in your agent’s settings. If keyword matching is configured, check that messages contain the expected keywords. Review the agent’s task logs in Relevance AI for errors — a 401 Unauthorized error indicates the OAuth token has expired or been revoked, and you should reconnect the Microsoft integration.

Frequently asked questions (FAQs)

The Microsoft Teams integration is built and maintained by Relevance AI. For integration-specific questions, contact our support team. For Microsoft Teams platform issues, contact Microsoft support.
The most common cause is that the Relevance AI app has not been installed in Teams or added to the specific channel. The Microsoft account you connected must also be a member of that channel. If your organization requires admin consent, the app may not be visible until an administrator approves it. Verify that you’ve completed both setup steps and added the app to the channel.
Yes, you can connect multiple Microsoft accounts through the Integrations & API Keys page. Each account can be used for different triggers and tool steps.
Yes, Teams triggers can monitor both channel messages and private chats. To monitor direct messages, select the “Direct chats with Relevance AI” option when configuring your trigger instead of a specific channel.
Yes, files shared in Teams channels are stored in SharePoint. You can access them through the Microsoft API Call tool step via the Microsoft Graph API.
Pre-built tool steps (like “Send Channel Message”) are designed for common tasks with simplified interfaces. The Microsoft API Call tool step gives you full access to Microsoft Graph API for advanced operations not covered by pre-built steps.
Yes, Microsoft Graph API enforces rate limits depending on your Microsoft 365 subscription. Microsoft returns a 429 Too Many Requests status code when limits are exceeded.
Go to the Integrations & API Keys page from the sidebar, find Microsoft (Teams, Outlook, SharePoint, OneDrive), click ”…” on the account you want to remove, and click “Remove” and confirm. This will disable all triggers and tool steps using this account across Teams, Outlook, SharePoint, and OneDrive. To also remove the app from Microsoft Teams, go to Apps in Teams, find Relevance AI, and click Uninstall.