Cloud License Portability: Bring Your Own License (BYOL) Guide

What is BYOL? (Definition & Why It Matters)

Bring Your Own License (BYOL) is a cloud consumption model that allows enterprises to use existing on-premise software licenses on cloud infrastructure instead of purchasing new cloud-provided licenses. In essence, you avoid paying the cloud provider's hourly per-core or per-instance software premium.

A typical scenario: You own 100 perpetual Windows Server 2022 Datacenter licenses and 50 perpetual Oracle Database Enterprise Edition licenses, all fully paid on-premise. When migrating to AWS, you have two choices:

• Pay-as-you-go (PAYG): AWS charges you hourly for the Windows/Oracle software licenses. For 100 Windows Server instances, that's approximately $1.5K per instance per year (on top of compute). For Oracle, it's approximately $12K per instance per year. Over 3 years, that adds up to $450K+ in unnecessary software costs.
• BYOL: You use your existing licenses. AWS charges only for the compute infrastructure (EC2, storage, networking). Over 3 years, you save $450K.

The math is why BYOL matters: enterprises pay 40–70% premium for software when buying through cloud providers compared to on-premise perpetual licensing. For large-scale cloud migrations, BYOL is a must-have cost optimization strategy.

BYOL on AWS: Windows Server, SQL Server, Oracle & SAP

AWS supports BYOL for several software categories, but each requires specific infrastructure configurations:

Windows Server BYOL on AWS

• Requirement: Dedicated Hosts (not Dedicated Instances or on-demand)
• License type: Windows Server Standard or Datacenter (per-core or per-processor licenses count)
• Configuration: You must launch instances on AWS Dedicated Hosts and assign your licenses. AWS does not charge per-instance software fees.
• Documentation: AWS requires you to track BYOL assignments in a license database and prove you have a valid license for every running instance.
• Cost model: Dedicated Host fees apply (approximately $3–5/hour for on-demand or discounted via Reserved Hosts). No additional Windows software charge.

SQL Server BYOL on AWS

• Requirement: Dedicated Hosts or Dedicated Instances (Dedicated Hosts preferred for cost efficiency)
• License type: SQL Server Standard, Enterprise, or Web (per-core licenses apply to cloud)
• Licensing metric: Per-core licensing. Your on-premise per-core licences (2-core packs) map to cloud vCores. A 16-vCore instance requires 8 licences.
• Cost saving: Approximately $6K per SQL Server Enterprise instance per year vs pay-as-you-go
• Note: SQL Server Web and Standard support on-demand instances as well, but Dedicated Hosts are more cost-effective at scale.

Oracle BYOL on AWS

• Requirement: AWS Dedicated Hosts only (Oracle is extremely strict about licensing)
• License types: Processor licenses (oldest model), Named User Plus (NUP), or Unlimited Licence Agreement (ULA)
• Processor metric portability: Oracle allows 1 processor licence to cover multiple vCores on cloud (processor factor chart applies). A 4-core Oracle licence may cover a 16-vCore instance in some cases.
• Cost saving: Approximately $12K per Oracle Enterprise Edition instance per year vs pay-as-you-go
• Audit risk: Oracle is aggressive about cloud audits. You must have written licence documentation and assignment records.
• Support level: Your support level (annual maintenance %) must continue even on cloud to avoid non-compliance.

SAP BYOL on AWS

• Requirement: Certified instance types (specific AWS instance families approved by SAP)
• Instance types: AWS instance families like x2iezn, x2iedn, r7i, r6i for HANA; c5, c6, m5, m6 for non-HANA applications
• License type: Named User, Processor, or RISE subscriptions (RISE limits BYOL flexibility)
• Cost saving: High (SAP licenses are expensive; typical enterprise saves $200K+/year)
• Documentation: SAP requires proof of SAP software licence and certification of the instance type.

BYOL on Azure: Hybrid Benefit, Windows, SQL & SAP

Azure's approach to BYOL is more automated than AWS, primarily through Azure Hybrid Benefit (AHB) and role-based license assignment.

Azure Hybrid Benefit (AHB) for Windows Server

• How it works: If you own Windows Server Datacenter or Standard licenses with Software Assurance (SA), you can apply them to Azure VMs at no software charge.
• Licensing metric: Each 2-core licence covers 2 vCores on Azure (1:1 normalised core mapping).
• Setup: Enable AHB at VM creation time in the Azure portal. No physical Dedicated Hosts required (unlike AWS).
• Cost saving: Approximately $1.5K per Windows Server instance per year
• SA requirement: Your licences must have active Software Assurance (expires 1 month after purchase window closes).

Azure Hybrid Benefit for SQL Server

• How it works: SQL Server per-core licences with SA can be applied to Azure SQL Database, Azure SQL Managed Instance, or SQL VMs.
• Licensing metric: Each 2-core licence covers up to 4 vCores on Azure (2:1 ratio). Abnormal compared to Windows, which is 1:1.
• Cost saving: Approximately $6K per SQL Server Enterprise instance per year
• Note: Azure also offers a "pay-as-you-go" SQL VM option, but AHB is almost always cheaper if you own the licences.

Azure Hybrid Benefit for Linux (RHEL/SUSE)

• How it works: If you own Red Hat Enterprise Linux or SUSE subscriptions, Azure applies discounts automatically.
• Discount: Approximately 50% off compute for qualifying subscriptions.
• Setup: Select "RHEL with HA" or "SUSE" images at VM creation; AHB is applied automatically if you have subscriptions on file.

Azure for SAP

• Requirement: Azure Certified Cloud Infrastructure (ACI) for HANA and non-HANA applications
• Instance types: Azure memory-optimised SKUs (E-series, M-series) certified by SAP
• BYOL approach: Similar to AWS; you bring existing SAP licences and deploy on certified instances.
• Cost benefit: High. Large enterprises save $300K+/year by bringing SAP licences to Azure.

BYOL on GCP: Windows, SQL Server & SAP

Google Cloud Platform supports BYOL through Committed Use Discounts (CUDs) and Sole-Tenant Nodes for specific software.

Windows Server BYOL on GCP

• Requirement: Sole-Tenant Nodes (similar to AWS Dedicated Hosts)
• Licensing: Bring your own Windows Server Datacenter or Standard licences
• Cost model: Sole-Tenant Node fees + compute. No per-instance Windows software charge.
• Node density: Each Sole-Tenant Node can host multiple VMs, so per-VM overhead is lower than AWS Dedicated Hosts.

SQL Server BYOL on GCP

• Requirement: Sole-Tenant Nodes for Enterprise Edition; Standard and Web supported on regular instances
• Licensing metric: Per-core (same as on-premise and other clouds)
• Cost saving: Approximately $4K–6K per instance per year depending on edition

SAP BYOL on GCP

• Requirement: Google Cloud SAP-certified machine types (M-series for HANA, N-series for others)
• BYOL approach: Bring SAP licences; deploy on certified instances.
• Cloud commitment: GCP offers 3-year Cloud Commitments for SAP workloads with up to 50% discount on compute.
• Cost model: Compute discounts + no software markup

BYOL Savings by Software Type (Annual per Instance)

Software	List PAYG Rate (/hr)	BYOL Rate (/hr)	Annual Saving (100-Instance Fleet)
Windows Server Datacenter	$0.26	$0.00	$227,600
SQL Server Enterprise	$1.29	$0.00	$1,129,240
Oracle Database Enterprise	$2.41	$0.00	$2,111,160
SAP HANA (per core)	$1.56	$0.00	$1,367,040
Redis Enterprise	$0.99	$0.00	$866,760
IBM SPSS	$0.45	$0.00	$394,200

Key insight: For a 100-instance Oracle fleet, BYOL saves $2.1M+ annually. Even a small 10-instance fleet saves $211K+. This is why BYOL negotiation is critical for large migrations.

AWS Dedicated Hosts: What You Need to Know

AWS Dedicated Hosts are the foundation for BYOL on AWS for Windows, SQL Server, and Oracle. Understanding Dedicated Hosts is critical for cost optimization.

What is a Dedicated Host?

A Dedicated Host is a physical server that you fully control. Unlike on-demand instances (which share hardware with other customers), Dedicated Hosts are yours exclusively. AWS does not charge per-instance software fees on Dedicated Hosts; instead, you pay a fixed monthly fee for the Host and then can launch as many instances as the Host's capacity allows.

Dedicated Host Pricing

• On-demand Dedicated Host: Approximately $3–5/hour (~$2,200–3,600/month) depending on instance family and region
• Dedicated Host Reservation (1-year): Approximately 30% discount vs on-demand
• Dedicated Host Reservation (3-year): Approximately 50% discount vs on-demand (~$1,100–1,800/month)
• Instances launched on Dedicated Hosts: On-demand compute charges apply (e.g., $1.50/hour for a m5.large), but no Windows/SQL/Oracle software charges

Dedicated Host Capacity & License Assignment

A Dedicated Host has fixed capacity. For example, a Dedicated Host for m5 instance family can hold up to 16 m5.large instances or 4 m5.4xlarge instances (capacity varies by instance family). You assign your BYOL licences to specific instances on the Host. AWS requires you to maintain a licence assignment database showing which licences are allocated to which instances.

Dedicated Hosts vs Dedicated Instances

Do not confuse Dedicated Hosts with Dedicated Instances. Dedicated Instances launch on hardware dedicated to your account, but AWS still charges per-instance software fees. For BYOL, you must use Dedicated Hosts.

When to Use Dedicated Hosts

• Large Windows Server fleets: 50+ instances benefit from Dedicated Host consolidation
• Oracle databases: Oracle's licensing model benefits from Dedicated Hosts because processor factors allow fewer licences per core
• SQL Server Enterprise: Break-even is typically 8+ instances (a Dedicated Host can fit 16 m5.large instances)
• 3+ year commitment: Dedicated Host Reservations (3-year) offer exceptional ROI

Azure Hybrid Benefit Deep Dive: Licensing & Stacking

Azure Hybrid Benefit (AHB) is the Azure equivalent of BYOL, but it's simpler to implement than AWS Dedicated Hosts. No special infrastructure required—just enable AHB when creating VMs.

AHB Eligibility Requirements

• Windows Server: Datacenter or Standard edition; must have Software Assurance (SA)
• SQL Server: Enterprise or Standard edition; must have SA
• System Center: Datacenter or Standard; must have SA
• RHEL/SUSE: Subscription on file (no SA required)

Software Assurance (SA): SA is a support/upgrade contract that renews annually (typically 30% of licence cost). Your SA is valid for up to 3 years after purchase (or 2 years after licence expiry if you lapsed). Once SA expires, you can no longer use AHB.

AHB Normalised Core Concept

Azure uses "normalised cores" to abstract the physical CPU mapping. Each licence covers a fixed number of normalised cores:

• Windows Server: 2-core licence = 2 normalised cores (1:1 ratio)
• SQL Server: 2-core licence = 4 normalised cores (2:1 ratio). This is a key advantage: you get more coverage per licence.

Example: You own 40 SQL Server Enterprise 2-core licences (80 cores). On Azure with AHB, those 40 licences cover up to 160 normalised cores. A D64s v5 VM (64 vCores) requires only 16 normalised cores (after rounding up), so your 40 licences can cover 10 such instances.

AHB + Reserved Instances Stacking

This is where Azure shines compared to AWS. You can stack AHB (removes software charges) with Reserved Instances (discounts compute charges). This combination offers maximum savings.

Pricing Model	Windows Server (per D4s v5 /month)	SQL Server Enterprise (per D8s v5 /month)
On-Demand + Software	$350 + $75 (software) = $425	$700 + $300 (software) = $1,000
On-Demand + AHB	$350 (no software)	$700 (no software)
Reserved Instance (1-year) + AHB	$245 (30% RI discount)	$490 (30% RI discount)
Reserved Instance (3-year) + AHB	$140 (60% RI discount)	$280 (60% RI discount)

Annual savings example: For a fleet of 100 SQL Server Enterprise VMs (D8s v5) with AHB + 3-year RIs, your savings vs on-demand + software is 72% ($9,000 vs $25,200 per instance per year). Over 3 years, that's $1.92M saved.

Oracle BYOL Rules: 10 Golden Rules for Cloud Licensing

Oracle is notoriously strict about cloud licensing. These 10 rules will keep you compliant and avoid audit penalties.

1. Dedicated Hardware Only: Oracle requires Dedicated Hosts on AWS (or bare metal on Azure/GCP). You cannot use shared cloud infrastructure for Oracle BYOL.
2. Processor Metric Portability: Oracle allows processor licences to cover multiple cloud cores via a "processor factor" chart. A 4-core Oracle licence may cover an 8-core cloud instance depending on the processor type. Consult Oracle's Processor Core Factor Table.
3. Named User Plus (NUP) Conversion: If you own NUP licences, you must own at least 5 NUPs per 100GB of data, or convert to processor licences. This is often overlooked.
4. ULA Portability: Unlimited Licence Agreements (ULAs) include cloud rights, but you must document that the cloud usage falls within the ULA scope (e.g., specific product/edition).
5. Support Level Continuity: Your Oracle support (annual maintenance %) must continue on cloud at the same level as on-premise. You cannot reduce support to save costs.
6. Licence Assignment Records: Maintain a database of BYOL licence assignments. Document which Oracle licence SKU is assigned to which cloud instance/database. Oracle auditors will ask for this.
7. Multi-Tenancy Not Allowed: If you run multiple databases on a single Dedicated Host, each database must have its own BYOL licence. You cannot share a licence across databases.
8. Data Guard & Standby: If you use Oracle Data Guard for failover, you must licence both the primary and standby databases (same as on-premise rules).
9. Audit Rights: Oracle reserves the right to audit cloud deployments. Expect audits every 2–3 years. Non-compliance penalties are severe (3–4× underpaid maintenance).
10. ELA Cloud Riders: If you have an Oracle Enterprise Licence Agreement (ELA), review the cloud rider carefully. Some ELAs limit cloud deployments to specific instance types or limit the number of cores covered.

SAP BYOL & Licensing: RISE vs BYOL Trade-offs

SAP offers multiple licensing models for cloud, and BYOL is not always the best choice. Understand the trade-offs.

SAP Named User Licensing

SAP Named User (NU) licences are the most common and most flexible for BYOL on cloud. You license by number of users (typically $100–500/user/year depending on product and region). Cloud does not change Named User counting; you use the same methodology as on-premise.

SAP Processor Licensing

Processor licences (per SAPS per physical processor) can be ported to cloud, but SAP has strict requirements: the instance type must be on SAP's certified list, and the SAPS value of the cloud instance must be documented. You cannot just assume a 64-vCore instance covers X processors.

SAP RISE Subscription

RISE (Run Simple in the Enterprise) is SAP's managed cloud offering. RISE includes SAP licences, cloud infrastructure (on AWS, Azure, or GCP), and support in one bundled price. RISE is attractive because it simplifies procurement, but it limits BYOL flexibility. You cannot mix RISE with your own cloud infrastructure; you must use SAP-selected cloud partners and instance types.

RISE vs BYOL comparison:

• RISE: Higher per-user cost (typically $250–400/user/year bundled), but includes infrastructure and support. Good for small-to-medium implementations or companies without cloud expertise.
• BYOL: Lower software cost (can be 30–50% cheaper if you already own licences), but you manage cloud infrastructure and negotiate cloud pricing separately. Good for large enterprises with existing SAP licences and cloud expertise.

SAP HANA Licensing on Cloud

SAP HANA can be licensed as Named User, Processor, or perpetual on-premise + cloud-only "Cloud Extension" licence. The Cloud Extension is attractive: you keep your on-premise licence and add a cloud-only licence for cloud-only instances (at reduced cost). This is especially useful for dev/test or seasonal cloud workloads.

Licence Mobility Through Software Assurance (LMSA)

Microsoft offers Licence Mobility Through Software Assurance (LMSA) as a formal mechanism to move eligible server software licences to cloud.

Eligible Software

• Windows Server Datacenter/Standard
• SQL Server Enterprise/Standard
• System Center Datacenter/Standard
• Exchange Server Enterprise
• SharePoint Server Enterprise

LMSA Requirements

• Software Assurance must be active
• Licences must not have been deployed to cloud in the previous 90 days (transfer limit)
• Can be used on Azure or third-party cloud (AWS, GCP) but not both simultaneously
• Requires License Verification Letter (LVL) from Microsoft to prove ownership

Server Farm Rules

Microsoft defines a "server farm" as a group of identical servers running the same software. LMSA has specific rules: you must maintain licence parity across all servers in the farm. If you have 10 SQL Server licences and 15 servers, you are under-licensed even on-premise.

BYOL Audit Risks: Cloud Usage Does Not Guarantee Compliance

BYOL is not a "set and forget" strategy. Cloud providers and vendors actively audit cloud usage for license compliance. Understand the risks.

Oracle Cloud Audits

Oracle has a history of aggressive audits, and cloud deployments are now in scope. Oracle will request:

• Licence assignment records for each cloud instance/database
• Proof that Dedicated Hosts are in use
• Usage history (database size, user count) to validate licence type matches usage
• Support contracts to verify SA is active

Non-compliance penalties are 3–4× the underpaid maintenance amount. A $500K Oracle audit shortfall can result in $1.5M–2M penalty.

SAP UDI Measurement

SAP uses "Usage Data" infrastructure (UDI) to measure cloud usage and validate licensing. SAP measures Named Users, Named User Plus, and processor metrics via UDI and can cross-check against your licence count. If you have 100 Named Users on cloud but only purchased 75, SAP will send an audit notice.

Microsoft SAM & Audits

Microsoft Software Asset Management (SAM) audits are typically less aggressive than Oracle, but compliance issues will be flagged. Microsoft reserves the right to audit any customer with EAs or high cloud spend. Common findings: under-licensed RIs, missing AHB assignments, or undocumented licence transfers.

Documentation Requirements for BYOL Compliance

• Maintain a BYOL licence assignment database (spreadsheet or CMDB)
• Document licence acquisition (purchase order, invoice, licence key)
• Document cloud instance/database assignment (with dates)
• Track support/SA renewal dates
• Keep audit trails showing why BYOL was chosen over PAYG

BYOL vs Cloud-Native Licences: When Does Each Model Win?

BYOL is not always the best choice. In some scenarios, cloud-native pricing is superior or simpler. Evaluate both.

BYOL Wins When:

• 3+ year steady-state workloads: Cloud-native pricing is typically 30–50% cheaper than PAYG, but only if you have mature licences with low maintenance costs. If you own perpetual Windows/SQL licences, BYOL wins.
• Large fleet deployments: BYOL for 100+ instances benefits from consolidated licensing and Dedicated Host pricing.
• High maintenance cost on-premise: If you're already paying 22–25% annual support (like SAP), BYOL does not save much. But if you have low maintenance (e.g., 10%), BYOL savings are substantial.
• Existing ELA/ULA with cloud riders: If your ELA already includes cloud rights, BYOL is free (no additional cost beyond maintenance).

Cloud-Native Licensing Wins When:

• Short-term workloads (< 1 year): No payback period for Dedicated Hosts or complex BYOL setup. PAYG is simpler.
• PaaS deployments: Azure SQL Database, Azure Database for PostgreSQL, etc. do not support BYOL. You pay per-DTU or per-vCore. BYOL is not an option.
• Serverless functions: AWS Lambda, Azure Functions, GCP Cloud Functions are consumption-based and don't support traditional BYOL.
• Development/test environments: Cloud-native discounts (Azure Dev/Test, AWS free tier) may be cheaper than BYOL setup overhead.
• Database as a Service (DBaaS): Managed databases (Aurora, Azure Database, Cloud SQL) include management overhead costs not present in BYOL. The total cost may be comparable.

8 BYOL Optimisation Tactics

Frequently Asked Questions