Pardot Knowledge Base

Installing the Pardot connector for hosted instances of Microsoft Dynamics CRM

Last Updated: Jul 26, 2016 | Print this Article
 
As of the Summer '16 release (June 2016), the Microsoft Dynamics connector is no longer available to new customers.

Before You Begin

If your CRM has security features enabled to restrict logins to a limited set of IP ranges, you will need to have your CRM administrator add these IP ranges to your CRM whitelist:
  • 136.147.104.20 - 136.147.104.23
  • 136.147.96.20 - 136.147.96.23
Please note:
  • The Microsoft Dynamics CRM connector is deprecated and is not available for Pardot accounts that allow multiple prospects with the same email address.
  • Pardot accounts will continue to integrate with Dynamics versions 4.0 and 2011 Rollups 8, 12, 13. New development will not be made to integrate with newer or future versions of Dynamics including all Live versions.
  • Pardot is not compatible with the ADFS method of authentication. Please do not upgrade your instance to this type of authentication, or the integration between MSCRM and Pardot will no longer function.
  • Setup of hosted versions of Dynamics require IIS configuration. It is therefore recommended that the connector setup be conducted by a system administrator.

Setting up the Connector

  1. In Pardot, Hover over Admin in the top navigation.
  2. Click Connectors in the resulting dropdown.
  3. Click + Add Connector.
  4. Select MicrosoftCRM from the list of vendors.
  5. Enter a Name for the connector that will only be used internally (i.e. "MS Dynamics Pardot Connector")
  6. Enter your Microsoft Dynamics Username and Password (note that if your Microsoft Dynamics password changes, it must be changed here as well to maintain the connection.) The user entered for the connector should have the ability to:
    • Read and update leads and contacts (found in Core Records tab of Security Role settings), including the ability to change the Owner
    • Read Accounts, Opportunities, field customizations related to Leads and Contacts, and Campaigns
    • Read users (found in Business Management tab of Security Role settings)
  7. Enter your MS Dynamics Organization Name. This can be found in MS Dynamics by going into Settings >> Customizations. Within this view you will see Organization Name.
  8. Select your CRM Deployment Type. Only standard ports (80 or 443) are allowed in the URL.
    • In a hosted environment, you have two options: You can either enable Microsoft's Internet Facing Deploy, or use standard web publishing techniques to expose the necessary MSCRM API end points that Pardot will use to communicate with MSCRM. Pardot can integrate with either setup, however the standard web setup is typically more successful while requiring less effort.
    • Regardless of IFD or simple web setup, you will want to choose one of the IFD (Internet-Facing Deployment) options, SPLA or AD. Which one will depend on your install - if you do not know, simply test each option.
    • The value for the URL field is the location of the discovery service for your particular installation.
      • SPLA URL Example - https://crm.yourcompany.com/MSCRMServices/2007/SPLA/CrmDiscoveryService.asmx?WSDL
      • AD URL Example - https://crm.yourcompany.com/MSCRMServices/2007/AD/CrmDiscoveryService.asmx?WSDL
  9. Depending on which service you are using (AD or SPLA) take the respective following actions: Note: You do not have to complete the following setup for both AD and SPLA; only for the service that you will be using within Pardot. If Windows Authentication is already enabled on one of the services (for example, AD), consider using the other service (in this case, SPLA) for Pardot, so as not to interfere with existing traffic.AD: In IIS go to the MSCRMServices/2007/AD folder Enable anonymous authentication Disable windows authenticationSPLA: In IIS go to the MSCRMServices/2007/SPLA folder Enable anonymous authentication Disable windows authenticationAlternatively, if anonymous authentication does not work for your setup and you are using NTLM, in IIS you can enable Windows authentication and disable anonymous authentication as seen below.                   dynamics 3
  10. Finally, regardless of IFD vs. standard web access, if your Dynamics IFD install is located behind a firewall, you may need to add the following IP ranges to allow access to Dynamics. These are the servers that Pardot will use to speak to your MSCRM instance.
    • 67.228.95.145
    • 67.228.168.139 to 67.228.168.141
    • 67.228.223.106 to 67.228.223.107
  11. Optional Items:
    • Allow editing of Prospect lists within the CRM -- checking this box allows CRM users to add/remove prospects from Pardot lists from within the CRM. If you check this box, you must add the Pardot Lists iframe to the Dynamics user interface by following the steps here.
    • Automatically create prospects in Pardot if they are created as a Lead or Contact in Microsoft CRM -- if this is enabled, any time a lead or contact is created in Microsoft CRM they are also created as a prospect in Pardot and synced with the CRM record. Note that this will not happen for historical leads or contacts, only those created after enabling the trigger.
  12. Click Create Connector to save the new connection.
Your Microsoft Dynamics connector will now appear in the connectors table. Note that the status is marked as Not Verified. To ensure that you have properly set up the connector, click Verify Now. If Pardot is able to successfully send and receive data to and from Microsoft Dynamics, the status will change to a checkmark denoting a proper integration.

You're now ready to set up syncing between Pardot fields with Microsoft Dynamics--continue in this series to Syncing Custom Fields with MSCRM.

Need more? Start a conversation with other Pardot users in our Success Community