Skip to content

Commit 30fc87e

Browse files
lucciz01lucciz01
authored
Merge pull request #8951 from MicrosoftDocs/sbm-s2s-enable-connection
AB#5915: Sbm s2s enable connection
2 parents 8aa830b + 70954b7 commit 30fc87e

2 files changed

Lines changed: 133 additions & 0 deletions

File tree

‎support/sales-copilot/crm-permissions-and-configurations/errors-enabling-salesforce-server-to-server-flow.md‎

Lines changed: 130 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,130 @@
1+
---
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 Microsoft Copilot for Sales.
4+
ms.date: 05/29/2025
5+
author: sbmjais
6+
ms.author: shjais
7+
manager: shujoshi
8+
ms.reviewer: marrabi
9+
ms.custom: sap:CRM Permissions and Configurations\CRM Settings
10+
---
11+
# Errors that occur when enabling Salesforce with server-to-server flow
12+
13+
This article helps you troubleshoot errors that might occur when you try to enable Salesforce with a server-to-server flow in Microsoft Copilot for Sales.
14+
15+
## Who is affected?
16+
17+
| Requirement type |Description |
18+
|---------|---------|
19+
|**Client app** | Microsoft Teams |
20+
|**Platform** | Web and desktop clients |
21+
|**OS** | Windows and Mac |
22+
|**Deployment** | User managed and admin managed |
23+
|**CRM** | Salesforce |
24+
|**Users** | Administrators |
25+
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 a 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.
33+
34+
### Cause
35+
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.
37+
38+
### Resolution
39+
40+
To resolve this issue:
41+
42+
1. In Salesforce, search for a user with the `copilotforsalesintegrationuser` prefix in the username.
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).
47+
48+
## Couldn't create user because Salesforce integration license limit reached
49+
50+
### Symptoms
51+
52+
When you try to enable Salesforce with a server-to-server flow, the following error message might occur:
53+
54+
> Couldn't create user because Salesforce integration license limit reached.
55+
56+
### Cause
57+
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.
59+
60+
### Resolution
61+
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.
63+
64+
To check the number of integration user licenses available in your Salesforce organization:
65+
66+
1. Sign in to Salesforce as an administrator.
67+
68+
2. Go to **Setup** > **Company Settings** > **Company Information**.
69+
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.
71+
72+
## Unexpected errors when enabling Salesforce with a server-to-server flow
73+
74+
### Symptoms
75+
76+
When you try to enable Salesforce with a server-to-server flow, you might receive one of the following error messages:
77+
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.
85+
86+
### Cause
87+
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+
90+
### Resolution
91+
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+
## No changes were made
95+
96+
### Symptoms
97+
98+
When you try to enable Salesforce with a server-to-server flow, the following error message might occur:
99+
100+
> No changes were made.
101+
102+
### Cause
103+
104+
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+
106+
### Resolution
107+
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).
109+
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 a 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.
117+
118+
### Cause
119+
120+
During the Salesforce server-to-server flow setup, a profile named **Copilot For 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+
122+
### Resolution
123+
124+
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+
126+
## More information
127+
128+
If your issue is still unresolved, go to the [Copilot for Sales - Microsoft Community Hub](https://techcommunity.microsoft.com/t5/viva-sales/bd-p/VivaSales) to engage with our experts.
129+
130+
[!INCLUDE [Third-party disclaimer](../../includes/third-party-disclaimer.md)]

‎support/sales-copilot/toc.yml‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@
1212
href: crm-permissions-and-configurations/update-settings-to-save-emails-error.md
1313
- name: Can't save email to CRM if enhanced email isn't enabled in Salesforce CRM
1414
href: crm-permissions-and-configurations/update-settings-in-saleforce-error.md
15+
- name: Errors when enabling Salesforce with server-to-server flow
16+
href: crm-permissions-and-configurations/errors-enabling-salesforce-server-to-server-flow.md
1517
- name: '"Fix mailbox errors in Dynamics 365" error'
1618
href: crm-permissions-and-configurations/fix-mailbox-errors-in-dynamics-365.md
1719
- name: Missing privileges error when signing in
@@ -68,4 +70,5 @@
6870
href: teams-collaboration-spaces/create-team-error.md
6971
- name: Opportunity summary not displayed in deal rooms
7072
href: teams-collaboration-spaces/opportunity-summary-not-displayed.md
73+
7174

0 commit comments

Comments
 (0)