Blog Post

Azure SQL Blog
3 MIN READ

Introducing Simplified Regional Limits for Azure SQL Managed Instance

DjordjeJeremic's avatar
Aug 24, 2026

We are pleased to announce improvements to regional subscription limits for Azure SQL Managed Instance. These changes simplify subnet management and provide more granular control over vCore capacity across hardware generations.

What’s changing?

Two changes are now generally available:

Regional subnet limits are removed

Azure SQL Managed Instance no longer applies service-specific regional subnet limits. Instead, deployments are governed by the applicable Azure Resource Manager virtual networking limits.

This simplifies resource planning and removes the need to monitor or request increases for Azure SQL Managed Instance regional subnet limits.

Regional vCore limits are now hardware-generation specific

Regional vCore limits are now managed separately for each supported hardware generation:

• Standard Series

• Premium Series

• Premium Series Memory Optimized

 

Previously, a single regional vCore limit applied across hardware generations. With hardware-generation-specific limits, customers can request additional capacity only for the hardware generation required by their workloads.

For example, if you need additional Premium Series capacity in a region, you can request an increase for Premium Series without changing the limits for Standard Series or Premium Series Memory Optimized.

Check vCore quota limit and usage with PowerShell

Use the Subscription Usages - Get REST API to retrieve the current vCore quota limit and consumption for Azure SQL Managed Instance in a subscription and region. Query each hardware generation separately by specifying its usage name:

Hardware generationUsage name
Standard-series (Gen5)SubscriptionSQLManagedInstanceStandardSeriesVCoreQuota
Premium-seriesSubscriptionSQLManagedInstancePremiumSeriesVCoreQuota
Memory optimized premium-seriesSubscriptionSQLManagedInstancePremiumSeriesMemoryOptimizedVCoreQuota

 

Run the following script in a PowerShell session with the Az module installed, or in Azure Cloud Shell using PowerShell. Your account needs permission to read subscription usage, such as the Reader role assigned at subscription scope.

Replace <subscription-id> with your subscription ID, set $location to the Azure region name (for example, eastus), and set $usageName to one of the values in the table. If you're already signed in through Cloud Shell, omit Connect-AzAccount.

$subscriptionId = "<subscription-id>"
$location = "eastus"
$usageName = "SubscriptionSQLManagedInstanceStandardSeriesVCoreQuota"

Connect-AzAccount -ErrorAction Stop | Out-Null
Set-AzContext -SubscriptionId $subscriptionId -ErrorAction Stop | Out-Null

$path = "/subscriptions/$subscriptionId/providers/Microsoft.Sql/locations/$location/usages/${usageName}?api-version=2025-01-01"
$response = Invoke-AzRestMethod -Method GET -Path $path -ErrorAction Stop

if ($response.StatusCode -ne 200) {
    throw "Unable to retrieve quota usage. HTTP $($response.StatusCode): $($response.Content)"
}

$response.Content | ConvertFrom-Json -ErrorAction Stop | ConvertTo-Json -Depth 10

 

Example output (excerpt; values are illustrative):

{
  "name": "SubscriptionSQLManagedInstanceStandardSeriesVCoreQuota",
  "properties": {
    "currentValue": 80,
    "limit": 320,
    "unit": "SubscriptionSQLManagedInstanceStandardSeriesVCoreQuota"
  }
}

In this example, `properties.currentValue` is the current quota consumption: 80 vCore units. `properties.limit` is the current quota limit: 320 vCore units. The remaining quota is `limit - currentValue`, or 240 vCore units, for standard-series hardware in the specified subscription and region.

 

The previously used VCoreQuota usage name, which represented a single regional quota shared across all hardware generations, is being deprecated in favor of hardware-generation-specific quotas. Use the usage names listed in the table above to retrieve the quota limit and consumption for each hardware generation.

What does this mean for existing customers?

Existing regional vCore limits will be automatically converted to hardware-generation-specific limits. No customer action is required.

Your new limits can be viewed and managed through the Azure portal. If the default limit for a hardware generation is insufficient for a planned deployment, you can request an increase for that specific hardware generation.

 

New hardware generation specific vCore limits apply to both single-zone and multi-zone (Zone Redundant) Managed Instance deployments. 

Benefits

These improvements provide:

• Simpler quota management through the removal of service-specific regional subnet limits.

• Better granularity with separate vCore limits for each hardware generation.

• Greater flexibility to request capacity only where it is needed.

• A seamless transition with automatic conversion of existing limits.

 

To learn more about Azure SQL Managed Instance resource limits and how to request an increase, see Request quota increases for Azure SQL Database and SQL Managed Instance.

We hope these changes make planning and scaling your Azure SQL Managed Instance deployments simpler and more flexible.

 

Updated Oct 12, 2026
Version 2.0
No CommentsBe the first to comment