what is the procedure for bring our own SQL server licence to azure VM

%3CLINGO-SUB%20id%3D%22lingo-sub-168192%22%20slang%3D%22en-US%22%3Ewhat%20is%20the%20procedure%20for%20bring%20our%20own%20SQL%20server%20licence%20to%20azure%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168192%22%20slang%3D%22en-US%22%3E%3CP%3Ewhat%20is%20the%20procedure%20for%20bring%20our%20own%20SQL%20server%20licence%20to%20azure%20VM%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-168192%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168635%22%20slang%3D%22en-US%22%3ERe%3A%20what%20is%20the%20procedure%20for%20bring%20our%20own%20SQL%20server%20licence%20to%20azure%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168635%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20reply..%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlso%2C%20Is%20it%20possible%20to%20install%26nbsp%3BTFS%20server%20inside%20azure%20vm(purchased%20only%20VM)%20and%20use%20my%20own%20license%20key%20to%20activate%20it...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168608%22%20slang%3D%22en-US%22%3ERe%3A%20what%20is%20the%20procedure%20for%20bring%20our%20own%20SQL%20server%20licence%20to%20azure%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168608%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20You!%20I%20was%20not%20aware%20of%20it%20as%20I%20never%20done%20it%20before.%3CBR%20%2F%3EIn%20my%20case%2C%20I%20create%20vanilla%20image%20and%20then%20do%20sql%20installation%20n%20configuration.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168594%22%20slang%3D%22en-US%22%3ERe%3A%20what%20is%20the%20procedure%20for%20bring%20our%20own%20SQL%20server%20licence%20to%20azure%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168594%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20can't.%20Even%20if%20you%20manage%20to%20change%20the%20license%20of%20the%20SQL%20Server%2C%20you're%20going%20to%20pay%20full%20price%20for%20it%20because%20the%20license%20is%20tied%20to%20the%20VM%20level%2C%20not%20OS.%20What%20you%20have%20to%20do%20is%20to%20create%20a%20new%20VM%2C%20install%20SQL%20Server%20(or%20use%20one%20of%20the%20BYOL%20Images%20from%20the%20gallery)%20with%20your%20license%20and%20then%20move%20the%20databases.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168571%22%20slang%3D%22en-US%22%3ERe%3A%20what%20is%20the%20procedure%20for%20bring%20our%20own%20SQL%20server%20licence%20to%20azure%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168571%22%20slang%3D%22en-US%22%3E%3CP%3EI%20never%20tried%20but%20have%20a%20look%20on%26nbsp%3B%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Fblog.sqlauthority.com%2F2015%2F11%2F06%2Fsql-server-how-to-change-sql-server-product-key-or-license-key%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblog.sqlauthority.com%2F2015%2F11%2F06%2Fsql-server-how-to-change-sql-server-product-key-or-license-key%2F%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20my%20case%2C%20I%20need%20more%20customization%20in%20SQL%20instance.%20So%20I%20have%20created%20SQL%20Image%20bakery%2C%20Where%20I%20setup%20custom%20SQL%20image%20with%20my%20own%20SQL%20version%20with%20right%20product%20key%20and%20all%20other%20customization%20using%20powershell%20dsc.%20This%20way%20I%20setup%20my%20SQL%20in%20less%20than%2020%20min%20and%20on%20top%20of%20it%2C%20need%20to%20run%20couple%20of%20dsc%20code%20(takes%203-4%20min)%20while%20creating%20SQL%20workload%20from%20my%20own%20custom%20image.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168229%22%20slang%3D%22en-US%22%3ERe%3A%20what%20is%20the%20procedure%20for%20bring%20our%20own%20SQL%20server%20licence%20to%20azure%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168229%22%20slang%3D%22en-US%22%3E%3CP%3EActually%20I%20have%20already%20purchased%20an%20azure%20VM%20with%20sql%20server%20pre%20installed.%20So%20if%20there%20is%20any%20way%20to%20add%20my%20license%20to%20that%20preinstalled%20sql%20server%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-168215%22%20slang%3D%22en-US%22%3ERe%3A%20what%20is%20the%20procedure%20for%20bring%20our%20own%20SQL%20server%20licence%20to%20azure%20VM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168215%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-in%2Fblog%2Feasily-bring-your-sql-server-licenses-to-azure-vms%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fazure.microsoft.com%2Fen-in%2Fblog%2Feasily-bring-your-sql-server-licenses-to-azure-vms%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

what is the procedure for bring our own SQL server licence to azure VM

6 Replies

Actually I have already purchased an azure VM with sql server pre installed. So if there is any way to add my license to that preinstalled sql server

I never tried but have a look on https://blog.sqlauthority.com/2015/11/06/sql-server-how-to-change-sql-server-product-key-or-license-...

 

In my case, I need more customization in SQL instance. So I have created SQL Image bakery, Where I setup custom SQL image with my own SQL version with right product key and all other customization using powershell dsc. This way I setup my SQL in less than 20 min and on top of it, need to run couple of dsc code (takes 3-4 min) while creating SQL workload from my own custom image.

You can't. Even if you manage to change the license of the SQL Server, you're going to pay full price for it because the license is tied to the VM level, not OS. What you have to do is to create a new VM, install SQL Server (or use one of the BYOL Images from the gallery) with your license and then move the databases.

Thank You! I was not aware of it as I never done it before.
In my case, I create vanilla image and then do sql installation n configuration.

Thanks for your reply..

 

Also, Is it possible to install TFS server inside azure vm(purchased only VM) and use my own license key to activate it...