The integration features are available in an app in Teams called Salesforce. The Salesforce app is accessible only from Teams apps. There isn’t a separate install file for the integration.
The integration requires Salesforce setup and Teams setup to ensure that users can access to the Salesforce app in Teams.
When you turn on the integration, this setup happens automatically. Both are required for the integration.
A site name https://*.scrt.sfdc.sh is added in the Cross-Origin Resource Sharing (CORS) list in Salesforce. This site is specific to your org and is required to create the preview cards available in Teams when a Salesforce record is mentioned.
The Salesforce integration with Microsoft Teams app is added in the Connected Apps OAuth list in Salesforce setup. The integration honors OAuth settings such as IP restrictions and session durations configured in the policies for the connected app. Learn more about connected apps and their policies in Salesforce Help.
When a Teams user mentions a record in Teams, the component that displays the record uses that user’s Salesforce language and locale settings. Other users see the mentioned record in the language of the person who mentioned the record.
The Teams integration runs on SCRT2, which is hosted on Heroku. In late 2021 or early 2022, SCRT2 will migrate to Hyperforce. Heroku and Hyperforce documentation applies as listed on the Trust and Compliance page
2. Consideration
REQUIRED EDITIONS
Available in: Lightning ExperienceAvailable with Sales Cloud and Service Cloud in: Enterprise, Performance, and Unlimited Editions
3. Configure
From Salesforce Setup, in the Quick Find box, enter Teams, and then select Teams Integration.
Turn on Let users access Teams Integration features.
Read and acknowledge the agreement.
Select Assign Permission Set, and assign the User for Teams Integration permission set to users who need access to Salesforce in Teams.
Select how much Salesforce data to include when a user shares a Salesforce record anywhere in Teams.
Show the object type onlyWhen a rep mentions a record in a conversation, the conversation shows only information about the object type mentioned. Users with Salesforce access can preview more record details in Teams. Users without Salesforce access see only that a record was mentioned and its type, such as contact, opportunity, lead, account, or case.Users see a card with limited information when they mention a record in a channel.
After users select Preview Record, they see different amounts of information based on their Salesforce permissions.
Show record summaryWhen a rep mentions a record, the record’s compact layout shows in the conversation, even to users who don’t have Salesforce access. This option provides the most insight into the record shown and is best for collaboration within Teams. However, ensure that the structure of your compact layouts and the data included are appropriate for all members of a Teams channel to see.
When a user mentions a record, all channel members see an adaptive card with record details. Details shown on the adaptive card are stored in your company’s Office 365 Teams storage.
After users who have a Salesforce license select View in Salesforce, they see the record detail page in Salesforce with any information available to them based on their permissions.
After users who don’t have a Salesforce license select View in Salesforce, they see a login page. They can’t view any additional Salesforce records’ details without acquiring a login.
Some fields aren’t displayed in Teams adaptive cards when the integration is configured for record mentions in a compact layout.
All empty fields
Address and rich text fields in the compact layout
The PhotoUrl field on contacts and leads
Work with your Teams administrator to provision the integration in the Teams application
4. Provision
After the setup is complete in Salesforce, work with your Microsoft Teams administrator to ensure that the Teams environment is set up correctly. The Salesforce app provides the integration features within the Teams interfaces. The app permission policies maintained in the Microsoft Teams admin center determine which apps users can install. Those policies also determine which apps users can pin to the Teams app bar in their desktop and mobile clients can pin within their teams
5. Integration
The integration uses cookies to maintain data access during a session.
The following table describes the cookies that Salesforce collects for the integration. These cookies are required for the app to work correctly.
COOKIE NAMEDURATIONCOOKIE TYPEDESCRIPTIONsessionIdSessionRequiredIdentifies a user’s unique session of the app for login, authentication, and data purposes. Each time a user logs in, a different session ID is created so information is stored and passed between the client and server for that session only.sessionId-legacySessionRequired (in older clients and browsers only)
Used if a client or browser doesn’t support SameSite=None and Secure attributes together. If those attributes are supported, the integration uses sessionId instead.
Identifies a user’s unique session of the app for login, authentication, and data purposes. Each time a user logs in, a different session ID is created so information is stored and passed between the client and server for that session only
.png)
