---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Azure Virtual Machine Scale Sets (VMSS) Instance

# Azure
Virtual Machine Scale Sets (VMSS) Instance discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Azure Virtual Machine Scale Sets (VMSS) Instance Discovery

This documentation describes how ServiceNow's Discovery and Service Mapping Patterns application identifies Azure Virtual Machine Scale Sets (VMSS) and their instances using two key patterns:Azure - VM Scale Set (LP)andAzure VM Instance - Uniform Scale Set.
VMSS allows you to create and manage groups of load-balanced virtual machines that can scale automatically based on demand or schedules.
Show full answer Show less  
VMSS supports two orchestration modes:

* **Uniform Orchestration:** Optimized for large-scale stateless workloads with identical VM instances based on a VM profile.
* **Flexible Orchestration:** Supports high availability at scale with identical or multiple VM types, offering a unified Azure VM experience.

Discovering these resources may require updating to the latest version of the Discovery and Service Mapping Patterns app from the ServiceNow Store.

## Prerequisites and Setup

Before running discovery, verify Microsoft Azure discovery prerequisites, including correct credentials and permissions. Starting with version 1.31.0 of the patterns application, you can create Server Configuration Items (CIs) during cloud discovery without needing IP-based discovery, streamlining the process.

## Data Collected and CMDB Population

Discovery populates multiple Configuration Item (CI) tables in the CMDB with detailed attributes for VMSS and related resources:

* **Instance Scale Set \[cmdbciinstancescaleset\]:** Tracks install status, provisioning state, unique object ID, and name.
* **Virtual Machine Instance \[cmdbcivminstance\]:** Records network adapters, state (e.g., On, Off), install and operational status, disk count, and total disk size.
* **Storage Volume \[cmdbcistoragevolume\]:** Contains storage volume details including install and operational status.
* **Cloud Mgmt Network Interface \[cmdbcinic\]:** Holds network interface information with status fields.
* **VNIC Endpoint \[cmdbciendpointvnic\]:** Stores endpoint identifiers.
* **Image \[cmdbciostemplate\]:** Contains OS image data, with a note that large volumes of records can be managed better by using the **Cloud Image \[cmdbcicloudosimage\]** table instead.
* **Hardware Type \[cmdbcicomputetemplate\]:** Captures hardware type info; large record sets can be handled using the **Cloud Hardware Type \[cmdbcicloudhardwaretype\]** table.

## CI Relationships

Discovery automatically establishes key relationships between CIs to represent the Azure VMSS environment accurately. Examples include:

* Resource Group contains Instance Scale Sets.
* Instance Scale Sets hosted on Azure Datacenters.
* Instance Scale Sets consuming Load Balancer Pools.
* Virtual Machine Instances managed by Instance Scale Sets and hosted on Azure Datacenters.
* Storage Volumes and Network Interfaces linked to VM instances.
* VM Instances provisioned from Hardware Types and Images.

## Tag Discovery

Both VM Scale Set patterns collect Azure resource tags and store them as key-value pairs in the **Key Value \[cmdbkeyvalue\]** table, capturing tag names and values to support richer metadata and filtering capabilities.

## What This Enables for You

* Automated discovery and accurate CMDB population of Azure VM Scale Sets and related virtual machines, improving visibility into your cloud environment.
* Understanding of orchestration modes to align discovery with your Azure VMSS deployment type.
* Comprehensive data capture including hardware, storage, networking, and operational states to support IT operations, change management, and service mapping.
* Robust relationship modeling to reflect dependencies and infrastructure topology.
* Tag collection for enhanced categorization and filtering of discovered resources.

By leveraging these discovery patterns, ServiceNow customers can maintain up-to-date and detailed configuration data for Azure VMSS, supporting effective cloud management and operational processes.  
The Discovery and Service Mapping Patterns application uses the Azure - VM Scale Set (LP) and the Azure VM Instance - Uniform Scale Set patterns to find Azure
Virtual Machine Scale Sets (VMSS). Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
VMSS let you create and manage a group of load balanced virtual machines (VMs). The number of VM instances can automatically increase or decrease in response to demand or a defined schedule. There Uniform Orchestration modes Flexible and achieve.

* VMSS with Flexible Orchestration achieves high availability at scale with identical or multiple virtual machine types. With Flexible orchestration, Azure provides a unified experience across the Azure VM ecosystem.
* VMSS with Uniform Orchestration optimized for large-scale stateless workloads with identical instances. VMSS with Uniform orchestration use a virtual machine profile or template to scale up to desired capacity. While there is some ability to manage or customize individual virtual machine instances, Uniform uses identical VM instances.
{#AzureVMScaleSetInstance__ul_p2y_bz5_gxb}

## Request apps on the Store {#AzureVMScaleSetInstance__id_z4l_ysx_rcc}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#AzureVMScaleSetInstance__inline-send-to-store}
To learn about VMSS and their versions that you can discover, refer to [Detailed information on products discovered by ITOM Visibility](https://servicenow-prod.fluidtopics.net/AB0jKyDtjf78iS3uAPUKpg "Discovery and Service Mapping can discover a wide range of operating systems and applications.").

## Prerequisites {#AzureVMScaleSetInstance__section_w3y_xrx_dgc}

Verify the Microsoft Azure discovery prerequisites
:   For more information, see the prerequisites section in [Microsoft Azure Cloud components discovery using patterns](https://servicenow-prod.fluidtopics.net/JeDZ0tlC9eLF5fei5qSv3w "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.").

Create Server CIs during cloud discovery without running IP-based discovery
:   Starting with Discovery and Service Mapping Patterns version 1.31.0, you can create Server CIs during cloud discovery without running IP-based discovery. For more information, see [Server CI population during cloud discovery](https://servicenow-prod.fluidtopics.net/l3F5FpeIB1umNnVxXqBEHg "Cloud discovery can populate Server CIs without running IP-based discovery, reducing discovery time in large environments.").

## Data collected by Discovery during horizontal discovery {#AzureVMScaleSetInstance__section_tz5_csx_dgc}

Discovery populates the data in the CMDB when running the Azure - VM Scale Set (LP) Pattern.  
{#AzureVMScaleSetInstance__table_h3h_ssx_dgc__entry__2}

| Field | Description |
|-|-|
| Install Status \[install_status\] | Install status of the instance scale set. Default value is Installed. |
| State \[state\] | Provisioning state of the instance scale set. Possible values are Available or Terminated. |
| Object ID \[object_id\] | A unique identifier for the instance scale set. |
| Name \[name\] | Name of the instance scale set. |
[Table 1. Instance Scale Set \[cmdb_ci_instance_scale_set\]]

{#AzureVMScaleSetInstance__table_h3h_ssx_dgc}

Discovery populates the data in the CMDB when running the Azure VM Instance - Uniform Scale Set pattern.  
{#AzureVMScaleSetInstance__table_sw5_lwx_dgc__entry__2}

| Field | Description |
|-|-|
| Network adapters \[nics\] | Number of Network Interface Cards (NICs) attached to the virtual machine (VM) instance. |
| State \[state\] | Current state of the instance. For example: On, Off, or Terminated. |
| Install Status \[install_status\] | Install status of the instance. Default value is Installed. |
| Operational status \[operational_status\] | Operational status of the instance. Default value is Operational. |
| Disks \[disks\] | Number of disks attached to the instance. |
| Disks size (GB) \[disk_size\] | Total storage capacity of all disks attached to the VM, in gigabytes (GB). |
[Table 2. Virtual Machine Instance \[cmdb_ci_vm_instance\]]

{#AzureVMScaleSetInstance__table_sw5_lwx_dgc}  
{#AzureVMScaleSetInstance__table_iks_hxx_dgc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name or ID for the storage volume. |
| Object ID \[object_id\] | A unique identifier, allocated by Microsoft Azure for this resource. |
| Install Status \[install_status\] | Install status of the storage volume. Default value is Installed. |
| Operational status \[operational_status\] | Operational status of the storage volume. Default value is Operational. |
[Table 3. Storage Volume \[cmdb_ci_storage_volume\]]

{#AzureVMScaleSetInstance__table_iks_hxx_dgc}  
{#AzureVMScaleSetInstance__table_vbt_4xx_dgc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name or ID for the network interface. |
| Object ID \[object_id\] | A unique identifier, allocated by Microsoft Azure for this resource. |
| Install Status \[install_status\] | Install status of the network interface. Default status is Installed. |
| Operational status \[operational_status\] | Operational status of the network interface. Default status is Operational. |
[Table 4. Cloud Mgmt Network Interface \[cmdb_ci_nic\]]

{#AzureVMScaleSetInstance__table_vbt_4xx_dgc}  
{#AzureVMScaleSetInstance__table_spv_5xx_dgc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name or ID for the endpoint. |
| Object ID \[object_id\] | A unique identifier, allocated by Microsoft Azure for this resource. |
[Table 5. VNIC Endpoint \[cmdb_ci_endpoint_vnic\]]

{#AzureVMScaleSetInstance__table_spv_5xx_dgc}  
{#AzureVMScaleSetInstance__table_hqw_gyx_dgc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name or ID for the image. |
| Object ID \[object_id\] | A unique identifier, allocated by Microsoft Azure for this resource. |
| Install Status \[install_status\] | Install status of the image. Default value is Installed. |
| Operational status \[operational_status\] | Operational status of the image. Default value is operational. |
[Table 6. Image \[cmdb_ci_os_template\]]

{#AzureVMScaleSetInstance__table_hqw_gyx_dgc}  
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](https://servicenow-prod.fluidtopics.net/iAsiMpLCnd7i_iXAf0iYGw "Enable the Cloud OS Image [cmdb_ci_cloud_os_image] table to store the cloud OS image records for Amazon AWS Cloud, Microsoft Azure Cloud, Google Cloud Platform (GCP), Oracle Cloud Infrastructure (OCI), and IBM Cloud.").  
{#AzureVMScaleSetInstance__table_ktg_bzx_dgc__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the hardware type. |
[Table 7. Hardware Type \[cmdb_ci_compute_template\]]

{#AzureVMScaleSetInstance__table_ktg_bzx_dgc}  
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](https://servicenow-prod.fluidtopics.net/KNU5OxYrIVSiFCfHbBF~6A "Enable the Cloud Hardware Type [cmdb_ci_cloud_hardware_type] table to store the predefined virtual machine (VM) hardware type records for Amazon AWS Cloud Microsoft Azure Cloud and Google Cloud Platform (GCP). This class extension helps prevent duplication of the VM hardware type records in the Hardware Type [cmdb_ci_compute_template] table, which improves performance for Discovery and related flows.").

## CI relationships {#AzureVMScaleSetInstance__section_hg4_zsx_dgc}

Discovery creates these relationships to support the VMSS discovery, when running the Azure - VM Scale Set (LP) pattern.  
{#AzureVMScaleSetInstance__table_xhq_2tx_dgc__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Instance Scale Set \[cmdb_ci_instance_scale_set\] |
| Instance Scale Set \[cmdb_ci_instance_scale_set\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| Instance Scale Set \[cmdb_ci_instance_scale_set\] | Consumes::Consumed by | Load Balancer Pool \[cmdb_ci_lb_pool\] |
[ ]

{#AzureVMScaleSetInstance__table_xhq_2tx_dgc}

Discovery creates these relationships to support the VMSS discovery, when running the when running the Azure - VM Scale Set (LP) pattern.  
{#AzureVMScaleSetInstance__table_r4x_szx_dgc__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | Managed by::Manages | Instance Scale Set \[cmdb_ci_instance_scale_set\] |
| 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\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| Hardware Type \[cmdb_ci_compute_template\] | 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\] |
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | Provisioned From::Provisioned | Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] |
| Cloud Mgmt Network Interface \[cmdb_ci_nic\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | Implement End Point To::Implement End Point From | Cloud Mgmt Network Interface \[cmdb_ci_nic\] |
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | Use End Point To::Use End Point From | VNIC Endpoint \[cmdb_ci_endpoint_vnic\] |
| Virtual Machine Instance \[cmdb_ci_vm_instance\] | Provisioned From::Provisioned | Image \[cmdb_ci_os_template\] |
| Image \[cmdb_ci_os_template\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
[ ]

{#AzureVMScaleSetInstance__table_r4x_szx_dgc}

## Tags discovery {#AzureVMScaleSetInstance__section_abn_133_y2c}

Both the Azure - VM Scale Set (LP) and the Azure VM Instance - Uniform Scale Set patterns collect tags and populate them in the Key Value \[cmdb_key_value\] table.{#AzureVMScaleSetInstance__table_axq_spc_y2c__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | Tag name. |
| Value \[value\] | Tag value. |
[Table 8. Key Value \[cmdb_key_value\]]

{#AzureVMScaleSetInstance__table_axq_spc_y2c}