BYOL to Cloud: Bring Your Software Licenses Legally 2026

Quick answer

BYOL (Bring Your Own License) means using the software licences your business already owns to run on cloud infrastructure (Azure, AWS), instead of renting a licence bundled with the virtual machine. Done right, BYOL saves from 29% to 80% versus pay-as-you-go pricing (Microsoft's published figures for Azure Hybrid Benefit). Done wrong — moving a licence that is not allowed to run on third-party cloud — and the "saving" turns into a contract breach and copyright risk.

There are two key Microsoft mechanisms. Azure Hybrid Benefit: use Windows Server / SQL Server licences with Software Assurance for discounted rates when running on Azure. License Mobility through Software Assurance: bring application servers (SQL Server, Exchange, SharePoint, System Center) to third-party clouds like AWS without buying new licences. The shared requirement: the licence must have active Software Assurance (SA). One key exception: Windows Server (the operating system) is NOT eligible for License Mobility — on Azure you must use Azure Hybrid Benefit instead.

On Vietnamese law: software is protected as a literary work under Điều 22, Luật Sở hữu trí tuệ 50/2005/QH11, and a "licence" is by nature a time-limited, conditional grant of the right to use (Điều 47). BYOL to the cloud creates no new right — it is only valid when the licence terms permit deployment on third-party infrastructure. Using software beyond the permitted scope can still be sanctioned administratively under Nghị định 341/2025/NĐ-CP (effective 15 Feb 2026, caps of VND 250 million for individuals / VND 500 million for organizations).

*Disclaimer: This article is for information only and is NOT legal advice or official licensing advice. Legal document names are kept in Vietnamese (original). Savings figures and program conditions are taken from official Microsoft/AWS pages at the time of writing (see sources) — vendor policies can change. Check your specific licence terms and consult experts before deploying.*

• Windows Server: Azure Hybrid Benefit saves an average of 36% versus the leading cloud provider (Microsoft published).
• SQL Server: saves an average of 29%; moving to Azure SQL Database / Managed Instance saves up to 30% or more.
• Combining Azure Hybrid Benefit with Azure Reserved VM Instance: up to 80% off standard pay-as-you-go for Windows Server; Linux (RHEL/SLES) subscriptions save up to 76%.
• License Mobility requires active Software Assurance and submitting a License Verification Form within 10 days of deployment.
• Maximum fines for copyright violations in Vietnam under Nghị định 341/2025: VND 250 million (individuals) / VND 500 million (organizations).

1. What BYOL is and why it matters for Vietnamese businesses

BYOL (Bring Your Own License) is the model of taking software licences you already own and running them in the cloud, instead of buying/renting new licences baked into the cloud price. For licence-heavy workloads like Windows Server and SQL Server, this is usually the biggest saving when moving to the cloud — Microsoft publishes average savings of 36% for Windows Server and 29% for SQL Server via Azure Hybrid Benefit.

The Vietnamese context: many businesses have already bought perpetual licences or Enterprise Agreements with Software Assurance. When they move infrastructure to the cloud, not knowing they have a BYOL right leads them to "double-buy" — paying twice for licences they already own, bundled into license-included VMs. Conversely, moving a licence that is not permitted to run on third-party cloud creates compliance risk.

In short, BYOL is a double-edged sword: on one side the clearest cost lever in a migration; on the other, the easiest place to get compliance wrong, because the right to move a licence to the cloud depends closely on the licence type, Software Assurance status and contract terms — it is not "my licence, so I can run it anywhere".

2. Azure Hybrid Benefit: how much you save moving Windows/SQL to Azure

Azure Hybrid Benefit lets you use Windows Server and SQL Server licences (with Software Assurance or an eligible subscription) to pay discounted rates on Azure, instead of the license-included price. Per Microsoft's published figures: Windows Server saves an average of 36% versus the leading cloud provider; SQL Server saves an average of 29%; and combined with an Azure Reserved VM Instance, savings reach up to 80% off standard pay-as-you-go. Table 1 summarises by workload.

A practical detail during migration: Azure Hybrid Benefit for Windows Server includes 180 days of dual-use rights — during the transition you can run the on-premises machine and the Azure machine on the same licence without being counted as exceeding scope, giving you time to complete the migration before turning off the old machine.

3. License Mobility: which software can move to third-party cloud

License Mobility through Software Assurance lets you move application servers — SQL Server, Exchange Server, SharePoint Server, System Center — to a third-party cloud (like AWS) without buying new licences, as long as the licence has active Software Assurance. This is the mechanism for BYOL onto NON-Microsoft infrastructure. The key exception: Windows Server (the operating system) is not eligible for License Mobility — on Azure you use Azure Hybrid Benefit, while on other clouds the OS is usually licensed by the provider itself.

On process: within 10 days of deployment, the customer must complete the License Verification Form and send it to their Microsoft representative or partner so Microsoft can verify eligibility. Table 2 lists the typical product groups — License Mobility is a program for application servers, not desktop software.

4. BYOL conditions compared: Azure vs AWS

With the same Microsoft licence, BYOL differs between Azure (Microsoft's own infrastructure) and AWS (a third party). The core difference: Windows Server onto Azure goes via Azure Hybrid Benefit; onto AWS you either use license-included machines or BYOL on dedicated infrastructure (Dedicated Hosts). For application servers, both rely on License Mobility and both require Software Assurance. Table 3 compares the conditions.

One important technical note for AWS: when you bring your own SQL Server licences (BYOL) to EC2, you must use your own software media — you cannot use the pre-built AMIs AWS provides for BYOL. Getting this wrong is a common compliance mistake.

5. The Vietnam compliance angle: BYOL does not erase copyright obligations

BYOL is a cloud vendor's commercial concept, NOT a legal exception. In Vietnam, software is still protected as a literary work (Điều 22, Luật SHTT), and the right to use software is always time-limited and conditional under the licence contract — exactly the "licensing of use" nature in Điều 47, Luật SHTT. Moving a licence to the cloud beyond what the contract permits can still be sanctioned administratively up to VND 500 million for organizations (Nghị định 341/2025/NĐ-CP).

Why does an infrastructure detail become a copyright issue? An author's economic rights include the right to reproduce and distribute copies of the work (Điều 20, Luật SHTT). Running multiple copies of software across many cloud VMs is reproduction — lawful only within the scope and quantity the licence permits. Done properly, BYOL ensures every copy running in the cloud is "covered" by a valid right to use (with SA, via the correct License Mobility / Azure Hybrid Benefit mechanism).

So the task before BYOL is not the technical question "where is the VM located?" but the contractual one: do the licence terms (Product Terms / EULA) permit deployment on third-party infrastructure, do they require dedicated infrastructure or allow shared, and is Software Assurance still active? Get those three wrong and the 29–80% saving can be traded for a vendor audit and sanctions under Vietnamese law.

6. A 7-step checklist for safe BYOL

Seven steps to make BYOL both cost-saving and compliant — in order, each step a question you must answer with documents, not guesses:

• Step 1 — Inventory licences & Software Assurance. List your Windows Server, SQL Server, Exchange, SharePoint… licences with each one's Software Assurance status. Without active SA, most BYOL rights do not apply.
• Step 2 — Read the third-party deployment terms. For each product, check the Product Terms/EULA: does it permit running on third-party cloud, does it require dedicated infrastructure or allow shared.
• Step 3 — Pick the right mechanism per destination. On Azure: Windows Server and SQL Server use Azure Hybrid Benefit. On AWS/other clouds: application servers use License Mobility; Windows Server uses license-included machines or BYOL on Dedicated Hosts.
• Step 4 — Avoid double-buying. Before spinning up a license-included VM, confirm you do NOT already own a BYOL-eligible licence for that workload — paying twice for the same right is a common migration waste.
• Step 5 — Prepare your own media (on AWS). BYOL on AWS must use your own software media, not AWS's pre-built AMIs for BYOL. Prepare a valid installer before deploying.
• Step 6 — Submit the License Verification Form on time. For License Mobility, complete and send the verification form within 10 days of deployment — easy to forget, but a program condition.
• Step 7 — Keep compliance records. Retain licence proofs, SA confirmations, verification forms and screenshots of the BYOL configuration — this is the evidence that protects you in a vendor audit or an inspection under Nghị định 341/2025.

Frequently asked questions

1. What does BYOL mean? BYOL (Bring Your Own License) is bringing software licences you already own to run in the cloud, instead of renting a licence bundled with the service. With Microsoft, the two main mechanisms are Azure Hybrid Benefit (on Azure) and License Mobility through Software Assurance (onto third-party clouds like AWS).

2. How much does BYOL save? Per Microsoft's published Azure Hybrid Benefit figures: Windows Server saves an average of 36%, SQL Server 29%, Azure SQL Database/Managed Instance up to 30% or more, Linux subscriptions up to 76%, and combined with a Reserved VM Instance up to 80% off standard pay-as-you-go. Actual savings vary by region, instance type and usage.

3. Which licences CANNOT move to the cloud via License Mobility? Windows Server (the operating system) is not eligible for License Mobility — on Azure you must use Azure Hybrid Benefit, on other clouds the OS is usually licensed by the provider. License Mobility is a program for application servers (SQL, Exchange, SharePoint, System Center…), not desktop software.

4. Does BYOL require Software Assurance? For License Mobility: yes — the licence must have active Software Assurance. For Azure Hybrid Benefit: you need Software Assurance or an eligible subscription. Without appropriate SA/subscription, most BYOL rights do not apply.

5. What are the risks in Vietnam of moving licences to the cloud incorrectly? Software is protected as a literary work (Điều 22, Luật SHTT); using it beyond the licence scope can be sanctioned administratively under Nghị định 341/2025/NĐ-CP — up to VND 250 million for individuals and VND 500 million for organizations — plus the risk of a vendor audit and having to legalise.

6. On AWS, do I need a specific image (AMI) for BYOL? Yes. When you bring your own SQL Server licences (BYOL) to EC2, you must use your own software media, not the AMIs AWS provides for BYOL. Application servers also need License Mobility with active Software Assurance.

*This article is for reference and does not replace legal or licensing advice. Please check your specific Product Terms/EULA and the original legal texts (ipvietnam.gov.vn, cov.gov.vn) before deciding.*

Conclusion

BYOL is the clearest cost lever when a business moves to the cloud — Microsoft publishes savings of 29% to 80% for Windows Server and SQL Server via Azure Hybrid Benefit — but on one condition: the licence must actually be allowed to run on the infrastructure you choose. The line between "cost optimisation" and "copyright violation" fits into three questions: does the licence have SA, do the terms permit third-party deployment, and have you chosen the right mechanism (Azure Hybrid Benefit or License Mobility)?

BYOL only saves for real when every copy of software running in the cloud is covered by a valid right to use — otherwise the saving is just a fine deferred.