Solutions Engineer Data Architect IT Admin — Use these industry templates as starting points for Fabric architecture design. Each scenario includes recommended components, data flow, governance model, and SKU sizing.
Customer Scenario Templates
Pre-built architecture blueprints for common industry use cases. Click any scenario to expand the full blueprint.
These scenario templates are illustrative blueprints. Specific SKU sizing, component selection, and architecture patterns should be validated against your organization's requirements and current Fabric capacity guidance.
Retail Analytics Platform
Unified analytics platform for multi-channel retail operations — combining POS transactions, e-commerce data, inventory, and customer behavior into a single Fabric lakehouse for real-time and historical insights.
🏗️ Architecture Components
🔄 Data Flow
📐 Recommended Sizing
🔒 Governance Model
- RLS per region/store: Store managers see only their location's data
- Sensitivity labels: Customer PII (loyalty data) classified as Confidential
- Workspaces: [Retail]-[Analytics]-[Dev/Test/Prod] naming convention
- Domain: "Retail Operations" with merchandising and supply chain sub-domains
Healthcare Data Platform
HIPAA-compliant data mesh architecture for healthcare organizations — separate domains for patient data, clinical operations, and financial analytics with strict access controls and audit trails.
🏗️ Architecture Components
🔄 Data Flow
📐 Recommended Sizing
🔒 Governance Model
- HIPAA compliance: Managed private endpoints, no public internet access to data
- PHI protection: Sensitivity labels auto-applied, CLS on SSN/MRN, dynamic masking
- Audit trail: Purview lineage from source EHR to report, full access logs
- Domain isolation: Patient, Clinical, Financial domains with separate security groups
Financial Services Reporting
Enterprise reporting platform for banks and financial institutions — regulatory compliance reports, risk analytics, and real-time trading dashboards with strong audit controls and SOX compliance.
🏗️ Architecture Components
🔄 Data Flow
📐 Recommended Sizing
🔒 Governance Model
- SOX compliance: Full deployment pipelines (Dev→Test→Prod) with approval gates
- CLS on sensitive fields: Account numbers and transaction amounts masked for non-privileged users
- Private endpoints: No public access, VNet-integrated for regulatory requirements
- Immutable audit: Purview lineage + activity logs retained per regulatory timelines
IoT & Manufacturing Analytics
Real-time operational intelligence for manufacturing and IoT — streaming sensor data into Eventhouse for live monitoring, anomaly detection, and predictive maintenance, with historical analysis in Lakehouse.
🏗️ Architecture Components
🔄 Data Flow
📐 Recommended Sizing
🔒 Governance Model
- Device-level access: Separate workspaces per plant/facility with dedicated security groups
- Retention policies: Raw sensor data 90 days in Eventhouse, summarized in Lakehouse long-term
- OT/IT separation: Network isolation between OT sensor networks and Fabric analytics
- Alert governance: Activator rules reviewed quarterly, escalation paths documented
📚 Related Sections
Real-Time Intelligence → Real-Time Intelligence Architecture → Capacity Management →Marketing Analytics — Customer 360
Unified customer view combining CRM, web analytics, social media, and campaign data — enabling identity resolution, attribution modeling, and personalized marketing with GDPR-compliant data handling.
🏗️ Architecture Components
🔄 Data Flow
📐 Recommended Sizing
🔒 Governance Model
- GDPR compliance: Consent-based processing, right-to-deletion via Spark notebooks
- PII masking: CLS hides email/phone from analysts, only aggregated segments visible
- Data retention: Raw web events deleted after 13 months per GDPR, aggregates retained longer
- Cross-team sharing: Marketing Gold layer shared via shortcuts with Sales domain (read-only)
Enterprise Data Platform
Full-scale enterprise data platform using data mesh principles — multiple business domains (Finance, HR, Operations, Sales) each owning their data products, with centralized governance and shared Fabric capacity.
🏗️ Architecture Components
🔄 Data Flow
📐 Recommended Sizing
🔒 Governance Model
- Federated governance: Central CoE defines standards; domain teams implement within guardrails
- Deployment pipelines: All domains use Dev→Test→Prod with branch policies and PR reviews
- Purview integration: Automated cataloging, lineage, sensitivity labels across all domains
- Capacity management: Separate capacities for Prod vs Dev; Metrics app monitored by CoE
- Workspace naming: [Domain]-[Product]-[Env] enforced by policy (e.g., Finance-AR-Prod)
Chargeback & Cost Attribution
Implement a chargeback model to attribute Fabric capacity costs back to business units, teams, or users. Combines the Fabric Chargeback App with Azure Cost Management for transparent, fair cost allocation.
🏗️ Architecture Components
🔄 Chargeback Flow
🔒 Governance Model
- Domain enforcement: Every workspace must be assigned to a Fabric domain for accurate attribution
- Workspace naming: [BU]-[Project]-[Env] convention for easy mapping
- Monthly review: Chargeback admin validates domain/workspace assignments before bills go out
- Dispute resolution: Clear escalation path for contested charges
These scenarios are starting points, not rigid blueprints. Every customer's needs are unique. Use these as conversation starters:
- 1. Identify which scenario is closest to your customer's situation
- 2. Walk through the architecture components and data flow together
- 3. Adjust the governance model based on their compliance requirements
- 4. Use the TCO Calculator to estimate costs
- 5. Start with a pilot using the recommended SKU, then iterate