Verification of SQL Server Licensing on New VM

Games Gremory 0 Reputation points
2026-05-26T08:02:04.6866667+00:00

The previously running live machine was configured with Windows Server 2022 Datacenter Azure Edition and SQL Server 2019.

That machine experienced an issue, so a new VM was provisioned. However, the configuration does not appear to match the original setup, and I would like to confirm the differences.

On the original VM, the [Azure Hybrid Benefit] SQL license was applied. On the newly installed machine, I am unable to locate or verify that this setting is in place.

For the new VM, SQL Server was installed by running the SQL Server ISO file on Windows Server 2022. I need to confirm whether the licensing has been correctly applied and handled in this configuration.

SQL Server on Azure Virtual Machines

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-05-26T08:02:27.83+00:00

    To verify and correctly apply SQL Server licensing (Azure Hybrid Benefit vs PAYG) on the new VM, use these steps and checks.

    1. Confirm how SQL Server was installed
    • Original VM: Likely an Azure Marketplace SQL Server on Azure VM image with Azure Hybrid Benefit (AHB) enabled.
    • New VM: SQL Server was installed manually from ISO on a plain Windows Server 2022 VM. In this case, Azure doesn’t automatically know about the SQL Server license; it must be registered and AHB explicitly enabled.
    1. Register the new VM with the SQL IaaS Agent extension For self-installed SQL Server on an Azure VM, registration with the SQL IaaS Agent extension is required so Azure can manage and bill SQL correctly and allow AHB:
    • Follow: Register with the SQL IaaS Agent Extension for a self-installed SQL Server VM.
    • Once registered, the VM appears as a SQL virtual machines resource in the Azure portal.
    1. Check and set the license model (AHB vs PAYG) After the VM is registered as a SQL VM, verify and configure the license model:

    Via Azure portal

    1. Open the Azure portal and go to the SQL virtual machines resource for the new VM.
    2. Under Settings, select Configure.
    3. Check the License type / Azure Hybrid Benefit setting:
      • If AHB is already enabled, it will show that Azure Hybrid Benefit is selected.
      • If not, select Azure Hybrid Benefit and confirm that there is a qualifying SQL Server license with Software Assurance.
    4. Select Apply.

    Changing this setting:

    • Incurs no downtime.
    • Does not restart the VM or SQL Server service.
    • Takes effect immediately and reduces cost when AHB is activated.

    Via Azure CLI (alternative) If the SQL VM resource exists, the license type can be set with:

    az sql vm update -n <VMName> -g <ResourceGroupName> --license-type AHUB

    Where AHUB = Azure Hybrid Benefit, PAYG = pay-as-you-go, DR = free HA/DR replica.

    Via PowerShell (alternative)

    Update-AzSqlVM -ResourceGroupName <resource_group_name> -Name <VM_name> -LicenseType AHUB
    1. Understand what AHB covers on the new VM With AHB enabled for SQL Server on the VM:
    • Existing SQL Server licenses (with Software Assurance) are applied to the SQL instance.
    • Azure still charges for:
      • Underlying compute (base VM rate),
      • Storage and backups,
      • I/O as applicable.
    1. Confirm that licensing is correctly handled To validate that licensing is correctly applied on the new VM:
    • Ensure the VM is registered as a SQL virtual machine (via SQL IaaS Agent extension).
    • Verify the license model is set to AHUB (or PAYG if using pay-as-you-go) in the SQL VM resource’s Configure blade or via CLI/PowerShell.
    • If the subscription uses centrally managed Azure Hybrid Benefit, license changes at the individual VM level may be blocked and a message like “Your organization manages licenses assigned to Azure at a scope level…” will appear. In that case, the billing admin must manage AHB at the subscription scope under Cost Management + Billing.

    These steps ensure that the manually installed SQL Server on the new Windows Server 2022 VM is correctly registered and that Azure Hybrid Benefit (or PAYG) is explicitly and verifiably applied for billing.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Manoj Kumar Boyini 19,590 Reputation points Microsoft External Staff Moderator
    2026-05-26T13:13:29.9733333+00:00

    Hi @Games Gremory

    Based on your description, the original VM was running Windows Server 2022 Datacenter Azure Edition with SQL Server 2019 Standard and had Azure Hybrid Benefit (AHB) enabled. The new VM appears to have been created as a standard Azure VM, with SQL Server installed manually using ISO media.

    In this scenario, the behavior you’re seeing is expected.

    When SQL Server is installed manually on an Azure VM, Azure does not automatically expose or manage SQL licensing in the same way as Marketplace-deployed SQL Server VMs. To manage SQL licensing and verify Azure Hybrid Benefit status, the VM should be registered with the SQL IaaS Agent extension, which creates the corresponding SQL Virtual Machine resource in Azure.

    Please validate the following:

    • Check whether the VM appears under SQL Virtual Machines in the Azure portal (not just under Virtual Machines).
    • If present, open the SQL Virtual Machine resource and review the License Type.
    • Confirm whether the license type is configured as:
      • Azure Hybrid Benefit (AHB) → using eligible existing SQL licenses
      • Pay-As-You-Go (PAYG) → SQL license cost included in Azure billing
      • If the SQL VM resource is not present, register the VM with the SQL IaaS Agent extension and configure the intended license model.

    Please also confirm licensing eligibility:

    • SQL Server 2019 Standard Edition supports Azure Hybrid Benefit.
    • AHUB requires eligible SQL Server licenses covered by active Software Assurance or qualifying subscription rights.

    Key point:

    The concern here is not the SQL installation itself, but that the VM may not currently be registered for SQL licensing visibility and management in Azure, meaning the intended licensing model (AHUB) may not currently be visible in the portal.

    References:
    https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/sql-server-iaas-agent-extension-automate-management?view=azuresql&tabs=azure-portal
    https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/sql-agent-extension-manually-register-single-vm?view=azuresql&tabs=azure-portal
    https://azure.microsoft.com/en-us/pricing/offers/hybrid-benefit/?

    Please let us know if you have any questions or concerns.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.