azurerm_mssql_managed_instance - increase storage_size_in_gb maximum to 32768#31387
Merged
mbfrahry merged 2 commits intohashicorp:mainfrom Jan 1, 2026
Merged
Conversation
…from 16384 to 32768 GB
oyiz-michael
requested review from
a team,
WodansSon and
magodo
as code owners
sreallymatt
previously requested changes
Dec 19, 2025
Collaborator
sreallymatt
left a comment
sreallymatt
left a comment
There was a problem hiding this comment.
Thanks @oyiz-michael, just one minor comment regarding the docs
mbfrahry
changed the title
azurerm_mssql_managed_instance - increase storage_size_in_gb maximum to 32768
Contributor
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fixes #31390
When building a SQL Managed Instance with anything higher than 16384 GB of storage, you get an error:
Error: expected storage_size_in_gb to be in the range (32 - 16384), got 20480
with module.sql_managed_instance.azurerm_mssql_managed_instance.sqlmi,
on ......\Modules\sql-managed-instance\v1.0\main.tf line 8, in resource "azurerm_mssql_managed_instance" "sqlmi":
8: storage_size_in_gb = var.storage_size_in_gb
resource "azurerm_mssql_managed_instance" "sqlmi" {
name = ""
resource_group_name = ""
location = "westus"
license_type = "BasePrice"
sku_name = "GP_Gen5"
storage_size_in_gb = 20480
vcores = 32
}
│ Error: expected storage_size_in_gb to be in the range (32 - 16384), got 20480
│
│ with module.sql_managed_instance.azurerm_mssql_managed_instance.sqlmi,
│ on ......\Modules\sql-managed-instance\v1.0\main.tf line 8, in resource "azurerm_mssql_managed_instance" "sqlmi":
│ 8: storage_size_in_gb = var.storage_size_in_gb
Expected Behaviour:
It should scale storage to 32768
Actual Behaviour:
Error: expected storage_size_in_gb to be in the range (32 - 16384), got 20480
Steps to Reproduce:
Build a SQL managed instance with 20480 GB of storage and it will fail.
I can see in the Azure Portal GUI, the slider goes up to 32768 GB (32 TB) for General Purpose Next-gen instances.
This PR increases the maximum value for
storage_size_in_gbinazurerm_mssql_managed_instancefrom 16,384 GB to 32,768 GB (32 TB) to align with Azure's current maximum limits.According to Azure SQL Managed Instance resource limits, General Purpose Next-gen instances now support up to 32 TB of storage. The previous validation limit of 16,384 GB was preventing users from provisioning instances with storage requirements between 16 TB and 32 TB.
This follows the same pattern as #17710 / #17711 from 2022, where the limit was increased from 8,192 GB to 16,384 GB.
Fixes #31390
This is a (please select all that apply):