Skip to content

Commit 1b30cfb

Browse files
Merge pull request #10460 from MicrosoftDocs/main
Auto Publish – main to live - 2026-01-07 18:00 UTC
2 parents 15f4c05 + 617db94 commit 1b30cfb

1 file changed

Lines changed: 59 additions & 41 deletions

File tree

Lines changed: 59 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,13 @@
11
---
2-
title: Errors When Enabling Salesforce with Server-to-Server Flow
3-
description: Troubleshoot errors that might occur when enabling Salesforce with a server-to-server flow in Sales app.
4-
ms.date: 11/20/2025
5-
author: sbmjais
6-
ms.author: shjais
7-
manager: shujoshi
8-
ms.reviewer: marrabi
2+
title: Errors When Enabling Salesforce in Server-to-Server Flow
3+
description: Troubleshoot errors that occur when you try to enable Salesforce with a server-to-server flow in the Sales app.
4+
ms.date: 12/16/2025
5+
ms.reviewer: marrabi, shjais, v-shaywood
96
ms.custom: sap:CRM Permissions and Configurations\CRM Settings
107
---
11-
# Errors that occur when enabling Salesforce with server-to-server flow
8+
# Errors occur when enabling Salesforce with a server-to-server flow
129

13-
This article helps you troubleshoot errors that might occur when you try to enable Salesforce with a server-to-server flow in Sales app.
10+
This article helps you troubleshoot errors that occur when you try to enable Salesforce with a server-to-server flow in the Sales app.
1411

1512
## Who is affected?
1613

@@ -27,107 +24,128 @@ This article helps you troubleshoot errors that might occur when you try to enab
2724

2825
### Symptoms
2926

30-
When you try to enable Salesforce with a server-to-server flow, the following error message might occur:
27+
When you try to enable Salesforce with a server-to-server flow, you receive the following error message:
3128

3229
> Couldn't assign permission set because the integration user is inactive in Salesforce.
3330
3431
### Cause
3532

36-
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 that is created automatically. A permission set is then assigned to the integration user. The error occurs when the integration user is inactive in Salesforce. The permission set can't be assigned to an inactive user.
33+
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 that's created automatically. A permission set is then assigned to the integration user. The error occurs if the integration user is inactive in Salesforce. The error occurs because a permission set can't be assigned to an inactive user.
3734

3835
### Resolution
3936

4037
To resolve this issue:
4138

4239
1. In Salesforce, search for the **Sales Integration User** user.
43-
44-
2. Confirm the user is active.
45-
- If inactive, set the user status to active.
46-
- If you can't activate the user, contact [Microsoft support](/microsoft-sales-copilot/get-support).
40+
1. Check whether the user is active.
41+
1. If the user is inactive, set the user status to active. If you can't activate the user, contact [Microsoft Support](/microsoft-sales-copilot/get-support).
4742

4843
## Couldn't create user because Salesforce integration license limit reached
4944

5045
### Symptoms
5146

52-
When you try to enable Salesforce with a server-to-server flow, the following error message might occur:
47+
When you try to enable Salesforce with a server-to-server flow, you receive the following error message:
5348

5449
> Couldn't create user because Salesforce integration license limit reached.
5550
5651
### Cause
5752

58-
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 that is created automatically. A Salesforce Integration user license is assigned to this integration user. The error occurs when the maximum number of Salesforce Integration user licenses has already been reached.
53+
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 that's created automatically. A Salesforce Integration user license is assigned to this integration user. The error occurs if the maximum number of Salesforce Integration user licenses is reached.
5954

6055
### Resolution
6156

62-
To resolve this issue, check if the maximum number of Salesforce Integration user licenses has been reached. If so, you need to reassign existing integration users to other licenses or purchase more licenses.
57+
To resolve this issue, check whether you reached the maximum number of Salesforce Integration user licenses. If you reached the maximum, reassign existing integration users to other licenses, or purchase more licenses.
6358

6459
To check the number of integration user licenses available in your Salesforce organization:
6560

6661
1. Sign in to Salesforce as an administrator.
6762

68-
2. Go to **Setup** > **Company Settings** > **Company Information**.
63+
1. Go to **Setup** > **Company Settings** > **Company Information**.
6964

70-
3. Under **User Licenses**, check the number of available **Salesforce Integration** licenses under the **Remaining Licenses** column. If the number is **0**, you need to deactivate existing integration users or change their licenses to other types. You can also purchase more licenses.
65+
1. Under **User Licenses**, check the number of available **Salesforce Integration** licenses in the **Remaining Licenses** column. If the number is **0**, deactivate existing integration users or change their licenses to other types. You can also purchase more licenses.
7166

72-
## Unexpected errors when enabling Salesforce with a server-to-server flow
67+
## Errors when enabling Salesforce with a server-to-server flow
7368

7469
### Symptoms
7570

76-
When you try to enable Salesforce with a server-to-server flow, you might receive one of the following error messages:
71+
When you try to enable Salesforce with a server-to-server flow, you receive one of the following error messages:
72+
73+
> Couldn't get deployment status due to incorrect ID format.
74+
75+
> Couldn't find the connected app.
76+
77+
> Couldn't get user license ID is missing to create connection user.
78+
79+
> Couldn't fully remove connection data from Dataverse. Contact Sales support to request manual cleanup.
80+
81+
> Couldn't complete the connected app or permission set deployment to Salesforce. Try again.
7782
78-
- > Couldn't get deployment status due to incorrect ID format.
79-
- > Couldn't find the connected app.
80-
- > Couldn't get user license ID is missing to create connection user.
81-
- > Couldn't fully remove connection data from Dataverse. Contact Sales support to request manual cleanup.
82-
- > Couldn't complete the connected app or permission set deployment to Salesforce. Try again.
83-
- > Couldn't complete the connected app deployment to Salesforce. Try again.
84-
- > Couldn't complete the permission set deployment to Salesforce. Try again.
83+
> Couldn't complete the connected app deployment to Salesforce. Try again.
84+
85+
> Couldn't complete the permission set deployment to Salesforce. Try again.
8586
8687
### Cause
8788

88-
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 that is created automatically. A permission set is then assigned to the integration user. In this process, some unexpected errors might occur.
89+
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 that's created automatically. A permission set is then assigned to the integration user. During this process, errors occur.
8990

9091
### Resolution
9192

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).
93-
94-
> [!NOTE]
95-
> You might encounter an error message that's not listed above. This issue can happen for several reasons. For example, your Salesforce organization might have a validation rule that requires specific values for user records. If this prevents the integration user from being created, try temporarily disabling the validation rule. Once the integration user is created, you can re-enable the rule.
93+
To resolve this issue, retry the operation. If the problem continues, gather the error details, and contact [Microsoft Support](/microsoft-sales-copilot/get-support).
9694

9795
## No changes were made
9896

9997
### Symptoms
10098

101-
When you try to enable Salesforce with a server-to-server flow, the following error message might occur:
99+
When you try to enable Salesforce with a server-to-server flow, you receive the following error message:
102100

103101
> No changes were made.
104102
105103
### Cause
106104

107-
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 that is created automatically. A permission set is then assigned to the integration user. The error occurs when the same permission set has already been assigned to the user.
105+
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 that's created automatically. A permission set is then assigned to the integration user. The error occurs if the same permission set is already assigned to the user.
108106

109107
### Resolution
110108

111-
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).
109+
To resolve this problem, check for any manual changes to the connected app or profiles that have the `CopilotForSales` prefix. If you find unintentional changes, revert them. Otherwise, retry the operation. If the problem continues, contact [Microsoft Support](/microsoft-sales-copilot/get-support).
112110

113111
## The profile name is already in use. Pick a different name or rename the existing profile in Salesforce
114112

115113
### Symptoms
116114

117-
When you try to enable Salesforce with a server-to-server flow, the following error message might occur:
115+
When you try to enable Salesforce with a server-to-server flow, you receive the following error message:
118116

119117
> The profile name is already in use. Pick a different name or rename the existing profile in Salesforce.
120118
121119
### Cause
122120

123-
During the Salesforce server-to-server flow setup, a profile named **Sales Integration Profile** is created in the Salesforce organization. The error occurs when a profile with the same name already exists, preventing the creation process.
121+
During the Salesforce server-to-server flow setup, the process creates a profile that's named **Sales Integration Profile** in the Salesforce organization. The error occurs if a profile that has the same name already exists. This situation prevents you from creating a new profile.
124122

125123
### Resolution
126124

127-
To resolve this issue, check if a profile with the same name already exists in the Salesforce organization. If it was created before enabling the server-to-server flow, rename the existing profile and try again. If the profile wasn't created previously, contact [Microsoft support](/microsoft-sales-copilot/get-support).
125+
To resolve this issue, check whether a profile that has the same name already exists in the Salesforce organization. If you created the profile before you enabled the server-to-server flow, rename the existing profile, and then try again. If you didn't create the profile, contact [Microsoft Support](/microsoft-sales-copilot/get-support).
126+
127+
## Required fields are missing
128+
129+
### Symptoms
130+
131+
When you try to enable Salesforce with a server-to-server flow, you receive the following error message:
132+
133+
> Required fields are missing: \<FieldNames\>
134+
135+
### Cause
136+
137+
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 that's created automatically. This error occurs if custom validation rules for user creation prevent the integration user from being automatically created in Salesforce.
138+
139+
### Resolution
140+
141+
To resolve this issue:
142+
143+
1. Temporarily disable the custom validation rules for user creation. To make this change, go to **Setup** > **Object Manager** > **User** > **Validation Rules**.
144+
1. Try again to set up the Salesforce connection in the [Sales app admin settings](/microsoft-sales-copilot/connect-agent-datasource).
145+
1. After the Salesforce connection is set up and the integration user is created, re-enable your validation rules.
128146

129147
## More information
130148

131-
If your issue is still unresolved, go to the [Sales in Microsoft 365 Copilot - Microsoft Community Hub](https://techcommunity.microsoft.com/t5/viva-sales/bd-p/VivaSales) to engage with our experts.
149+
If your problem isn't resolved, go to the [Sales in Microsoft 365 Copilot - Microsoft Community Hub](https://techcommunity.microsoft.com/t5/viva-sales/bd-p/VivaSales) to engage with experts.
132150

133151
[!INCLUDE [Third-party disclaimer](../../includes/third-party-disclaimer.md)]

0 commit comments

Comments
 (0)