Bring your own license or subscription to the public cloud
Bring your own license (BYOL) support enables you to determine the license compliance of your Microsoft and Oracle software products across hybrid infrastructures. Bring your own subscription (BYOS) support enables you to determine the license compliance of your Red Hat Enterprise Linux (RHEL) software products across hybrid infrastructures.
When organizations move to the public cloud, existing on-premise perpetual licenses are carried over to the cloud using BYOL. Existing on-premise subscription licenses are also carried over to the cloud using BYOS. BYOL and BYOS help improve license optimization, as organizations must pay only for infrastructure costs.
| Product | Product edition | BYOL or BYOS | Supported cloud providers | Supported service model | Supported infrastructure type 注: This column applies to Infrastructure as a Service (IaaS) models only. |
|---|---|---|---|---|---|
| Microsoft SQL Server | All editions | BYOL |
|
Infrastructure as a Service (IaaS) | Shared and dedicated |
| Microsoft Windows Server | All editions | BYOL |
|
Infrastructure as a Service (IaaS) | Shared and dedicated |
| Oracle Database |
|
BYOL |
|
|
Shared and dedicated |
| Oracle WebLogic Server |
|
BYOL |
|
Infrastructure as a Service (IaaS) | Shared and dedicated |
| Red Hat Enterprise Linux Server | All editions | BYOS |
|
Infrastructure as a Service (IaaS) | Shared |
- Discover perpetual and subscription-based software licenses automatically across on-premise and cloud environments, such as AWS, Microsoft Azure, and GCP.
- Determine the license compliance of the following software products across your hybrid infrastructure:
- Microsoft SQL Server
- Microsoft Windows Server
- Oracle Database
- Oracle WebLogic Server (Standard, Enterprise, and Suite Editions)
- Red Hat Enterprise Linux Server
- Provide advanced support for optimization through Cloud Special Rights, such as dual use rights, edition flexibility, and unlimited virtualization.
- Perform remediation when your software is out of compliance.
Prerequisites
- Activate the Discovery (com.snc.discovery) plugin on your ServiceNow instance.
See Request Discovery for detailed instructions.
- Request and install the Discovery and Service Mapping Patterns application from the ServiceNow Store.
See Discovery patterns used by ITOM Visibility for more information on Discovery and Service Mapping patterns.
- Migrate cloud discoveries from Cloud API (CAPI) probes to pattern-based discovery.
See CAPI to Pattern Migration: Procedure for switching from CAPI-based Cloud Discovery to pattern-based Cloud Discovery [KB0827153] for detailed instructions.
- Request and install the CMDB CI Class Models application from the ServiceNow Store.
See CMDB CI Class Models store app for more information on the CMDB CI Class Models application.
- Request and install the Cloud Cost Management application from the ServiceNow Store.
The Cloud Cost Management application is required for discovering the license types of software in your Microsoft SQL Server deployments on AWS. See Cloud Insights application for more information on the Cloud Cost Management application.
BYOL and BYOS discovery
- Cloud provider
- Virtual machine details
- Service model type, such as IaaS or PaaS
- Host infrastructure type for IaaS, such as shared or dedicated
- License type, such as BYOL, BYOS, or License Included
- Software that is installed on the virtual machine
Resources for your discovered software are populated and stored in corresponding Configuration Management Database (CMDB) tables, including the Host [cmdb_ci_cloud_host] and Serverless Hardware [cmdb_ci_serverless_hardware] tables, on your ServiceNow instance.
- For Microsoft Windows Server and Oracle Database on AWS, Microsoft Azure, and Google Cloud Platform (GCP), the Software Asset Management application determines license types independently.
- For Microsoft SQL Server on AWS, the Software Asset Management application determines license types using billing records from the Cloud Cost Management application.
- For
- Microsoft SQL Server on Microsoft Azure and Google Cloud Platform (GCP)
- and Red Hat Enterprise Linux Server on AWS, Microsoft Azure, and Google Cloud Platform (GCP),
- For Oracle WebLogic Server on AWS and Microsoft Azure, you must specify license types manually.
For all software products except Oracle WebLogic Server, license types are applied to associated configuration items (CIs) using automatically generated key-value pairs. The key-value pairs are stored in the Key Values [cmdb_key_value] table. Each key-value pair consists of a Key in the <software-product>_License_Type_automatic format and a Value of either License Included, BYOL, or BYOS.
- AWS RDS (PaaS): The BYOL licensing model is supported on Oracle Database Standard Edition, Standard Edition One, Standard Edition 2, and Enterprise Edition. The License Included licensing model is supported on only Oracle Database Standard Edition 2.
- AWS EC2 (IaaS): Only the BYOL licensing model is supported.
- Microsoft Azure (IaaS): Only the BYOL licensing model is supported.
Software reconciliation for BYOL and BYOS license compliance
After your discovered software is marked as BYOL, BYOS, or License Included, reconciliation runs on the software that is marked as BYOL or BYOS. You can then use the resulting information to determine the software compliance across your hybrid infrastructure.
BYOL and BYOS licensing rules can differ for the same software products across different cloud providers. For example, Windows Server has different licensing rules on AWS and on Microsoft Azure. These rules must be combined with existing on-premise rules so that you can determine the complete license compliance position of each software product across your hybrid infrastructures. Microsoft offers special rights for products that are deployed on AWS vs Microsoft Azure, such as dual use rights, edition flexibility, and unlimited virtualization. For more information on licensing rules, see Licensing rules for BYOL and BYOS.
- You can view BYOL license rights for your Microsoft software products in the Microsoft publisher overview of the Software Asset Workspace. For more information on the Microsoft publisher overview, see Publisher overview for Microsoft in the Software Asset Workspace.
- You can view BYOL license rights for your Oracle software products in the Oracle publisher overview of the Software Asset Workspace. You can also view information about your Oracle Database server deployments across hybrid infrastructures, based on the agreement type, in the Oracle DB Server Deployments per Agreement report. For more information on the Oracle publisher overview, see Publisher overview for Oracle in the Software Asset Workspace. For more information on the Oracle DB Server Deployments per Agreement report, see the Oracle DB Server Deployments per Agreement report.
- You can view BYOS license rights for your RHEL software products in the Red Hat publisher overview of the Software Asset Workspace. For more information on the Red Hat publisher overview, see Publisher overview for Red Hat in the Software Asset Workspace.
Cloud-based remediation options
- Remove Unlicensed Installs - Cloud
-
The Remove Unlicensed Installs - Cloud remediation option removes all cloud installations that are unlicensed for the associated software product.
When you select the Remove Unlicensed Installs - Cloud remediation option, removal candidates that follow the regular remediation workflow are created. After the removal candidates reach the Awaiting Revocation state, you can uninstall the cloud installations from your cloud provider and then mark the removal candidates as complete.
- Optimize vCPU
-
The Optimize vCPU remediation option provides vCPU sizing optimizations based on the core count and core thread count. This remediation option is applicable only to Oracle Database Per Processor licenses on AWS RDS (PaaS). That Per Processor licensing is based on the number of vCPUs on which you install or run an Oracle database.
For more information on AWS core counts and core thread counts, see Configuring the processor for a DB instance class.