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-enabling-salesforce-server-to-server-flow.md
+30-6Lines changed: 30 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Errors When Enabling Salesforce With Server-to-server Flow
3
3
description: Resolves errors that might occur when enabling Salesforce with server-to-server flow in Microsoft Copilot for Sales.
4
-
ms.date: 05/23/2025
4
+
ms.date: 05/26/2025
5
5
author: sbmjais
6
6
ms.author: shjais
7
7
manager: shujoshi
@@ -10,7 +10,7 @@ ms.custom: sap:CRM Permissions and Configurations\CRM Settings
10
10
---
11
11
# Errors that occur when enabling Salesforce with server-to-server flow
12
12
13
-
This article helps you solve errors that might occur when you try to enable Salesforce with server-to-server flow in Microsoft Copilot for Sales.
13
+
This article helps you troubleshoot errors that might occur when you try to enable Salesforce with server-to-server flow in Microsoft Copilot for Sales.
14
14
15
15
## Who is affected?
16
16
@@ -23,7 +23,13 @@ This article helps you solve errors that might occur when you try to enable Sale
23
23
|**CRM**| Salesforce |
24
24
|**Users**| Administrator |
25
25
26
-
## "Couldn't assign permission set because the integration user is inactive in Salesforce" error
26
+
## Couldn't assign permission set because the integration user is inactive in Salesforce
27
+
28
+
### Symptoms
29
+
30
+
When you try to enable Salesforce with server-to-server flow,the following error message might occur:
31
+
32
+
> Couldn't assign permission set because the integration user is inactive in Salesforce.
27
33
28
34
### Cause
29
35
@@ -39,7 +45,13 @@ To resolve this issue,
39
45
- If inactive, set the user status to active.
40
46
- If you can't activate the user, contact [Microsoft support](/microsoft-sales-copilot/get-support).
41
47
42
-
## "Couldn't create user because Salesforce integration license limit reached" error
48
+
## Couldn't create user because Salesforce integration license limit reached
49
+
50
+
### Symptoms
51
+
52
+
When you try to enable Salesforce with server-to-server flow,the following error message might occur:
53
+
54
+
> Couldn't create user because Salesforce integration license limit reached.
43
55
44
56
### Cause
45
57
@@ -79,7 +91,13 @@ During Salesforce server-to-server flow setup, a connected app is deployed to th
79
91
80
92
To resolve this issue, retry the operation. If the issue persists, gather the error details and contact [Microsoft support](/microsoft-sales-copilot/get-support).
81
93
82
-
## "No changes were made" error
94
+
## No changes were made
95
+
96
+
### Symptoms
97
+
98
+
When you try to enable Salesforce with server-to-server flow,the following error message might occur:
99
+
100
+
> No changes were made.
83
101
84
102
### Cause
85
103
@@ -89,7 +107,13 @@ During Salesforce server-to-server flow setup, a connected app is deployed to th
89
107
90
108
To resolve this issue, check for any manual changes to the connected app or profiles with the `CopilotForSales` prefix. If the changes were unintentional, revert them. Otherwise, retry the operation. If the issue continues, contact [Microsoft support](/microsoft-sales-copilot/get-support).
91
109
92
-
## "The profile name is already in use. Pick a different name or rename the existing profile in Salesforce" error
110
+
## The profile name is already in use. Pick a different name or rename the existing profile in Salesforce
111
+
112
+
### Symptoms
113
+
114
+
When you try to enable Salesforce with server-to-server flow,the following error message might occur:
115
+
116
+
> The profile name is already in use. Pick a different name or rename the existing profile in Salesforce.
0 commit comments