Microsoft Dynamics 365

Analyze CRM, ERP, and customer engagement data with AI-powered insights


Connect Microsoft Dynamics 365 to Scoop for sophisticated sales pipeline analysis, customer journey tracking, and cross-functional business insights. Snapshot CRM data to track changes over time, blend with ERP and marketing systems, and gain AI-powered analysis across your entire Microsoft ecosystem.


What You Can Analyze

Dynamics ModuleAnalysis Types
SalesPipeline progression, deal velocity, win/loss analysis, forecast accuracy
Customer ServiceCase resolution, SLA compliance, customer satisfaction trends
MarketingCampaign performance, lead conversion, customer journey
Field ServiceWork order completion, resource utilization, service efficiency
Finance & OperationsRevenue trends, order fulfillment, inventory levels

Why Connect Dynamics 365 to Scoop

CapabilityBenefit
Snapshot AnalysisTrack how opportunities, cases, and accounts change over time
Cross-Module BlendingCombine Sales + Service + Finance for 360° customer view
External Data IntegrationJoin Dynamics with marketing platforms, support tools, spreadsheets
AI-Powered InsightsNatural language queries against your Dynamics data
Process VisualizationSankey diagrams showing deal flow and customer journeys

Connecting to Dynamics 365

Step 1: Select Applications Source

On the datasets page, select Applications as a source:

Step 2: Select Microsoft Dynamics 365

Choose Dynamics 365 from the application list:

Step 3: Choose Dataset Type

Select whether your data should be snapshotted or treated as transactional:

TypeUse WhenExamples
SnapshotEntity records that change over timeOpportunities, Accounts, Cases, Leads
TransactionalEvent records that don't changeActivities, Emails, Phone Calls

Step 4: Authorize Access

Complete the OAuth flow to grant Scoop access to your Dynamics 365 environment:

  1. Click Connect to Dynamics 365
  2. Sign in with your Microsoft credentials
  3. Grant permissions for the requested scopes
  4. Return to Scoop

Step 5: Select Entity and Fields

Choose the Dynamics entity and specific fields to extract:

Popular EntitiesDescription
OpportunitySales pipeline deals
AccountCustomer/company records
ContactIndividual people
LeadProspective customers
CaseCustomer service incidents
QuoteSales quotes
OrderSales orders
InvoiceCustomer invoices

Step 6: Configure and Extract

  • Name your dataset descriptively (e.g., "Dynamics Opportunities")
  • Enable Extract data now for immediate sync
  • Scoop automatically syncs overnight daily

Available Data Objects

Sales Module

EntityKey FieldsSnapshot?
Opportunityopportunityid, name, estimatedvalue, stepname, closeprobability, actualclosedateYes
Leadleadid, fullname, leadqualitycode, statuscode, estimatedvalueYes
Quotequoteid, totalamount, statecode, effectivefrom, effectivetoYes
Ordersalesorderid, totalamount, ordernumber, submitdateNo
Accountaccountid, name, revenue, numberofemployees, industrycodeYes
Contactcontactid, fullname, emailaddress1, jobtitleYes

Customer Service Module

EntityKey FieldsSnapshot?
Caseincidentid, title, prioritycode, statuscode, ownerid, createdonYes
Entitlemententitlementid, name, remainingterms, startdate, enddateYes
Knowledge Articleknowledgearticleid, title, statecode, ratingNo

Marketing Module

EntityKey FieldsSnapshot?
Campaigncampaignid, name, budgetedcost, actualcost, expectedresponseYes
Campaign Responseactivityid, responsecode, customer, createdonNo
Marketing Listlistid, listname, membercount, typeYes

Recommended Fields by Entity

For Opportunity Analysis

FieldPurpose
opportunityidUnique identifier for snapshotting
nameDeal name
stepnameCurrent pipeline stage
estimatedvalueDeal amount
closeprobabilityWin likelihood
estimatedclosedateForecast date
actualclosedateWhen deal closed
owneridAssigned sales rep
createdonAge calculation
modifiedonActivity tracking
statecodeOpen/Won/Lost
parentaccountidAccount linkage

For Case Analysis

FieldPurpose
incidentidUnique identifier
titleCase description
prioritycodeUrgency level
statuscodeCurrent status
owneridAssigned agent
createdonCase age
resolvedonResolution time
customeridCustomer linkage
productidRelated product

Snapshot Analysis

Configure as Snapshot dataset to track entity changes over time.

What Snapshotting Enables

AnalysisDescription
Pipeline movementHow opportunities progress through stages
Velocity metricsTime spent in each stage
Conversion ratesStage-to-stage win percentages
Case agingHow long cases remain unresolved
Account health trendsHow account metrics change

Snapshot Examples

Opportunity Stage Progression:

  • See exactly when deals moved from Qualify → Develop → Propose → Close
  • Calculate average time in each stage
  • Identify bottlenecks where deals stall

Case Resolution Tracking:

  • Track case status changes: New → In Progress → Waiting → Resolved
  • Measure SLA compliance over time
  • Identify agents with fastest resolution

See Snapshot Datasets for details.

Use Cases: Dynamics Only

Enhanced Sales Reporting

Move beyond Dynamics' built-in dashboards:

Native DynamicsWith Scoop
Current pipeline valuePipeline value over time
Win rate (current)Win rate trends by period
Deals by stageStage progression patterns
Rep performanceRep performance trends

Pipeline Process Analysis

Deep dive into sales process health:

  • Waterfall reports: What's been added, won, lost, or resized this period
  • Stage conversion funnels: Where deals drop off
  • Cycle time analysis: How long deals spend in each stage
  • Forecast accuracy: Predicted vs. actual close dates

Customer Journey Mapping

Understand the full lifecycle:

  • Lead → Opportunity → Customer progression
  • Conversion rates at each stage
  • Time to convert by lead source
  • Customer engagement patterns

Blending Dynamics with Other Data

Dynamics + Marketing Automation

Goal: Connect campaigns to revenue

Dynamics DataMarketing DataCombined Insight
Opportunity sourceCampaign spendCAC by campaign
Deal close datesCampaign timingAttribution analysis
Win/loss outcomesLead scoresLead quality validation

Examples:

  • HubSpot campaigns → Dynamics opportunities
  • Marketo leads → Dynamics conversions
  • Google Ads → Dynamics revenue

Dynamics + Finance (NetSuite, QuickBooks)

Goal: Complete financial visibility

AnalysisData Required
True CACMarketing spend + Sales effort + Dynamics wins
Revenue recognitionDynamics close dates + Invoice timing
Customer profitabilityDynamics deals + Actual costs

Dynamics + Customer Service (Zendesk, Freshdesk)

Goal: 360° customer view

  • Sales activity → Support ticket volume
  • Deal complexity → Service costs
  • Customer segment → Support needs
  • Churn risk scoring from combined signals

Dynamics + Product (Mixpanel, Amplitude)

Goal: Usage-driven insights

  • Product usage → Renewal likelihood
  • Feature adoption → Upsell opportunities
  • Engagement patterns → Churn prediction

Dynamics + Spreadsheets

Goal: Augment with uncaptured data

Spreadsheet DataCombined Insight
Territory mappingsSales by custom regions
Account tiersPerformance by segment
Campaign attributesChannel efficiency
Quota targetsAttainment tracking

Best Practices

Entity Selection

  • Start with Opportunities for sales analysis
  • Add Accounts for customer context
  • Include Cases if analyzing service
  • Sync Leads for full-funnel visibility

Field Selection

Always IncludePurpose
Primary key (e.g., opportunityid)Snapshot tracking
Status/stage fieldsProcess analysis
Date fields (created, modified, closed)Time analysis
Owner fieldsPerformance analysis
Amount/value fieldsFinancial analysis

Sync Frequency

Entity TypeRecommended
Active opportunitiesDaily
CasesDaily
AccountsDaily
Historical/closedWeekly

Data Quality

  • Ensure consistent stage names
  • Keep close dates updated
  • Use standard status codes
  • Maintain owner assignments

Troubleshooting

Connection Issues

  • Verify Azure AD permissions
  • Check that user has access to entities
  • Confirm Dynamics environment URL
  • Review OAuth token expiration

Missing Records

  • Check security roles in Dynamics
  • Verify entity sharing settings
  • Confirm filters aren't excluding data
  • Check business unit access

Data Discrepancies

  • Compare date ranges
  • Check timezone alignment
  • Verify currency conversion settings
  • Confirm filter definitions match

Slow Extracts

  • Reduce number of fields selected
  • Add filters for large entities
  • Use views for pre-filtered data
  • Check Dynamics API throttling

Related Topics