Licensing glossary
What is Bring Your Own License (BYOL)?
Bring Your Own License (BYOL) means using licenses you already own on a cloud provider's infrastructure, instead of paying a rate with the license included.
How it works
Each vendor sets its own rules for counting a license in the cloud. For Oracle on Amazon EC2, RDS and Azure, the cloud licensing policy counts two vCPUs as one Processor license when multithreading is enabled and one vCPU as one license when it is not; the core factor table does not apply. That policy is not a contract, and Oracle can change it.
For Microsoft, Azure Hybrid Benefit brings SQL Server and Windows Server licenses with active Software Assurance to Azure at the base compute rate. On Amazon RDS, SQL Server can run License Included or with your own license through License Mobility.
Worked example
Illustrative numbers. Oracle Database Enterprise Edition on an EC2 instance with 16 vCPUs:
- Multithreading enabled
- 16 ÷ 2 = 8 Processor licenses
- Multithreading disabled
- 16 Processor licenses
- Core factor
- Not applied in the cloud
A lift-and-shift to AWS changes the count even when the core count does not change.
What to watch
- Support status. Oracle licenses on third-party support are not eligible for BYOL on Oracle Database@AWS.
- ULA licenses in AWS, Azure or Google Cloud. They cannot be counted at certification.
- Dual use. A SQL Server license moved to Azure may keep running on premises for 180 days, then the old deployment needs its own license.
- Server + CAL. Those licenses cannot be used for Azure Hybrid Benefit on SQL Server.