--- sourceDocument: Zurich IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-operations-management Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Azure Key Vault Key # Azure Key Vault Key pattern-based discovery {#ariaid-title1} * Release version: Zurich * * Updated April 28, 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 Key pattern-based discovery The Azure Key Vault Key pattern-based discovery in ServiceNow enables automated detection and inventory of Azure Key Vault Keys within your cloud environment. This capability is part of the Discovery and Service Mapping Patterns application and helps populate both CMDB and non-CMDB tables with detailed key information, facilitating comprehensive cloud asset management. Show full answer Show less This pattern is disabled by default and requires activation. It supports Azure GovCloud (US) accounts by configuring the discovery schedule with the appropriate datacenter URL. To ensure successful discovery, Microsoft Azure discovery prerequisites must be met. ## Key Features * **Pattern Activation and Updates:** Starting from Visibility Content version 6.28.0, enabling or disabling discovery patterns is no longer treated as customization, allowing for seamless updates and version resets without losing activation status. * **Data Population:** The discovery process populates data into: * **Non-CMDB tables:** Specifically, the `cmdbazurekeyvaultkey` table captures detailed key attributes such as name, unique object ID, key ID, cryptographic algorithm, curve, key operations, size, status, recovery level, and lifecycle dates. * **CMDB tables:** The `cmdbcicmpresource` table records key vault keys as cloud resources, including resource type, install status, and operational status. * **CI Relationships and References:** The pattern creates relationships linking keys to Azure datacenters and other cloud resources, supporting dependency mapping and infrastructure visualization. * **Azure Tag Discovery:** Tags associated with Azure Key Vault Keys are discovered and stored in the `cmdbkeyvalue` table, enabling enhanced categorization and filtering. ## Practical Considerations for ServiceNow Customers * Ensure that Microsoft Azure discovery prerequisites are fulfilled before enabling this pattern to guarantee accurate key vault key discovery. * Activate the Azure Key Vault Key pattern to start discovering these resources; note that this pattern is disabled by default. * Configure discovery schedules properly, especially when working with Azure GovCloud environments, by using the correct datacenter URLs. * Use the populated CMDB and non-CMDB tables to gain detailed visibility into your Azure Key Vault Keys, their configurations, and operational statuses. * Leverage CI relationships and tags to understand resource dependencies and to facilitate better asset management and compliance reporting. Discovery and Service Mapping Patterns finds Azure Key Vault Keys 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-key__section_rpj_fj2_bgc} Verify the Microsoft Azure discovery prerequisites{#azure-key-vault-key__verify-azure-discovery-prerequisites-dlentry} : For more information, see the prerequisites section in [Microsoft Azure Cloud discovery using patterns](https://www.servicenow.com/docs/5NmnHdhD8h3YVHs729mwBw "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-key__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/9WxHMTzMhtdL1v_zeCDjPw "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#azure-key-vault-key__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud{#azure-key-vault-key__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/og2qLP8eLs7FT8U~fqyM6Q "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-key-vault-key__configure-govcloud-azure-dd} {#azure-key-vault-key__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-key__section_aq4_qkq_hfc} The Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Key Vault Key - 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-key__table_non_cmdb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the Key Vault Key. | | Object Id \[object_id\] | Unique identifier for the Key Vault Key, in the format of the Azure Resource Manager (ARM) resource ID followed by /keys/\. For example: /subscriptions/\/resourceGroups/\/providers/Microsoft.KeyVault/vaults/\/keys/\. | | Key ID \[key_id\] | The versioned URI of the key in Azure Key Vault. | | Key Type \[key_type\] | The cryptographic algorithm of the key. For example: RSA or EC. | | Curve \[curve\] | The elliptic curve name for EC keys. For example: P-256 or P-384. | | Key Ops \[key_ops\] | The operations permitted for the key. For example: sign,verify or sign,verify,wrapKey,unwrapKey,encrypt,decrypt. | | Key Size \[key_size\] | The size of the key in bits. | | Enabled \[enabled\] | Indicates whether the key is enabled. | | Recovery Level \[recovery_level\] | The deletion recovery level for the key. For example: Recoverable, Purgeable, or Recoverable+Purgeable. | | Created Date \[created_date\] | Date and time when the key was created. | | Updated Date \[updated_date\] | Date and time when the key was last updated. | | Expiration Date \[expiration_date\] | Date and time when the key expires. | | Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. | [Table 1. Azure Key Vault - Key \[cmdb_azure_key_vault_key\]] {#azure-key-vault-key__table_non_cmdb} ## Data stored in CMDB tables {#azure-key-vault-key__section_ggp_ql2_bgc} The Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Key Vault Key - Extended Inventory(LP) pattern. {#azure-key-vault-key__table_cmdb__entry__2} | Field | Description | |-|-| | Name \[name\] | Name of the Key Vault Key. | | Object ID \[object_id\] | Unique identifier for the Key Vault Key, in the format of the ARM resource ID followed by /keys/\. For example: /subscriptions/\/resourceGroups/\/providers/Microsoft.KeyVault/vaults/\/keys/\. | | Resource type \[resource_type\] | The Azure resource type: microsoft.keyvault/vaults/keys. | | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | | Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. | [Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]] {#azure-key-vault-key__table_cmdb} ## CI relationships {#azure-key-vault-key__section_dc4_ghc_dgc} The Azure - Key Vault Key - Extended Inventory(LP) pattern creates the following relationships and references to support Azure Key Vault Key discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table. {#azure-key-vault-key__table_relationships__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud Resource \[cmdb_ci_cmp_resource\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] | | Cloud Resource \[cmdb_ci_cmp_resource\] | Members::Member of | Cloud Resource \[cmdb_ci_cmp_resource\] | [Table 3. CI relationships] {#azure-key-vault-key__table_relationships} {#azure-key-vault-key__table_ci_references__entry__3} | CI | Field | Referenced CI | |-|-|-| | Azure Key Vault - Key \[cmdb_azure_key_vault_key\] | Configuration Item \[configuration_item\] | Cloud Resource \[cmdb_ci_cmp_resource\] | | Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | Cloud Resource \[cmdb_ci_cmp_resource\] | [Table 4. CI references] {#azure-key-vault-key__table_ci_references} ## Azure Tag discovery {#azure-key-vault-key__section_lyw_zhc_dgc} The Azure - Key Vault Key - Extended Inventory(LP) pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-key-vault-key__table_ojy_vss_5hc__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | | Configuration item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. | [Table 5. Key Value \[cmdb_key_value\]] {#azure-key-vault-key__table_ojy_vss_5hc} *[\>]: and then