BYOL for manually installing SQL Server on Azure VM

Question

Hi,

Anyone idea if I create a azure windows vm, and install sql standard manually and use my own sql standard licence key, is this ok?

The sql licence doesn't include volume licencing or hybrid benefits, its just a sql server licence that we want to make sure we're not going outside of MS licencing by using it on a azure vm, if we install sql ourselves.

Any ideas?

Answer 1

The sql licence doesn't include volume licencing or hybrid benefits, its just a sql server licence

BYOL in Azure requires Software Assurance. So no.

Bringing your own SQL Server license through License Mobility, also referred to as BYOL, means using an existing SQL Server Volume License with Software Assurance in an Azure VM.

https://learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/pricing-guidance#byol

SQL Server licenses can only be applied to a physical server, and licensing individual virtual machines requires applying a number of core licenses to the underlying physical servers equal to the vCores for all SQL VMs, and re-assigning those licenses whenever the virtual machine moves between hosts. In a public cloud environment, you simply have no way to assign the license to a server hosting a SQL Server VM. This is explained in the Licensing Guide. Software Assurance adds unlimited license mobility and Azure Hybrid Use benefits in addition to the rights granted by the SQL Server license itself.

For licenses without Software Assurance acquired before October 1, 2019 you can deploy the licenses for Azure VMs running on an Azure Dedicated Host, per: https://www.microsoft.com/en-us/licensing/news/updated-licensing-rights-for-dedicated-cloud

Also they must inform Microsoft about the BYOL license use, and if you are deploying customer licenses in your Azure tenant, you must have a SPLA agreement with Microsoft.

Deploy with an Authorized Mobility Partner

To take advantage of License Mobility, you can deploy on Microsoft Azure or work with any Authorized Mobility Partner. They need to have a current Microsoft Services Provider License Agreement in place to accept your assigned licenses and deploy them as appropriate to your chosen hosted deployment solution.

https://www.microsoft.com/en-us/licensing/licensing-programs/software-assurance-license-mobility

Answer 2

Hmm. So two very contradictory answers, which doesn't bode well for clarity of the documentation!

I'm also not sure what you mean by 'In a public cloud environment, you simply have no way to assign the license to a server hosting a SQL Server VM.' If the public cloud contains a specific windows os and sql vm, then the licence can be assigned when its created.

From the link, it states "License individual virtual machines (VM), and when licensing per core, buy core licenses only for the virtual cores assigned to the VM." Which contradicts what you've said above, as it can licence vm's, not just physical machines?