UrbanPulse Data Lab
UrbanPulse · Smart City on Microsoft Fabric
Closing
Wrap-up

Closing

You have built a vertically integrated solution. The diagram below shows what this architecture looks like as a productized SaaS offering deployed across multiple customer tenants, followed by a recap of everything you stood up today.

The Multi-Tenant Pattern, in One Picture

UrbanPulse · SaaS Product Domain-agent catalog · Orchestrator · Customer onboarding tooling · Per-tenant config Tenant A · Hospital Network workspace: tenA-urbanpulse agents enabled: Hospital streams: vitals, movement capacity: F8 dedicated Per-tenant: full data isolation, customer-specific guardrails. "We have HIPAA constraints." Tenant B · Smart City workspace: tenB-urbanpulse agents enabled: BOTH + orchestrator capacity: F32 dedicated Premium tier with cross-domain orchestrator unlocked. "We need the full picture." Tenant C · Transit Authority workspace: tenC-urbanpulse agents enabled: Transit streams: train only capacity: F4 shared pool Single-domain SKU. Shared capacity to keep cost low. "Just transit, please."
Figure C.1 - One UrbanPulse product, three customer SKUs. Same reusable agent & pipeline catalog; per-tenant workspace, capacity, and feature toggles.
💡
The reusability dividend. Onboarding a new tenant does not require new code - only stamping out a new workspace from your template, attaching the customer's data, and toggling the agents that are enabled. The platform is the product.

What You Built Today

LayerYou builtModule
Workspace foundationPre-provisioned workspace bound to a shared Fabric capacity0–1
Warm path · Lakehouse3 ingest patterns, 1 SQL endpoint, 5 tables2
Hot path · Eventhouse3 KQL tables, 3 Eventstreams, all live3
Curate · Silver + GoldNotebook-built Silver Delta table + Gold SQL views4
Real-Time Dashboard5 tiles + 2 parameters + auto-refresh5
Direct Lake + Power BISemantic model + 1-page report6
Semantic layer · Ontology4 entity types + 4 relationships across 2 domains7
AI layer · domain agentHospital Operations Fabric Data Agent8
Optional · multi-agent catalogTransit Operations agent (full two-agent catalog)9
Optional · Foundry orchestratorConnected-agent orchestrator with cross-domain reasoning10
Optional · source controlWorkspace connected to Azure DevOps Git with commit and update11

That covers ten Fabric capability areas - Lakehouse, Mirroring, Shortcuts, Notebooks, Eventhouse, Eventstream, RTI Dashboard, Power BI Direct Lake, Fabric Ontologies, and Data Agents - plus Azure AI Foundry, composed into one product narrative. You now have a complete reference architecture you can take back to your team and adapt for your own SaaS product.

✓
Next steps: Module 0 now includes the canonical setup and environment reference, and the appendices contain Microsoft reference links plus a data setup guide for replicating the lab in your own subscription. Operational documentation for the lab environment also covers the simulator runbook.