MS Dynamics 365 Common Data Model Explained
The Microsoft Common Data Model (CDM) is a standardized, extensible collection of schemas -- including entities, attributes, relationships, and semantic metadata -- that represents commonly used business concepts across industries. It is the foundational data language that powers Dataverse, Dynamics 365, Power Platform, and Azure data services, enabling seamless data integration and interoperability across the entire Microsoft ecosystem. At EPC Group, we leverage the CDM in every Dynamics 365 implementation to ensure our clients' data architectures are future-proof, extensible, and aligned with industry best practices.
Understanding the Common Data Model
At its simplest, the Common Data Model is a shared data language. Just as SQL provides a standard language for querying databases, the CDM provides a standard schema for representing business data. When your sales application, finance system, marketing platform, and analytics warehouse all speak the same data language, integration becomes trivial rather than painful.
The CDM is open-source (hosted on GitHub) and defines hundreds of standard entity definitions organized into subject areas: People, Places, Organizations, Products, Sales, Service, Finance, Marketing, and more. Each entity definition includes attributes (columns), data types, relationships to other entities, and semantic annotations that describe what the data represents.
For example, the CDM defines a standard "Account" entity with attributes like accountName, accountNumber, address, industry, revenue, and numberOfEmployees. When Dynamics 365 Sales, Dynamics 365 Finance, Power BI, and Azure Synapse Analytics all use this same Account definition, data flows between them without complex mapping or transformation.
CDM Architecture and Components
- Standard Entities: Over 400 predefined entity schemas covering core business concepts -- Customer, Contact, Account, Product, Invoice, Case, Lead, Opportunity, Employee, and many more. These are the building blocks that Dynamics 365 applications use natively.
- Entity Groups: Related entities organized into logical subject areas like Sales (Lead, Opportunity, Quote, Order, Invoice), Service (Case, Knowledge Article, Entitlement), and Finance (General Ledger, Budget, Tax).
- Industry Accelerators: Pre-built CDM extensions for specific verticals including Healthcare (Patient, Encounter, Care Plan), Financial Services (Banking Account, Loan, KYC), Automotive (Vehicle, Dealer, Service Appointment), and Nonprofit (Donor, Grant, Program).
- Semantic Annotations: Metadata that describes the meaning and purpose of each attribute, enabling AI and analytics tools to automatically understand data context without manual configuration.
- CDM Folders: A file format specification for storing CDM data in Azure Data Lake Storage as Parquet or CSV files with accompanying model.json metadata. This enables large-scale analytics on CDM-conformant data outside of Dataverse.
How the CDM Powers Dynamics 365
Every Dynamics 365 application stores its data in Dataverse using the CDM schema. This creates a unified data layer across all Dynamics 365 modules:
| Dynamics 365 Module | Key CDM Entities | Shared Across |
|---|---|---|
| Sales | Lead, Opportunity, Quote, Order, Invoice | Marketing, Finance, Customer Service |
| Customer Service | Case, Knowledge Article, Entitlement, SLA | Sales, Field Service |
| Finance | General Ledger, Vendor, Customer, Budget | Supply Chain, Sales |
| Supply Chain | Product, Warehouse, Purchase Order, Work Order | Finance, Sales, Field Service |
| Marketing | Contact, Segment, Campaign, Journey | Sales, Customer Service |
Because all modules share the same Account and Contact entities, a customer record updated by the sales team is immediately visible to service, finance, and marketing -- no integration or sync required.
Extending the CDM for Your Business
While the standard CDM covers most common business scenarios, every organization has unique data requirements. Dataverse allows you to extend the CDM in several ways:
- Custom Columns: Add new attributes to standard entities. For example, add a "HIPAA Consent Date" column to the Contact entity for healthcare organizations.
- Custom Tables: Create entirely new entities that follow CDM conventions. For example, a "Clinical Trial" table for pharmaceutical companies or a "Loan Application" table for financial services.
- Option Sets: Define custom picklists (dropdown values) that are shared across entities and applications, ensuring consistent data entry.
- Custom Relationships: Create additional relationships between standard and custom entities to model your specific business processes.
- Business Rules: Add server-side validation and logic to enforce data quality standards specific to your organization.
The key principle is to extend, not replace, the standard CDM entities. This preserves compatibility with Dynamics 365 application updates, Power Platform connectors, and third-party integrations.
CDM and Azure Data Integration
The CDM extends beyond Dynamics 365 into the broader Azure data ecosystem:
- Azure Synapse Link for Dataverse: Continuously replicates Dataverse data (in CDM format) to Azure Synapse Analytics for large-scale reporting, data warehousing, and machine learning -- without impacting Dynamics 365 performance.
- Azure Data Factory: Supports CDM-formatted data flows for ETL/ELT operations, enabling transformation and enrichment of CDM data at scale.
- Azure Data Lake Storage: CDM Folders store business data in Parquet format with metadata, creating a governed data lake that any analytics tool can consume.
- Power BI Dataflows: Transform and load data from any source into CDM-conformant entities, making non-Dynamics data accessible through the same standardized schema.
Why Choose EPC Group for CDM Architecture
With 29 years of enterprise Microsoft consulting and deep expertise in data architecture, EPC Group helps organizations design CDM-based data platforms that scale:
- Data model design: We architect Dataverse schemas that leverage CDM standards while accommodating your unique business requirements, ensuring long-term maintainability and upgrade compatibility.
- Industry accelerators: We implement healthcare (HL7 FHIR), financial services, and government CDM extensions that accelerate time-to-value for regulated industries.
- Data integration: Our architects design integration patterns that connect Dynamics 365 with legacy systems, third-party applications, and Azure data services using CDM as the common language.
- Governance frameworks: We establish data governance policies, naming conventions, and change management processes that keep your CDM implementation clean and consistent as it grows.
Need Help with Your Data Architecture?
Our data architects can review your current Dynamics 365 and Dataverse environment, identify opportunities to better leverage the CDM, and design an integration architecture that unifies your data landscape. Contact us for a complimentary architecture assessment.
Frequently Asked Questions
Is the Common Data Model the same as Dataverse?
No, they are related but distinct. The Common Data Model is a specification -- a standardized set of entity schemas. Dataverse is the implementation -- the cloud database platform that stores data according to CDM schemas. Think of CDM as the blueprint and Dataverse as the building. You can also use CDM schemas outside of Dataverse, such as in Azure Data Lake Storage or Power BI Dataflows.
Can I use the CDM with non-Microsoft systems?
Yes. The CDM is open-source and published on GitHub under the MIT license. Any application can read and write CDM-formatted data. SAP, Adobe, and other major vendors have contributed to and support the CDM standard. This makes it a viable interoperability standard even in heterogeneous IT environments.
What happens if I customize CDM entities heavily?
Dataverse supports extensive customization -- adding custom columns, relationships, and business logic to standard CDM entities. These customizations are preserved during Dynamics 365 updates. However, we recommend following the "extend, don't replace" principle: add custom columns to standard entities rather than creating duplicate entities. This preserves compatibility with out-of-the-box features, reports, and third-party integrations.
Are there industry-specific CDM models for healthcare?
Yes. The Healthcare Accelerator extends the CDM with entities like Patient, Encounter, Care Plan, Observation, Medication Request, and Allergy Intolerance -- aligned with the HL7 FHIR standard. This accelerator is included with Dynamics 365 and provides a foundation for building HIPAA-compliant healthcare applications, patient portals, care coordination systems, and population health analytics.
How does the CDM relate to data governance and compliance?
The CDM strengthens data governance by establishing a single, consistent definition for every business entity across your organization. When every system uses the same definition of "Customer," "Product," or "Transaction," it becomes easier to enforce data quality standards, implement access controls, and satisfy compliance requirements. Combined with Dataverse's audit logging, field-level security, and data loss prevention policies, the CDM provides a governance-ready foundation for regulated industries.
Why Organizations Choose EPC Group
EPC Group is a Houston-based Microsoft consulting firm with 29 years of enterprise implementation experience and over 10,000 successful deployments across Power BI, Microsoft Fabric, SharePoint, Azure, Microsoft 365, and Copilot. We serve organizations across all industries including Fortune 500, federal agencies, healthcare, financial services, government, manufacturing, energy, education, retail, technology, and global enterprises.
What sets EPC Group apart is our governance-first approach. Every engagement begins with a security and compliance assessment. Our team of senior architects brings hands-on delivery experience across HIPAA, SOC 2, FedRAMP, and CMMC environments. We own outcomes, not hours.
- Fixed-fee accelerators with predictable pricing and defined deliverables
- Senior architect engagement on every project, not rotating juniors
- Compliance-native delivery for regulated industries
- End-to-end coverage from strategy through 24/7 managed services
- 11,000+ enterprise engagements refined into repeatable, risk-controlled patterns
Call (888) 381-9725 or email contact@epcgroup.net for a free assessment.
Dynamics 365 Implementation: 2026 Considerations for Ms Dynamics 365 Common Data Model Explained
Dynamics 365 in 2026 is structured into 3 commercial app families: Customer Engagement (Sales, Customer Service, Field Service, Marketing) at $65-$210/user/month, Finance & Operations (Finance, Supply Chain Management, Commerce, HR) at $180-$210/user/month, and Business Central (small/midsize ERP) at $70-$100/user/month. Selection criteria are organization size, vertical-specific functionality requirements, and Microsoft 365 ecosystem fit.
Power Platform integration is the dominant Dynamics 365 differentiator in 2026: Power Automate workflows, Power Apps custom screens, Copilot Studio agents, and Dataverse as the unified data layer make Dynamics 365 deployments materially more extensible than Salesforce alternatives at the same price point. EPC Group typical Dynamics 365 implementation includes 8-15 Power Platform extensions as part of the base scope.
Decision factors EPC Group evaluates
- Customer Engagement vs Finance & Operations vs Business Central app-family selection
- Migration from Salesforce/SAP/Oracle with phased coexistence
- Power Platform extensibility scope (Power Automate, Power Apps, Copilot Studio)
- Microsoft Cloud for Industry verticalization (Healthcare, Financial Services, Retail, Manufacturing)
- Dataverse data model design for cross-app reporting
For a tailored read on this topic in your specific tenant, contact EPC Group at contact@epcgroup.net or +1 (888) 381-9725. Engagement options at /pricing.