Skip to main content
With Relevance AI’s Microsoft Teams integration, you can seamlessly connect your Teams workspace to your AI agents, enabling them to monitor channels, respond to messages, and automate communication workflows directly within your team’s collaboration environment.

​
Connect the integration

Connecting your Microsoft account to Relevance AI is a straightforward process. The Microsoft integration provides unified authentication across Teams, Outlook, SharePoint, and OneDrive.
  1. Go to the “Integrations & API Keys” page in the sidebar of your Relevance AI dashboard.
  2. Click on “Microsoft (Teams, Outlook, SharePoint, OneDrive)” from the available integrations.
  3. Click on the “Add Integration” button.
  4. In the pop-up window, sign into your Microsoft account.
  5. Grant the necessary permissions for Relevance AI to access your Microsoft Teams data.
  6. Once authenticated, your Microsoft account will appear as a connected integration.
You may need admin consent depending on your organization’s Microsoft policies. After connecting, you can use Microsoft Teams as a trigger for your agents to automatically respond to messages, or use Teams tool steps in your custom tools to send messages and manage channels.

​
Microsoft integration overview

Relevance AI uses a unified Microsoft authentication that works across multiple Microsoft services:
  • Microsoft Teams - Monitor and respond to Teams messages
  • Outlook - Access email and calendar
  • SharePoint - Connect to SharePoint sites and documents
  • OneDrive - Access files stored in OneDrive
This means connecting one Microsoft account gives you access to all these services within Relevance AI.
Learn more about our Outlook integration and SharePoint knowledge source.

​
Set up Microsoft Teams as a trigger

You can configure your agents to automatically respond to Microsoft Teams messages by setting up Teams as a trigger. Your agent will process messages in real-time as they are posted to the monitored channel or chat.
Teams triggers activate only on new messages. They do not trigger on new chat creation, group creation, or webhooks.

​
How to set up the Microsoft Teams trigger

​
Other trigger settings

Available tool steps

Check out the available tool steps you can connect and use with your trigger to automate responses.

Configure trigger conditions

Optionally set up keyword matching to filter which messages activate your workflow.

Configure tool permissions

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

Write agent instructions

In the “Core Instructions” section, write a prompt that guides your agent on how to respond to Teams messages.

​
Tool steps for Microsoft Teams

The Microsoft Teams integration provides actions that your agents can use to send messages and manage Teams. These actions can be incorporated into your agent’s workflows as tool steps, enabling sophisticated communication automation capabilities.

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 Channels

Get all channels in a Team

List Shifts

Retrieve shift information from Teams

Microsoft API Call

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

​
Example use cases

Here are some ways you can leverage the Microsoft Teams integration with your agents:

IT support bot

Monitor your IT support channel and automatically respond to common technical questions, provide troubleshooting steps, create support tickets, and escalate urgent problems.

Onboarding assistant

Welcome new team members, answer common questions about company policies and tools, share relevant documentation, and guide new hires through their first week.

Customer success agent

Monitor customer inquiries, provide initial responses, search for relevant case history, and route complex issues to the appropriate team member.

Sales pipeline assistant

Log important deal updates to your CRM, remind team members of follow-up tasks, and post daily pipeline summaries.

​
Frequently asked questions (FAQs)

The Microsoft Teams integration in Relevance AI was built by Relevance AI, and is therefore supported by our team, not Microsoft. If you have a question or issue with using Microsoft Teams in Relevance AI, please reach out to our support team. If you have a question or issue that is only about Microsoft Teams, you can reach out to Microsoft support.
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, making your team communication more efficient.
Yes, you need a Microsoft account with access to Microsoft Teams. 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.
Yes, you can connect multiple Microsoft accounts to your workspace through 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.
The integration requires permissions to read messages, send messages, and access team/channel information. The exact permissions will be shown during the OAuth flow when you connect your account. You may need admin consent depending on your organization’s policies.
Yes, Teams triggers can monitor both channel messages and private chats, depending on your configuration. You can set up triggers for specific channels or direct message conversations.
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.
Set your message-sending tools to “approval mode” in the agent settings. This ensures your agent will always ask for permission before sending a Teams message. You can review the draft, make edits if needed, and then approve or reject the send action.
Yes, files shared in Teams channels are stored in SharePoint. You can use the Microsoft Graph API to access these files through the API Call tool step. The files are typically accessible via the channel’s associated SharePoint document library.
Pre-built tool steps (like “Send Channel Message” or “Create Channel”) are designed for specific, common tasks and have simplified interfaces with guided inputs. The Microsoft API Call tool step gives you full access to Microsoft Graph API, allowing you to implement any functionality available in the API, including advanced operations not covered by pre-built steps.
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 be designed to handle rate limiting gracefully. Microsoft typically returns a 429 Too Many Requests status code when limits are exceeded.
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.
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
Note: Removing the Microsoft integration will disable all triggers and tool steps using this account across Teams, Outlook, SharePoint, and OneDrive.
The beta status indicates that while the Microsoft Teams integration is fully functional and available for use, we’re still gathering user feedback and may make refinements to improve the experience. We recommend testing your workflows thoroughly before deploying them in production. If you encounter any issues or have suggestions, please contact our support team.