--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/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 Compute Snapshot # Azure Compute Snapshot pattern-based discovery {#ariaid-title1} * Release version: Yokohama * * Updated August 11, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Compute Snapshot pattern-based discovery The Azure Compute Snapshot pattern-based discovery in ServiceNow enables automated identification and data collection of Azure compute snapshot resources within your cloud environment. This discovery uses pattern-based methods within the Discovery and Service Mapping Patterns application to populate both CMDB and non-CMDB tables with detailed resource information, helping maintain an accurate and up-to-date asset inventory. Show full answer Show less ## Key Features * **Pattern Activation:** The Azure Compute Snapshot pattern is disabled by default and requires manual activation. Starting with Visibility Content version 6.28.0, enabling or disabling patterns no longer counts as customization, and patterns reset to the latest predefined version after upgrades while preserving activation status. * **Azure GovCloud Support:** For discovering Azure GovCloud (US) accounts, configure the discovery schedule using appropriate datacenter URLs and set up Azure service accounts accordingly. * **Data Storage:** Discovery populates data into both CMDB and non-CMDB tables: * **Non-CMDB table \[cmdbazurecomputesnapshot\]:** Stores details like disk state, encryption type, geographic location, network access policy, OS type, provisioning state, resource group, SKU tier, subscription and tenant IDs, and resource type. * **CMDB table \[cmdbcistoragevolsnapshot\]:** Contains storage volume snapshot details including capacity, install and operational status, location, name, unique object IDs, and disk state. * **CI Relationships:** The pattern automatically establishes relationships among configuration items, such as resource groups containing snapshots, snapshots hosted on Azure datacenters, and references between compute snapshots and storage volume snapshots. * **Tag Collection:** Azure resource tags are discovered and stored in the Key Value \[cmdbkeyvalue\] table, enabling tag-based categorization and reporting. ## Practical Benefits By implementing this pattern-based discovery, ServiceNow customers gain: * Automated, accurate visibility of Azure compute snapshots and their associated storage volumes. * Enhanced CMDB accuracy with detailed metadata and relationships, facilitating better asset management and impact analysis. * Support for Azure GovCloud environments, ensuring compliance and coverage of specialized cloud regions. * Consistent updates and management of discovery patterns aligned with ServiceNow upgrades without losing configuration states. 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 {#azure-compute-snapshot__section_ipy_53n_jfc} Verify the Microsoft Azure discovery prerequisites{#azure-compute-snapshot__verify-azure-discovery-prerequisites-dlentry} : For more information, see the prerequisites section in [Microsoft Azure Cloud components discovery using patterns](https://www.servicenow.com/docs/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."). Enable the relevant pattern{#azure-compute-snapshot__enable-pattern-reuse-dlentry} : 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](https://www.servicenow.com/docs/R5W5GP640V_5uNIhVNRPCw "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#azure-compute-snapshot__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud{#azure-compute-snapshot__configure-govcloud-azure-dlentry} : 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](https://www.servicenow.com/docs/wA59_lRoV_0PzpuODHnNjA "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-compute-snapshot__configure-govcloud-azure-dd} {#azure-compute-snapshot__configure-govcloud-azure-dd} Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables. ## Data stored in non-CMDB tables {#azure-compute-snapshot__section_aq4_qkq_hfc} 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 AllConfigurationAzure. You can also search the navigation filter for the specific pattern name. {#azure-compute-snapshot__section_aq4_qkq_hfc__entry__2} | 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. | [Table 1. Azure Compute - Snapshot \[cmdb_azure_compute_snapshot\]] ## 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. {#azure-compute-snapshot__entry__32} | 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. | [Table 2. Storage Volume Snapshot \[cmdb_ci_storage_vol_snapshot\]] ## CI relationships The pattern creates these relationships to support discovery. {#azure-compute-snapshot__entry__49} | 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 {#azure-compute-snapshot__section_ezc_jwt_jfc} The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-compute-snapshot__table_axq_spc_y2c__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | [Table 3. Key Value \[cmdb_key_value\]] {#azure-compute-snapshot__table_axq_spc_y2c} *[\>]: and then