What is the minimum cost of an Azure SQL Managed Instance?

About $1,460/month. Managed Instance has a 4-vCore minimum, and General Purpose Gen5 runs roughly $0.50/vCore-hour, so 4 vCores x 730 hours is around $1,460 before storage. There is no scale-to-zero, so this is a continuous floor.

Why is Managed Instance so much more expensive than Azure SQL Database?

Managed Instance runs a full SQL Server engine inside your VNet with instance-scoped features (SQL Agent, cross-database queries, CLR, Service Broker) and enforces a 4-vCore minimum. A single Azure SQL Database can run on a far smaller vCore or DTU allocation, so it starts at a fraction of the price for workloads that don't need instance-level features.

How much does Business Critical cost vs General Purpose?

Business Critical runs roughly 2.7x General Purpose per vCore. It adds local SSD storage and a built-in readable replica. A 4-vCore Business Critical instance is around $3,900/month vs $1,460 for General Purpose, so only choose it when you need the latency or the included read replica.

Does Azure Hybrid Benefit reduce Managed Instance cost?

Yes, significantly. Setting license_type to AHUB removes the SQL Server license component from the vCore rate, typically a 30-40% reduction, if you own SQL Server licenses with active Software Assurance. It is the single biggest lever for organizations that qualify.

How does C3X estimate Managed Instance cost from Terraform?

C3X reads sku_name (tier and hardware generation), vcores, and storage_size_in_gb from your azurerm_mssql_managed_instance resource, prices the compute per vCore-hour at 730 hours/month, and adds storage beyond the 32 GB included with General Purpose. You see the number before you apply.

Azure SQL Managed Instance cost: the $1,460/month floor and how to lower it

Quick answer

Azure SQL Managed Instance has a 4-vCore minimum, so even an idle instance starts around $1,460/month on General Purpose Gen5. Business Critical is ~2.7x that. The four levers that move the bill: Azure Hybrid Benefit (30-40% off if you own licenses), staying on General Purpose unless you need BC features, reserved capacity (~30% off), and right-sizing vCores. Storage beyond the included 32 GB is a minor add-on.

Azure SQL Managed Instance (SQL MI) is the "lift and shift SQL Server without managing a VM" option. You get near-full engine compatibility, deployed into your own VNet, as a managed service. The catch shows up on the first invoice: the minimum viable instance costs more than most teams expect, because of a vCore floor and a continuous billing model with no scale-to-zero.

This post breaks down exactly what drives the cost, what the realistic minimum is, and the four changes that actually lower it.

The three cost components

SQL MI bills on compute, storage, and backup. Compute dominates.

1. Compute (vCores)

Billed per vCore-hour by service tier and hardware generation
General Purpose Gen5: ~$0.50/vCore-hour (includes the SQL license)
Business Critical Gen5: ~$1.35/vCore-hour (~2.7x)
4-vCore minimum — you cannot provision fewer

At the 4-vCore floor, General Purpose is roughly 4 x $0.50 x 730 hours = $1,460/month. There is no pause or scale-to-zero for a Managed Instance, so that figure runs continuously whether or not queries are hitting it.

2. Storage

General Purpose includes 32 GB; above that, ~$0.115/GB-month
Business Critical bundles storage into the compute price
A 256 GB General Purpose instance adds ~$25.76/month (224 billable GB)

3. Backup storage

Point-in-time restore and long-term retention backups bill per GB-month beyond the included allowance. For most instances this is a small, usage-driven line; it only matters with long retention windows on large databases.

What a realistic instance actually costs

Configuration	Compute	Storage	Monthly
GP, 4 vCore, 32 GB (the floor)	$1,460	$0	~$1,460
GP, 8 vCore, 256 GB	$2,920	$26	~$2,946
BC, 8 vCore, 512 GB	$7,884	included	~$7,884

The jump from General Purpose to Business Critical is the single biggest swing. Confirm you actually need the local-SSD latency or the built-in readable secondary before paying ~2.7x.

The four levers that lower the bill

1. Azure Hybrid Benefit (biggest single lever)

If your organization owns SQL Server licenses with Software Assurance, set license_type = "AHUB". This strips the SQL license out of the vCore rate, typically a 30-40% reduction. For a steady 8-vCore instance that is roughly $1,000/month back.

2. Stay on General Purpose

Business Critical is worth ~2.7x only for latency-sensitive OLTP or when you need the included read replica. Many workloads run fine on General Purpose with zone redundancy enabled, at a fraction of the cost.

3. Reserved capacity

A 1-year reserved capacity commitment on the vCores saves ~30% over pay-as-you-go; 3-year more. Managed Instances are almost always steady-state, which makes them ideal reservation candidates. Reserved capacity stacks with Azure Hybrid Benefit.

4. Right-size vCores

Cost is linear in vCores. An instance provisioned at 16 vCores that averages 20% CPU is paying for headroom it never uses. Pull the actual CPU and memory metrics and drop to the smallest tier that holds your peak, respecting the 4-vCore minimum.

Catch it before you apply

The reason SQL MI surprises teams is that the floor is invisible in the Terraform: vcores = 4 looks cheap until you multiply it out. C3X prices an azurerm_mssql_managed_instance directly from the resource block, so the ~$1,460 floor shows up in the cost breakdown in your pull request, not on next month's invoice.

# Fail CI if the database tier pushes the estimate over budget
c3x estimate --path . --budget 2000

If a teammate bumps the instance to Business Critical or doubles the vCores, the diff is right there in the PR. For the broader pattern, see budget guardrails that block PRs and how to estimate Azure costs from Terraform.

When SQL MI is the wrong tool

If you don't need instance-scoped SQL Server features, a single azurerm_mssql_database starts far cheaper because it has no 4-vCore floor. And if you can move off SQL Server entirely, PostgreSQL Flexible Server is usually the lowest-cost managed relational option on Azure. Estimate all three before committing.