Pricing for Azure SQL Managed Instance Pool

Hello Riaz

Compute charges apply as soon as an Azure SQL Managed Instance pool is created, even if no managed instances are deployed into the pool.

• An instance pool reserves compute capacity (vCores) at the pool level.
• Billing is based on the vCores allocated to the pool, not on the number of managed instances inside it.
• Because the compute capacity is pre‑allocated for the pool, charges start immediately after the pool is created.

This is also why:

• Managed instances created inside a pool show zero compute cost — compute is already billed at the pool level.
• The Azure portal cost estimation showing “0” during pool creation is misleading and does not reflect actual billing after deployment.

Storage billing clarification:

• Storage is billed only when a managed instance is created.
• The first 32 GB of storage per instance is included at no additional cost.

Reference:

https://learn.microsoft.com/azure/azure-sql/managed-instance/instance-pools-overview

Create and manage an instance pool : https://learn.microsoft.com/azure/azure-sql/managed-instance/instance-pools-configure

Azure SQL Managed Instance Pool pricing Official pricing page showing that vCore pricing applies to the pool itself: https://azure.microsoft.com/pricing/details/azure-sql-managed-instance/pools/

So, Creating an Azure SQL Managed Instance pool immediately incurs compute charges based on the pool’s allocated vCores, even if no managed instances are created. The zero cost shown during portal creation is only an estimation artifact and does not reflect actual billing behavior.

Thanks,
Suchitra.

Hi,

As soon as you create Azure SQL Managed Instance pool, compute charges start accruing. You pay for the vCores regardless of how many instances you deploy to the pool. Please see excerpt from documentation below:

Instance pool billing

Instance pools help you scale compute and storage independently. You pay for:

• Compute allocated to the pool, measured in vCores.
• Storage associated with every instance, measured in gigabytes (the first 32 GB are free for each instance).

You pay the vCore price for a pool no matter how many instances you deploy to that pool. You can't set different pricing options for individual instances in a pool. All instances in the pool must use the same licensing model. You can change the license model for the pool after you create the pool.

The compute price (measured in vCores) depends on whether you're paying the full SQL Server license price. Two price options are available:

• License included: The price of the SQL Server licenses is included.
• Azure Hybrid Benefit: A reduced price that includes the Azure Hybrid Benefit for SQL Server. To use this price, you must have existing SQL Server licenses with Software Assurance.

For full instance pool pricing details, see the instance pools section on the SQL Managed Instance pricing page.

Unsure why you aren't seeing estimate when you create instance via portal. Please see screenshot below:

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Compute for an Azure SQL Managed Instance pool is billed as soon as the pool is created, regardless of whether any managed instances are deployed into that pool.

Billing is based on the vCores allocated to the pool itself, not on the number of instances inside it. The documentation states:

• "You pay the vCore price for a pool no matter how many instances you deploy to that pool."
• "You can't set different pricing options for individual instances in a pool. All instances in the pool must use the same licensing model."

When a managed instance is created inside the pool, its compute cost shows as 0 because compute is already being charged at the pool level. The portal cost estimation showing zero during pool creation is not reflected in the billing model described in the documentation; charges apply for the pool’s allocated vCores once the pool exists.

Storage is billed per managed instance (with the first 32 GB free per instance) when instances are created.

References:

• What is an instance pool? - Azure SQL Managed Instance
• Create an instance pool - Azure SQL Managed Instance
• What is Azure SQL Managed Instance?