Microsoft Dynamics Integration
Microsoft Dynamics Integration
● A Dynamics admin who has coordinated with a Microsoft Global admin to grant prior
permission to connect the ZoomInfo integration in the Azure portal. The Dynamics admin can
then complete the connection.
Permissions
The following permissions are needed in Microsoft Dynamics:
● Read access to the Opportunity, System User, Events and Task objects
3. Go to My App and click Dynamics 365 - custom. You are redirected to your Microsoft
Dynamics CRM.
Implementation Overview
Here's the flow for initial implementation:
3. Configure your export settings (supported objects, limits and other settings)
4. Configure mapping between ZoomInfo data fields and Dynamics fields and behavior for each
field when exporting.
5. If you have ZoomInfo Copilot, Advanced Sync is enabled by default to allow ZoomInfo to
import and analyze information about your team and prospects/customers from Dynamics.
6. Turn on the integration for your users and enable them to begin exporting.
7. Understand how duplicate checking logic and data sharing with ZoomInfo works.
A service account simplifies the onboarding process as your organization evolves and changes, and
eliminates the need for your Support team to troubleshoot individual Dynamics connection issues for
your users.
The Basics
● The service account is simply a single account through which the integration is connected for
your organization's users. This account can be a dedicated Dynamics Global Admin or have the
permissions described in Permissions and Considerations.
● All exports and Dynamics Filtering jobs will be run using this account.
● Other ZoomInfo admins and users will not need to connect to Dynamics using their own
credentials.
● Assuming your org's ZoomInfo user accounts match to Dynamics user accounts, exports will
be associated with the user that made the export.
● The ZoomInfo admin that makes the initial connection to Dynamics is considered the primary
connected admin.
● Only the primary connected admin can disconnect the connection to Dynamics.
● Any other ZoomInfo admins defined in your organization can manage the configuration
settings such as adjusting mapping and export settings. However, these admins cannot
directly disconnect the connection to Dynamics.
Secondary Admins
Any other ZoomInfo admins defined in your organization are considered a secondary admin. These
admins:
● Can view the existing Dynamics integration configured for the org without connecting their
own Dynamics account to Zoominfo.
● Can manage the configuration settings such as adjusting mapping and export settings.
● Can disable all exports for users by toggling off the connections.
● Can switch the service account user by using the Change User option on the General Settings
page for the integration (Service Account option only). Ensure the new service account user
has the same Dynamics permissions as the previous user.
Reset Mapping
Some orgs utilize a sandbox instance and a production instance of their CRM for internal testing and
may switch their connected instance in ZoomInfo from one instance to the other. Check your user
mapping to ensure it reflects users in your production instance. Click the Reset Mapping reset the
mapping to reflect the users found in the currently-connected instance. The User Mapping table will
be reset based on the connected org instance and will populate with the users from that instance.
If the exporting user's email address in ZoomInfo is the same as their Dynamics user email address:
● ZoomInfo will automatically associate exports of net new records with the user that performed
the export.
If the exporting user's email address in ZoomInfo does not match their Dynamics user email
address:
● The record Owner, Created By and Last Modified By fields will reflect the primary connected
admin.
● If this logic presents an issue for your organization, you can choose the Individual User
Account Connections option instead. This will require your organization's users to individually
connect to Dynamics.
● Ensure that your org's users have the required permissions in Dynamics.
● You'll still need to make the initial admin connection for the integration using the required
Dynamics credentials.
● Once you have enabled the integration for all users by clicking the toggle to the left of the
integration in the Admin Portal, individual ZoomInfo users can connect to Dynamics.
● Admins should share the following link with users for instructions on how to connect to
Dynamics.
1. Login to ZoomInfo and select Admin Portal from the waffle menu.
2. Click Integrations.
5. Enter the Organization URL found on the Developer Resources page in Dynamics.
Note: If you're not sure where to find the Organization URL, see Identify Your Organization
URL.
7. Grant access to all users to be able to connect to Dynamics from ZoomInfo. You will need to
be a Microsoft Global admin to do this.
● If you've already closed the connection success message, navigate to the Connected tab and
click … > Settings in the Action column.
2. Select each object type you want your users to be able to export to Dynamics.
3. For each object type, set a maximum number of records a user can export to Dynamics at one
time (up to 2,000).
Note: For the Contacts object, ensure that you review the export considerations below for
details on the impact and expected behavior of account association settings.
4. Click Save to apply the changes for all users in your organization's ZoomInfo instance.
Export Considerations
For the Contacts object, you have a few options in how account association logic is applied when your
organization's users export ZoomInfo contacts to Dynamics.
● If an account does not exist, the user is asked to confirm the creation of the account. If
confirmed, ZoomInfo will assign the contact to the newly created account.
● If only one account exists, the user is asked to confirm that they want to associate the contact
with that account.
● If we match on multiple accounts, the user is asked to choose the account with which they
want to associate the contact.
On the Mapping tab, use the Accounts and Contacts, and Leads tabs to review the default mappings
for each object type and make any mapping changes.
Field Description
ZoomInfo Field Available ZoomInfo fields. Required fields are marked with an asterisk (*).
Dynamics Field Available Dynamics fields. These fields are retrieved directly from your
Dynamics instance.
Click the trash icon to remove any fields that you do not want to map.
Important: If you are mapping to a picklist field (dropdown select) in Dynamics, you will want to take
into account the internal values for each option.
For example, you may want to import both the ZoomInfo Direct Phone and Company Phone fields into
the Dynamics Business Phone field.
The first occurrence of the Business Phone field is denoted with number 1, and the second with
number 2.
Field hierarchy allows for both first and second choice values for selected Dynamics fields. For
exported records where more than one data point is available from ZoomInfo (such as phone
numbers) you can prioritize the data by preference within your mapping.
● If the test record cannot be created, this is typically due to an error in the mapping settings.
For example, mappings cannot be saved with a blank field.
● If the mappings are not set correctly, an error notification displays indicating the adjustments
needed.
● Intent ID
To map all of the possible Intent data points to custom fields, you'll need to create 5 custom fields per
Intent topic, as the custom field in Dynamics is dedicated to capturing Intent data for each specific
topic. For example, if your organization has subscribed to 6 Intent topics, and you want to capture all 5
ZoomInfo Intent data points for each topic, you'll need a total of 30 custom fields.
1. Use the toggle to turn an integration on or off for users in your organization. Toggling an
integration to off does not affect the mapping and export settings you've configured.
2. Update the settings for an integration by clicking the integration name, or by clicking … >
Settings in the Action column.
3. Delete a connected integration (including any mapping and export settings you've configured)
by clicking … > Delete in the Action column.
Duplicate Checking
When a user exports records from ZoomInfo to Dynamics, duplicate checking logic is applied to avoid
creating duplicate records within Dynamics.
For companies: Companies in ZoomInfo are equivalent to accounts in Dynamics. When exporting
companies to Dynamics, ZoomInfo will check for duplicate Dynamics accounts using criteria applied in
the following logical order:
1. ZoomInfo ID
For people: People in ZoomInfo are designated as contacts, and can be exported as Dynamics
contacts or leads.
When exporting contacts to Dynamics, ZoomInfo will check for duplicate Dynamics contacts or leads
using criteria applied in the following order:
1. ZoomInfo ID
2. Email Address
1. ZoomInfo ID
2. Email Address
Note: If a person in Dynamics exists as both a contact and a lead, ZoomInfo will present the contact
record as the duplicate.
● Account
● Contact
● Lead
● Opportunity
● Non-matched data: This data is used to create rich signals, ensuring that we can present the
full picture to your users instead of relying only on a subset that consists of matched-only data.
The specific capabilities of Advanced Sync depend on your ZoomInfo product and package.
Advanced Sync allows ZoomInfo to import and analyze information about your team and
prospects/customers from Dynamics. This sync is required to deliver auto-configurations of ZoomInfo
settings and tailored recommendations to enhance your team's productivity.
For the optimum ZoomInfo Copilot user experience, it's crucial that Copilot has read access to all
fields for the specified objects.
Here are some of the user experience enhancements delivered when Advanced Sync is enabled for
your Dynamics integration with Copilot:
● Comprehensive Data Integration: Copilot aggregates extensive Dynamics data, which is crucial for
generating detailed insights and highly targeted recommendations.
● Efficiency and Productivity: Automation of data collection and analysis reduces manual data
handling, allowing sales teams to focus on engaging with clients and closing deals.
● Enhanced Personalization: Copilot can tailor interactions more precisely to each prospect's context
and needs, enhancing personalization and relevancy at scale.
● Target Account Activation: Target accounts are automatically activated, enabling a more efficient
sales process.
● Dynamic Company Lists: Users gain a new 'My Target Accounts' company list, dynamically populated
with accounts assigned to them in Dynamics, facilitating a user-friendly experience for building
advanced searches.
● Signal Routing: When a funding signal from ZoomInfo intersects with your org's Dynamics data,
Copilot can route this signal precisely to customers whose solutions align with the growth
objectives of these freshly funded companies.
● Dynamics Filtering: ZoomInfo users can see Dynamics ownership data on contact and
company profiles within ZoomInfo. ZoomInfo users can utilize this information to refine their
ZoomInfo searches to find new prospects faster. See ZoomInfo Sales Experience for a full
description of this capability that's also available for Copilot.
● Account records: Include or exclude based on Account ownership or Account type. You can
also filter companies based on Opportunity data in Dynamics.
● Contact records: Include or exclude based on Contact ownership with an option to exclude
Contacts who have opted out of email.
● Lead records: Include or exclude based on lead ownership and status with an option to exclude
leads who have opted out of email.
● Include all owners to see all of the records matched from Dynamics, or exclude all records
matched from Dynamics.
● Create saved search alerts based on Dynamics ownership, helping users maintain a narrow
focus on prospecting efforts.
● If you chose to use the default Service Account export preference, turning on the toggle
enables the ability to export for all users in your organization.
○ Individual ZoomInfo users must connect to Dynamics with their own credentials to be
able to export.
○ Admins should share the following link with users for instructions on how to connect to
Dynamics.
2. Ensure the new admin has the same Dynamics permissions as the outgoing admin.
In this scenario, the Service Account user is also switched to the secondary admin's account.
2. On the Connected tab, temporarily turn off the integration for your organization using the
toggle.
Note: Saving the changes will enable the Edit User Mapping link.
6. Verify the user mapping configuration to ensure your org's users are mapped to Dynamics
users by clicking Edit User Mapping.
7. Return to the Connected tab and turn on the integration using the toggle.
● If you do not proactively make the mapping, the system will automatically regenerate this
mapping when the new user performs their first export.
If the system is unable to map a user, the user can still perform exports as described in Record
Ownership When Exporting Using a Service Account Connection.
Data Sharing
The Data Sharing page in the Admin Portal is enabled if your organization has not contractually opted
out of data sharing with ZoomInfo that is intended to analyze your use of connected integrations.
Data sharing helps to improve the ZoomInfo service and make recommendations to you.
● If your organization has chosen to opt-out of data sharing, the following message
displays:
As a precaution, this function is set to OFF and is not editable, in order to prevent
unintended changes that may be in conflict with your organization's contractual
terms.
● If your organization has not opted out of data sharing, the Data Sharing page displays
with the ON/OFF toggles enabled.
2. Data collection is subject to ZoomInfo's Privacy Policy. Review the policy details using the link
provided.
3. Review and manage the data sharing settings according to your organization's data sharing
preferences.
4. Over time, you can review the Contributions tab to monitor the contributions made by your
organization.