---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia 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: Australia  
Updated March 12, 2026  
![](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

The Discovery and Service Mapping Patterns application in ServiceNow enables automated discovery of 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 allow dynamic scaling of load-balanced virtual machines in Azure, supporting both Uniform and Flexible orchestration modes for different workload types.
To utilize these discovery capabilities fully, customers may need to update to the latest version of the Discovery and Service Mapping Patterns app from the ServiceNow Store.
Show full answer Show less  

## Key Features

* **Discovery Patterns:** Support for discovering VMSS resources including instances, storage volumes, network interfaces, endpoints, OS images, and hardware types.
* **Support for Orchestration Modes:** Discovery accommodates both Uniform orchestration (identical VM instances for stateless workloads) and Flexible orchestration (multiple VM types with high availability).
* **CMDB Population:** Key Azure VMSS components are mapped to specific Configuration Item (CI) tables such as *Instance Scale Set* , *Virtual Machine Instance* , *Storage Volume* , *Cloud Mgmt Network Interface* , *VNIC Endpoint* , *Image* , and *Hardware Type*.
* **CI Relationships:** Discovery automatically creates relationships between CIs to represent resource group containment, hosting, management, provisioning, and endpoint connections, facilitating accurate service mapping and impact analysis.
* **Tag Collection:** Both discovery patterns collect Azure resource tags and store them in the *Key Value* table, enabling enhanced filtering and reporting.
* **Improved Server CI Creation:** From version 1.31.0 onwards, Server CIs can be created during cloud discovery without requiring IP-based discovery, streamlining CI population.

## Practical Considerations for ServiceNow Customers

* **Prerequisites:** Ensure Microsoft Azure discovery prerequisites are met according to the ServiceNow documentation on Azure Cloud discovery using patterns.
* **Data Accuracy:** Discovery captures detailed fields such as install status, provisioning state, operational status, disk size, NIC count, and unique Azure object IDs to maintain accurate and complete CMDB records.
* **Handling Large Data Sets:** To avoid excessive records for OS images and hardware types, consider enabling Cloud OS Image and Cloud Hardware Type class extensions for optimized storage.
* **Version Updates:** Regularly update the Discovery and Service Mapping Patterns app to leverage the latest improvements and support for new Azure VMSS features.

## Expected Outcomes

* Comprehensive and automated discovery of Azure VM Scale Sets and their instances within the CMDB.
* Accurate modeling of VMSS resources and their relationships to support effective service mapping and operational visibility.
* Enhanced ability to track scaling behavior and resource utilization of VMSS environments in Azure.
* Streamlined cloud infrastructure management through up-to-date configuration data and tag information.  
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 might 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) 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://www.servicenow.com/docs/mNB7NqS~kRULRDp~CJup5g "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 discovery using patterns](https://www.servicenow.com/docs/e2521~KHAw8EO7j1nC9QMA "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources might 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://www.servicenow.com/docs/DnhIkU5n0wxBSzI8Km1BBQ "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://www.servicenow.com/docs/AM9L2gpoJH8rga6KPXl_5g "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://www.servicenow.com/docs/FYZ59iLYyJYVuQbHJF8iXQ "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}