Use this article to connect Microsoft Teams to Intercom, configure Fin to handle conversations in your Teams channels, and understand what your customers experience. Microsoft Teams is supported on all data residency regions and works with Fin for platforms.
How to connect Microsoft Teams
Setup is done in your Intercom workspace by a teammate with admin access.
Step 1: Connect your Teams workspace
Click + Connect Teams workspace.
Complete the Microsoft admin-consent OAuth flow — a Microsoft admin authorizes the Intercom app for your tenant.
After authorization, you're redirected back to Intercom where you can select which Microsoft Team to connect.
Step 2: Add channels
Once your Teams workspace is connected, choose which channels Fin should monitor.
Standard channels connect automatically via the team-level install.
Private and shared channels require a separate install: add the Intercom bot directly to the channel in Teams. The channel connects automatically as soon as the bot is added.
Step 3: Configure conversation triggers
Choose when Fin or a Workflow starts a conversation in a channel. You can trigger on every message, or only on specific signals:
When a specific user or tag is @mentioned
When a specific emoji reaction is added to a message
When a specific keyword is used
Workspace-level triggers apply to all connected channels by default. You can override triggers on a per-channel basis.
Step 4: Set up customer authentication (optional)
Under Security > Customer authentication, you can require identity verification before Fin runs data connector requests. Microsoft Teams supports two options:
No verification — Fin responds to all messages without confirming who the customer is. Use this for public-facing or low-sensitivity channels.
Email OTP (one-time passcode sent to the customer's email)
Step 5: Deploy Fin to Microsoft Teams
Once your channel is connected, you need to activate Fin so it starts handling conversations in Teams.
Go to Deploy > Chat in your Intercom workspace.
Under In selected channels, click the Channels dropdown.
Select Microsoft Teams from the list.
Click Save. Fin is now live. To verify it's working, send a test message in your connected Teams channel — Fin should respond according to your configured triggers.
How Microsoft Teams conversations appear in Intercom
Once Microsoft Teams is connected and Fin is deployed, conversations from Teams appear in your Intercom inbox alongside conversations from all other channels. Here's what to expect:
Teams conversations appear in the Intercom inbox like any other channel, with a Microsoft Teams indicator on each conversation.
Workflows run over Teams conversations — Teams is a fully supported chat channel in the workflow engine.
Fin responds in Teams threads, keeping each conversation neatly organized.
Ticket status updates can be configured per channel or workspace-wide, matching the controls available for Slack.
What does the Microsoft Teams experience look like for customers?
When a customer messages in a connected Microsoft Teams channel, Fin handles their conversation using the features below. Each is delivered natively within Teams — customers don't need to leave the Teams interface.
First-run welcome: When the Intercom bot is installed, customers see a connection-aware welcome message. Connected workspaces also display a disclosure that messages may be stored by a third-party help desk service.
Threaded replies: Fin responds in Teams threads, keeping support conversations organized and easy to follow.
Quick replies and CSAT surveys: Delivered as interactive Microsoft Adaptive Cards directly in the thread.
Emoji and reactions: Inbound emoji are preserved in Intercom. A channel emoji reaction can also start a new conversation.
AI-powered translations: Fin detects and responds in your customer's language automatically.
Ticket forms: Structured data is collected via hosted ticket forms, letting Fin gather the information it needs to help.
Note: Microsoft Teams uses custom emoji, so some emoji may not display in the Intercom inbox. The emoji name will be shown instead.
What are the current limitations of Microsoft Teams?
The following limitations apply to the Microsoft Teams integration. Workarounds are noted where available.
Voice notes — Voice notes in channel messages are not supported. Message content is limited to text and Adaptive Cards. Workaround: ask customers to type their message instead.
Message edits — If a teammate edits a message in Teams, the change is not currently reflected in the Intercom inbox. Workaround: send a follow-up message to clarify any edits needed.
Channel archival and deletion — If a connected Teams channel is archived or deleted in Microsoft Teams, this is not currently handled in Intercom. Workaround: manually disconnect the channel in Settings > Channels > Microsoft Teams before archiving or deleting it in Teams.
FAQs
Why isn't Fin posting in my private or shared channel?
Why isn't Fin posting in my private or shared channel?
Private and shared channels require the Intercom bot to be added directly to the channel in Teams — a team-level install isn't enough. Add the bot to the channel and the connection will form automatically.
What does Microsoft error 53003 mean for a customer in Teams?
What does Microsoft error 53003 mean for a customer in Teams?
This applies if you've been added as a guest to another company's Microsoft Teams workspace (for example, to collaborate on a shared project) and hit an error signing in from the Teams desktop or mobile app. Error 53003 means Conditional Access blocked your sign-in. Conditional Access is a Microsoft Entra ID (Azure AD) feature that lets an organization restrict access to their resources based on rules like device type, location, or device management status. Your sign-in itself succeeded — the error means the other organization's Conditional Access policy then blocked access because your device doesn't meet that org's requirements (for example, it isn't enrolled as a managed/registered device in their system).
This is controlled entirely by the other organization's IT/Microsoft Entra admin — it isn't something Intercom or you can change from your end. To resolve it, ask that organization's admin to either:
Allow guest access from unmanaged devices, or add an exception for the customer's account, or
Enroll the customer's device in their device management system, if they'd prefer that route
The same policy can affect some access paths but not others — for example, blocking the Teams desktop and mobile apps while still allowing sign-in through a web browser (or blocking all three). If you can access Teams in a browser but not in the desktop/mobile app, that's consistent with a Conditional Access policy targeting specific client types, and it's still something the other organization's admin controls.
When you contact the other organization's admin, share the Correlation ID and Timestamp shown on the Microsoft error screen — this lets their IT team look up the exact sign-in attempt in their own logs to confirm the policy that blocked it.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts