Azure virtual machine pattern-based discovery

  • Release version: Xanadu
  • Updated January 29, 2026
  • 4 minutes to read
  • Summarize
    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 Azure Virtual Machine Pattern-Based Discovery

    The Azure Virtual Machine pattern-based discovery feature enables the identification and mapping of Azure virtual machines (VMs) within your cloud environment. To utilize this functionality effectively, ensure that you have the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store and verify the Microsoft Azure discovery prerequisites.

    Show full answer Show less

    Key Features

    • Data Collection: The Azure - Virtual Machine (LP) pattern gathers various data points related to VMs, including unique identifiers, power states, memory, CPU allocation, and associated disks.
    • Configuration Item Relationships: This pattern establishes relationships among various configuration items (CIs) like instances, storage volumes, and network interfaces to create a comprehensive cloud asset mapping.
    • Tag and License Discovery: The pattern collects Azure tags and identifies license types, including Bring Your Own License (BYOL) and License Included, to maintain compliance and management oversight.

    Key Outcomes

    By implementing this discovery feature, ServiceNow customers can expect to:

    • Automatically populate the Configuration Management Database (CMDB) with detailed information about Azure VMs and related resources.
    • Enhance visibility and management of cloud infrastructure through structured relationships between different components.
    • Ensure license compliance and effective resource management by tracking licensing details and associated tags.

    Discovery and Service Mapping Patterns finds Azure virtual machines (VMs) on your cloud environment. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

    Pattern-based discovery and mapping requirements

    Verify the Microsoft Azure discovery prerequisites
    For more information, see the prerequisites section in Microsoft Azure Cloud components discovery using patterns.

    Data collected by Discovery during horizontal discovery

    Discovery populates the data in the CMDB when running the Azure - Virtual Machine (LP) pattern.

    Table 1. Virtual Machine Instance [cmdb_ci_vm_instance]
    Field Description
    Name [name] Name of the virtual machine.
    Object ID [object_id] A unique identifier allocated by Azure for this virtual machine.
    VM Instance ID [vm_inst_id] The unique virtual machine identifier assigned by Azure.
    State [state] Power state of the virtual machine.

    Possible values include: On, Off, or Terminated.

    Memory (MB) [memory] Memory capacity of the virtual machine in megabytes (MB).
    CPUs [cpus] Number of virtual CPUs (vCPUs) allocated to the virtual machine.
    Disks [disks] Total number of disks attached to the virtual machine, including OS disk and data disks.
    Disk size [disks_size] Total size of all disks attached to the virtual machine in gigabytes (GB).
    Network adapters [nics] Number of network interface cards (NICs) attached to the virtual machine.
    Install Status [install_status] Install status of the resource. Default value is Installed.
    Table 2. Instance Scale Set [cmdb_ci_instance_scale_set]
    Field Description
    Object ID [object_id] A unique identifier allocated by Azure for this Virtual Machine Scale Set instance.
    Table 3. Storage Volume [cmdb_ci_storage_volume]
    Field Description
    Object ID [object_id] A unique identifier for the managed disk.
    Name [name] Name of the managed disk.
    Table 4. Block Endpoint [cmdb_ci_endpoint_block]
    Field Description
    Object ID [object_id] A unique identifier for the disk endpoint.
    Name [name] Name of the disk endpoint.
    Host [host] The virtual machine object ID to which this disk endpoint is attached.
    Table 5. Cloud Mgmt Network Interface [cmdb_ci_nic]
    Field Description
    Object ID [object_id] A unique identifier for the NIC.
    Primary [primary] Indicates whether this NIC is the primary network interface.
    Table 6. VNIC Endpoint [cmdb_ci_endpoint_vnic]
    Field Description
    Object ID [object_id] A unique identifier for the virtual network interface endpoint.
    Name [name] Name of the virtual network interface endpoint.
    Table 7. Availability Zone [cmdb_ci_availability_zone]
    Field Description
    Object ID [object_id] A unique identifier for the availability zone in the format: region-zone.
    Name [name] A unique identifier for the availability zone in the format: region-zone.
    Install Status [install_status] Install status of the resource. Default value is Installed.
    Table 8. Image [cmdb_ci_os_template] or Cloud Image [cmdb_ci_cloud_os_image]
    Field Description
    Object ID [object_id] A unique identifier for the OS image or custom image.
    Name [name] Name of the OS image or custom image.
    Provider [provider] Cloud provider. The value is set to AZURE.

    This field is only populated in the Cloud Image [cmdb_ci_cloud_os_image] table.

    Note:
    When using the Image [cmdb_ci_os_template] table to store Cloud OS Images, you may notice an unusually large number of records. To avoid this issue, you can store the discovered OS images in the Cloud Image [cmdb_ci_cloud_os_image] table. For more information, see Enable Cloud OS Image discovery.
    Table 9. Hardware Type [cmdb_ci_compute_template] or Cloud Hardware Type [cmdb_ci_cloud_hardware_type]
    Field Description
    Object ID [object_id] The VM size Stock Keeping Unit (SKU) name.
    Provider [provider] Cloud provider. The value is set to AZURE.

    This field is only populated in the Cloud Hardware Type [cmdb_ci_cloud_hardware_type] table.

    Note:
    When using the Hardware Type [cmdb_ci_compute_template] table to store the hardware types, you may notice an unusually large number of records. To avoid this issue, you can store the discovered hardware types in the Cloud Hardware Type [cmdb_ci_cloud_hardware_type] table. For more information, see Enable the Cloud Hardware Type class extension.

    CI relationships

    The Azure - Virtual Machine (LP) pattern creates these relationships to support Azure VM discovery.

    CI Relationship CI
    Virtual Machine Instance [cmdb_ci_vm_instance] Managed by::Manages Instance Scale Set [cmdb_ci_instance_scale_set]
    Virtual Machine Instance [cmdb_ci_vm_instance] Hosted on::Hosts Azure Datacenter [cmdb_ci_azure_datacenter]
    Virtual Machine Instance [cmdb_ci_vm_instance] Provisioned From::Provisioned Hardware Type [cmdb_ci_compute_template] or Cloud Hardware Type [cmdb_ci_cloud_hardware_type]
    Storage Volume [cmdb_ci_storage_volume] Hosted on::Hosts Azure Datacenter [cmdb_ci_azure_datacenter]
    Block Endpoint [cmdb_ci_endpoint_block] Implement End Point To::Implement End Point From Storage Volume [cmdb_ci_storage_volume]
    Virtual Machine Instance [cmdb_ci_vm_instance] Use End Point To::Use End Point From Block Endpoint [cmdb_ci_endpoint_block]
    Virtual Machine Instance [cmdb_ci_vm_instance] Use End Point To::Use End Point From VNIC Endpoint [cmdb_ci_endpoint_vnic]
    VNIC Endpoint [cmdb_ci_endpoint_vnic] Implement End Point To::Implement End Point From Cloud Mgmt Network Interface [cmdb_ci_nic]
    Resource Group [cmdb_ci_resource_group] Contains::Contained by Virtual Machine Instance [cmdb_ci_vm_instance]
    Virtual Machine Instance [cmdb_ci_vm_instance] Provisioned From::Provisioned Image [cmdb_ci_os_template] or Cloud Image [cmdb_ci_cloud_os_image]
    Image [cmdb_ci_os_template] or Cloud Image [cmdb_ci_cloud_os_image] Hosted on::Hosts Azure Datacenter [cmdb_ci_azure_datacenter]
    Availability Zone [cmdb_ci_availability_zone] Contains::Contained by Virtual Machine Instance [cmdb_ci_vm_instance]
    Azure Datacenter [cmdb_ci_azure_datacenter] Contains::Contained by Availability Zone [cmdb_ci_availability_zone]
    Availability Set [cmdb_ci_availability_set] Contains::Contained by Virtual Machine Instance [cmdb_ci_vm_instance]
    Key Value [cmdb_key_value] References Virtual Machine Instance [cmdb_ci_vm_instance]

    Azure Tag discovery

    The Azure - Virtual Machine (LP) pattern collects tags and populates them in the Key Value [cmdb_key_value] table.

    Table 10. Key Value [cmdb_key_value]
    Field Description
    Key [key] Tag name.
    Value [value] Tag value.
    Configuration item [configuration_item] References the Virtual Machine Instance [cmdb_ci_vm_instance] table.

    Azure BYOL discovery

    The pattern extension section discovers the following license types for Windows and Red Hat Enterprise Linux (RHEL) VMs:
    • Bring Your Own License (BYOL)
    • License included
    The pattern stores the license type and model in the Key Value [cmdb_key_value] table.
    Note:
    • For Windows VM using a custom image, Discovery populates key values only when the primary OS disk details are available.
    • For RHEL VMs, Discovery populates information only for VMs that use Marketplace images.
    Table 11. Key Value [cmdb_key_value]
    Field Description
    Key [key] The license type key, which is one of the following:
    • Windows_OS_License_Type_automatic
    • RHEL_OS_License_Type_automatic
    Value [value] The license model, which is one of the following:
    • BYOL
    • License Included
    Configuration item [configuration_item] References the Virtual Machine Instance [cmdb_ci_vm_instance] table.