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

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

Azure Key Vault pattern-based discovery in ServiceNow enables automated identification and mapping of Azure Key Vault resources within your cloud environment using Discovery and Service Mapping Patterns.
This functionality helps maintain an accurate and up-to-date Configuration Management Database (CMDB) by discovering resources, their configurations, and relationships.
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, pattern activation changes are preserved across upgrades without being treated as customizations.
* **Permissions and Prerequisites:** Proper REST API permissions must be granted following guidelines in the Cloud Discovery patterns spreadsheet, which is regularly updated with new patterns and relevant details. Also, Microsoft Azure discovery prerequisites must be met.
* **Resource Inclusion List Management:** To avoid duplicate discovery, ensure Azure Key Vault resources are not listed in the Resource Inclusion List table.
* **GovCloud Support:** Discovery of Azure GovCloud (US) accounts requires configuring Azure service accounts with the appropriate datacenter URL.
* **Data Population:** The discovery pattern populates both CMDB and non-CMDB tables. Non-CMDB Azure tables can be accessed for extended inventory details.
* **Tag Collection:** Azure Key Vault tags are collected and stored in the Key Value table, allowing tag-based identification and management.

## Key Outcomes

* **Comprehensive Resource Data:** Key Vault resource details such as kind, location, object ID, provisioning state, public network access, resource group, subscription ID, and tenant ID are captured in a dedicated Azure Key Vault table.
* **CMDB Integration:** Discovered Key Vaults are represented as cloud resources in the CMDB with fields including install status, operational status, resource type, and descriptive information.
* **CI Relationships:** The pattern establishes critical relationships between Key Vaults, resource groups, cloud resources, and Azure datacenters, facilitating accurate service mapping and impact analysis.  
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-key-vault__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-key-vault__cloud-discovery-api-ph-short-prereq}

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 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-key-vault__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-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://www.servicenow.com/docs/aypCYVQdO8oFebLMLEI89g "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://www.servicenow.com/docs/XKQpJvxWTKNL58XCkRHVxA "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