Teams Integration
Teams Integration is the Salesforce feature, and its matching Setup page, that connects Salesforce CRM with Microsoft Teams.
Definition
Teams Integration is the Salesforce feature, and its matching Setup page, that connects Salesforce CRM with Microsoft Teams. Once it is on, people work with Salesforce records directly inside Teams channels and chats. They can mention records in a conversation, pin them as tabs, and view or edit details without leaving the Teams window.
The integration is built for organizations that run on Microsoft Teams as their main collaboration tool, the same way the Slack integration serves Slack shops. It is available in Lightning Experience for Enterprise, Performance, Unlimited, and Developer editions with Sales Cloud and Service Cloud. The feature reached general availability in the Summer '21 release.
How the Teams Integration brings CRM into the chat window
What the integration actually does
The Teams Integration adds a Salesforce app to Microsoft Teams so reps and agents can pull CRM data into the place where they already talk to each other. When someone mentions a Salesforce record in a channel message, the integration unfurls it into a rich card that shows key fields and a link back to the full record. Teammates reading the thread see the same context without opening a separate browser tab. People can also pin a record as a tab at the top of a channel or chat. A deal room for a big opportunity might pin the Opportunity, the Account, and a couple of related Cases so everyone tracks the same data. The pinned tab shows a live view of the record, and users with edit access can update fields right there. The integration respects Salesforce sharing and field-level security, so a person only sees and changes what their profile and permission sets already allow. Custom objects work too, not just standard ones like Account and Contact.
Why Microsoft-shop teams reach for it
Sales and service work involves constant back-and-forth. A rep asks a solution engineer about a technical requirement, an agent loops in a manager on a tricky case, a deal desk weighs in on pricing. If all of that happens in Teams while the system of record lives in Salesforce, people spend their day copying details between two windows. The Teams Integration closes that gap by letting the record travel into the conversation. The payoff is fewer context switches and fewer stale screenshots pasted into chat. Instead of someone typing out an account's renewal date from memory, they mention the record and the live value appears. When the deal moves, the pinned tab reflects it. For a Microsoft-standardized company, this matters because Teams is where the workforce already lives. An integration that behaves like a native Teams app, rather than a clumsy add-on, is the difference between adoption and a feature nobody touches. That is why the Setup configuration and the rollout plan deserve real attention.
The two-sided setup: Salesforce and Teams
Standing up the integration takes work on both platforms, and the order matters. On the Salesforce side, an admin opens Setup, searches for Teams in Quick Find, selects Teams Integration, and turns on the setting that lets users access Teams Integration features. Salesforce shows an agreement that the admin reads and acknowledges before the toggle takes effect. After that, the admin assigns the User for Teams Integration permission set to everyone who needs CRM access from inside Teams. On the Microsoft side, a Teams administrator provisions the Salesforce app for the organization through the Teams admin center, so users can add it. The two sides connect through a Connected App style trust between Salesforce and Microsoft, and each user authenticates to Salesforce the first time they open the app in Teams. Because the rollout spans two admin consoles, it usually pairs a Salesforce admin with whoever owns the Microsoft 365 tenant. Skipping the Teams provisioning step is a common reason the app never shows up for users even after the Salesforce toggle is on.
Permissions, security, and what users can see
The integration never widens access. A person operating inside Teams sees exactly the records, fields, and actions their Salesforce profile, permission sets, and sharing rules grant them. The User for Teams Integration permission set is what enables the feature for a given user, but it does not override object or field permissions. If a rep cannot see a competitor field in Salesforce, that field stays hidden in the Teams card too. This is worth stressing because Teams channels can include people from many teams, and even guests. Pinning an Opportunity to a channel does not expose it to channel members who lack Salesforce access to that record. Each viewer is evaluated against their own Salesforce permissions when the card or tab loads. Admins should still treat the integration as part of routine access reviews. When someone changes roles or leaves, removing the permission set assignment cuts off their CRM access from Teams, and deauthorizing the connection in Setup is a clean way to revoke a stale session.
A worked example: a deal room in Teams
Picture an account team chasing a renewal. They spin up a Teams channel for the account and pin the Account record and the open Renewal opportunity as tabs. The account executive watches the amount and close date update as the deal progresses, with no need to open Salesforce in a browser. When a pricing question comes up, the AE types a message and mentions the opportunity, which unfurls into a card showing stage, amount, and the next step. A solution engineer in the channel reads that card and replies with a technical note. The sales manager, also in the channel, opens the pinned Account tab, checks the related cases, and sees an open support issue that could stall the renewal. She updates the opportunity's next step right from the tab because she has edit access. Everything she touches writes back to Salesforce immediately, so the rest of the org sees the same truth. No screenshots, no copy-paste, no second window. The conversation and the CRM record stay in sync because they share the same data.
Teams Integration next to Slack and the Microsoft suite
Salesforce ships a parallel integration for Slack, and the two solve the same problem for different chat platforms. A company picks the one that matches its collaboration stack. Teams Integration is the right choice when the workforce already runs on Microsoft 365 and Teams, while Slack is the natural fit after Salesforce acquired it. Both let users surface records, get notifications, and act on CRM data inside the chat tool rather than switching apps. Teams Integration also sits in a broader family of Salesforce connections to Microsoft. The Outlook integration brings Salesforce into email and calendar, and Einstein Activity Capture can sync events and messages. Teams Integration covers the real-time collaboration surface specifically. Knowing where each one fits helps you avoid overlap and explain the toolset to stakeholders. For a Microsoft-heavy org, the combination of Outlook plus Teams integrations can cover most of the day, putting Salesforce data into both the inbox and the channel where work happens.
Turn on the Teams Integration
Enabling the Teams Integration is a two-part job. You turn it on in Salesforce Setup and assign access, then a Microsoft Teams administrator provisions the Salesforce app in the Teams admin center. Do the Salesforce side first, then coordinate the Teams side.
- Open the Teams Integration setup page
In Salesforce Setup, type Teams in the Quick Find box and select Teams Integration. This is the central page for the feature.
- Turn on the feature and accept the agreement
Switch on the setting that lets users access Teams Integration features. Salesforce displays an agreement you must read and acknowledge before the change is saved.
- Assign the permission set
Assign the User for Teams Integration permission set to every user who needs to work with Salesforce records from inside Teams. Without it, the app will not load CRM data for them.
- Provision the app in Microsoft Teams
Have your Microsoft Teams administrator make the Salesforce app available in the Teams admin center so users can add it. Then users authenticate to Salesforce the first time they open it.
The master toggle on the Setup page. It must be on for any of the Teams capabilities to work.
Enables the integration for an individual user. It gates access to the feature but does not override object, field, or record permissions.
The trust link between Salesforce and Microsoft Teams. Deauthorizing it in Setup is how you revoke a stale or compromised connection.
- Turning on the Salesforce toggle is not enough. If a Teams admin never provisions the Salesforce app in the Teams admin center, users will not find it to add.
- The integration never expands access. A user sees only the records and fields their Salesforce sharing, profile, and permission sets already allow, even on a pinned channel tab.
- It requires Lightning Experience in Enterprise, Performance, Unlimited, or Developer edition with Sales Cloud or Service Cloud. Classic-only or lower editions cannot use it.
- Remember to remove the permission set when someone changes roles or leaves, since it is what keeps their CRM access in Teams alive.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Teams Integration.
Hands-on resources to go deeper on Teams Integration.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Who can benefit from understanding Teams Integration?
Q2. How does Salesforce's multi-tenant model affect Teams Integration?
Q3. What does Teams Integration represent in the Salesforce Platform?
Discussion
Loading discussion…