Where should domain boundaries, environments, and ownership live?
Define workspace taxonomy, naming, dev/test/prod patterns, capacity boundaries, and access groups before usage scales.
Advisory Playbook 02 | Microsoft Fabric Analytics
Scale Fabric analytics without creating reporting sprawl.
A working advisory method for assessing a Fabric estate, clarifying ownership and lifecycle choices, and producing a governed scaling roadmap.
Client Decision
The Fabric question is not only "which workspace should we create?"
The real decision is how to balance domain autonomy, governed semantic models, lifecycle discipline, and adoption signals before Fabric becomes another reporting estate to clean up.
Which metrics should become shared, certified models?
Clarify who owns measures, model quality, RLS, documentation, certification, and reuse across reports.
How will teams know what is trusted, used, retired, or broken?
Track usage, refresh health, support demand, certified-model reuse, report retirement, and quality indicators.
What I Would Assess
Evidence needed before recommending a Fabric operating model.
The assessment connects the reporting estate, ownership gaps, delivery lifecycle, capacity constraints, and support demand to the choices leaders need to make.
Workspaces, models, reports, and capacities
Inventory what exists, who uses it, where duplication appears, and which dependencies or failures carry business risk.
Decision rights and support responsibilities
Map who owns domains, workspaces, measures, access, releases, quality, incidents, and retirement decisions.
How demand becomes trusted production content
Review intake, development, testing, certification, deployment, monitoring, support, adoption, and retirement.
Example Client Deliverables
Fabric operating-model canvas.
Domains
FinanceCertified metrics and reporting packs
OperationsOperational dashboards and data products
SalesPipeline, customer, and performance reporting
Workspaces
DevelopmentBuild and test data products
TestValidation, user review, deployment checks
ProductionCertified reports and governed access
Fabric
OneLakeShared storage and shortcuts
EngineeringDataflows, notebooks, warehouses
SemanticReusable models and measures
Controls
SecurityAccess groups, RLS, sensitivity labels
LifecycleDeployment pipelines, approvals
AdoptionUsage, quality, support model
Recommendation Method
Turn assessment evidence into operating-model choices.
| Control Area | Architecture Decision | Evidence Produced |
|---|---|---|
| Workspace governance | Separate development, test, and production workspaces by domain. | Workspace taxonomy, ownership matrix, access model. |
| Semantic consistency | Use certified semantic models for shared enterprise metrics. | Metric catalog, model standard, certification checklist. |
| Lifecycle | Use controlled deployment pipelines and report retirement process. | Release flow, review checklist, adoption dashboard. |
Rollout Sequence
Move from reporting demand to governed adoption.
Step 01
Organize
Define workspace taxonomy, domain ownership, and naming standards.
Step 02
Standardize
Create semantic model, report, and deployment standards.
Step 03
Migrate
Move priority reports and models into governed Fabric patterns.
Step 04
Adopt
Track usage, quality, support, and certified model reuse.
Apply this playbook to a real Fabric operating-model decision.
Start with the current reporting estate, workspace sprawl, semantic ownership issues, and where business teams need speed without losing trust.