Azure Compute Snapshot pattern-based discovery

  • Release version: Yokohama
  • Updated June 16, 2026
  • 2 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 Compute Snapshot pattern-based discovery

    The Azure Compute Snapshot pattern-based discovery uses ServiceNow Discovery and Service Mapping Patterns to identify and collect information about Azure compute snapshots within your cloud environment. This enables you to maintain an accurate and detailed Configuration Management Database (CMDB) with data about your Azure resources, supporting effective cloud resource management and operational insight.

    Show full answer Show less

    To fully leverage this discovery, you need to ensure prerequisites for Microsoft Azure discovery are met, including proper setup of Azure service accounts, especially when working with Azure GovCloud (US).

    Key Features

    • Pattern Activation: The Azure Compute Snapshot pattern is disabled by default. Starting with Visibility Content version 6.28.0, enabling or disabling a pattern is no longer treated as a customization and will receive updates automatically after upgrades.
    • Discovery Scope: The pattern populates data into both CMDB and non-CMDB tables, capturing a comprehensive set of attributes for Azure compute snapshots and related storage volume snapshots.
    • Non-CMDB Data: Fields such as disk state, encryption type, geographic location, network access policy, OS type, provisioning state, public network access, resource group, SKU tier, subscription ID, tenant ID, and resource type are collected and stored in the cmdbazurecomputesnapshot table.
    • CMDB Data: The cmdbcistoragevolsnapshot table stores key snapshot details including capacity, install status, location, name, object identifier, operational status, and state.
    • CI Relationships: The discovery establishes relationships between Azure compute snapshots, storage volume snapshots, resource groups, and Azure datacenters to reflect accurate resource dependencies and hosting information.
    • Tag Discovery: Azure tags associated with snapshots are collected and stored in the cmdbkeyvalue table, enabling enhanced categorization and filtering of resources.

    Practical Considerations for ServiceNow Customers

    • Verify and configure Azure discovery prerequisites to ensure successful pattern execution.
    • Enable the Azure Compute Snapshot pattern to start collecting snapshot inventory data.
    • Configure discovery schedules appropriately for Azure GovCloud environments, using the correct datacenter URLs.
    • Leverage the populated CMDB and non-CMDB tables to improve visibility into Azure compute snapshots, their configurations, and relationships.
    • Use the collected tag data to enhance reporting, automation, and resource management within your ServiceNow environment.

    Discovery and Service Mapping Patterns finds Azure services 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.
    Enable the relevant pattern
    The pattern for this service is disabled by default. Starting with Visibility Content version 6.28.0, activating or deactivating a pattern won't be considered a customization, and it will continue to receive updates. Patterns that were previously activated or deactivated will reset to the latest predefined version after upgrading while retaining the last active field value. For more information on enabling patterns, see Activate a disabled pattern.
    Configure the Discovery schedule to support GovCloud
    Discovering Azure GovCloud (US) accounts requires using a datacenter URL when setting up an Azure service account. For more information, see Set up Azure service accounts.

    Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables.

    Data stored in non-CMDB tables

    Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Compute Snapshot - Extended Inventory(LP) pattern.

    You can review the non-CMDB Azure tables by navigating to All > Configuration > Azure. You can also search the navigation filter for the specific pattern name.

    Table 1. Azure Compute - Snapshot [cmdb_azure_compute_snapshot]
    Field Description
    Disk State [disk_state] The current state of the disk. For example: Attached or Unattached.
    Encryption Type [encryption_type] The encryption mechanism applied to the resource data. For example: EncryptionAtRestWithCustomerKey or EncryptionAtRestWithPlatformKey.
    DC Location [location] The geographic location where the resource is deployed.
    Network Access Policy [network_access_policy] The policy that governs network access to the resource.
    Object Id [object_id] A unique identifier for the queried resource.
    OS Type [os_type] The type of operating system associated with the resource.
    Provisioning State [provisioning_state] Current provisioning state of the resource. For example: Succeeded or Failed.
    Public Network Access [public_network_access] Indicates whether the resource can be accessed via the public network.
    Resource Group [resource_group] Name of the resource group.
    SKU Tier [sku_tier] The tier of the stock keeping unit (SKU) that determines resource performance and costs.
    Subscription Id [subscription_id] The subscription ID.
    Tenant Id [tenant_id] The unique identifier of the tenant owning the resource.
    Type [type] The type or category of the resource.
    Configuration Item [configuration_item] References the Storage Volume Snapshot [cmdb_ci_storage_vol_snapshot] table.

    Data stored in CMDB tables

    Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Compute Snapshot - Extended Inventory(LP) pattern.

    Table 2. Storage Volume Snapshot [cmdb_ci_storage_vol_snapshot]
    Field Description
    Capacity [capacity] The size of the disk in terms of storage capacity.
    Install Status [install_status] Install status of the resource. Default value is Installed.
    Location [location] The geographic location where the resource is deployed.
    Name [name] The name of the resource.
    Object ID [object_id] A unique identifier for the queried resource in the following format: /subscriptions/{subscriptionId}/resourceGroups/{resouceGroupName}/providers/Microsoft.Compute/snapshots/{snapshotName}.
    Operational status [operational_status] Operational status of the resource. Default value is Operational.
    State [state] The current state of the disk. For example: Attached or Unattached.

    CI relationships

    The pattern creates these relationships to support discovery.

    CI Relationship CI
    Resource Group [cmdb_ci_resource_group] Contains::Contained by Storage Volume Snapshot [cmdb_ci_storage_vol_snapshot]
    Storage Volume Snapshot [cmdb_ci_storage_vol_snapshot] Hosted on::Hosts Azure Datacenter [cmdb_ci_azure_datacenter]
    Azure Compute - Snapshot [cmdb_azure_compute_snapshot] References Storage Volume Snapshot [cmdb_ci_storage_vol_snapshot]

    Azure tag discovery

    The pattern collects tags and populates them in the Key Value [cmdb_key_value] table.
    Table 3. Key Value [cmdb_key_value]
    Field Description
    Key [key] Tag name.
    Value [value] Tag value.