Those of you with multiple data domains in Fabric — one big semantic model or split by domain? How are you handling the trade-offs?

Summary

Semantic model strategy in Microsoft Fabric: one large model or split by domain

In Microsoft Fabric implementations with multiple data domains, choosing between a single semantic model or split models per domain is a critical architecture decision.

The question

Organizations using Direct Lake with a single gold lakehouse and Power BI reports across multiple domains - Sales, Finance, Operations - face a choice. One large model enables cross-domain analysis but becomes complex. Split models are more manageable but limit cross-domain reporting.

Why this matters

Model architecture determines performance, maintainability, and user experience. A wrong choice leads to slow reports, duplicated logic, and end-user frustration. In Fabric, this decision is especially relevant due to Direct Lake constraints.

Action: choose deliberately and document

Analyze your cross-domain reporting needs before deciding. Consider a hybrid approach with domain models and a limited cross-domain model for executive reporting.