Skip to content

Commit 4026b4f

Browse files
committed
S2S TSGs
1 parent e0477c3 commit 4026b4f

3 files changed

Lines changed: 94 additions & 0 deletions

File tree

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
title: Couldn't assign permission set when enabling Salesforce server-to-server flow
3+
description: Resolves an error that occurs due to an inactive integration user in Salesforce.
4+
author: sbmjais
5+
ms.author: shjais
6+
ms.custom: sap:CRM Permissions and Configurations\CRM Settings
7+
---
8+
9+
# Couldn't assign permission set when enabling Salesforce server-to-server flow
10+
11+
This article helps you troubleshoot the "Couldn't assign permission set because the integration user is inactive in Salesforce." error when you enable Salesforce server-to-server flow.
12+
13+
## Who is affected?
14+
15+
| Requirement type |Description |
16+
|---------|---------|
17+
|**Client app** | Teams |
18+
|**Platform** | Web and desktop clients |
19+
|**OS** | Windows and Mac |
20+
|**Deployment** | User managed and admin managed |
21+
|**CRM** | Salesforce |
22+
|**Users** | Administrator |
23+
24+
## Symptoms
25+
26+
When you try to enable Salesforce with server-to-server flow, the following error message is displayed.
27+
28+
> Couldn't assign permission set because the integration user is inactive in Salesforce.
29+
30+
## Cause
31+
32+
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 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+
34+
## Resolution
35+
36+
To resolve this issue, check if there's a user with prefix "copilotforsalesintegrationuser" in the username. If the user exists, confirm that the user is active. If the user is set to inactive manually, revert the status to active. Otherwise, reach out to Microsoft support.
37+
38+
## More information
39+
40+
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.
41+
42+
[!INCLUDE [Third-party disclaimer](../../includes/third-party-disclaimer.md)]
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
title: Unexpected errors when enabling Salesforce server-to-server flow
3+
description: Resolves an error that occurs during the Salesforce server-to-server flow setup.
4+
author: sbmjais
5+
ms.author: shjais
6+
ms.custom: sap:CRM Permissions and Configurations\CRM Settings
7+
---
8+
9+
# Unexpected errors when enabling Salesforce server-to-server flow
10+
11+
This article helps you troubleshoot some unexpected errors when you enable Salesforce server-to-server flow.
12+
13+
## Who is affected?
14+
15+
| Requirement type |Description |
16+
|---------|---------|
17+
|**Client app** | Teams |
18+
|**Platform** | Web and desktop clients |
19+
|**OS** | Windows and Mac |
20+
|**Deployment** | User managed and admin managed |
21+
|**CRM** | Salesforce |
22+
|**Users** | Administrator |
23+
24+
## Symptoms
25+
26+
When you try to enable Salesforce with server-to-server flow, one of the following error messages is displayed.
27+
28+
- Couldn't get deployment status due to incorrect ID format.
29+
- Couldn't find the connected app.
30+
- Couldn't get user license ID is missing to create connection user.
31+
- Couldn't fully remove connection data from Dataverse. Contact Sales support to request manual cleanup.
32+
- Couldn't complete the connected app or permission set deployment to Salesforce. Try again.
33+
- Couldn't complete the connected app deployment to Salesforce. Try again.
34+
- Couldn't complete the permission set deployment to Salesforce. Try again.
35+
36+
## Cause
37+
38+
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 that is created automatically. A permission set is then assigned to the integration user. In this process, some unexpected errors may occur.
39+
40+
## Resolution
41+
42+
To resolve this issue, try again. If the issue persists, gather the error details and contact Microsoft support.
43+
44+
## More information
45+
46+
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.
47+
48+
[!INCLUDE [Third-party disclaimer](../../includes/third-party-disclaimer.md)]

support/sales-copilot/toc.yml

Lines changed: 4 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: Couldn't assign permission set when enabling Salesforce server-to-server flow
16+
href: crm-permissions-and-configurations/assign-perm-set-sf-ss.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
@@ -28,6 +30,8 @@
2830
href: crm-permissions-and-configurations/salesforce-permission-error.md
2931
- name: '"This contact already exists" error when creating a CRM record'
3032
href: crm-permissions-and-configurations/duplicate-record-error.md
33+
- name: Unexpected errors when enabling Salesforce server-to-server flow
34+
href: crm-permissions-and-configurations/enable-error-sf-ss.md
3135
- name: You don't have permission for this error
3236
href: crm-permissions-and-configurations/no-admin-exists-error.md
3337
- name: Outlook side panel

0 commit comments

Comments
 (0)