Salesforce Copilot: Fix Incorrect Custom Domain Configuration for Seamless Sales Integration

Table of Contents

This article addresses and provides solutions for issues encountered when users input an incorrect custom domain while attempting to sign in to Salesforce CRM. This problem specifically impacts users leveraging the Salesforce Copilot for Sales integration, particularly within the Outlook add-in environment. Understanding and rectifying this configuration error is crucial for ensuring a smooth and uninterrupted sales workflow. This guide will walk you through identifying the affected users, recognizing the symptoms, understanding the root cause, and implementing the necessary resolution to restore seamless integration.

Who is Affected?¶

This issue primarily affects users who are attempting to access Salesforce CRM through Microsoft Copilot for Sales. The scope of impact spans across various platforms, operating systems, and deployment scenarios, ensuring broad coverage within organizations utilizing these tools. The table below summarizes the specific user profiles and environments susceptible to this configuration problem.

Requirement type	Description
Client app	Copilot for Sales Outlook add-in
Platform	Web and desktop clients
OS	Windows and Mac
Deployment	User managed and admin managed
CRM	Salesforce
Users	Users trying to sign in to Salesforce

As detailed in the table, the problem is not confined to a specific operating system or deployment method, indicating a potential widespread impact across diverse IT infrastructures. Users on both web and desktop clients, running Windows or Mac, and under both user-managed and admin-managed deployments can experience this issue. The common thread is the attempt to sign in to Salesforce through the Copilot for Sales Outlook add-in, highlighting the integration point as the area of concern. Therefore, any user within an organization relying on this integration for their daily sales activities could potentially be affected if an incorrect custom domain is configured.

Symptoms¶

The most prominent symptom of an incorrect custom domain configuration is the inability to access the Salesforce environment after attempting to sign in through the Copilot for Sales add-in for Outlook. Instead of successful login and access to Salesforce functionalities, users are met with an error message indicating an authentication failure. This error message is crucial for diagnosing the problem and typically appears as follows:

OAuth2 authorization flow failed for service ‘Salesforce’. OAuth 2 sign in failed to exchange code for access token. Client ID and secret sent in form body.. Response status code-BadRequest. Response body: {"error":"invalid_grant","error_description":"authentication failure"} Client ID and secret sent in Basic authorization header.. Response status code=BadRequest. REsponse body: {"error":"invalid_grant","error_description":"authentication failure"}

This error message, while seemingly technical, clearly points to an issue within the OAuth 2.0 authorization process, which is the standard protocol for secure delegated access. The “invalid_grant” error specifically indicates that the provided credentials or authorization grant are invalid, leading to the failure in exchanging the authorization code for an access token. This breakdown in the token exchange process effectively prevents the Copilot for Sales add-in from establishing a secure and authorized connection with the Salesforce CRM. Users experiencing this symptom will find themselves locked out of their Salesforce environment when attempting to access it through the intended integration point within Outlook. The consistency of this error message across different scenarios helps to quickly narrow down the potential causes and focus on domain configuration as the primary suspect.

Cause¶

The root cause of this login failure is directly attributed to entering an incorrect custom domain during the Salesforce CRM sign-in process. Salesforce allows organizations to set up custom domains to personalize their Salesforce URLs, often reflecting their company branding and enhancing security. However, when configuring the Copilot for Sales integration, it is imperative to use the exact and correct custom domain associated with your organization’s Salesforce instance. Entering a domain that is misspelled, outdated, or simply incorrect will lead to the authentication errors described in the symptoms section.

Custom domains in Salesforce are not just cosmetic changes; they are integral to how your organization’s Salesforce instance is identified and accessed. The domain acts as the unique address for your Salesforce environment. When Copilot for Sales attempts to connect to Salesforce, it relies on this domain to locate and authenticate against the correct server. An incorrect domain effectively points the Copilot for Sales add-in to the wrong location, preventing it from finding your organization’s Salesforce instance and thus leading to authentication failures. This issue highlights the importance of precision and accuracy when configuring integration settings, particularly concerning domain names and server addresses. Even a minor typographical error in the custom domain can disrupt the entire integration process.

Resolution¶

The resolution to this problem is straightforward and involves ensuring the correct custom domain is entered when signing in to Salesforce CRM through the Copilot for Sales add-in. Users need to carefully verify and input the accurate custom domain that is specifically configured for their organization’s Salesforce instance. This typically involves checking internal documentation, consulting with IT administrators, or confirming the domain directly within the Salesforce setup if accessible through other means.

For example, a correct custom domain might resemble yourcompany.my.salesforce.com. In this example, yourcompany.my.salesforce.com represents the host, which is the crucial part to verify and enter accurately. The /login path, as shown in some configurations, points to a custom sign-in page, but the host domain remains the primary identifier. Users should pay close attention to every character of the domain, ensuring there are no typos, extra spaces, or incorrect extensions.

To implement the resolution, users should:

1. Identify the Correct Custom Domain: Confirm the exact custom domain for your organization’s Salesforce instance. Consult internal resources or IT support if needed.
2. Re-enter the Domain: When prompted to sign in to Salesforce within the Copilot for Sales add-in, carefully type or paste the correct custom domain. Double-check for any errors before proceeding.
3. Attempt Sign-in Again: After entering the verified custom domain, attempt to sign in to Salesforce CRM once more.

By meticulously ensuring the accuracy of the custom domain, users can effectively bypass the authentication errors and establish a successful connection between Copilot for Sales and Salesforce CRM, restoring the intended integration functionality. It is a simple yet critical step to resolve this common login issue.

More Information¶

If, after implementing the resolution steps and ensuring the correct custom domain is entered, the issue persists, further assistance and community support are available. For additional troubleshooting and to engage with experts and peers, users are encouraged to explore community resources dedicated to Copilot for Sales. These platforms offer forums, knowledge bases, and direct interaction with experienced users and support professionals who can provide more tailored guidance and solutions for complex or persistent issues.

These community hubs often contain a wealth of information, including frequently asked questions, troubleshooting guides, and discussions on various aspects of Copilot for Sales, including integration with Salesforce. Engaging with these resources can provide alternative perspectives, advanced troubleshooting techniques, and insights into less common configuration problems. The collective knowledge and experience within these communities can be invaluable in resolving issues that may not be immediately apparent or easily solved through standard troubleshooting steps.

Third-party information disclaimer:

It is important to acknowledge that the third-party products discussed in this article, such as Salesforce, are manufactured by companies independent of Microsoft. While this article aims to provide guidance and solutions for integration issues, Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these third-party products. Users should refer to the respective vendors for product-specific warranties, support, and terms of service. This disclaimer ensures clarity on the scope of Microsoft’s responsibility and emphasizes the role of third-party vendors in the functionality and support of their products.

If you continue to experience difficulties or have further questions, we encourage you to leave a comment below to engage with the community and share your experiences. Your input can help others facing similar challenges and contribute to a more comprehensive understanding of these integration scenarios.