---
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 Disk Encryption Set

# Azure Disk Encryption Set pattern-based discovery {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Disk Encryption Set pattern-based discovery

The Azure Disk Encryption Set pattern-based discovery enables ServiceNow customers to detect and map Azure Disk Encryption Set resources within their cloud environments.
This discovery process integrates with the Discovery and Service Mapping Patterns application, populating both CMDB and non-CMDB tables with detailed information about these Azure resources.
Show full answer Show less  

## Key Features

* **Pattern Activation:** The Azure Disk Encryption Set pattern is disabled by default and must be enabled to start discovery. With Visibility Content version 6.28.0 and later, enabling or disabling patterns does not count as customizations and patterns receive automatic updates.
* **Permissions and Prerequisites:** Proper REST API permissions are required to run the discovery patterns. Customers should download the Cloud Discovery patterns spreadsheet for guidance on necessary permissions and pattern details. Microsoft Azure discovery prerequisites must also be met.
* **Resource Management:** To avoid duplicate discoveries, ensure that Azure Disk Encryption Set resources are not listed in the Resource Inclusion List table.
* **GovCloud Support:** When discovering Azure GovCloud (US) accounts, configuring the Azure service account with the appropriate datacenter URL is necessary.
* **Data Population:** Discovery populates detailed Azure Disk Encryption Set information in non-CMDB tables (e.g., encryption type, identity type, key URL, provisioning state) and in CMDB tables (e.g., install status, operational status, resource type).
* **CI Relationships:** The discovery pattern establishes relationships between Azure Disk Encryption Sets, resource groups, cloud resources, and Azure datacenters to provide comprehensive mapping.
* **Tag Collection:** Azure tags associated with Disk Encryption Sets are discovered and stored in the Key Value table for easier asset categorization and management.

## What Customers Can Expect

* Accurate discovery and inventory of Azure Disk Encryption Sets, enabling better visibility and management within the ServiceNow CMDB.
* Automated updates to the discovery patterns ensuring the latest Azure features and resources are supported without additional customization overhead.
* Comprehensive data collection including encryption details, location, provisioning state, and resource relationships to support effective cloud governance and security compliance.
* The ability to avoid duplicate data by managing resource inclusion lists and following best practices for pattern activation.
* Support for Azure GovCloud environments via appropriate service account configuration.  
Discovery and Service Mapping Patterns finds Azure services on your cloud environment. Discovering some of these resources might 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-disk-encryption-set__section_ipy_53n_jfc}

Verify the REST API permissions
:   Download the [Cloud Discovery patterns spreadsheet](https://downloads.docs.servicenow.com/resource/enus/api/servicenow-discovery-patterns-api-details.xlsx) so you can grant user permissions required for running the Discovery patterns. In addition to permissions, the spreadsheet also includes useful information such as pattern names, types, CI Classes, and links to vendor documentation. New patterns are available quarterly, so check periodically to be sure you have the latest version of the spreadsheet.{#azure-disk-encryption-set__cloud-discovery-api-ph-short-prereq}

Verify the Microsoft Azure discovery prerequisites{#azure-disk-encryption-set__verify-azure-discovery-prerequisites-dlentry}
:   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.").

Remove resources from the Resource Inclusion List table{#azure-disk-encryption-set__remove-resource-inclusion-list-azure}
:   Verify that the relevant resource isn't listed in the Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table to avoid duplicate discovery. For more information on removing resources from the Resource
    Inclusion List, see [Microsoft Azure resource inventory discovery](https://www.servicenow.com/docs/tO3nNqXv4zOe7q99krvAnA "The ServiceNow Discovery application uses the Azure Resource Inventory (LP) pattern to find resources available through Azure that don’t have a dedicated pattern. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.").

Enable the relevant pattern{#azure-disk-encryption-set__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/aypCYVQdO8oFebLMLEI89g "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#azure-disk-encryption-set__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud{#azure-disk-encryption-set__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/XKQpJvxWTKNL58XCkRHVxA "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-disk-encryption-set__configure-govcloud-azure-dd}
{#azure-disk-encryption-set__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-disk-encryption-set__section_aq4_qkq_hfc}

Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Disk Encryption Set - 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-disk-encryption-set__section_aq4_qkq_hfc__entry__2}

| Field | Description |
|-|-|
| Encryption Type \[encryption_type\] | The method used to encrypt the resource data. |
| Identity type \[identity_type\] | The classification of the identity assigned to the resource. For example: SystemAssigned or UserAssigned. |
| Key Url \[key_url\] | The URL where the encryption key is stored or accessible. |
| Location \[location\] | The geographic region where the resource is deployed. |
| Object Id \[object_id\] | The unique identifier of the resource. |
| Provisioning State \[provisioning_state\] | The current status of the resource provisioning process. |
| Resource Group \[resource_group\] | Name of the resource group. |
| Tenant Id \[tenant_id\] | The identifier for the tenant that owns the resource. |
| Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. |
[Table 1. Azure Disk Encryption Set \[cmdb_azure_disk_encryption_set_disk_encryption_set\]]

## Data stored in CMDB tables

Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Disk Encryption Set - Extended Inventory(LP) pattern.  
{#azure-disk-encryption-set__entry__22}

| Field | Description |
|-|-|
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Location \[location\] | The geographic region where the resource is deployed. |
| Name \[name\] | The name of the resource. |
| Object ID \[object_id\] | The unique identifier of the resource. |
| Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. |
| Resource type \[resource_type\] | Type of resource. The value is set to microsoft.compute/diskencryptionsets. |
[Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]]

## CI relationships

The pattern creates these relationships to support discovery.
{#azure-disk-encryption-set__entry__37}

| CI | Relationship | CI |
|-|-|-|
| Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud Resource \[cmdb_ci_cmp_resource\] |
| Cloud Resource \[cmdb_ci_cmp_resource\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| Azure Disk Encryption Set \[cmdb_azure_disk_encryption_set_disk_encryption_set\] | References | Cloud Resource \[cmdb_ci_cmp_resource\] |
[ ]

## Azure tag discovery {#azure-disk-encryption-set__section_ezc_jwt_jfc}

The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-disk-encryption-set__table_axq_spc_y2c__entry__2}

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

{#azure-disk-encryption-set__table_axq_spc_y2c}

*[\>]: and then