Microsoft Teams

Microsoft Teams is a collaboration platform that combines workplace chat, video meetings, file storage, and application integration.

With Relevance AI’s Microsoft Teams integration, you can connect your Teams workspace to your AI agents, enabling two-way conversations in real-time. Users can interact with AI agents directly in Teams — through channels, group chats, or direct messages — without leaving the platform. Agents monitor messages, respond in real-time, and automate communication workflows across your organization.

The integration uses native OAuth-based tool steps that call Microsoft Graph API directly, giving you faster execution, more reliable performance, and tighter security compared to third-party relay approaches.

Relevance AI uses a unified Microsoft authentication that works across Teams, Outlook, SharePoint, and OneDrive — connecting one account gives you access to all services.

The Relevance AI Bot App is officially approved on the Microsoft marketplace and available to install directly from within Teams.

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 (see Admin consent & permissions)

A Teams channel, chat, or DM

At least one channel, group chat, or direct message where you want your agent to operate

Setup is a two-step process: first connect your Microsoft account via OAuth in Relevance AI, then install the Relevance AI app in Microsoft Teams. Both steps are required.

Step 1: Connect the integration

1. Go to Integrations & API Keys in the sidebar of your Relevance AI dashboard.
2. Click Microsoft (Teams, Outlook, SharePoint, OneDrive) and then click Add Integration.
3. In the pop-up window, sign into your Microsoft account and approve the requested permissions.
4. Once complete, you’ll see a green Connected status indicator in Relevance AI.

Note: If a pop-up window doesn’t appear, check your browser’s pop-up blocker settings. If you see a “Need admin approval” message, see Admin consent & permissions.

Step 2: Install the Relevance AI app in Microsoft Teams

After connecting your Microsoft account, install the Relevance AI Bot App from the Microsoft marketplace so your agents can interact with channels, group chats, and direct messages.

1. Open the Teams app store

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

2. Search and install

   Search for Relevance AI, then click Add or Install to add the Bot App to your workspace.

   If you don’t see an install button, your organization may require admin approval. See Admin consent & permissions.
3. Add the app to channels, group chats, or direct messages

   After installing, add the app to each location where you want your agent to operate. The Bot App supports three contexts:

   Channels

   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

   Group chats

   1. Open the group chat where you want your agent to work
   2. Click the + icon or Add apps button
   3. Search for and select Relevance AI
   4. Add the app to the chat

   Direct messages (DMs)

   To use the bot in a 1:1 direct message conversation:

   1. In the Teams search bar at the top, search for Relevance AI
   2. Under People, select the Relevance AI bot
   3. Send the bot any message to open the conversation — this establishes the DM connection and makes it appear as a trigger option in Relevance AI

   Once you’ve sent a message, the DM will appear in the channel/chat selection dropdown when setting up triggers.

   The app must be added to every channel or chat where you want your agent to respond. Triggers will not work for locations where the app has not been added.
4. Verify the app is active

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

Set up Microsoft Teams as a trigger

You can configure your agents to automatically respond to Teams messages by setting up a trigger. When a message is received, your agent processes it and replies in real-time — creating a two-way conversation between the user and your AI agent directly within Teams.

Triggers work across channels, group chats, and direct messages with the bot.

Important: Teams triggers activate only on new messages. They do not trigger on new chat creation, group creation, or webhooks.

1. Navigate to your agent in Relevance AI and go to the Triggers section.
2. Click Add Trigger and select Microsoft Teams from the list.
3. Choose the Microsoft account you connected, then select the Team and specific channel, group chat, or direct message you want to monitor.
4. Optionally, 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.
5. In the Core Instructions section, write a prompt that guides how your agent should respond — including its role, tone, and when to respond.

Note: Only channels where the authenticated user is a member and the Relevance AI app has been added will appear in the dropdown.

Set tool permissions to “approval mode” initially so your agent asks before sending messages. Switch to autopilot once you’re confident.

Attachment support

Agents connected via Microsoft Teams can receive and process attachments sent in channels and chats.

Supported attachment types

Inline images

Images pasted directly into the Teams message composer are sent to the agent for processing

File uploads

Files attached via the Teams file picker (PDFs, documents, images, and other formats) are passed to the agent

Messages with only attachments

If a user sends a message that contains attachments but no text, the agent receives a [N attachments] indicator (e.g., [1 attachments]) in place of the message body. The agent can use this signal to recognize that attachments were sent and respond accordingly.

The agent’s ability to interpret attachment content depends on which tools and capabilities are configured for that agent.

Agent Notifications

This feature is currently in beta for some users

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.

Setting up Teams notifications

1. Navigate to your agent and click the Build tab
2. In the left sidebar, click Escalations
3. Under “Agent Notifications”, click Add agent notification
4. Configure your notification settings:
   • Select Microsoft Teams as the platform
   • Choose the notification trigger:
     • Agent enters status - Select specific task statuses (e.g., “Running”, “Completed”, “Failed”)
     • Tool errors (any tool) - Get notified when any tool encounters an error
   • Select a Microsoft Teams account that you have previously connected, or add a new Teams account
   • Select the Teams channel where you want to receive notifications
5. Click Publish changes to save your notification configuration
6. Test the notification by running your agent - you should receive a notification in your selected Teams channel based on your configured triggers

Make sure you have a Microsoft Teams account connected in your Integrations & API Keys page before setting up agent notifications.

What you’ll receive

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

• Agent name and status
• Task details and context
• A link to view the full task in Relevance AI
• For tool errors: information about which tool failed and why

You can click through to the task in Relevance AI to take further action or investigate issues.

Tool steps for Microsoft Teams

The Microsoft Teams integration provides 10 native OAuth-based tool steps that call Microsoft Graph API directly. These can be incorporated into your agent’s workflows to automate communication and team management tasks.

Team & channel management

List Teams

Retrieve all Microsoft Teams that the authenticated user is a member of

List Channels

Get all channels within a specific Team

Create Channel

Create a new channel in a Team

List Team Members

Retrieve the members of a specific Team

List Teams — details

Returns all Teams that the authenticated user belongs to, including the team name, ID, description, and visibility (public or private).

Use cases:

• Let an agent discover which teams exist before routing a message to the right channel
• Build a dynamic team selector when automating cross-team notifications
• Audit team membership across your organization

Key parameters: none required — returns results scoped to the authenticated user’s memberships.

Output: An array of team objects, each containing id, displayName, description, and visibility.

List Channels — details

Returns all channels within a given Team, including channel name, ID, description, and membership type (standard or private).

Use cases:

• Identify the correct channel ID before sending a message
• List available channels so an agent can present options to a user
• Check whether a channel already exists before creating a duplicate

Key parameters: teamId — the ID of the Team whose channels you want to list.

Output: An array of channel objects, each containing id, displayName, description, and membershipType.

Create Channel — details

Creates a new standard or private channel within a specified Team.

Use cases:

• Automatically create project-specific channels when a new project is kicked off
• Set up dedicated support channels for high-priority customers
• Provision onboarding channels for new team members

Key parameters: teamId, displayName (channel name), description (optional), membershipType (standard or private).

Output: The newly created channel object, including its id and webUrl.

List Team Members — details

Returns the members of a specific Team, including their display names, email addresses, and roles (owner or member).

Use cases:

• Look up a team member’s user ID before sending them a direct message
• Check whether a specific person is already a member of a team before adding them
• Generate membership reports for compliance or auditing

Key parameters: teamId — the ID of the Team whose members you want to list.

Output: An array of member objects, each containing id, displayName, email, and roles.

Messaging & communication

Send Channel Message

Post a message to a specific Teams channel

Send Chat Message

Send a direct message in a Teams chat

Retrieve Chat Messages

Fetch messages from a specific Teams chat or conversation

Search Messages

Search across Teams messages using keywords or filters

Send Channel Message — details

Posts a message to a channel within a specified Team. Supports plain text and basic HTML formatting.

Use cases:

• Send automated status updates to a project channel
• Post alerts when a monitored event occurs (e.g., a failed deployment or a new support ticket)
• Notify a team channel when a report is ready

Key parameters: teamId, channelId, content (message body), contentType (text or html).

Output: The created message object, including its id and createdDateTime.

Send Chat Message — details

Sends a message to an existing one-on-one or group chat thread.

Use cases:

• Send a personalized follow-up message directly to a user
• Notify a small group chat about a time-sensitive update
• Reply to a user who contacted your agent via direct message

Key parameters: chatId, content (message body), contentType (text or html).

Output: The created message object, including its id and createdDateTime.

Retrieve Chat Messages — details

Fetches messages from a specific chat thread, returning them in chronological order. Useful for giving your agent context about an ongoing conversation before it responds.

Use cases:

• Read the history of a support chat before drafting a reply
• Summarize recent conversation context for a handoff between agents
• Extract action items from a group chat discussion

Key parameters: chatId, top (number of messages to return), skip (pagination offset).

Output: An array of message objects, each containing id, from, body, createdDateTime, and lastModifiedDateTime.

Search Messages — details

Searches across Teams messages using a keyword query, returning matching messages from channels and chats the authenticated user has access to.

Use cases:

• Find all messages mentioning a specific project or customer name
• Locate a past decision or approval that was recorded in Teams
• Audit messages containing sensitive terms for compliance purposes

Key parameters: query (search keywords or phrases), top (maximum results to return).

Output: An array of matching message objects with id, from, body, channelIdentity or chatInfo, and createdDateTime.

Team operations

List Team Shifts

Retrieve shift schedule information from Microsoft Teams Shifts

List Team Shifts — details

Returns shift schedule data from the Teams Shifts feature, including shift times, assigned users, and shift notes.

Use cases:

• Let an agent check the current schedule before assigning tasks to team members
• Notify on-call staff of incidents based on who is currently on shift
• Summarize the week’s schedule and post it to a team channel

Key parameters: teamId, startDateTime, endDateTime (date range for shifts to retrieve).

Output: An array of shift objects, each containing id, userId, sharedShift (with startDateTime, endDateTime, activities), and draftShift.

Advanced operations

Microsoft API Call

Make custom calls to any Microsoft Graph API endpoint for operations not covered by the pre-built tool steps

Microsoft API Call — details

Gives you direct access to any Microsoft Graph API endpoint. Use this for operations not covered by the pre-built tool steps, or when you need fine-grained control over request parameters.

Use cases:

• Access Teams meeting transcripts or recordings
• Manage team membership (add or remove members)
• Retrieve files from a channel’s SharePoint document library

Key parameters: method (GET, POST, PATCH, DELETE), endpoint (Graph API path, e.g. /teams/{teamId}/members), body (JSON request body for write operations), params (query string parameters).

Output: The raw JSON response from the Microsoft Graph API.

These tool steps use native OAuth and call Microsoft Graph API directly. If you encounter issues with a specific tool step, please contact support.

Permissions Reference

When you connect Microsoft Teams to Relevance AI, you grant specific permissions through the Microsoft Graph API. These permissions determine what actions Relevance AI can perform on your behalf within Teams.

Requested Permissions

The following Microsoft Graph API scopes are requested during the OAuth connection flow:

offline_access

Maintain access to data when not actively using the app. This keeps your connection active without requiring re-authentication each time your agent needs to access Teams.

Chat.Create

Create new chats. Allows your agents to initiate new chat conversations in Teams.

Chat.ReadWrite

Read and write to all chats the user participates in. This enables your agents to view chat history and send messages in existing conversations.

ChatMessage.Read

Read messages in chats the user participates in. Required for triggers to monitor incoming messages and for agents to understand conversation context.

ChatMessage.Send

Send messages in chats. Allows your agents to respond to messages in chat conversations.

ChannelMessage.Read.All

Read messages in all channels the connected user has access to. This permission enables triggers to monitor channel messages across your Teams workspace.

ChannelMessage.Send

Send messages to channels. Allows your agents to post messages in Teams channels.

Channel.ReadBasic.All

Read basic channel information including names and descriptions. Required to list available channels when configuring triggers and tool steps.

Team.ReadBasic.All

Read basic Teams information. Needed to list available Teams in your organization when setting up integrations.

User.Read

Read basic profile information including name and email. This is a standard permission for Microsoft integrations.

User.Read.All

List all users in your organization. Required for the “Select specific users” filter option in trigger configuration, allowing you to limit which users’ messages activate your agent.

The exact permissions may evolve as Relevance AI updates the integration. Always review the consent screen carefully before accepting to understand what access you’re granting.

Troubleshooting

Common admin issues and fixes

If you encounter issues connecting or using the Microsoft Teams integration, these solutions address the most common problems:

"The application is not authorized" error

Problem: You see an error stating the application is not authorized when trying to connect.

Solution: Your Azure AD tenant may have an application allowlist enabled. Contact your Microsoft 365 administrator and ask them to:

• Add Relevance AI’s application ID to the approved application list in Azure AD
• Or grant tenant-wide admin consent for the Relevance AI application

Your admin can manage this in the Azure Portal under Azure Active Directory > Enterprise applications.

"Consent was denied" error

Problem: An administrator denied consent when you tried to connect the integration.

Solution: If an admin denies consent, the integration cannot function. You’ll need to:

• Work with your administrator to understand their concerns about the integration
• Provide context about how Relevance AI will use the data (see the Permissions Reference section above)
• Share Relevance AI’s Privacy Policy with your admin
• Request they reconsider and approve the consent request

Relevance AI app not visible in Teams app store

Problem: You can’t find the Relevance AI app when searching in the Microsoft Teams app store.

Solution: Your Teams administrator may have restricted third-party apps. Ask your admin to:

• Go to the Teams Admin Center
• Navigate to Teams apps > Permission policies
• Allowlist the Relevance AI app or adjust the policy to allow third-party apps

Once the policy is updated, the Relevance AI app should appear in your Teams app store.

Trigger is configured but agent isn't responding

Problem: You’ve set up a Teams trigger, but your agent doesn’t respond to messages.

Solution: This is the most common issue. Check the following:

1. Is the Relevance AI app installed and added to the channel or chat?

   • The app must be present in the specific channel or chat where you want the trigger to work
   • Install the Relevance AI app from the Teams app store
   • Add it to the relevant channel or chat

2. Is the Microsoft account that authenticated a member of that channel?

   • The user who connected the Microsoft integration must have access to the channel
   • Verify the authenticated user is a member of the channel in Teams

3. Is the trigger active and properly configured?

   • Check that the trigger is toggled to “Active” in Relevance AI
   • Verify that keyword filters aren’t excluding your test messages
   • Ensure you’re testing in the correct channel or chat that matches your trigger configuration

Example use cases

IT support bot

Monitor your IT support channel, search message history for similar past issues, and respond in real-time to common technical questions. Escalate unresolved issues by creating a dedicated channel or messaging the on-call engineer.

Onboarding assistant

When a new hire joins, retrieve their team membership, create a dedicated onboarding channel, and send a personalized welcome message with links to relevant documentation and contacts.

Customer success agent

Search Teams messages for mentions of a specific customer, retrieve recent chat history for context, and post a summary of open action items to the account team’s channel.

Sales pipeline assistant

Post daily pipeline summaries to a sales channel, send direct messages to remind reps of follow-up tasks, and list team members to route new leads to the next available rep.

Shift handoff bot

At the end of each shift, retrieve current shift data, summarize open tickets or tasks from the channel, and send the outgoing team a handoff message with a status summary.

Compliance monitor

Periodically search messages for flagged terms, retrieve the surrounding conversation for context, and post a digest to a compliance team channel for review.

Admin consent & permissions

Enterprise organizations often require administrator approval before users can connect third-party applications or install apps in Microsoft Teams.

If you see “Need admin approval” or “This app requires admin approval”, follow the steps below.

OAuth connection approval

If you see an admin approval message when connecting your Microsoft account:

1. Copy the consent URL that appears in the Microsoft login window.
2. Forward the URL to your Microsoft 365 admin with a request to grant consent, including what Relevance AI is and how it will be used.
3. Your administrator will open the URL, review the requested permissions, and grant consent on behalf of the organization.
4. Return to Relevance AI and retry the Microsoft integration connection.

Teams app installation approval

If your organization requires admin approval for app installations:

1. Contact your IT administrator and request approval to install the Relevance AI app.
2. Your administrator will go to the Microsoft Teams Admin Center, navigate to Teams apps > Manage apps, search for Relevance AI, and change the app status to Allowed.
3. Once approved, follow the steps in Step 2: Install the Relevance AI app.

Work with your IT team early in the process to avoid delays.

Best practices

Use List Teams and List Channels to resolve IDs dynamically

Team and channel IDs are required parameters for most tool steps, but they are not human-readable. Rather than hardcoding IDs in your tool configuration, use the List Teams and List Channels tool steps to look up IDs at runtime. This makes your agent more flexible when teams or channels are renamed or reorganized.

Start message-sending tools in approval mode

Before deploying an agent that sends messages autonomously, set your Send Channel Message and Send Chat Message tool steps to “approval mode”. This lets you review and approve each outgoing message before it is sent, which is useful for catching formatting issues or unintended content during initial testing.

Retrieve chat messages before responding

When your agent is triggered by a new message, use the Retrieve Chat Messages tool step to fetch recent conversation history before composing a reply. This gives the agent the context it needs to respond accurately rather than treating each message in isolation.

Use Search Messages for context retrieval, not real-time monitoring

The Search Messages tool step is designed for querying historical message content. It is not suited for real-time monitoring — use a Teams trigger for that. Reserve Search Messages for cases where your agent needs to look up past decisions, approvals, or discussions before taking action.

Handle rate limits gracefully

Microsoft Graph API enforces rate limits that vary by subscription tier. Design your agent workflows to spread out API calls where possible and handle 429 Too Many Requests responses by waiting before retrying. Avoid polling patterns that make repeated API calls in quick succession.

Troubleshooting

Tool step returns an authorization error

This typically means the OAuth token does not have the permissions required for that operation. Reconnect your Microsoft account through the Integrations & API Keys page and ensure you grant all requested permissions during the OAuth flow. If your organization requires admin consent, ask your Microsoft 365 admin to approve the permission request.

List Teams returns an empty array

The authenticated user must be a member of at least one Team for this tool step to return results. If the user is a guest in your tenant rather than a full member, Team visibility may be restricted. Verify the account is a direct member of the Teams you expect to see.

Send Channel Message fails with a 403 error

A 403 error on Send Channel Message usually means the authenticated user does not have permission to post in that channel. Check the channel’s moderation settings in Teams — some channels are configured to allow posts only from owners or specific roles.

Search Messages returns no results for a known message

Microsoft Graph search indexes Teams messages with a short delay after they are sent. If you are searching for a very recent message, wait a few minutes and try again. Search results are also scoped to content the authenticated user has access to — messages in private channels the user is not a member of will not appear.

Retrieve Chat Messages returns messages out of order

Messages are returned in the order specified by the Graph API, which defaults to ascending createdDateTime. If you need the most recent messages first, sort the output by createdDateTime in descending order within your tool configuration.

Frequently asked questions (FAQs)

What is the Teams Bot App?

The Relevance AI Teams Bot App is an officially approved application available on the Microsoft marketplace. It enables two-way conversations between Teams users and your AI agents — users can message the bot directly in channels, group chats, or direct messages, and your agent responds in real-time within Teams.

Where can I use the bot?

The bot works in three contexts within Microsoft Teams:

• Channels — add the app to a channel and your agent can monitor and respond to messages there
• Group chats — add the app to a group chat for your agent to participate in group conversations
• Direct messages (DMs) — users can open a 1:1 conversation with the Relevance AI bot and interact with your agent privately

Each location requires the app to be added separately before triggers will work there.

How do I start a direct message conversation with the bot?

To start a DM with the Relevance AI bot:

1. In the Teams search bar, type Relevance AI
2. Under People, select the Relevance AI bot
3. Send any message to open the conversation

Once you’ve sent a message, the DM will appear in the channel/chat selection dropdown when setting up triggers in Relevance AI.

Who supports the Microsoft Teams integration?

The Microsoft Teams integration was built by Relevance AI and is supported by our team, not Microsoft. If you have a question or issue, please reach out to our support team. For Microsoft Teams-specific issues, contact Microsoft support.

What is Microsoft Teams and why should I use it with Relevance AI?

Microsoft Teams is a collaboration platform that combines workplace chat, video meetings, and file storage. Using it with Relevance AI allows you to automate responses to messages, trigger workflows from Teams conversations, and send automated messages to channels or chats.

Do I need a Microsoft Teams account to use this integration?

Yes, you need an active Microsoft 365 account with a Teams license. This integration is designed for Microsoft Teams for business and enterprise. You’ll need to authenticate your Microsoft account through Relevance AI to connect the integration.

What's the difference between connecting my Microsoft account and installing the Teams app?

These are two separate required steps:

1. OAuth connection (in Relevance AI): Authenticates your Microsoft account and grants Relevance AI permission to access Microsoft services
2. App installation (in Microsoft Teams): Installs the Relevance AI app so it can interact with channels and chats

Both steps are necessary for the integration to work.

Why don't I see my Teams channel in the dropdown when setting up a trigger?

Common reasons:

1. App not installed: The Relevance AI app must be installed in Teams and added to the specific channel
2. User not a member: The Microsoft account you connected must be a member of the channel
3. Permissions issue: You may not have sufficient permissions to access the channel
4. Admin approval needed: Your organization may require admin consent

Verify that you’ve completed both setup steps and added the app to the channel.

Can I connect multiple Microsoft accounts?

Yes, you can connect multiple Microsoft accounts to your workspace from the Integrations & API Keys page. Each account can be used for different triggers and tool steps, which is useful for managing different Teams workspaces or separating different projects. When configuring a trigger or tool step, you can choose which connected account to use.

What permissions does the Microsoft Teams integration require?

The integration requires permissions to read messages, send messages, and access team and channel information. The exact permissions are shown during the OAuth flow when you connect your account. Some operations — such as listing team members or accessing private channels — may require admin consent depending on your organization’s Microsoft 365 policies. See the Permissions Reference section above for a detailed breakdown of all requested permissions.

Why don't I see all my Teams channels when setting up a trigger?

The integration only shows channels and group chats that the authenticated Microsoft user is a member of. If a channel is missing:

1. Have the user join the channel in Microsoft Teams
2. Return to Relevance AI and refresh the trigger setup page
3. The channel should now appear in the dropdown list

This is a security feature that ensures agents can only access channels the authenticated user has permission to view.

I set up a trigger but my agent isn't responding. What's wrong?

The most common cause is that the Relevance AI app hasn’t been added to the channel or chat. Even with a trigger configured, the app must be present in the channel to receive messages. To fix this:

1. Install the Relevance AI app from the Microsoft Teams app store
2. Add the app to the specific channel or chat where you want the trigger to work
3. Test by sending a message that matches your trigger conditions

Also verify that the trigger is toggled to “Active” and that keyword filters aren’t excluding your messages.

Do triggers work for direct messages?

Yes, Teams triggers can monitor channels, group chats, and 1:1 direct messages with the bot. To enable DM triggers, first send a message to the Relevance AI bot in Teams to establish the connection, then select that DM when configuring your trigger in Relevance AI.

Can I filter which messages trigger my agent?

Yes, you can configure trigger conditions such as keyword matching to filter which messages activate your workflow. This allows you to have your agent respond only to relevant messages rather than every message in a channel.

How do I prevent my agent from sending messages automatically?

Set your message-sending tools to “approval mode” in the agent settings. Your agent will ask for permission before sending a Teams message, and you can review, edit, approve, or reject.

Can my agent access files shared in Teams?

Yes, in two ways. First, agents can directly receive file uploads and inline images sent in a Teams message — these are passed as attachments when the trigger fires. Second, files shared in Teams channels are also stored in SharePoint, which you can access through the Microsoft API Call tool step via the Microsoft Graph API.

What's the difference between the pre-built Teams tool steps and the Microsoft API Call tool step?

Pre-built tool steps (like Send Channel Message or List Teams) are designed for specific, common tasks and have simplified interfaces with guided inputs. The Microsoft API Call tool step gives you direct access to any Microsoft Graph API endpoint, allowing you to implement functionality not covered by pre-built steps.

My agent's tools are returning a 401 Unauthorized error. How do I fix this?

This typically happens when the Microsoft OAuth connection is set to Private instead of Project level. Tools using Private OAuth may return 401 errors because the agent cannot access the credentials. To fix this:

1. Go to Integrations & API Keys in your Relevance AI dashboard
2. Find your Microsoft connection
3. Ensure the sharing level is set to “Project level” (not Private)
4. Save the changes and test your agent again

Project-level connections allow all agents in your project to use the integration.

Are there rate limits for Microsoft Teams API calls?

Yes, Microsoft Graph API enforces rate limits. The specific limits depend on your Microsoft 365 subscription and the type of requests being made. Your agents should handle rate limiting gracefully. Microsoft returns a 429 Too Many Requests status code when limits are exceeded.

Can I use this integration with Microsoft Teams for personal use?

This integration is designed for Microsoft Teams for business and enterprise. Personal Microsoft accounts may have limited functionality. We recommend using a business or enterprise Microsoft 365 account for the best experience.

How do I remove the Microsoft Teams integration?

To remove the Microsoft Teams integration:

1. Go to the Integrations & API Keys page from the sidebar
2. Search for Microsoft (Teams, Outlook, SharePoint, OneDrive) from the list
3. Click ”…” on the account you want to remove
4. Click “Remove” and confirm your choice

This will revoke Relevance AI’s access to your Microsoft account. Note that removing the Microsoft integration will disable all triggers and tool steps using this account across Teams, Outlook, SharePoint, and OneDrive. If you no longer need the Relevance AI app in Teams, you should also uninstall it from Microsoft Teams.