|
| 1 | +--- |
| 2 | +title: Errors When Enabling Salesforce With Server-to-server Flow |
| 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 |
| 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 solve errors that might occur when you try to enable Salesforce with server-to-server flow in Microsoft Copilot for Sales. |
| 14 | + |
| 15 | +## Who is affected? |
| 16 | + |
| 17 | +| Requirement type |Description | |
| 18 | +|---------|---------| |
| 19 | +|**Client app** | Teams | |
| 20 | +|**Platform** | Web and desktop clients | |
| 21 | +|**OS** | Windows and Mac | |
| 22 | +|**Deployment** | User managed and admin managed | |
| 23 | +|**CRM** | Salesforce | |
| 24 | +|**Users** | Administrator | |
| 25 | + |
| 26 | +## "Couldn't assign permission set because the integration user is inactive in Salesforce" error |
| 27 | + |
| 28 | +### Cause |
| 29 | + |
| 30 | +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. |
| 31 | + |
| 32 | +### Resolution |
| 33 | + |
| 34 | +To resolve this issue, |
| 35 | + |
| 36 | +1. In Salesforce, search for a user with the `copilotforsalesintegrationuser` prefix in the username. |
| 37 | + |
| 38 | +2. Confirm the user is active. |
| 39 | + - If inactive, set the user status to active. |
| 40 | + - If you can't activate the user, contact [Microsoft support](/microsoft-sales-copilot/get-support). |
| 41 | + |
| 42 | +## "Couldn't create user because Salesforce integration license limit reached" error |
| 43 | + |
| 44 | +### Cause |
| 45 | + |
| 46 | +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. Salesforce Integration user license is assigned to this integration user. The error occurs when the maximum allowed number of Salesforce Integration user licenses has already been reached. |
| 47 | + |
| 48 | +### Resolution |
| 49 | + |
| 50 | +To resolve this issue, check if the maximum allowed number of Salesforce Integration user licenses has been reached. If so, you need to either reassign existing integration users to other licenses or purchase more licenses. |
| 51 | + |
| 52 | +To check the number of integration user licenses available in your Salesforce organization: |
| 53 | + |
| 54 | +1. Sign in to Salesforce as an administrator. |
| 55 | + |
| 56 | +2. Go to **Setup** > **Company Settings** > **Company Information**. |
| 57 | + |
| 58 | +3. Under **User Licenses**, check the number of **Salesforce Integration** licenses available under the **Remaining Licenses** column. If the number is 0, you need to either deactivate existing integration users or change their licenses to other types. You can also purchase more licenses. |
| 59 | + |
| 60 | +## Unexpected errors when enabling Salesforce with server-to-server flow |
| 61 | + |
| 62 | +### Symptoms |
| 63 | + |
| 64 | +When you try to enable Salesforce with server-to-server flow, you might receive one of the following error messages: |
| 65 | + |
| 66 | +- > Couldn't get deployment status due to incorrect ID format. |
| 67 | +- > Couldn't find the connected app. |
| 68 | +- > Couldn't get user license ID is missing to create connection user. |
| 69 | +- > Couldn't fully remove connection data from Dataverse. Contact Sales support to request manual cleanup. |
| 70 | +- > Couldn't complete the connected app or permission set deployment to Salesforce. Try again. |
| 71 | +- > Couldn't complete the connected app deployment to Salesforce. Try again. |
| 72 | +- > Couldn't complete the permission set deployment to Salesforce. Try again. |
| 73 | +
|
| 74 | +### Cause |
| 75 | + |
| 76 | +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 might occur. |
| 77 | + |
| 78 | +### Resolution |
| 79 | + |
| 80 | +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 | + |
| 82 | +## "No changes were made" error |
| 83 | + |
| 84 | +### Cause |
| 85 | + |
| 86 | +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 same permission set has already been assigned to the user. |
| 87 | + |
| 88 | +### Resolution |
| 89 | + |
| 90 | +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 | + |
| 92 | +## "The profile name is already in use. Pick a different name or rename the existing profile in Salesforce" error |
| 93 | + |
| 94 | +### Cause |
| 95 | + |
| 96 | +During 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, thereby preventing the creation process. |
| 97 | + |
| 98 | +### Resolution |
| 99 | + |
| 100 | +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). |
| 101 | + |
| 102 | +## More information |
| 103 | + |
| 104 | +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. |
| 105 | + |
| 106 | +[!INCLUDE [Third-party disclaimer](../../includes/third-party-disclaimer.md)] |
0 commit comments