LICENSEWARE
Contribute

Cloud BYOL and authorized cloud environments

From the LICENSEWARE WikiLast edited 22 ReferencesCited

This article is about how existing vendor license metrics are counted on named public clouds. It is not a publisher and not a unit of measure. It is not legal advice. Do not treat this page as a substitute for the executed Order.

On This Page

Cloud BYOL and authorized cloud environments is topology: a customer already owns Processor, Core, PVU, Named User, or the like, and the vendor document says where those entitlements may run and how to count them there. AWS, Azure, and GCP are destinations, not the LICENSEWARE Wiki publishers. BYOL, vCPU, OCPU, AHB, and Cloud Access are not Vendor License Metrics in the catalog. Vendor ratios are given only where the vendor prints them; there are no published conversions for clouds a vendor does not name.

Editions

There is no BYOL edition. Each vendor names a program or policy and a list of destinations. Destinations not on that vendor’s list are outside that policy’s counting method; contractual rights remain the ordering document. Oracle ACE does not extend to OCI, nor Microsoft AHB to AWS, unless that vendor says so.

Metrics

Fifteen vendor programs, sorted A–Z by vendor. Each row is an overlay on existing encyclopedias — not a purchase meter.

# Vendor Program (vendor name) Encyclopedia What the vendor says 
1 Adobe none published Adobe Named User licensing Named User remains Named User. No Authorized Cloud Environment, Cloud Access, or AHB analogue on adobe.com legal pages. Adobe publishes no BYOL of Named User onto AWS, Azure, or GCP.[citation needed] 
2 Atlassian none published Atlassian Cloud and Data Center licensing meters Cloud User and Data Center User are separate purchase meters. You cannot BYOL Data Center seats onto Atlassian Cloud, or onto AWS as a substitute for Cloud.[citation needed] Bitbucket Hybrid License is a bundled Cloud+DC model, not a hyperscaler mapping.[19] 
3 Autodesk none (BYOS is not IaaS) Autodesk Single User and Flex licensing BIM Collaborate Pro “Bring Your Own Subscription” is an invite/collaboration policy among Autodesk subscribers, not hyperscaler IaaS BYOL.[20] 
4 Cisco none (portfolio) Cisco software subscription and Flex Plan licensing No cross-portfolio BYOL topology.[citation needed] Isolated Marketplace BYOL AMIs still consume the same product meters (for example ISE VM). There is no Cisco BYOL unit of measure.[21] 
5 Citrix none published Citrix User/device, Concurrent, and Flex licensing No ACE-style mapping of User/device or Concurrent onto AWS/Azure/GCP.[citation needed] DaaS / Universal Hybrid Multi-Cloud is Citrix’s own hybrid subscription.[22] Windows/RDS inside a Citrix image is Microsoft AHB/License Mobility, not a Citrix meter.[citation needed] 
6 IBM Eligible Public Cloud BYOSL IBM Passport Advantage licensing Policy overlay; does not modify IPAA/IPLA/LI. Named EPCs include AWS, Azure, GCP, IBM Cloud, Oracle, and others IBM lists. When used under BYOSL, entitlements may not be used elsewhere at the same time. Note 1 (where IBM footnotes it): 1 vCPU = 1 Core = 1 VPC = 70 PVU. Hyperthreading containers: 2 vCPUs = 1 Core. Oracle Cloud Note 3: 1 OCPU = 2 vCPU = 140 PVU. Bare metal follows PVU tables, not the flat 70. BYOSL and vCPU are not separate metrics.[10][11] 
7 Microsoft Azure Hybrid Benefit Windows Server licensing Product Terms use right in the customer’s Azure account. Windows Server: processor license = 16 cores; VM floor 8 cores. SQL Server core table is printed in Product Terms (Enterprise Core to GP is 1:4; Business Critical 1:1; Standard GP 1:1; Standard to BC 4:1). SQL VM floor 4 cores.[citation needed] Not available in Azure SQL Database serverless. Applies to Windows Server Core and SQL Server Core; AHB is not a separate metric.[7][17][18] 
8 Microsoft License Mobility through Software Assurance SQL Server licensing Server-pool SA benefit. Not Windows Server OS. Azure Services or qualified License Mobility Partners. Per-core with SA: one virtual core, minimum 4 cores per OSE. SQL Server+CAL: one OSE per Server License with SA. Fail-over under LM is narrower than AHB. M365 User SLs are SaaS, not BYOL.[citation needed][4][6] 
9 Oracle Authorized Cloud Environments Oracle Database licensing Educational PDF, policies as of 12 June 2024; may not be incorporated into any contract. Named: Amazon EC2 and RDS, Microsoft Azure, Google Cloud Platform. OCI is not in that ACE list. Two vCPUs = one Processor if HT enabled; one vCPU = one Processor if not. Processor Core Factor Table is not applicable. SE family uses instance-size sockets, not Core Factor. ULA licenses may run in ACE but may not be included in ULA certification. Applies to Processor and Named User Plus; vCPU and ACE are not separate metrics.[1] 
10 Oracle BYOL to PaaS / Universal Credits Oracle ULA and PULA licensing Contractual mapping in PaaS and IaaS Universal Credits Service Descriptions (27 August 2026). FAQ: one Processor license maps to two OCPUs at a high level; every 25 NUP may activate 1 OCPU on printed PaaS listings; Autonomous examples use ECPU (for example 8 ECPUs per EE Processor). Licenses applied to BYOL PaaS are deemed deployed (not also on-prem) after transition (up to 100 days). OCPU/ECPU are OCI service meters, not on-prem catalog rows. Database@Azure/@AWS/@Google is a different contract class, not covered here.[2][3] 
11 Red Hat Cloud Access (BYOS) Red Hat Enterprise Linux and OpenShift subscription licensing Appendix 1 §3 (February 2026): deploy Eligible Subscriptions in a Vendor’s Cloud if Units are sufficient and not solely physical-attribute Units. Terms and duration do not change. Featured CCSPs: Alibaba, AWS, GCP, IBM Cloud, Azure. Counting stays Socket-pair, Virtual Guest, Core, vCPU. No published 2-vCPU = 1-socket conversion. Cloud Access is not a separate metric.[14][15] 
12 SAP Certified IaaS / ASE BYOL AMI SAP Named User and Digital Access licensing Certified IaaS (AWS, GCP, Azure, IBM Cloud, and others SAP lists) is deployment of already-licensed Packages / Named User on certified infrastructure. ASE on AWS Marketplace is BYOL of existing ASE keys. No Named User↔vCPU table. RISE/FUE is SAP cloud subscription, not BYOL. BYOL is not a separate metric, and FUE is out of scope here.[12][13] 
13 Salesforce none published Salesforce User and consumption licensing SaaS. No ACE/AHB analogue for bringing Salesforce User licenses onto customer-managed hyperscaler VMs.[citation needed] 
14 ServiceNow none (own products) ServiceNow user and subscription-unit licensing No BYOL of ServiceNow products. SAM Pro materials titled “Bring your own on-premises licenses to the cloud” help customers manage Microsoft/Oracle BYOL — a SAM product feature, not a ServiceNow license mapping.[citation needed] 
15 VMware VCF License Portability VMware vSphere and VMware Cloud Foundation licensing SPD June 2026: port entitlements only to the then-current Certified Cloud Services list (July 2026 header includes AWS, Azure, GCVE, Oracle, and listed providers). Metric stays per Core with 16 Cores per Processor. Portability does not convert Core to vCPU. Entire component set; customer remains licensee. OEM, non-Enterprise legacy upgrades, and CSP/Metal-as-a-Service (provider is licensee) are not eligible. License Portability is not a separate metric.[8][9] 

Counting / floors

Quote only what the vendor printed. Destinations not on that vendor’s list are outside that method.

  • Oracle ACE (educational, 12 June 2024). AWS/Azure/GCP: 2 vCPUs = 1 Processor with HT; 1 vCPU = 1 Processor without HT. Core Factor Table does not apply. SE2 NUP minimum: 10 NUP per 8 Amazon/Azure/GCP vCPUs. Four Amazon vCPUs, HT on → two Processor licenses (Oracle’s example).[1]
  • Oracle BYOL to PaaS (UCM 27 August 2026). High-level FAQ: 1 Processor → 2 OCPUs; 25 NUP → 1 OCPU on printed listings. Ratios are per service line; the ECPU examples do not apply globally.[2][3]
  • Microsoft AHB Windows Server. Processor license = 16 cores. VM minimum 8 cores. Dedicated Host (Datacenter): cover physical cores, unlimited VMs. Dual-use windows: Standard 180 days; Datacenter VM licensing indefinitely; Dedicated Host 180 days.[17]
  • Microsoft AHB SQL Server. Product Terms table only. SQL VM minimum 4 cores.[citation needed] Not serverless Azure SQL Database. Product Terms print no Server+CAL → vCore ratio.[18]
  • Microsoft License Mobility. 1 Core License with SA → 1 virtual core, minimum 4 cores per OSE. Not Windows Server OS.[4][6]
  • VMware VCF. Still 16 Cores per Processor. No vCPU mapping.[8]
  • IBM BYOSL. 1 vCPU = 1 VPC = 70 PVU only where IBM footnotes Note 1. HT containers 2 vCPU = 1 VPC. OCPU Note 3 is 140 PVU. Bare metal uses PVU tables.[10][11]
  • Red Hat Cloud Access. Appendix 1 Units unchanged. No 2-vCPU = 1-socket rule.[14]
  • SAP. Named User / Digital Access / engine metrics unchanged on certified IaaS. No vCPU table.[12][13]

Virtualization

Oracle Core Factor, IBM PVU tables, and VMware per-Core floors apply only to the vendor that prints them. IBM BYOSL does not replace ILMT / License Service.[10] VMware: every Core on the Server, including BIOS-deactivated Cores.[8] Microsoft AHB Dedicated Host unlimited VMs is Datacenter-only as printed.[17]

Cloud / BYOL

This section is the article. Hyperscaler license-included / PAYG marketplace images are the cloud seller’s offer, not BYOL. Gold / BYOS images (Red Hat) keep the Red Hat subscription; PAYG bundles a second fee.[15][16] SPLA, CSP hoster, VMware Metal-as-a-Service, and IBM partner hosting are cases where the provider is the licensee — out of this overlay.[8][citation needed]

Programs

  • Oracle ACE — educational cloud-licensing PDF; not contractual.[1]
  • Oracle PaaS/IaaS Universal Credits — contractual BYOL-to-PaaS mapping.[2]
  • Microsoft Product Terms — AHB and License Mobility through SA.[4][7]
  • VMware Cloud Foundation SPD — License Portability + Certified Cloud Services list by URL.[8][9]
  • IBM Eligible Public Cloud BYOSL — policy; does not modify IPAA/IPLA/LI.[10]
  • SAP certified IaaS / ASE BYOL HOWTO — deployment of existing licenses.[12][13]
  • Red Hat Appendix 1 Cloud Access — Eligible Subscriptions in a Vendor’s Cloud.[14]

Buying programs and private price books are not catalog units.

Out of scope

  • Hardware / HAM.
  • PAYG / license-included marketplace SKUs.
  • Microsoft 365, Adobe Creative Cloud, Salesforce, ServiceNow, Atlassian Cloud as if they were BYOL.
  • RISE with SAP / FUE.
  • Oracle Database@Azure / @AWS / @Google service descriptions (different contract).
  • 2-vCPU-per-core rules for vendors that do not print them.
  • Duplicating vendor encyclopedia bodies.
  • Partner and reseller blogs and SAM tool vendor marketing.
  • The ITAM Handbook “Cloud Metrics” archive is not this page.

Catalog rows

Sample catalog rows for this article, grouped by table.

References

  1. Licensing Oracle Software in the Cloud Computing EnvironmentPolicies as of 12 June 2024. Educational; may not be incorporated into any contract. ACE; vCPU counting.Effective 2024-06-12. Retrieved 2026-08-31.
  2. Oracle PaaS and IaaS Universal Credits Service Descriptions27 August 2026 (UCM v082726). BYOL-to-PaaS.Effective 2026-08-27. Retrieved 2026-08-31.
  3. Oracle Bring Your Own License FAQRetrieved 2026-08-31.
  4. Product Terms — Software Assurance BenefitsLicense Mobility.Retrieved 2026-08-31.
  5. Product Terms — Microsoft AzureAzure Hybrid Benefit.Retrieved 2026-08-31.
  6. License Mobility through Software AssuranceRetrieved 2026-08-31.
  7. Azure Hybrid BenefitRetrieved 2026-08-31.
  8. VMware Cloud Foundation Specific Program DocumentationJune 2026. License Portability.Retrieved 2026-08-31.
  9. VCF License Portability — List of Certified Cloud ServicesJuly 2026 header.Retrieved 2026-08-31.
  10. Eligible Public Cloud BYOSL PolicyChange log March 2024.Retrieved 2026-08-31.
  11. Container LicensesRetrieved 2026-08-31.
  12. SAP and HyperscalersRetrieved 2026-08-31.
  13. Quick Start Guide for BYOL Versions of SAP ASE on AWSASE 16.0 SP04 PL04; AMI base 15 July 2023.Retrieved 2026-08-31.
  14. Product Appendix 1 Software and Support SubscriptionsFebruary 2026. Cloud Access §3.Retrieved 2026-08-31.
  15. Red Hat Cloud AccessRetrieved 2026-08-31.
  16. Red Hat Cloud Access FAQRetrieved 2026-08-31.
  17. Azure Hybrid Benefit for Windows ServerMicrosoft Learn. 8-core-license minimum per VM; processor license = 16 core licenses; migration allowance; Dedicated Host unlimited virtualization (Datacenter).Retrieved 2026-09-26.
  18. Azure Hybrid Benefit - Azure SQL Database & SQL Managed InstanceMicrosoft Learn. Enterprise/Standard core-to-vCore table; not available on serverless compute tier; 180-day migration allowance.Retrieved 2026-09-26.
  19. Maximize flexibility with the Bitbucket Hybrid LicenseBitbucket Data Center plus Bitbucket Cloud under a single license.Retrieved 2026-09-26.
  20. Bring Your Own Subscription (BYOS) for BIM Collaborate ProBYOS is a policy defining access to Autodesk modules and services; invite other subscribers to projects.Retrieved 2026-09-26.
  21. Overview of Cisco ISE instances on AWSA Cisco ISE VM license must be purchased to use ISE instances on AWS.Retrieved 2026-09-26.
  22. Compare Citrix Subscriptions (feature matrix)Names Citrix Universal Hybrid Multi-Cloud; DaaS capabilities and hybrid multi-cloud workload support included in that subscription.Retrieved 2026-09-26.

See also

Esc