You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/sales-copilot/crm-permissions-and-configurations/errors-when-accessing-salesforce-with-server-to-server-flow.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
1
---
2
-
title: Errors When Accessing Salesforce With Server-to-server Flow
2
+
title: Errors When Accessing Salesforce with Server-to-Server Flow
3
3
description: Troubleshoot and resolve errors that occur when accessing Salesforce with server-to-server flow or during setup in Microsoft Copilot for Sales.
4
-
ms.date: 05/26/2025
4
+
ms.date: 05/28/2025
5
5
author: sbmjais
6
6
ms.author: shjais
7
7
ms.reviewer: marrabi
8
8
ms.custom: sap:CRM Permissions and Configurations\CRM Settings
9
9
---
10
-
# Errors that occur when accessing Salesforce with server-to-server flow
10
+
# Errors that occur when accessing Salesforce that uses a server-to-server flow
11
11
12
-
This article helps you troubleshoot and resolve errors that might occur when a user tries to access Salesforce with server-to-server flow or when an administrator sets up the server-to-server flow for Salesforce in Microsoft Copilot for Sales.
12
+
This article helps you troubleshoot and resolve errors that might occur when a user tries to access Salesforce with a server-to-server flow or when an administrator sets up the server-to-server flow for Salesforce in Microsoft Copilot for Sales.
13
13
14
14
## Who is affected?
15
15
@@ -30,7 +30,7 @@ When a user tries to access Salesforce with the server-to-server flow, the follo
30
30
31
31
> Access denied for this user.
32
32
33
-
You might also see:
33
+
You might also see the following message:
34
34
35
35
> User doesn't have admin permission to access the connected app.
36
36
@@ -52,7 +52,7 @@ To resolve this issue, update the connected app configuration in Salesforce:
52
52
53
53
1. Go to **Administration** > **Users** > **Users** and confirm that the profile of the integration user is **CopilotForSalesIntegrationProfile**.
54
54
55
-
Also, check if there were unintended changes made to the connected app configuration. If yes, revert the changes to the original configuration.
55
+
In addition, check if any unintended changes are made to the connected app configuration. If yes, revert the changes to the original configuration.
56
56
57
57
## Server-to-server authentication failed
58
58
@@ -95,7 +95,7 @@ To resolve this issue, ensure that the connected app and integration user config
95
95
1. The user is associated with the **Copilot for Sales connected app permission set**.
96
96
1. The user is associated with the **Salesforce API Integration** permission set license assignments.
97
97
98
-
Also, check if there were unintended changes made to the connected app or integration user configuration. If yes, revert the changes to the original configuration.
98
+
In addition, check if any unintended changes are made to the connected app or integration user configuration. If yes, revert the changes to the original configuration.
99
99
100
100
## Server-to-server authorization failed
101
101
@@ -111,13 +111,13 @@ You might also see one of the following messages:
111
111
112
112
##### Cause
113
113
114
-
During Salesforce server-to-server flow setup, a connected app is deployed to the Salesforce organization. The connected app is associated with an integration user. An access token is retrieved with the client ID and the secret of the connected app. The error occurs when the secret is invalid.
114
+
During the Salesforce server-to-server flow setup, a connected app is deployed to the Salesforce organization. The connected app is associated with an integration user. An access token is retrieved with the client ID and the secret of the connected app. The error occurs when the secret is invalid.
115
115
116
116
##### Resolution
117
117
118
118
To resolve this issue, contact [Microsoft support](/microsoft-sales-copilot/get-support) and provide the following information:
119
119
120
-
- Whether the "Copilot for Sales Connected App" connected app was updated accidentally.
120
+
- Whether the "Copilot for Sales Connected App" connected app is updated accidentally.
121
121
- If the connected app is still available, provide its ID.
122
122
123
123
#### Error 2: Session ID isn't allowed for use REST API access at Salesforce
@@ -136,7 +136,7 @@ To resolve this issue, contact your administrator to set the appropriate OAuth s
136
136
137
137
1. On **Copilot for Sales Connected App** row, select the down arrow, and then select **Edit**.
138
138
139
-
1. Under **API (Enable OAuth Settings)**, ensure the **Manage user data via APIs (api)** is selected in the **Selected OAuth Scopes** list. If it's not selected, check if the setting was changed manually by mistake. If yes, revert the changes.
139
+
1. Under **API (Enable OAuth Settings)**, ensure the **Manage user data via APIs (api)** is selected in the **Selected OAuth Scopes** list. If it's not selected, check if the setting is changed manually by mistake. If yes, revert the changes.
140
140
141
141
> [!NOTE]
142
142
> If the **Manage user data via APIs (api)** isn't selected, the connected app can't access Salesforce data.
@@ -149,26 +149,26 @@ When a user tries to access Salesforce with the server-to-server flow, the follo
149
149
150
150
> Trouble connecting to Salesforce.
151
151
152
-
You might also see:
152
+
You might also see the following message:
153
153
154
154
> Couldn't get Client ID for access token retrieval from Salesforce. The connected app might be misconfigured.
155
155
156
156
### Cause
157
157
158
-
This error occurs when the client ID of the Salesforce connected app is invalid. During server-to-server flow setup, a connected app is deployed in Salesforce and linked to an integration user. The access token is retrieved using the client ID and secret of this app. If the client ID is missing or incorrect, authentication fails.
158
+
This error occurs when the client ID of the Salesforce connected app is invalid. During the server-to-server flow setup, a connected app is deployed in Salesforce and linked to an integration user. The access token is retrieved using the client ID and secret of this app. If the client ID is missing or incorrect, authentication fails.
159
159
160
160
### Resolution
161
161
162
162
To resolve this issue, contact [Microsoft support](/microsoft-sales-copilot/get-support) and provide the following information:
163
163
164
-
- Whether the "Copilot for Sales Connected App" connected app was deleted accidentally.
164
+
- Whether the "Copilot for Sales Connected App" connected app is deleted accidentally.
165
165
- If the connected app is still available, provide its ID.
166
166
167
167
## Try again
168
168
169
169
### Symptoms
170
170
171
-
As an administrator, when you try to set up the server-to-server flow for Salesforce, you may receive one of the following error messages:
171
+
As an administrator, when you try to set up the server-to-server flow for Salesforce, you might receive one of the following error messages:
172
172
173
173
-> Try again.
174
174
-> This might be a temporary error. Try again. If it doesn't work, check back in 5-10 minutes.
@@ -189,7 +189,7 @@ When a user tries to access Salesforce with the server-to-server flow, the follo
189
189
190
190
> Unauthorized access denied.
191
191
192
-
You might also see:
192
+
You might also see the following message:
193
193
194
194
> Access token expired or invalid. Try saving again to refresh it.
195
195
@@ -199,7 +199,7 @@ The access token used for authentication is expired or invalid.
199
199
200
200
### Resolution
201
201
202
-
To resolve this issue, try again after 10-15 minutes. If this issue persists, check with your administrator to confirm if the connection is still active.
202
+
To resolve this issue, try again after 10 to 15 minutes. If this issue persists, check with your administrator to confirm if the connection is still active.
0 commit comments