--- 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 Key # Azure Key Vault Key pattern-based discovery {#ariaid-title1} Release version: Australia 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 enables ServiceNow customers to discover and map Azure Key Vault Keys within their cloud environments using Discovery and Service Mapping Patterns. This discovery populates detailed information about these keys into both CMDB and non-CMDB tables, supporting comprehensive cloud resource management and visibility. Show full answer Show less ## Key Features * **Pattern Activation:** The Azure Key Vault Key discovery pattern is disabled by default and must be enabled. Activating or deactivating patterns no longer counts as customization, ensuring seamless updates with the latest predefined versions. * **REST API Permissions:** Proper Azure REST API permissions must be granted to run the discovery patterns. Customers should download the Cloud Discovery patterns spreadsheet for required permissions, pattern details, CI classes, and vendor documentation links. * **Azure Prerequisites:** Customers must meet Microsoft Azure discovery prerequisites and ensure resources are not listed in the Resource Inclusion List to avoid duplicate discoveries. * **GovCloud Support:** Discovery of Azure GovCloud (US) accounts requires configuring service accounts with datacenter-specific URLs. * **Data Population:** The discovery populates key details in the `cmdbazurekeyvaultkey` (non-CMDB) table and general cloud resource information in the `cmdbcicmpresource` (CMDB) table. * **Tag Collection:** Tags associated with Key Vault Keys are collected and stored in the `cmdbkeyvalue` table, linked to cloud resources for enhanced metadata management. * **CI Relationships and References:** The pattern creates specific relationships such as "Hosted on" Azure Datacenter and "Members" of cloud resources to maintain accurate service mapping and configuration item (CI) associations. ## Key Outcomes * **Comprehensive Discovery:** Customers gain visibility into Azure Key Vault Keys including attributes like key type, size, operations permitted, recovery level, and lifecycle dates. * **Accurate CMDB Population:** Key Vault Keys are accurately represented as configuration items in the CMDB, enabling better asset management and integration with IT service workflows. * **Improved Cloud Resource Mapping:** Relationships and references enhance understanding of how keys relate to other Azure resources and datacenters. * **Tagging and Metadata:** Captured tags provide additional context for governance, compliance, and operational purposes. * **Ongoing Pattern Updates:** Quarterly updates to discovery patterns ensure customers have access to the latest capabilities and fixes. Discovery and Service Mapping Patterns finds Azure Key Vault Keys 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-key__section_rpj_fj2_bgc} 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-key__cloud-discovery-api-ph-short-prereq} 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/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-key__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-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/aypCYVQdO8oFebLMLEI89g "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/XKQpJvxWTKNL58XCkRHVxA "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