Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
DictionaryTTeams Integration
PlatformAdvanced

Teams Integration

Teams Integration is a Setup page for configuring the integration between Salesforce and Microsoft Teams.

§ 01

Definition

Teams Integration is a Setup page for configuring the integration between Salesforce and Microsoft Teams. It enables features like Salesforce record sharing in Teams channels, CRM data access from the Teams interface, and meeting notifications synced between the two platforms.

§ 02

In plain English

👋 Study buddy

“Here's a simple way to think about it: Teams Integration brings Salesforce into the Microsoft-shop collaboration surface. For organizations standardized on Microsoft Teams rather than Slack, the parallel feature for record sharing, CRM data access, and meeting notifications.”

§ 03

Worked example

scenario · real-world use

The admin at Pinnacle Analytics configures Teams Integration so that when a sales rep shares a Salesforce Opportunity link in a Teams channel, an interactive card appears showing the deal amount, stage, and close date. Team members can click the card to open the full Opportunity record in Salesforce or update the stage directly from Teams.

§ 04

Why Teams Integration brings Salesforce into the Microsoft-shop collaboration surface

For organizations standardized on Microsoft Teams rather than Slack, Teams Integration is the parallel feature that brings Salesforce capabilities into the Teams workspace. Salesforce records shareable in Teams channels, CRM data accessible from inside Teams, meeting notifications synced between the two - the same integration shape Slack provides, scoped to a different host platform.

The reason it deserves careful configuration is that Microsoft-shop organizations use Teams as their universal communication surface, and any integration into it has to behave like a native Teams citizen. The configuration on this page determines whether the Salesforce features feel like a useful Teams app or an awkward bolt-on. Test integration behaviors with actual Teams users before broad rollout, tune notification settings to match the team's communication norms, and treat the integration as a first-class part of the workflow - not a side feature.

§ 05

How to set up Teams Integration

Teams Integration connects Microsoft Teams to Salesforce — collaborate on records, share Salesforce content in Teams chats, surface Salesforce data in Teams meetings. Useful for orgs standardized on Microsoft 365 with Salesforce as the CRM.

  1. Open Setup → Teams Integration

    Setup gear → Quick Find: Teams → Teams Integration.

  2. Click Set Up Teams Integration

    Wizard walks through the OAuth dance with your Microsoft 365 tenant.

  3. Authenticate as the M365 admin

    Required permissions: read user profile, post to channels, access Salesforce app.

  4. Configure default Teams channel for sharing

    Salesforce content shared from records goes to this channel by default. Users can override per-share.

  5. Pin the Salesforce tab in Teams (per-channel)

    In Teams, in any channel: Add a Tab → Salesforce → pick a Salesforce list view / report / dashboard. Users in the channel see Salesforce content live.

  6. Save → users can now share Salesforce records into Teams

    From any record in Salesforce, click Share → Teams → pick channel → post.

Key options
Default Teams Channelremember

Where Salesforce shares default to.

Per-User OAuthremember

Each user links their Salesforce account to their Teams identity.

Pinned Salesforce Tabsremember

Per-channel — admins or owners can pin Salesforce content as a Teams tab.

Gotchas
  • Microsoft 365 admin consent is required for the OAuth flow. A Salesforce admin alone can't complete setup — coordinate with M365 admin.
  • Teams Integration is rate-limited by Microsoft Graph API. High-volume Salesforce-to-Teams notification flows can hit limits — design for graceful degradation.
  • Pinned Salesforce tabs in Teams enforce Salesforce sharing. A user without Salesforce access to a list view sees an empty pinned tab — confusing UX.
§ 06

How organizations use Teams Integration

Embergate Defense

Standardized on Microsoft Teams for all internal collaboration as part of FedRAMP-compliant infrastructure; Teams Integration brings Salesforce records into Teams channels without sending data outside the M365 boundary. Every Opportunity update an account team sees in Teams is rendered from a Salesforce-side card, not duplicated into Teams.

Westshore Holdings

PE-firm portfolio managers live in Teams; Teams Integration means they can review portfolio-company Account updates without opening Salesforce. The integration's adaptive cards show the latest health metric, last activity date, and notable risks inline, with deep-links to the Salesforce record for the rare cases where a deeper drill is needed.

Pelican Forge

Configured Teams Integration so engineering reviews of customer-impact Cases happen in the existing engineering Teams channel - no context switch into Salesforce. The card-rendered Case shows symptom, customer, severity, and last update; comments in Teams flow back to Chatter as Activity records on the Case so the support team's view stays complete.

§

Trust & references

Official documentation

Straight from the source - Salesforce's reference material on Teams Integration.

Was this entry helpful?
Help us write better definitions. Quick reactions or detailed edit suggestions.
§

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…

Loading discussion…

Back to Dictionary