--- 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 App Configuration Store # Azure App Configuration store 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 App Configuration store pattern-based discovery The Azure App Configuration store pattern-based discovery enables ServiceNow customers to automatically detect and map Azure App Configuration resources within their cloud environment. This discovery is part of the Discovery and Service Mapping Patterns application and is essential for maintaining an accurate and up-to-date Configuration Management Database (CMDB) representing Azure services. Show full answer Show less ## Key Features * **Pattern Activation:** The Azure App Configuration pattern is disabled by default and requires explicit activation. Starting with Visibility Content version 6.28.0, enabling or disabling patterns is no longer considered a customization, ensuring patterns receive updates without losing configured states. * **Discovery Prerequisites:** Customers must verify Microsoft Azure discovery prerequisites, including setting up Azure service accounts properly---especially for Azure GovCloud (US), which requires a datacenter URL. * **Data Population:** The discovery populates data into both CMDB and non-CMDB tables, providing comprehensive inventory details: * **Non-CMDB Data:** Stored in tables such as *cmdbazureappconfigurationconfigurationstore*, capturing detailed attributes like authentication mode, endpoint, provisioning state, SKU, and Key Vault properties. * **CMDB Data:** Populated in the *cmdbcicmpresource* table with core resource details including name, location, install status, and operational status. * **CI Relationships:** The pattern establishes relationships between discovered Configuration Items (CIs), such as associations with resource groups and datacenters, supporting comprehensive service mapping. * **Tag Collection:** Tags from Azure resources are collected and stored in the *cmdbkeyvalue* table to help with resource classification and management. ## What Customers Can Expect By implementing this pattern-based discovery, ServiceNow customers gain automated, detailed visibility into their Azure App Configuration resources, including configuration details and their relationships within the Azure environment. This supports accurate CMDB updates, improved cloud asset management, and better operational insight. The discovery ensures that both typical CMDB tables and extended inventory tables are populated, enabling richer data for governance, compliance, and operational workflows. 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-app-configuration-store__section_ipy_53n_jfc} 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 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-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://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "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://servicenow-prod.fluidtopics.net/wA59_lRoV_0PzpuODHnNjA "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