Alliela Logo
Microsoft Fabric - Center of Excellence

Fabric Blueprint: Implementation Framework

Environment Structure

Workspace Strategy Overview: Organize your Microsoft Fabric environment using a clear, prefix-based workspace strategy. This approach improves manageability, security, and reusability across your data platform.

Admin Workspaces

admin_ prefix

Used for Fabric management, housekeeping automations, and monitoring. Centralizes platform administration and operational tasks.

Source Workspaces

src_ prefix

Dedicated to specific data sources. Subdivided into:

  • src_str_: Storage (lakehouses, warehouses, databases)
  • src_etl_: ETL (notebooks, dataflows, pipelines)

Isolating sources makes them project-agnostic and reusable. A single source workspace can connect to multiple project workspaces.

Project Workspaces

prj_ prefix

Contain business logic and project-specific implementations. Subdivided into:

  • prj_str_: Storage (lakehouses, warehouses, databases)
  • prj_etl_: ETL (notebooks, dataflows, pipelines)

These workspaces are where data is transformed and business rules are applied for a particular initiative.

BI Workspaces

bi_ prefix

Dedicated to reports, apps, and dashboards. Keeps analytics and presentation layers separate from data processing and logic.

admin_housekeeping
admin_monitoring
Admin
src_str_salesforce
src_etl_salesforce
src_str_sqlserver
src_etl_sqlserver
Source
prj_str_customer360
prj_etl_customer360
prj_str_marketing
prj_etl_marketing
Project
bi_sales
bi_marketing
BI
Benefits: Isolating storage and ETL (str/etl) in both source and project workspaces allows for clear separation of lakehouses/warehouses/databases from notebooks and ETL tools. This is crucial for CI/CD and development strategies, enabling independent deployment, testing, and scaling of storage and transformation components.
Note: These separations are also essential for pipeline orchestration and dependency management. Isolation makes it easier to set dependencies when one source is connected to multiple projects (or vice versa), and helps avoid duplicating data and compute for data collection and transformation.

This is a living document. As your team and Fabric environment evolve, revisit and refine your blueprint to ensure ongoing success.