You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It only accepts:
vcores - (Required) Number of cores that should be assigned to the SQL Managed Instance. Values can be 8, 16, or 24 for Gen4 SKUs, or 4, 8, 16, 24, 32, 40, 64, or 80 for Gen5 SKUs.
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Is there an existing issue for this?
Community Note
Terraform Version
latest
AzureRM Provider Version
latest
Affected Resource(s)/Data Source(s)
azurerm_mssql_managed_instance
Terraform Configuration Files
N/A
Debug Output/Panic Output
Expected Behaviour
Accept the new configuration announced here: https://techcommunity.microsoft.com/t5/azure-sql-blog/improved-price-performance-amp-flexibility-in-the-business/ba-p/3983617
vcores options: 4,6,8,10,12,16,20,24,32,40,48,56,64,80,96 & 128 CPU vCores
Actual Behaviour
It only accepts:
vcores - (Required) Number of cores that should be assigned to the SQL Managed Instance. Values can be 8, 16, or 24 for Gen4 SKUs, or 4, 8, 16, 24, 32, 40, 64, or 80 for Gen5 SKUs.
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: