Semantic model guide. Dataset vs Semantic Model, calculation groups, field parameters, Direct Lake, governance.
Microsoft Power BI Semantic Model: Enterprise Guide (2026)
A Microsoft Power BI semantic model (formerly "dataset") is the foundational analytics layer that defines tables, relationships, measures, hierarchies, sensitivity labels, and security for enterprise Microsoft Power BI deployments. In 2026, Microsoft Power BI semantic models are the grounding layer for Microsoft Power BI Copilot, Microsoft 365 Copilot Chat, and Microsoft Copilot Studio agents.
EPC Group has delivered enterprise Microsoft Power BI semantic models since the original Microsoft Power BI beta program (Project Crescent, 2010-2013).
TL;DR — Microsoft Power BI Semantic Model 8-Component Framework
| Component |
Purpose |
| 1. Tables (Fact + Dimension) |
Star-schema foundation |
| 2. Relationships |
Single-direction filtering |
| 3. DAX Measures |
Calculated business metrics |
| 4. Calculation Groups |
DAX organization at scale |
| 5. Hierarchies |
Natural drill-down paths |
| 6. RLS / OLS |
Security model |
| 7. Sensitivity Labels |
Microsoft Purview integration |
| 8. Microsoft Power BI Copilot |
F64+ capacity grounding |
Component 1: Tables
Fact Tables
- Transactional data (sales, orders, claims, encounters, trades)
- High volume (1M-100M+ rows)
- Foreign keys to dimensions
- Numeric measures
- Date keys for time intelligence
Dimension Tables
- Conformed dimensions (Customer, Product, Date, Geography, Organization)
- Lower volume (1K-10M rows)
- Surrogate primary keys (integer)
- Descriptive attributes for slicing/filtering
- Slowly Changing Dimension (SCD) handling
- DimCustomer
- DimProduct
- DimDate
- DimGeography
- DimOrganization
- DimEmployee
- DimAccount (for financial scenarios)
Component 2: Relationships
Cardinality
- One-to-many (most common)
- Many-to-many (use bridge table when possible)
- One-to-one (rare)
Filter Direction
- Single-direction (default, recommended)
- Bidirectional (only when necessary, document reason)
Inactive Relationships
- For multi-date scenarios (OrderDate vs ShipDate)
- Activated via USERELATIONSHIP() in DAX measures
Component 3: DAX Measures
(Detail in Power BI DAX Formulas Enterprise Reference Guide)
Standard Measure Categories
- Aggregation (SUM, AVERAGE, COUNT)
- Time Intelligence (YTD, QTD, MTD, prior year)
- Filter (CALCULATE patterns)
- Iterator (SUMX, AVERAGEX)
- Statistical (MEDIAN, PERCENTILE)
Measure Best Practices
- Variables (VAR) for clarity + performance
- DIVIDE() for safe division
- Microsoft Power BI Performance Analyzer for tuning
- Microsoft Power BI Copilot generates DAX
Component 4: Calculation Groups
When to Use
- Time intelligence scaling (YTD, QTD, MTD, prior year × N base measures = N×4 measures)
- Currency conversion
- Unit of measure conversion
- Format string variations
Calculation Group Pattern
Calculation Group: Time Intelligence
Items:
- Current Period
- YTD
- QTD
- MTD
- Prior Year
- YoY Growth
Apply to base measures via SELECTEDMEASURE().
Component 5: Hierarchies
Natural Drill-Down Paths
- Date Hierarchy (Year > Quarter > Month > Day)
- Geography Hierarchy (Country > State > City > ZIP)
- Product Hierarchy (Category > Subcategory > Product)
- Organization Hierarchy (Division > Department > Team > Employee)
Hierarchies + Microsoft Power BI Copilot
Microsoft Power BI Copilot uses hierarchies for natural language Q&A. Well-defined hierarchies improve Microsoft Copilot answer quality.
Component 6: Row-Level Security (RLS) + Object-Level Security (OLS)
Row-Level Security
- Static RLS (fixed DAX filters)
- Dynamic RLS (USERPRINCIPALNAME() / USERNAME() based)
- Hierarchical RLS (manager-employee chains)
- Multi-tenant RLS (Microsoft Power BI Embedded scenarios)
Object-Level Security
- Column-level hiding
- Microsoft Purview sensitivity label respect
- Restricted-tier columns hidden from non-authorized users
- Financial services: research-banking-trading separation
- Healthcare: clinical-administrative separation
- Government: agency-of-record separation
Component 7: Sensitivity Labels
Microsoft Purview Integration
- Semantic model sensitivity labels
- Microsoft Power BI Copilot grounding control
- Restricted-tier blocking
- Microsoft Sentinel custom analytics
Industry-Specific Sub-Labels
- Restricted-PHI (healthcare)
- Restricted-MNPI (financial services)
- Restricted-CUI (government)
- Restricted-Clinical (pharma)
Auto-Labeling
- Microsoft Purview AI auto-labeling rules
- 80%+ coverage on regulated semantic models within 90 days
Component 8: Microsoft Power BI Copilot
F64+ Capacity Gate
Microsoft Power BI Copilot requires F64+ Microsoft Fabric capacity.
Microsoft Power BI Copilot Capabilities
- Natural language Q&A on semantic models
- Automatic visualization generation
- Semantic model creation assistance
- DAX measure suggestions
Microsoft Purview AI Hub
- Microsoft Power BI Copilot prompt + response monitoring
- Sensitive data exposure detection
- Risk scoring per user
Microsoft Sentinel Integration
- Custom analytics rules for Microsoft Power BI Copilot risk events
- Microsoft Power BI Copilot grounding on Restricted-tier attempts
- Cross-correlation with Microsoft Purview Insider Risk
Microsoft Fabric Modes
DirectLake Mode (Preferred for Microsoft Fabric)
- Reads OneLake Delta tables directly
- No semantic model refresh required
- Sub-second query response on petabyte-scale
- Microsoft Power BI Copilot foundation
Import Mode (Non-Microsoft Fabric)
- In-memory storage
- Requires refresh
- Fastest mid-scale queries
DirectQuery Mode
- Live source query
- Slowest performance
- Source database load
Industry-Specific Semantic Model Patterns
Healthcare
- Patient, Encounter, ClaimsLine, Provider conformed dimensions
- HEDIS / CMS Star Ratings DAX measure library
- Restricted-PHI sensitivity tier
- HIPAA-aligned audit retention
Financial Services
- Trade, Position, Account, Security conformed dimensions
- Trading P&L DAX measure library
- Restricted-MNPI sensitivity tier
- FINRA Rule 3110 supervisory analytics
Manufacturing
- WorkOrder, Asset, Material, Facility conformed dimensions
- OEE DAX measure library
- Microsoft Defender for IoT integration
- SAP CDC integration
Pharma
- Clinical trial enrollment dimensions
- 21 CFR Part 11 audit trail
- Restricted-Clinical sensitivity tier
- IND/NDA submission tracking
EPC Group Microsoft Power BI Semantic Model Engagement
EPC Group fixed-fee Microsoft Power BI semantic model:
- Single semantic model: $80K-$200K (4-8 weeks)
- Multi-domain semantic models: $200K-$700K (3-6 months)
- Enterprise semantic model architecture: $500K-$2M (6-12 months)
Plus Microsoft Power BI Center of Excellence: $300K-$1M (6 months).
Standard Deliverables
- Semantic model design
- Star-schema implementation
- DirectLake mode configuration (Microsoft Fabric)
- DAX measure library
- Calculation groups
- RLS / OLS implementation
- Microsoft Purview sensitivity label integration
- Microsoft Power BI Copilot enablement
- Documentation + training
Frequently Asked Questions
Semantic model vs dataset?
Microsoft renamed "dataset" to "semantic model" in Microsoft Fabric. Same concept.
How long does enterprise semantic model design take?
Single semantic model: 4-8 weeks. Multi-domain: 3-6 months. Enterprise architecture: 6-12 months.
What about Microsoft Power BI Copilot semantic model creation?
Microsoft Power BI Copilot can suggest semantic model design. Always review by senior data architect before production.
Who delivers EPC Group semantic model engagements?
Errin O'Connor (CEO, 4-time Microsoft Press author including Power BI book, Project Crescent original beta team) leads. Senior data architects with Microsoft Power BI experience since 2010.
Next Steps
Schedule a 30-minute Microsoft Power BI semantic model discovery call at /schedule or call (888) 381-9725. Senior architects (not sales) take discovery calls.
Related reading: Power BI Data Modeling Best Practices Enterprise Guide, Power BI DAX Formulas Enterprise Reference Guide, Microsoft Fabric Consulting Services Enterprise, Microsoft Power BI Copilot Enterprise Guide, and Power BI Center of Excellence Enterprise Playbook.