Why it matters
If your organization already owns SQL Server licenses with Software Assurance, paying for the license again in Azure is a double cost. The switch is a setting change with no downtime.How nOps finds it
nOps reads the last 7 days of Azure SQL Database billing and looks for SQL license lines on each database. The saving is the license cost from your bill (net of discounts), scaled to a month. A database is left out when its license was not billed in the last 3 days of the window, when the service is mostly paid with credits (90% or more), or when the saving is under $5 a month.Before you start
Enough SQL Server core licenses with active Software Assurance to cover the database’s vCores, and permission to update the database.How to implement
- Confirm with your licensing team that you have eligible SQL Server licenses for the vCores.
- In the Azure portal, open the database, go to Compute + storage, and choose to use Azure Hybrid Benefit (an existing SQL Server license). Save.
- Or use the Azure CLI:
az sql db update --resource-group RESOURCE_GROUP --server SERVER --name DATABASE --license-type BasePrice. For an elastic pool, useaz sql elastic-pool update ... --license-type BasePrice. - Set
license_type = "BasePrice"in Terraform (orlicenseTypein Bicep or ARM templates) so a later deployment does not change it back.
Risks and considerations
- You are responsible for having the licenses. Using Hybrid Benefit without enough eligible licenses is a licensing compliance risk.
- Hybrid Benefit applies to the vCore model only, not to DTU-based or serverless databases.
- To roll back, set the license type back to
LicenseIncluded.
FAQs
Is there downtime?
Is there downtime?
No. It only changes how the database is billed.