You are here:
Configure Credentials for Remote Engagement with Microsoft Teams
The Life Sciences Customer Engagement managed package includes the named and external credentials that support remote engagement with Microsoft Teams. To complete the setup, register an application in Microsoft Azure. Then, use the Microsoft Azure app details to update the named credential configuration in your Salesforce org. The named credential configuration enables secure authentication between Salesforce and Microsoft Teams and allows Life Sciences Customer Engagement to create and start Microsoft Teams meetings on behalf of users.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise and Unlimited Editions with Life Sciences Cloud, Life Sciences Cloud for Customer Engagement Add-on license, and the Life Sciences Customer Engagement managed package. |
| User Permissions Needed | |
|---|---|
| To view named credentials: | View Setup and Configuration |
| To create, edit, or delete external credentials: | Manage Named Credentials or Customize Application |
| To edit permission sets and user profiles: | Manage Profiles and Permission Sets |
Register an App in Microsoft Azure
Register an application in Microsoft to enable access to Microsoft’s Graph API on behalf of the user. Follow the Microsoft instructions to complete these steps. You use the values that you save when you create the external auth identity provider in Salesforce.
-
Register a new application in Microsoft Azure.
Give the app a name that makes sense for your organization.
-
After you create your app, retrieve and save these values from your app’s Overview page.
- Directory (tenant) ID
- Application (client) ID
-
Generate and save a client secret for your app.
Copy the client secret value immediately, as it’s available only when you first create it. If you lose the client secret value, generate a new one.
-
Add these Microsoft Graph API permissions to your
app.
- openid
- offline_access
- OnlineMeetings.Read
- Calendars.ReadWrite
These permissions allow Life Sciences Customer Engagement to authenticate users via OAuth 2.0, create and manage Microsoft Teams meetings, and access calendar data for scheduling purposes. - If required by your organization’s policies, grant admin consent after you add Microsoft Graph API permissions.
-
From your app’s Endpoints page, retrieve and save these endpoints for your app.
- OAuth 2.0 authorization endpoint (v2)
- OAuth 2.0 token endpoint (v2)
Configure an External Auth Identity Provider
In Salesforce, update the external auth identity provider for the Microsoft Teams integration. The external auth identity provider allows Salesforce to obtain OAuth 2.0 tokens for secure authentication with Microsoft Teams.
Before you create the external auth identity provider in Salesforce, make sure that you retrieved these values from your Microsoft Azure app.
- Application (client) ID
- Directory (tenant) ID
- Client secret value
- OAuth 2.0 authorization endpoint (v2)
- OAuth 2.0 token endpoint (v2)
- From Setup, in the Quick Find box, search for and select Named Credentials.
- Select External Auth Identity Providers.
- Select Microsoft Teams Auth Provider (Life Sciences), and then click Edit.
-
Enter or update these values.
Field Description Client ID Enter the Application (client) ID from your Microsoft Azure app. Client Secret Enter the client secret from your Microsoft Azure app. Authorize Endpoint URL In the URL, replace /common/with the directory (tenant) ID from your Microsoft Azure app.Token Endpoint URL In the URL, replace /common/with the directory (tenant) ID from your Microsoft Azure app. - Save your changes.
-
On the external auth identity provider detail page, copy the callback URL that Salesforce
generated.
The callback URL is also called the redirect URI.
Set Up a Redirect URI in Microsoft Azure
To complete the OAuth 2.0 configuration for the Microsoft Teams integration, add a redirect URI to your Microsoft Azure app registration. The redirect URI lets users log into Microsoft Teams from Life Sciences Customer Engagement and then redirects users back to Salesforce after they authenticate.
- In Microsoft Azure, return to your app.
-
In the Authentication section for your app, add a redirect URI.
Use the callback URL that you copied from your Salesforce external auth identity provider.
Create a Permission Set and Grant Principal Access
In Salesforce, use a permission set to grant access to the Microsoft Teams credentials. Only users who have this permission set can authenticate with Microsoft Teams to schedule and conduct remote sessions.
If you don’t have a permission set that allows users to access external systems, create one first. See Create Permission Sets.
- From Setup, in the Quick Find box, search for and select Permission Sets.
- Open the permission set that you created for accessing external systems.
-
Grant access to Microsoft Teams OAuth 2.0 external credential for users who are assigned
to this permission set.
- In the permission set, under Apps, click External Credential Principal Access.
- Click Edit.
- Move the principal for the Life Sciences Microsoft Teams external credential to the enabled principals column.
- Save your changes, and then return to the permission set.
-
Enable user external credential object permissions so that Salesforce can securely create,
manage, and store encrypted access tokens that the named credential uses for callouts to
Microsoft Teams.
- In the permission set, under Apps, click Object Settings.
- Click User External Credentials.
-
Enable these permissions on the User External Credentials object.
- Read
- Create
- Edit
- Delete
- Save your changes.
-
Assign the permission set to all users who use
Microsoft Teams to schedule and conduct remote sessions.
Users can have multiple assigned permission sets. If users also have access to Twilio, you can grant them both permission sets.

