--- 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 App Configuration Store # Azure App Configuration store 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 App Configuration store pattern-based discovery The Azure App Configuration store pattern-based discovery enables ServiceNow customers to identify and map Azure App Configuration stores within their cloud environment. This functionality is part of the Discovery and Service Mapping Patterns application and requires proper configuration and permissions to operate effectively. It helps populate accurate data in both the Configuration Management Database (CMDB) and related non-CMDB tables, supporting comprehensive cloud resource management. Show full answer Show less ## Key Features * **Pattern Activation:** The Azure App Configuration store pattern is disabled by default and must be enabled to function. Starting with Visibility Content version 6.28.0, pattern activation changes are preserved through updates. * **Permissions and Prerequisites:** Proper REST API permissions must be granted, as detailed in the Cloud Discovery patterns spreadsheet, which also provides pattern-specific information and vendor documentation links. Additionally, Azure discovery prerequisites must be met. * **Resource Inclusion List Management:** To avoid duplicate discoveries, relevant Azure resources should not be listed in the Resource Inclusion List \[sacloudinventoryresourcewhitelist\] table. * **Support for Azure GovCloud:** Discovery of Azure GovCloud (US) accounts requires configuring the Azure service account with the appropriate datacenter URL. * **Data Population:** The pattern populates data into: * **Non-CMDB Tables:** For extended inventory details such as authentication mode, endpoint URL, Key Vault properties, provisioning state, SKU, and tenant information. * **CMDB Tables:** For core cloud resource information including install status, operational status, location, resource type, and unique identifiers. * **CI Relationships:** The pattern establishes relationships among configuration items, such as grouping resources under resource groups and associating them with Azure datacenters. * **Tag Discovery:** Azure tags are collected and stored in the Key Value \[cmdbkeyvalue\] table, capturing tag names and values for enhanced resource categorization. ## Practical Impact for ServiceNow Customers By leveraging this pattern-based discovery, customers can: * Gain automated visibility into Azure App Configuration stores within their cloud infrastructure. * Ensure accurate and up-to-date inventory data is maintained in the CMDB and related tables, supporting better cloud resource management and governance. * Integrate Azure-specific resource attributes and tags into ServiceNow, enabling more granular reporting and operational insights. * Prevent duplicate discovery by managing resource inclusion lists properly. * Support discovery in regulated or specialized Azure environments such as GovCloud by configuring service accounts accordingly. 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-app-configuration-store__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-app-configuration-store__cloud-discovery-api-ph-short-prereq} Verify the Microsoft Azure discovery prerequisites{#azure-app-configuration-store__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-app-configuration-store__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-app-configuration-store__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-app-configuration-store__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud{#azure-app-configuration-store__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-app-configuration-store__configure-govcloud-azure-dd} {#azure-app-configuration-store__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-app-configuration-store__section_aq4_qkq_hfc} The Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - App Configuration Configuration Store - 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-app-configuration-store__section_aq4_qkq_hfc__entry__2} | Field | Description | |-|-| | Authentication Mode \[authentication_mode\] | The method or strategy used for authenticating access. | | Disable Local Auth \[disable_local_auth\] | Indicates whether local authentication methods are disabled. | | Enable Purge Protection \[enable_purge_protection\] | Indicates if purge protection is enabled for the resource. | | Endpoint \[endpoint\] | The URL endpoint through which the service is accessed. | | Key Vault Properties \[key_vault_properties\] | Properties related to the configuration of Key Vault services. | | Location \[location\] | The Azure region where the resource is deployed. | | Object Id \[object_id\] | The unique identifier of the resource. | | Private Link Delegation \[private_link_delegation\] | Configurations related to the delegation of private links. | | Provisioning State \[provisioning_state\] | The current state of the resource provisioning process. | | Resource Group \[resource_group\] | Name of the resource group. | | SKU Name \[sku_name\] | The stock keeping unit (SKU) representing the pricing tier of the resource. | | Subscription ID \[subscription_id\] | The subscription ID. | | Tenant ID \[tenant_id\] | The unique identifier of the Azure Active Directory tenant. | | Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. | [Table 1. Azure App Configuration - Configuration Store \[cmdb_azure_app_configuration_configuration_store\]] ## Data stored in CMDB tables The Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - App Configuration Configuration Store - Extended Inventory(LP) pattern. {#azure-app-configuration-store__entry__32} | Field | Description | |-|-| | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | | Location \[location\] | The Azure region where the resource is deployed. | | 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.appconfiguration/configurationstores. | [Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]] ## CI relationships The pattern creates these relationships to support discovery. {#azure-app-configuration-store__entry__47} | 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 App Configuration - Configuration Store \[cmdb_azure_app_configuration_configuration_store\] | References | Cloud Resource \[cmdb_ci_cmp_resource\] | [ ] ## Azure tag discovery {#azure-app-configuration-store__section_ezc_jwt_jfc} The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-app-configuration-store__table_axq_spc_y2c__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | [Table 3. Key Value \[cmdb_key_value\]] {#azure-app-configuration-store__table_axq_spc_y2c} *[\>]: and then