Tenant isolation
Estimate isolation across shared and dedicated resources
Shared infrastructure can improve utilisation, while dedicated resources can simplify some boundaries. Compare the complete operating model rather than only the database bill.
In this article
Start with the required isolation
Clarify whether tenants need logical data separation, independent recovery, performance isolation or a particular deployment arrangement. These requirements can lead to different resource choices.
A separate database may simplify some backup or access decisions while leaving the application, cache and support tools shared. A shared database can support strong logical controls, but those controls need careful implementation and testing.
Avoid using the word dedicated as a complete security claim. Identify which resources are actually separate and which dependencies remain common.
Model tenant size and variation
Measure typical and peak workload by tenant. A few large tenants can dominate shared capacity, while many small tenants may use dedicated resources inefficiently.
Include noisy-neighbour controls, quotas and scheduling in the shared design. Independent storage does not automatically isolate CPU, network or external API limits if those remain shared.
Use realistic growth scenarios and current service pricing for a financial estimate. Keep assumptions visible instead of presenting one average tenant as representative of the whole customer base.
Count operational differences
Dedicated resources can multiply provisioning, migrations, monitoring and recovery tasks. Automation becomes important as tenant count grows.
Shared resources can make schema changes efficient but complicate tenant-specific restore or movement. Evaluate those operations with actual procedures rather than assuming the platform handles them transparently.
Include support access, key management and data-retention work. The cheapest steady-state storage option may require more engineering effort to meet the intended operating requirements.
Consider a controlled hybrid
Some systems use shared resources for smaller tenants and dedicated resources for those with different needs. That can be practical if routing, deployment and migration remain explicit and well tested.
Avoid maintaining two unrelated application behaviours accidentally. Keep the business contract consistent while the resource placement differs.
Test moving a tenant and recovering one tenant's data under the proposed model. The useful decision balances utilisation, isolation and operating effort for the real workload, with a clear account of what each deployment choice does and does not separate.
Primary sources
Microsoft Learn: multitenant storage approachesOWASP: multitenant securityReferences checked 11 September 2026.