Connecting to Dynamics CRM
To connect, set Url to the root URL of your organization and set User, Password, and CRMVersion.
Internet Facing DeploymentsFor Dynamics CRM with IFD, set InternetFacingDeployment to true.
Authenticating to CRM On-Premises
Additionally for CRM on-premises, select an authentication method. By default, the provider uses Windows (NTLM) authentication. To use another authentication type, such as Kerberos delegation, set AuthScheme.
Fine Tuning Data Access
Use the following connection properties to control column name identifiers and other aspects of data access useful in more advanced integrations:
Securing Dynamics CRM Connections
By default, the provider attempts to negotiate SSL/TLS by checking the server's certificate against the system's trusted certificate store. To specify another certificate, see the SSLServerCert property for the available formats to do so.
Connecting Through a Firewall or Proxy
By default, the provider will connect through the Windows system proxy if one is defined. To connect to other proxies, set ProxyAutoDetect to false and in addition set the following.
To authenticate to an HTTP proxy, set ProxyAuthScheme, ProxyUser, and ProxyPassword, in addition to ProxyServer and ProxyPort.
To connect to other proxies, set FirewallType, FirewallServer, and FirewallPort. To tunnel the connection, set FirewallType to TUNNEL. To authenticate to a SOCKS proxy, set FirewallType to SOCKS5. Additionally, specify FirewallUser and FirewallPassword.
Troubleshooting the Connection
To show provider activity from query execution to HTTP calls, use Logfile and Verbosity. The examples of common connection errors below show how to use these properties to get more context. Contact the support team for help tracing the source of an error or circumventing a performance issue.
- Authentication errors: Typically, recording a Logfile at Verbosity 4 is necessary to get full details on an authentication error.
- Queries time out: A server that takes too long to respond will exceed the provider's client-side timeout. Often, setting the Timeout property to a higher value will avoid a connection error. Another option is to disable the timeout by setting the property to 0. Setting Verbosity to 2 will show where the time is being spent.