--- sourceDocument: Yokohama IT Asset Management sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/it-asset-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Asset Management ft:clusterId : - itam bundleId : - itam workflow : - Technology --- # Bring your own license or subscription to the public cloud # Bring your own license or subscription to the public cloud {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Bring your own license or subscription to the public cloud The Bring Your Own License (BYOL) and Bring Your Own Subscription (BYOS) capabilities in ServiceNow's Software Asset Management (SAM) application enable organizations to manage and determine license compliance for Microsoft, Oracle, and Red Hat Enterprise Linux (RHEL) software across hybrid infrastructures including on-premise and public cloud environments. BYOL applies to perpetual licenses, while BYOS applies to subscription-based licenses. These models help organizations optimize costs by paying only for cloud infrastructure rather than software licenses when migrating software to public clouds such as AWS, Microsoft Azure, and Google Cloud Platform (GCP). Show full answer Show less ## Supported Software and Cloud Environments * **Microsoft SQL Server and Windows Server:** All editions supported via BYOL on AWS, Azure, and GCP using IaaS models (shared and dedicated infrastructure). * **Oracle Database:** Multiple editions supported via BYOL on AWS (both IaaS and PaaS), Azure (IaaS), with specific licensing models depending on cloud provider and Oracle version. * **Oracle WebLogic Server:** Standard and Enterprise editions supported via BYOL on AWS and Azure, with license types specified manually. * **Red Hat Enterprise Linux Server:** All editions supported via BYOS on AWS, Azure, and GCP in IaaS shared infrastructure. ## Key Capabilities * Automatic discovery and identification of perpetual and subscription software licenses across hybrid environments using ServiceNow Discovery and Cloud Cost Management applications. * Determination of license types (BYOL, BYOS, or License Included) and application of license data to Configuration Management Database (CMDB) items using key-value pairs. * Support for complex licensing rules including cloud provider-specific rights such as dual use rights, edition flexibility, and unlimited virtualization. * License reconciliation to provide accurate compliance positions across hybrid clouds by combining cloud and on-premises licensing rules. * Cloud-based remediation options such as removing unlicensed cloud installations and optimizing vCPU usage for Oracle Database Per Processor licenses on AWS RDS. * Reporting capabilities including publisher overviews for Microsoft, Oracle, and Red Hat, and detailed infrastructure reports for Microsoft Windows and SQL Server deployments across clouds. * Support for using on-premise Core Infrastructure Suite (CIS) entitlements to license Windows Server installations on cloud platforms. ## Prerequisites for Implementation * Activation of the Discovery plugin and installation of Discovery and Service Mapping Patterns application to enable cloud resource discovery. * Migrating cloud discoveries from Cloud API probes to pattern-based discovery. * Installation of CMDB CI Class Models and Cloud Cost Management applications to support license discovery and cost data integration. ## Practical Benefits for ServiceNow Customers By leveraging BYOL and BYOS support, ServiceNow customers can: * Gain comprehensive visibility into license usage and compliance across hybrid cloud environments. * Optimize license costs by leveraging existing licenses in cloud deployments and avoiding unnecessary cloud license purchases. * Automate license discovery, classification, and compliance reporting for Microsoft, Oracle, and Red Hat products. * Effectively manage complex cloud licensing rules and ensure compliance through automated reconciliation workflows. * Utilize remediation workflows to address non-compliant cloud installations, supporting governance and cost control. 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. The Software Asset Management application supports BYOL for Microsoft and Oracle software products and BYOS for RHEL software products as follows:{#byol-concepts__table_dh3_w2x_cbc__entry__6} | Product | Product edition | BYOL or BYOS | Supported cloud providers | Supported service model | Supported infrastructure type Note: This column applies to Infrastructure as a Service (IaaS) models only. | |-|-|-|-|-|-| | Microsoft SQL Server | All editions | BYOL | * AWS * Microsoft Azure * Google Cloud Platform (GCP) {#byol-concepts__ul_gmb_kfx_cbc} | Infrastructure as a Service (IaaS) | Shared and dedicated | | Microsoft Windows Server | All editions | BYOL | * AWS * Microsoft Azure * Google Cloud Platform (GCP) {#byol-concepts__ul_myz_mfx_cbc} | Infrastructure as a Service (IaaS) | Shared and dedicated | | Oracle Database | * Oracle Database Standard Edition * Oracle Database Standard Edition One * Oracle Database Standard Edition 2 * Oracle Database Enterprise Edition {#byol-concepts__ul_gwr_dgx_cbc} | BYOL | * AWS * Microsoft Azure {#byol-concepts__ul_psv_5fx_cbc} | * AWS: Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) Note: In AWS, the IaaS model refers to the Amazon Elastic Computing (EC2) web service, while the PaaS model refers to the Amazon Relational Database Service (RDS). * Microsoft Azure: Infrastructure as a Service (IaaS) {#byol-concepts__ul_oqj_53x_cbc} | Shared and dedicated | | Oracle Weblogic Server | * Oracle WebLogic Server Standard Edition * Oracle WebLogic Server Enterprise Edition {#byol-concepts__ul_i5r_4x5_qpb} | BYOL | * AWS * Microsoft Azure {#byol-concepts__ul_pbc_vfx_cbc} | Infrastructure as a Service (IaaS) | Shared and dedicated | | Red Hat Enterprise Linux Server | All editions | BYOS | * AWS * Microsoft Azure * Google Cloud Platform (GCP) {#byol-concepts__ul_ltg_yrx_cbc} | Infrastructure as a Service (IaaS) | Shared | [ ] {#byol-concepts__table_dh3_w2x_cbc} BYOL and BYOS support on the Software Asset Management application help you: * 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 * Red Hat Enterprise Linux Server {#byol-concepts__ul_ey4_bxx_1bc} * 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. {#byol-concepts__ul_rql_w3n_1nb} Figure 1. Bring your own license or subscription flow ## Prerequisites {#byol-concepts__section_rfw_prc_wrb} Before you can begin determining the license compliance of software across your hybrid infrastructures, you must complete the following prerequisites: * Activate the Discovery (com.snc.discovery) plugin on your ServiceNow instance. See [Request Discovery](https://www.servicenow.com/docs/access?context=t_ActivateTheDiscoveryPlugin&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) for detailed instructions. * Request and install the Discovery and Service Mapping Patterns application from the [ServiceNow Store](https://store.servicenow.com/). See [Discovery patterns used by ITOM Visibility](https://www.servicenow.com/docs/access?context=c_MappingPatternsCustomization&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) 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\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0827153) for detailed instructions. * Request and install the CMDB CI Class Models application from the [ServiceNow Store](https://store.servicenow.com/). See [CMDB CI Class Models store app](https://www.servicenow.com/docs/access?context=cmdb-ci-class-models&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) for more information on the CMDB CI Class Models application. * Request and install the Cloud Cost Management application from the [ServiceNow Store](https://store.servicenow.com/). 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](https://www.servicenow.com/docs/r~pSu0wKv7zMxt661P~C2w "ServiceNow Cloud Cost Management application (formerly known as Cloud Insights) gives you visibility and control of your cloud usage and costs and helps you to discover all of your cloud resources, breaks down cloud spend by cost center, business service, and other entity, provides recommendations on how to reduce cloud spend, and automates repetitive cost optimization tasks.") for more information on the Cloud Cost Management application. {#byol-concepts__ul_ccm_xrc_wrb} ## BYOL and BYOS discovery {#byol-concepts__section_zvg_xnc_wrb} With BYOL and BYOS, the ServiceNow® Discovery application locates and identifies licensable software in both your on-premise and cloud environments using Discovery and Service Mapping patterns. The Discovery application uses Amazon AWS Cloud, Microsoft Azure Cloud, and Google Cloud discovery patterns to discover the following resources for software in cloud environments: * 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 {#byol-concepts__ul_hng_qbd_wrb} Note: The Amazon AWS Cloud, Microsoft Azure Cloud, and Google Cloud discovery patterns are included in the Discovery and Service Mapping Patterns store application. For more information on Amazon AWS Cloud discovery patterns, see [Amazon AWS Cloud components discovery using patterns](https://www.servicenow.com/docs/access?context=data-discovered-aws-patterns&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US). For more information on Microsoft Azure Cloud discovery patterns, see [Microsoft Azure Cloud components discovery using patterns](https://www.servicenow.com/docs/access?context=azure-cloud-discovery-patterns&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US). For more information on Google Cloud discovery patterns, see [Google Cloud Platform (GCP) resource inventory discovery](https://www.servicenow.com/docs/access?context=gcp-resource-inventory-discovery&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US) and [Google Cloud Platform (GCP) Organization discovery with Patterns](https://www.servicenow.com/docs/access?context=google-gcp-organization-discovery&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US). 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. The Software Asset Management application then determines the license types of your discovered software either independently or with the Discovery or Cloud Cost Management application. * 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), {#byol-concepts__ul_vtn_vmx_cbc}the Software Asset Management application determines license types using resources that are discovered through the Discovery application. * For Oracle WebLogic Server on AWS and Microsoft Azure, you must specify license types manually. {#byol-concepts__ul_ucm_2bk_wrb} 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. For Oracle WebLogic Server, you must specify license types manually by creating key-value pairs. The key-value pairs must have a Key of Oracle_WebLogic_Server_License_Type and a Value of either License Included or BYOL. After you create these key-value pairs, the specified license types can be applied to the associated CIs. Note: If the license type is not manually specified for a software product, the Software Asset Management application won't license the installation due to insufficient information. You can use these key-value pairs to determine whether the associated software licenses are using the BYOL, BYOS, or License Included licensing model. The BYOL and BYOS licensing models include license purchasing options such as Azure Hybrid Benefit. The License Included licensing model includes license purchasing options such as Pay As You Go (PAYG), SPOT, and On Demand. With the License Included licensing model, the cloud provider is responsible for managing licenses. Note: For Oracle Database, support for the BYOL and License Included licensing models is based on the cloud provider and Oracle Database version that you're using. * 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. {#byol-concepts__ul_fqz_w5j_spb} ## Software reconciliation for BYOL and BYOS license compliance {#byol-concepts__section_fvn_znc_wrb} 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](https://www.servicenow.com/docs/HnVeyg9Jo5aplofSQc7Bcw "View the bring your own license (BYOL) licensing rules for Microsoft and Oracle products in public cloud environments. In addition, view bring your own subscription (BYOS) licensing rules for Red Hat Enterprise Linux (RHEL) products in public cloud environments. Licensing rules can differ for virtual machines that reside on shared hosts or dedicated hosts across different cloud providers."). The Software Asset Management application automatically reconciles these rules and provides an accurate license position report that can be viewed in the License usage view of the Software Asset Workspace. * 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](https://www.servicenow.com/docs/VkeYTSf8wV4~g82qcyXbQg "View license usage information related to Microsoft in the 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](https://www.servicenow.com/docs/k2lhFKZNyw_8NhOpcpGPvQ "View license usage information related to Oracle in the 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](https://www.servicenow.com/docs/VK1WXov~wi4ASvfvlV1PpQ "You can use the Oracle DB Server Deployments per Agreement report to gain visibility into your Oracle Database server deployments across hybrid infrastructures, based on the agreement type."). * 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](https://www.servicenow.com/docs/~O_9trshNqkgqKKcNzXT_A "View license usage information related to Red Hat Enterprise Linux (RHEL) in the publisher overview for Red Hat in the Software Asset Workspace."). {#byol-concepts__ul_ckq_wz2_3bc} ## Cloud-based remediation options {#byol-concepts__section_qfr_lbk_spb} To remediate non-compliance for cloud installations, the Software Asset Management application provides the following 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.{#byol-concepts__p_cr1_v3r_b1c} For more information on AWS core counts and core thread counts, see [Configuring the processor for a DB instance class](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.DBInstanceClass.html#USER_ConfigureProcessor). * **[Microsoft Windows and SQL Server infrastructure details reports](https://www.servicenow.com/docs/H0dRlmgggwE2C_2YEACB_Q)** You can use the Microsoft Windows and SQL Server infrastructure details reports to gain visibility into the SQL Server and Windows Server deployments and infrastructure for different cloud providers including Microsoft Azure, AWS, and GCP. * **[Core infrastructure suite (CIS) support for BYOL](https://www.servicenow.com/docs/736DW8rSbL2UrsNYUuWj1w)** Use your on-premise CIS entitlements to license Windows Server installations on cloud platforms such as AWS and Microsoft Azure.