Contoso runs workloads in East US and West Europe under a single Microsoft Entra tenant. It has no data residency requirement, and one central operations team monitors everything. Contoso wants the simplest log design, with cross-resource queries that need no extra syntax and the best chance of reaching a commitment tier discount. What should you recommend?
Choose one.
Start a Log Analytics design with a single workspace and add workspaces only when a criterion forces it.
Microsoft's workspace design guidance says to start with one workspace and add more only for specific criteria such as data residency, separate Microsoft Entra tenants, data ownership, split billing or different retention for the same table. None of those applies here. One workspace also pools all ingestion, which is how a commitment tier discount is reached. Per-region, per-subscription and per-application workspaces all add complexity without meeting a stated need.
- List the criteria that force extra workspaces: residency, tenants, ownership, billing, retention.
- Check the stem: one tenant, no residency need, one team.
- With no forcing criterion, keep one workspace so queries and commitment tiers stay simple.
Exam tip: No residency, tenant or ownership split? Recommend one Log Analytics workspace.
AZ-305 Logging and Monitoring Design: Log Analytics Workspaces, Log Routing, Alerts and Azure Monitor — the lesson that teaches this.