Skip to content

Commit 14129d1

Browse files
authored
Update errors-when-accessing-salesforce-with-server-to-server-flow.md
1 parent ea9a086 commit 14129d1

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

support/sales-copilot/crm-permissions-and-configurations/errors-when-accessing-salesforce-with-server-to-server-flow.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
---
2-
title: Errors When Accessing Salesforce With Server-to-server Flow
2+
title: Errors When Accessing Salesforce with Server-to-Server Flow
33
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
55
author: sbmjais
66
ms.author: shjais
77
ms.reviewer: marrabi
88
ms.custom: sap:CRM Permissions and Configurations\CRM Settings
99
---
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
1111

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.
1313

1414
## Who is affected?
1515

@@ -30,7 +30,7 @@ When a user tries to access Salesforce with the server-to-server flow, the follo
3030

3131
> Access denied for this user.
3232
33-
You might also see:
33+
You might also see the following message:
3434

3535
> User doesn't have admin permission to access the connected app.
3636
@@ -52,7 +52,7 @@ To resolve this issue, update the connected app configuration in Salesforce:
5252

5353
1. Go to **Administration** > **Users** > **Users** and confirm that the profile of the integration user is **CopilotForSalesIntegrationProfile**.
5454

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.
5656

5757
## Server-to-server authentication failed
5858

@@ -95,7 +95,7 @@ To resolve this issue, ensure that the connected app and integration user config
9595
1. The user is associated with the **Copilot for Sales connected app permission set**.
9696
1. The user is associated with the **Salesforce API Integration** permission set license assignments.
9797

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.
9999

100100
## Server-to-server authorization failed
101101

@@ -111,13 +111,13 @@ You might also see one of the following messages:
111111

112112
##### Cause
113113

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.
115115

116116
##### Resolution
117117

118118
To resolve this issue, contact [Microsoft support](/microsoft-sales-copilot/get-support) and provide the following information:
119119

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.
121121
- If the connected app is still available, provide its ID.
122122

123123
#### 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
136136

137137
1. On **Copilot for Sales Connected App** row, select the down arrow, and then select **Edit**.
138138

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.
140140

141141
> [!NOTE]
142142
> 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
149149

150150
> Trouble connecting to Salesforce.
151151
152-
You might also see:
152+
You might also see the following message:
153153

154154
> Couldn't get Client ID for access token retrieval from Salesforce. The connected app might be misconfigured.
155155
156156
### Cause
157157

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.
159159

160160
### Resolution
161161

162162
To resolve this issue, contact [Microsoft support](/microsoft-sales-copilot/get-support) and provide the following information:
163163

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.
165165
- If the connected app is still available, provide its ID.
166166

167167
## Try again
168168

169169
### Symptoms
170170

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:
172172

173173
- > Try again.
174174
- > 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
189189

190190
> Unauthorized access denied.
191191
192-
You might also see:
192+
You might also see the following message:
193193

194194
> Access token expired or invalid. Try saving again to refresh it.
195195
@@ -199,7 +199,7 @@ The access token used for authentication is expired or invalid.
199199

200200
### Resolution
201201

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.
203203

204204
## More information
205205

0 commit comments

Comments
 (0)