Getting started with Microsoft Dynamics sync

Transcript

Hello, I’m Marisol Lopez. I’m currently a Name Support Engineer at Adobe. I’ve been using Marketo Engage for three years. I’m a Marketo Certified Expert and I’ve been working with our marketing automation customers for five years. The Microsoft Dynamics integration is a native sync. Understanding how the sync works and the setup is extremely important as it is how the two systems speak to each other. In this video, I will be talking about how to set up Microsoft Dynamics 365 Sync and sharing my tips and tricks along the way. Please note that in this video, we will be going over how to sync for Microsoft Dynamics 365 Server-to-Server connection. If you have a different version of Dynamics, we have documentation on the steps for that setup as well. The sync between Marketo Engage and Microsoft Dynamics is bi-directional for leads and contacts. If you make changes in either Marketo Engage or Microsoft Dynamics, your updates will be reflected in both systems. All other objects in their respective fields, such as accounts and opportunities, are synced one way only, from Microsoft Dynamics to Marketo Engage. What is synced between Marketo Engage and Microsoft Dynamics? Leads, contacts, accounts, users, teams, also known as groups of system users, and opportunities. The first action that needs to be taken to get the Microsoft Dynamics sync setup is that we need to download the Marketo Lead Management solution. You may see this referred as MLM and product documentation or communications with Marketo support. Home screen. Click on Admin in the navigation bar and go to the Admin section. CRM. You will click on CRM and then click Microsoft. Microsoft Dynamics. Click Download the Microsoft Solution. Download Marketo Solution. Select the appropriate solution. A zip file of the solution will now be downloaded to your device. Step 1 of 3. Install the Marketo Solution with server-to-server connection. Dynamics home page. Log in to Microsoft Office 365. In a production instance, you would click Menu and select CRM. Here we will be selecting the Solution tab. Solutions. Click on Import. Click Browse and select the solution you downloaded. Click Next. View the solution information and click View Solution Package Details. Please note that when updating the solution later on, you will need to use different settings. Please see our documentation linked below on updating the existing Marketo solution with the latest version for Dynamics. When you’re done checking the Marketo lead management package details, click Close. Solution information page. Click Next. Import options. Make sure SDK option checkbox is selected. Click Import. Wait for the import to finish. You will need to enable popups on your browser to complete the installation process. Here’s a helpful note. You may see a message saying Marketo lead management complete with warning. This is fully expected. All solutions page. Marketo lead management will now appear on all solutions page. Select the Marketo solution and click Publish all customizations. Step 2 of 3. Set up Marketo Solution with server-to-server connection. Navigate client application in Azure AD. Navigate to this Microsoft article. Sign in to the Azure portal using the account with administrator permissions. You must use an account in the same Microsoft 365 subscription as you intend to register the app with. In the Azure portal, select Azure Active Directory in the left pane and select App Registration and click on New Registration. In the Register an Application page, enter your application’s registration information. In the Name section, enter a meaningful application name that will be displayed to the users. Under the Support Account type, select Accounts in this organizational directory only. Set the redirect URI. Click on Register to create the application. On the App Overview page, set the application ID URI value by selecting Add an application ID URI and then add a scope. Set the URI value to your target environment base address. When creating a scope, the base address that you’ll be using here will be the same base address that you used when creating a redirect URI for your app. That can be found by going over to the Overview in your app, going to Redirect URIs, selecting the link here, and you will find the web redirect URIs here. This will match what you create the scope with here. On the App Overview page, hover over Application Client ID value and select Copy to Clipboard icon to copy the value as you’ll need to specify this in your application authentication code or app config file when appropriate. Select Manifest tab in the Manifest Editor. Set the Allow Public Client property to true and click on Save. Select API Permissions tab. Click on Add a Permission. Search for and choose Dataverse under the API’s My Organization Uses tab. If Dataverse is not found, then search for Common Data Service. Click on Delegated Permissions and check the options and click on Add Permissions. This completes the registration of your application in Azure Active Directory. Grant Consent for Client ID and App Registration. In order to grant consent for all users in the app registration, you will need to click on API Permissions. From there, you will click on Grant Admin Consent for Marketo. And click Yes. Back in the app registration, generate a client secret in the Admin Center by clicking Certificates and Secrets. Click the New Client Secret button. Enter a Client Secret description and click Add. Make sure to make note of the Client Secret value as you’ll need it later. It is only shown once and you won’t be able to retrieve it again. Create an Application User. You can create an unlicensed application user in your environment. This application user will be given access to your environment’s data on behalf of the user who’s using your application. In an environment, you can only have one application user for each Azure AD registered application. To get to the page, type in the URL on the screen or find them in the reference section on the tutorial page. Sign in to the Power Platform Admin Center as a System Administrator. Select Environments and then select the environment from the list. Select Settings. Select Users and Permissions and then select Application Users. Select a new app user to open the Create a New App User page. Select Add an App. In this demo, the app user has already been created. Originally, you would see the application you created shown here and you would be able to select it. Because this app user has already been created, you don’t see the option here. The selected Azure AD app is displayed under App. You can select Edit to choose another Azure AD application. Under Business Units, select a business unit from the dropdown list. After choosing a business unit, you can select Edit for Security Roles to choose security roles for the chosen business unit to add to the new application user. After adding security roles, select Save. The specific role of Marketo Sync User must be added to enable the sync. This role will be created by Marketo Solution as you import it. Select Create. Configure Marketo Solution. Go back to the Advanced Settings section and click the dropdown arrow icon next to Settings and select Marketo Config. Click Default. Click the Search button on the Marketo User field and select the Sync User you created. Click the Add button in the bottom right corner to save the changes. Click the X in the upper right to close the screen. Click the dropdown arrow icon next to Settings and select Solutions. Click the Publish All Customization button. Another thing to check is to run the Validate Microsoft Dynamics sync process. It verifies that your initial setups were done correctly. Common errors happen when Marketo Sync User role is not checked, or Marketo Solution is not properly installed, or the Sync User is not assigned on the Marketo default page in Microsoft Dynamics. To fix these errors, please refer to our documentation on how to fix Dynamics validation sync issues. To validate sync setup, you will need a few different credentials. Here’s how to access them. For the username, you’ll want to go into your Power Platform Admin Center, go to Environments, select the environment associated to the Sync User, hit See All Users. Then you’ll see your Sync User and you’ll want to copy this username to use into the Validate Sync Setup. You’ll also want to provide a URL. To access the URL, you’ll want to go into Settings, Customizations, Developer Resources, and then copy the organization service URL here. You’ll also need a Client ID. To access the Client ID, you’ll go into the App Registration, select the app you’re using, and you’ll find Client ID here. You’ll want to copy this and paste it into the Validate Sync Setup. You’ll also need the Client Secret. If you go into your app, go to Certificates and Secrets, and find the one associated to your Sync User, the Market Integration. You can find the value here. This is a value that you will have copied when it was first set. You should have a copy of this in a notepad or in a Word document, something of that sort. You’ll copy that and you’ll enter that into the Validate Sync Setup. Lastly, you’ll need a Tenant ID. If we go back to the app in Overview, you’ll see here, Tenant ID. You’ll want to copy this and insert that into the Validate Sync Setup as well. Before proceeding to Step 3, Connecting MarketoEngage and Microsoft Dynamics in MarketoEngage Admin section, you’ll want to decide if you want to restrict the number of records you sync. You can do this by setting up a custom sync filter in Microsoft Dynamics. Step 3 of 3, Connect the Marketo Solution with Server-to-Server Connection. Enter dynamic sync user information. Log into Marketo and click Admin. Click on CRM. Select Microsoft. Click Edit in Step 1, Enter Credentials. Enter the dynamic sync user information and click Save when done. Please make sure your org URL is correct as we are unable to revert the set schema changes after submission. If an incorrect org URL is used, you’ll have to obtain a new MarketoEngage subscription. If you don’t know the URL, learn how to find it in the View the Organization Service URL product doc below. The username in Marketo must match the email address of the application user in the CRM. The format can be user at domain dot com or domain backslash user.

Step 3 of 3 continues, Fields to Sync. Click Edit in Step 2, Select Fields to Sync. Select the fields that you want to sync to Marketo so they will be preselected. Click Save. Marketo stores a reference to the fields to sync. If you delete a field in Dynamics, we recommend doing so with the Sync Disabled. Then refresh the schema in Marketo by editing and saving the select fields to sync. If you have created a custom sync filter, you will want to make sure the fields used for that are syncing as well. Enable Sync. Click Edit in Step 3, Enable Sync. Caution, Marketo will not automatically dedupe against a Microsoft Dynamics Sync or when you manually enter people or leads. Read everything in the popup, enter your email address and click Start Sync. The first sync may take a few hours. Once it’s done, you’ll receive an email notification. Remember, the initial sync will take time, from days to weeks. The sync cycle runs every 5 minutes. This does not mean that it updates every 5 minutes. This means that a sync cycle runs, which can take 1 minute, 10 minutes, 30 minutes and so on, depending on the amount of updates we need to make. Once that completes, the sync pauses for 5 minutes and then restarts again. And that’s it for this instructional video. You have learned how to download the MLM solution, how to install Marketo solution for server-to-server connection and how to connect Marketo Engage from Microsoft Dynamics. I hope you find it helpful for setting up your Dynamics Sync with Marketo Engage. Thanks so much for tuning in.