Help center Core configuration Integrations & migrations Configure Dynamics 365 synchronization Updated Thursday, October 29, 2026 · Marc Staine Dynamics 365 synchronization imports supported customer data and exports support cases. Configure authentication and object ownership before starting a sync or resync. Applies to: Supportbench Core. Location: Settings → Integrations → Dynamics 365. Requires Administer all integrations. Before you begin You need Administer all integrations and authorization to connect the intended provider organization. Obtain credentials through your approved provider process; keep them out of screenshots and support messages.Record existing connection, mapping and routing choices. Use controlled records to verify the intended data direction before a broad sync or live customer workflow. Configure and verify Open Settings → Integrations → Dynamics 365. Choose Authentication and verify Organization URL, Tenant ID and Client ID all identify the intended environment.For Application client secret, enter the Azure client secret value only when setting or replacing it; blank preserves the stored secret. For Delegated Microsoft user, use Authorize Microsoft user and confirm the intended identity. Choose Test connection.Use Refresh fields for current mapping choices. Set Failure notification recipients to monitored addresses.Configure Companies before Contact import, because imported Contacts depend on Company synchronization. Review the separate object modes, mappings and Case export lookback.Choose Save Changes before starting synchronization. Use Synchronize now only after reviewing the saved configuration and controlled test records.Use Resynchronize all only for an intentional full pass. After confirmation it marks every enabled domain for full synchronization and queues it immediately. Inspect status and representative results afterward.Disable synchronization pauses processing while preserving connection and mappings. Remove integration also retains imported Supportbench records; review the confirmation and dependent work. Settings reference Connection and operating controlsSettingWhat it controlsHow to chooseAuthenticationApplication client secret or Delegated Microsoft user.Use the mode approved for the provider application.Organization URL / Tenant ID / Client IDIdentifies the Dynamics organization and application.Verify all values refer to the same intended environment.Azure client secret valueSecret for Application client secret authentication; blank preserves the stored value.Enter it only through the credential control.Authorize Microsoft user / Test connectionCompletes delegated authorization or verifies the connection.Confirm the provider identity and intended organization.Failure notification recipientsRecipient for integration failures.Choose a monitored address.Refresh fields / Synchronize now / Resynchronize allRefreshes mapping choices, starts saved synchronization, or marks every enabled domain for a full pass and queues it immediately after confirmation.Inspect the impact before restarting a broad synchronization.Disable synchronization / Remove integrationPauses while retaining connection/mappings, or removes integration configuration while retaining imported Supportbench data.Review dependent processes first. Synchronization objectsSettingWhat it controlsHow to chooseCompaniesDisabled or Import; Only active, filters and mappings.Choose the fields Dynamics owns.ContactsDisabled, Import or Import + Export; Only active, filters and mappings.Confirm the related company can be resolved.CasesDisabled or Export; lookback choices are 1, 3, 7, 14, 30, 60 or 90 days.Review exported notes and field mappings before broad use. Behavior to knowContact import depends on Company configuration. Case export has mapping and notes guidance; no separate case-filter control is shown. Recommended use Treat Company synchronization as a prerequisite for imported Contact relationships, not a separate optional cleanup after contact import.Keep authentication choice and data-direction choice separate. Delegated authentication does not define which system owns a field.Review mappings, imported values and exported notes before widening the Case lookback. A full resynchronization is an operational action across enabled domains, not a status reload. Worked example: keep a customer and its support contacts associated during CRM synchronization Illustrative situation: Meridian Industrial maintains customer account data in Dynamics 365. Its support team needs the corresponding Company and Contacts in Supportbench, and wants eligible recent Cases visible to the CRM team. Choose one approved test Company, one Contact belonging to it, and one recent Case before enabling wider processing.Confirm that Organization URL, Tenant ID and Client ID refer to the intended Dynamics environment. Use the approved Authentication mode and Test connection. A successful connection to a different environment would still be the wrong setup; compare the returned identity with the agreed environment.Configure Companies → Import and review the field mappings first. Then choose Contacts → Import for this example, because Dynamics owns those contact details. Use Import + Export only when the team has explicitly agreed to send Supportbench contact changes back. Identify the fields that can be overwritten before choosing the latter.Configure Cases → Export with the 1-day lookback for the approved recent test Case and review its relevant mappings and notes. Save Changes and start Synchronize now. This example does not promise automatic replication of a Company hierarchy; inspect the actual supported relationship and field results.Verify that the Contact resolves to the intended imported Company and that the exported Case belongs to the correct customer in Dynamics. Compare representative field values and exported notes against the agreed purpose. Record the identifiers and any mismatch before broadening the export period.If the Contact cannot resolve its Company, correct and verify Company synchronization and the related mapping first. If a field is unavailable, use Refresh fields and check environment/permissions. Do not use Resynchronize all as a substitute for finding the missing relationship.After correcting the configuration, decide whether ordinary saved synchronization is sufficient or an intentional full pass is necessary. Resynchronize all queues every enabled domain immediately after confirmation, so review all domains and existing data before choosing it. Monitor failure recipients and resulting records after the run. Troubleshooting ProblemWhat to checkContact import is blocked or cannot resolve the CompanyConfigure and verify Company synchronization first, then inspect the Contact’s related Company mapping.A provider field is missingUse Refresh fields and verify the connected environment and provider permissions.Sync cannot start after editingSave the configuration and resolve any running/unsaved state before starting.A full pass started unexpectedlyResynchronize all queues all enabled domains immediately after confirmation; use status refresh to inspect rather than resync.Removed integration data is still presentImported Supportbench data is retained; removal is not an erasure workflow. Related configuration Integrations → Use the data synchronization logOrganization → Configure agent roles and division accessManage companies and contacts with the full support relationship in viewWork a case from first response to resolution Was this article helpful? Yes No Thank you for your feedback.