Is Hyperscale only worth it for very large databases?

No. Microsoft describes Hyperscale as suitable for all workload types and the recommended default for new OLTP and HTAP workloads, and you pay only for storage actually allocated. Azure Hybrid Benefit can't be applied to newly created Hyperscale databases, though.

Can we stop a client's Managed Instance outside business hours?

Yes, for General Purpose instances. A stopped instance isn't billed for vCores or SQL licensing, only for data and backup storage, and you can set a recurring stop and start schedule. Instances in a failover group, with zone redundancy or in an instance pool can't be stopped.

Does deleting an unused database stop the charges straight away?

Not entirely. Azure keeps a deleted database's backups for its point-in-time retention period and bills that storage until they age out. Long-term retention backups remain even if the logical server is deleted, so review them when offboarding a client.

Coverage

Azure SQL cost optimisation for MSPs

When each client gets its own database, usage is hard to predict, so databases are usually sized for peak demand and overpaid for the rest of the time. Microsoft's own example shows a database sized for a brief spike leaving most of its resources unused.

17

automated finders for Azure SQL

Read-only, across every connected client tenant, tied to real billing data.

Deallocate
Remove unused
Rightsizing
Off-hours schedules

Where Azure SQL spend goes to waste

The main cost levers Microsoft documents for Azure SQL, and the ones an MSP should check across every client.

Serverless auto-pause for intermittent databases

Serverless compute scales vCores with demand, bills compute per second and pauses the database after an idle period, so only storage is charged while it sleeps. It suits single databases with intermittent, unpredictable usage that can tolerate a short warm-up. ^[2]

Pool databases with spiky, low usage

Elastic pools let many databases share a fixed allocation of resources, so you stop sizing every database for its own peak. They work best when average utilisation is low and spikes happen at different times. Keep databases with sustained medium-to-high load out of shared pools. ^[1]

Move from DTU bundles to vCore

Microsoft recommends the vCore model, which lets you choose compute and storage separately and unlocks serverless and Azure Hybrid Benefit. Converting from DTU to vCore is an online operation, so applications stay up. ^[3]

Reserve compute for steady workloads

One- or three-year reservations give a discounted rate on vCore compute, applied automatically to matching databases and managed instances. Size flexibility keeps the discount when you scale within a tier and region. Reservations cover compute only, not storage, and DTU databases cannot be reserved. ^[4]

Bring existing SQL Server licences

Clients with SQL Server licences covered by Software Assurance can apply them through Azure Hybrid Benefit, with no downtime to switch it on. In SQL Database it applies to provisioned vCore compute only, not DTU or serverless. ^[5]

Rightsize backup redundancy and retention

Backups default to geo-redundant storage with seven days of point-in-time restore. Locally redundant storage is the cheapest option and Microsoft suggests it wherever possible, such as dev and test, though it disables geo-restore. Trimming retention to each client's real requirement cuts billable backup storage. ^[6]

How Cerberus Cloud covers Azure SQL

Cerberus Cloud runs 17 automated finders for Azure SQL across every connected client tenant. Each one ties a technical signal to real billing data, so findings arrive with an estimated recoverable value, ranked by impact, effort and risk, with evidence and remediation scripts for your engineers to review.

Access is read-only, so nothing changes in a client environment until your team decides it should. See how it works or the multi-tenant portfolio view.

Deallocate
Remove unused
Rightsizing
Off-hours schedules

Frequently asked questions

Is Hyperscale only worth it for very large databases?: No. Microsoft describes Hyperscale as suitable for all workload types and the recommended default for new OLTP and HTAP workloads, and you pay only for storage actually allocated. Azure Hybrid Benefit can't be applied to newly created Hyperscale databases, though.
Can we stop a client's Managed Instance outside business hours?: Yes, for General Purpose instances. A stopped instance isn't billed for vCores or SQL licensing, only for data and backup storage, and you can set a recurring stop and start schedule. Instances in a failover group, with zone redundancy or in an instance pool can't be stopped.
Does deleting an unused database stop the charges straight away?: Not entirely. Azure keeps a deleted database's backups for its point-in-time retention period and bills that storage until they age out. Long-term retention backups remain even if the logical server is deleted, so review them when offboarding a client.

See Azure SQL findings on a sample portfolio

A 15-minute walkthrough: tenant connection, prioritised findings, remediation scripts and savings history.

Book a Walkthrough All coverage

Sources

Last checked 15 October 2026. Product details change; tell us if something here is out of date.

All 15 coverage families