Microsoft Teams

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.

This occurs when you or your administrator explicitly declined the permissions request during the OAuth flow. To resolve this, retry the integration connection from the Integrations page and click Accept when prompted. If the consent was denied by an admin policy, your administrator will need to grant consent on your behalf.

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.

Magic links are time-limited and may expire before you click them. If your magic link no longer works, connect your Microsoft Teams account directly through the standard OAuth flow: go to Integrations & API Keys in the sidebar, find the Microsoft integration, and click Add Integration.

The consent page shows two email addresses: your Relevance AI account email and your Microsoft Teams account email. If either address looks incorrect, click Cancel and verify that you’re logged in to the correct Relevance AI account before trying again. To switch accounts, sign out of Relevance AI and sign in with the correct account, then click the magic link again.

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. Set the Thread Reply Method to “No reply” in your MS Teams trigger’s Advanced Settings. This allows your agent to process messages without posting a response back to Teams — useful when the agent’s output goes somewhere else, such as a database, email, or another workflow. The default is “Agent auto-reply”, which maintains existing behavior. To verify the agent is running correctly, check the task history in Relevance AI.

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.

A magic link is an alternative way to connect your Microsoft Teams account to Relevance AI. When you click the link, you’re taken to a consent page in Relevance AI that shows your Relevance AI account email and your Microsoft Teams account details. Click Confirm to complete the connection or Cancel to abort it. The magic link method achieves the same result as connecting via the standard OAuth flow on the Integrations page.

Both methods work and achieve the same result. You can connect your Microsoft Teams account through the standard OAuth flow on the Integrations & API Keys page, or by clicking a magic link you received from Microsoft Teams or via email. Use whichever is more convenient.

If you’re not logged in to Relevance AI when you click the magic link, you’ll be redirected to the sign-in page. After signing in, you’ll be automatically returned to the consent page to complete the account linking.