---
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 Key Vault

# Azure Key Vault 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 Key Vault pattern-based discovery

The Azure Key Vault pattern-based discovery enables ServiceNow customers to automatically detect and map Azure Key Vault resources within their cloud environment.
This capability is part of the Discovery and Service Mapping Patterns application, which helps populate both CMDB and non-CMDB tables with detailed information about Azure services.
Proper configuration and enabling of the relevant patterns are required to ensure accurate discovery.
Show full answer Show less  

## Key Features

* **Pattern Activation:** The Azure Key Vault discovery pattern is disabled by default and must be enabled. Starting with Visibility Content version 6.28.0, enabling or disabling patterns does not count as customization and patterns receive updates automatically.
* **Prerequisites:** Verification of Microsoft Azure discovery prerequisites is necessary. Guidance is provided for setting up Azure service accounts, especially for GovCloud environments requiring datacenter URLs.
* **Data Population:** The discovery process populates data in both CMDB and non-CMDB tables:
  * **Non-CMDB Table (cmdbazurekeyvaultkeyvault):** Stores detailed Azure Key Vault attributes such as kind, location, object ID, provisioning state, public network access, resource group, subscription ID, tenant ID, and links to the Cloud Resource table.
  * **CMDB Table (cmdbcicmpresource):** Captures general cloud resource information including install status, location, name, object ID, operational status, resource type (set to microsoft.keyvault/vaults), and description.
* **CI Relationships:** The pattern establishes relationships to reflect resource group containment, hosting on Azure datacenters, and references between Azure Key Vault and cloud resource CIs to provide a comprehensive service map.
* **Tag Collection:** Azure tags are collected and stored in the Key Value \[cmdbkeyvalue\] table, capturing tag names and values to support asset management and filtering.

## Practical Benefits for ServiceNow Customers

By leveraging the Azure Key Vault pattern-based discovery, customers can:

* Automatically detect and inventory Azure Key Vault resources within their cloud infrastructure.
* Ensure accurate and updated CMDB records that support IT service management, compliance, and operational visibility.
* Benefit from ongoing updates to discovery patterns without losing custom activation settings.
* Understand resource relationships and configurations through comprehensive mapping, enabling better impact analysis and change management.
* Manage resource tags effectively for improved categorization and reporting.  
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-key-vault__section_ipy_53n_jfc}

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

Enable the relevant pattern{#azure-key-vault__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://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#azure-key-vault__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud{#azure-key-vault__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://servicenow-prod.fluidtopics.net/wA59_lRoV_0PzpuODHnNjA "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-key-vault__configure-govcloud-azure-dd}
{#azure-key-vault__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-key-vault__section_aq4_qkq_hfc}

Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Key Vault - 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-key-vault__section_aq4_qkq_hfc__entry__2}

| Field | Description |
|-|-|
| Kind \[kind\] | The specific form or variant of the resource type. |
| Location \[location\] | The geographical location where the resource is hosted. |
| Object Id \[object_id\] | The unique identifier of the resource. |
| Provisioning State \[provisioning_state\] | The current provisioning status of the resource. |
| Public Network Access \[public_network_access\] | Indicates whether the resource is accessible over a public network. |
| Resource Group \[resource_group\] | Name of the resource group. |
| Subscription ID \[subscription_id\] | The subscription ID. |
| Tenant ID \[tenant_id\] | The unique identifier of the Azure Active Directory tenant to which the resource belongs. |
| Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. |
[Table 1. Azure Key Vault \[cmdb_azure_key_vault_key_vault\]]

## Data stored in CMDB tables

Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Key Vault - Extended Inventory(LP) pattern.  
{#azure-key-vault__entry__22}

| Field | Description |
|-|-|
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Location \[location\] | The geographical location where the resource is hosted. |
| Name \[name\] | The name assigned to 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.keyvault/vaults. |
| Description \[short_description\] | Description of the resource or service. |
[Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]]

## CI relationships

The pattern creates these relationships to support discovery.
{#azure-key-vault__entry__39}

| 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 Key Vault \[cmdb_azure_key_vault_key_vault\] | References | Cloud Resource \[cmdb_ci_cmp_resource\] |
[ ]

## Azure tag discovery {#azure-key-vault__section_ezc_jwt_jfc}

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

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

{#azure-key-vault__table_axq_spc_y2c}

*[\>]: and then