--- title: Sample payload for BYOL description: A sample payload that populates the Software Installation \[cmdb\_sam\_sw\_install\] table in the ServiceNow instance with discovery data collected by the BYOL licensing model. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-asset-management/software-asset-management/sample-payload-byol.html release: australia product: Software Asset Management classification: software-asset-management topic_type: reference last_updated: "2026-03-12" reading_time_minutes: 4 breadcrumb: [Reference, Software Asset Management, IT Asset Management, Asset Management] --- # Sample payload for BYOL A sample payload that populates the Software Installation \[cmdb\_sam\_sw\_install\] table in the ServiceNow instance with discovery data collected by the BYOL licensing model. Certain entities need to be populated for BYOL to work with software asset connection as a third party discovery source. The relationship between these entities is crucial for BYOL to work smoothly with software asset connections. For example, some values required for populating Cloud Hosts is different for AWS and Azure. Though the object ID and the name of the host is required for both AWS and Azure, for AWS, the CPU core count is required and for Azure, the host type value is required. For details on entities and their relationships, refer to [Entities for BYOL](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/sample-payload-byol.md) and [Relationships between the entities for BYOL](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/sample-payload-byol.md). In this example, Cloud Service Account is the topmost entity. All the other entities listed in the Entities for BYOL table are dependent entities of Cloud Service Account. If an entity is marked as a dependent entity, then the parent entity and the relationship between that entity and it's parent needs to be mentioned in the same payload. For example, if you want to create an AWS data center on Cloud Service Account, you need to include the Cloud Service Account entity in the same payload; even if Cloud Service Account already exists in your instance. Similarly, when you create software installations, you need to include all the dependent entities for software installations all through the hierarchy in the same payload. ## Entities for BYOL
| Entities | Required fields |
|---|---|
| Cloud Service Account \[cmdb\_ci\_cloud\_service\_account\] | account\_id – Unique identifier |
| AWS Datacenters \[cmdb\_ci\_aws\_datacenter\] | object\_id – Unique identifier |
| Azure Datacenters \[cmdb\_ci\_azure\_datacenter\] | object\_id – Unique identifier |
| Cloud Hosts \[cmdb\_ci\_cloud\_host\] **Note:** Not needed for shared VMs. | - object\_id – Unique identifier - name - name of the host - host\_type - host type for Azure. For example, DSv3-Type1 \(for Azure hosts only\). - cpu\_core-count - Total CPU core count of the host \(for AWS hosts only\). |
| Virtual Machine Instances \[cmdb\_ci\_vm\_instance\] | object\_id – Unique identifier |
| Computers \[cmdb\_ci\_computer\] | - name - name of the virtual machine - cpu\_count - CPU count of the virtual machine - cpu\_core\_count - CPU core count of the virtual machine - cpu\_core\_thread - CPU core thread count of the virtual machine - virtual – indicates if the computer is a VM \(always set to true\) |
| Software Installations \[cmdb\_sam\_sw\_install\] **Note:** Software Installations \[cmdb\_sam\_sw\_install\] is a related entry for Computers \[cmdb\_ci\_computer\] | - publisher - version - display\_name - cloud\_license\_type - license type of the cloud install \(BYOL or License Included\) - cloud\_license\_type\_source - source from where cloud license type gets populated. The value is set to third\_party\_integration for Software asset connections. |