Pre-Call Preparation Checklist — Microsoft Dynamics 365

Last updated: June 9, 2026

Complete the items below before your CRED integration setup call. This ensures we can connect and configure your Dynamics 365 instance without blockers.

Admin Account

  • ☐ Identify the admin who will be on the call and authorising the connection

  • ☐ Confirm they have the Dynamics 365 Administrator (or Global Admin) role in Azure AD

  • ☐ Confirm they have the System Administrator or System Customizer security role in Dynamics 365

  • ☐ Confirm they can complete MFA during the call (if enabled)

  • ☐ Confirm they can grant OAuth consent for third-party applications

Dynamics 365 Instance

  • ☐ Know your Dynamics 365 subdomain (the part before .dynamics.com in your URL — e.g., yourcompany.crm or yourcompany.crm4)

  • ☐ Decide which environment to connect: Production or Sandbox

  • ☐ Admin is logged into Dynamics 365 in their browser before the call

  • ☐ Web API access is enabled for the admin account

Data Scope

  • ☐ Decide which entities to sync (Account, Contact, Opportunity, Lead, Campaign, Task, Note, Email, Custom Entity, etc.)

  • ☐ Know your approximate record volumes (e.g., ~5,000 accounts, ~25,000 contacts)

  • ☐ Identify any custom objects that need syncing

Write-Back (If Applicable)

  • ☐ Decide: read-only or bidirectional sync

  • ☐ If writing back to Dynamics on day one: custom fields created on target entities

  • ☐ Field-level security grants Read + Write to the CRED service account on those fields

  • ☐ Review any required fields or validation rules/plugins that could block incoming records

  • ☐ Run Publish All Customizations after any field changes

Network & Security

  • ☐ No IP restrictions blocking external API access (or contact CRED for IPs to allowlist)

  • ☐ Azure AD Conditional Access policies won't block the OAuth flow

  • ☐ Note any other integrations currently syncing with Dynamics (e.g., HubSpot, Marketo, Power Automate)