salesforce crm connectivity

24 Topics

Access announces removal of Salesforce ODBC driver in October 2025
MS Access 2019 (and newer) ships a licensed Salesforce ODBC driver from InsightSoftware that will lose sustaining support after June 30th, 2026. But because we can no longer provide updates for the driver, the Access team has decided to accelerate the removal of this driver and remove it from the product in October 2025. Applies to: Access 2019 volume licensed and Enterprise plans Access 2021, Access 2024, and Microsoft 365 subscriptions Access 2021 and Access 2024 as part of the Office 2021 and Office 2024 perpetual licenses (standalone versions) The Salesforce ODBC driver bundled with Office includes shared libraries such as: libcurl.dll libcrypto-3.dll libssl-3.dll These libraries are located under the following path: Program Files\Microsoft Office\ODBC Drivers\Salesforce. They may also be present in different locations. Drivers installed by Office and used to access your Salesforce data will be removed on permanently on October 28, if you are using Access as part of a Microsoft 365 Apps monthly version and on November 11 if you are on the semi-annual release. For customers using perpetual Access 2019, 2021, or 2024, the drivers will be removed on November 11. You do not need to manually remove the drivers. Access currently doesn't have a way to talk directly to the Salesforce APIs so customers must continue to use the standardized ODBC driver framework that we currently support. Customers can independently purchase the Simba.DLL driver if needed from InsightSoftware. There are also other vendors that offer a Salesforce driver. Simba driver from InsightsSoftware https://insightsoftware.com/simba/ ODBC driver from devart https://www.devart.com/odbc/salesforce/ Salesforce integration from boomi https://boomi.com/solutions/application/salesforce/ Salesforce driver from cdata https://www.cdata.com/drivers/salesforce Once you purchase and install the driver, Access can connect to your Salesforce external data source. On the External Data ribbon, choose New Data Source > From Other Sources > ODBC Database We will provide more updates when available.
lindalu-MSFT
Aug 13, 2025 Place Access Blog
30KViews
2likes
1Comment
Scanning Salesforce with Purview / Connector Exception: Can not retrieve access token.
Hello everyone, I am trying to scan a demo Salesforce system that is publicly available over the internet (so no SHIR needed as I see it). Nevertheless even when trying out the SHIR as well as AIR to run a scan after registering the Salesforce with the URL, i get the error message: "Failed to testConnection: Exception when processing request: Connector Exception: Can not retrieve access token. Make sure you specify proper parameters." I know it has to do with the User Name & Password and Connected App Consumer Key & Consumer Secret combination. I created a key vault that is connected, the MI of Purview has sufficient read rights (Key Vault Secrets Officer as well as Key Vault Secrets User) on that key vault and I created 4 secrets. the concatted api user password & security token just the API User Password just the Consumer Secret of the Connected App and finally just the security token I tried every possible combination maybe I did overlook something here? From the Connect to and manage Salesforce in Microsoft Purview documentation: Select Consumer key while creating a credential. (Automatically checked) Provide the username of the user that the connected app is imitating in the User name input field. (I am using an integration user with permission set for this) Store the password of the user that the connected app is imitating in an Azure Key Vault secret. If your self-hosted integration runtime machine's IP is within the trusted IP ranges for your organization set on Salesforce, provide just the password of the user. Otherwise, concatenate the password and security token as the value of the secret. The security token is an automatically generated key that must be added to the end of the password when logging in to Salesforce from an untrusted network. Learn more about how to get or reset a security token. (not applicable but I also tried through an SHIR with the concatenated password and security key) Provide the consumer key from the connected app definition. You can find it on the connected app's Manage Connected Apps page or from the connected app's definition. (took this exactly) Stored the consumer secret from the connected app definition in an Azure Key Vault secret. You can find it along with consumer key. (took this exactly and stored in key vault) I found an older post where some people seem to have made it work: Trying to connect purview to salesforce ... - Microsoft Q&A So I think you always need to concatenate the user password and securtiy token when using AIR too no? I'd really appreciate any input or ideas! Best regards and a nice day to you all, Matthias
Solved
MatthiasSobiech
Feb 11, 2025 Place Microsoft Purview
466Views
1like
4Comments
Unable to see the Contract & custom Salesforce object records using Microsoft Copilot for Sales
Hi, We could see the Opportunity records of the Accounts from Salesforce on outlook using Microsoft CoPilot for Sales. But unable to see the Contract & custom Salesforce object records related to that account. We have provided all the required permissions to the objects (entities - Opportunity, Contract & custom objects) Via Permission Sets on Salesforce. We are working on high priority POC for one of our customers. Please help us on this? Thanks Santosh
Santosh_Katti
Mar 13, 2024 Place Microsoft Copilot for Sales Discussion
11KViews
1like
3Comments
Add custom entities to Viva Sales through the new forms customization
With the new capabilities in the Viva Sales forms customization, admins can add custom as well as new out-of-the-box entities, control list views and much more. https://cloudblogs.microsoft.com/dynamics365/it/2023/06/05/enhancing-seller-productivity-customize-viva-sales-forms/
eranmanor
Jun 07, 2023 Place Microsoft Copilot for Sales Discussion
1.1KViews
1like
0Comments