Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article helps you troubleshoot errors that might occur when you try to disable Salesforce with a server-to-server flow in Microsoft Copilot for Sales.
Who is affected?
| Requirement type | Description |
|---|---|
| Client app | Microsoft Teams |
| Platform | Web and desktop clients |
| OS | Windows and Mac |
| Deployment | User managed and admin managed |
| CRM | Salesforce |
| Users | Administrators |
Couldn't get connected app details for the Salesforce organization
Symptoms
When you try to disable Salesforce with a server-to-server flow, the following error message might occur:
Couldn't get connected app details for the Salesforce organization.
Cause
When a disable request is received, the server attempts to delete deployed resources, such as the connected app and permission set. The error occurs when the server can't retrieve the connected app information during the deletion process.
Resolution
To resolve this issue, try disabling Salesforce again. If the issue persists, gather the error details and contact Microsoft support.
Couldn't remove the connected app
Symptoms
When you try to disable Salesforce with a server-to-server flow, the following error message might occur:
Couldn't remove the connected app. It may be read-only, missing, or restricted.
Cause
When a disable request is received, the server attempts to delete deployed resources, such as the connected app and permission set. The error occurs when the current user doesn't have permission to delete the connected app or the app has already been deleted.
Resolution
To resolve this issue, confirm that the connected app exists.
Sign in to Salesforce CRM as an administrator.
Go to Setup > Apps > Connected Apps > Manage Connected Apps.
Confirm that the Copilot for Sales Connected App connected app exists.
If this issue persists, contact Microsoft support for further assistance.
Couldn't remove the permission set
Symptoms
When you try to disable Salesforce with a server-to-server flow, the following error message might occur:
Couldn't remove the permission set. It may be read-only, missing, or restricted.
Cause
When a disable request is received, the server attempts to delete deployed resources, such as the connected app and permission set. The error occurs when the current user doesn't have permission to delete the permission set or the permission set has already been deleted.
Resolution
To resolve this issue, confirm that the permission set exists.
Open the Salesforce Developer Console.
Run the following query to confirm the permission set exists:
SELECT Id, Name, Label, Description FROM PermissionSet WHERE Name = 'CopilotForSalesPermissionSet'
If this issue persists, contact Microsoft support for further assistance.
Error when a resource can't be removed
Symptoms
When you try to disable Salesforce with a server-to-server flow, one of the following error messages might occur:
-
Couldn't remove the permission set assignment due to an invalid reference key.
-
Connection user ID not found or already removed.
-
Couldn't remove the permission assignment. Something else depends on it.
-
Couldn't remove the permission assignment because the assignment ID does not exist.
-
Couldn't find the connected app. It may have been deleted earlier.
-
Couldn't find the permission set. It may have been deleted earlier.
-
Couldn't find the connection user. It may have been deleted earlier.
Cause
When a disable request is received, the server attempts to delete deployed resources, such as the connected app and permission set. The error occurs when a resource either no longer exists or can't be deleted due to dependencies from other components.
Resolution
To resolve this issue, try disabling the connection again. If the issue persists, gather the error details and contact Microsoft support.
More information
If your issue is still unresolved, go to the Copilot for Sales - Microsoft Community Hub to engage with our experts.
Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.