# Suboptimal service tier selection in Azure SQL Managed Instance Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-service-tier-selection-in-azure-sql-managed-instance Azure SQL Managed Instances remain on the original General Purpose architecture, or on the separate premium Business Critical tier when they do not... By: Balazs Engedi Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Suboptimal Service Tier Selection in Azure SQL Managed Instance The short version Azure SQL Managed Instances remain on the original General Purpose architecture, or on the separate premium Business Critical tier when they do not need its capabilities (low-latency local SSD storage and a built-in read-only replica), despite the availability of the next-gen General Purpose tier. [Balazs Engedi](https://www.linkedin.com/in/engedib/) FinOps Specialist @ KPN Azure service [Azure SQL Managed Instance](https://www.pointfive.co/efficiency-hub/cloud-services/azure-sql-managed-instance) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0288 Type Suboptimal Tier or SKU ## Explanation Why the waste happens and who it affects. Next-gen General Purpose is an upgrade of the General Purpose tier, while moving from Business Critical to it is a tier downgrade with latency and read-scale trade-offs; zone redundancy for Next-gen General Purpose is currently in preview. The newer tier enables more granular scaling of vCPU, memory, and storage, allowing workloads to better match actual resource needs. In many cases, workloads running on Business Critical - or overprovisioned legacy General Purpose-do not require the premium performance or architecture of those tiers and could achieve equivalent outcomes at lower cost by moving to next-gen General Purpose. ## Billing model The pricing dimensions that drive this cost. Azure SQL Managed Instance is billed based on service tier, vCPU, memory, and storage configuration. The next-gen General Purpose tier offers improved performance characteristics and independent scaling of compute and storage at the same baseline cost as General Purpose (including 3 free IOPS per GB of reserved storage), though IOPS above that and memory above the default memory-to-vCore ratio are billed separately, while Business Critical incurs higher infrastructure and licensing costs. ## How to detect 4 checks to find it in your estate. - Review which SQL Managed Instances are running on the original General Purpose architecture or on Business Critical - Assess whether workloads truly require Business Critical capabilities (e.g., low-latency IO, high concurrency) - Identify instances where compute, memory, or storage appear overprovisioned relative to workload needs - Evaluate whether current tier selection reflects historical constraints rather than current platform options ## How to fix 3 ways to remove the waste. - Migrate eligible SQL Managed Instances to the next-gen General Purpose tier - Rebalance vCPU, memory, and storage independently to align with actual workload requirements - Periodically reassess tier selection as platform capabilities and pricing evolve ## Documentation Vendor references for pricing and configuration. [https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/service-tiers-next-gen-general-purpose-use](https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/service-tiers-next-gen-general-purpose-use) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure SQL Managed Instance CER-0435 ### [Non-Production SQL Managed Instances Running Without a Stop/Start Schedule](https://www.pointfive.co/efficiency-hub/inefficiencies/non-production-sql-managed-instances-running-without-a-stop-start-schedule) Azure SQL Managed Instance bills vCores and the SQL Server license every hour the instance is running, whether or not anyone is connected. Development, test, QA and training instances are usually needed only during working hours, yet they... Databases - Azure SQL CER-0264 ### [Suboptimal Use of Serverless Compute for Azure SQL Database](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-use-of-serverless-compute-for-azure-sql-database-4fe48) Serverless is attractive for variable or idle workloads, but it can become more expensive than Provisioned compute when database activity is high for long portions of the day. As active time increases, per-second compute accumulation... Databases - Azure SQL CER-0263 ### [Suboptimal Use of Provisioned Compute for Azure SQL Database](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-use-of-provisioned-compute-for-azure-sql-database-9bb83) Databases deployed on Provisioned compute incur continuous hourly charges even when workload demand is low. For databases that are active only briefly within an hour, or for limited hours per month, Serverless can provide significantly... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.