--- 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 Container Registry # Azure Container Registry 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 Container Registry pattern-based discovery Azure Container Registry pattern-based discovery is part of the Discovery and Service Mapping Patterns application in ServiceNow, designed to identify and map Azure Container Registry resources in your cloud environment. This pattern helps populate detailed Azure Container Registry data into both CMDB and non-CMDB tables, enabling comprehensive visibility and management of these resources. Show full answer Show less ## Key Features * **Pattern Activation and Updates:** The Azure Container Registry discovery pattern is disabled by default. Starting with Visibility Content version 6.28.0, enabling or disabling patterns will not be treated as customizations, ensuring patterns receive updates and reset to the latest versions after upgrades while retaining active status. * **Prerequisites and Setup:** Ensure Microsoft Azure discovery prerequisites are met, including configuring Azure service accounts with proper datacenter URLs to support GovCloud (US) discovery. * **Data Population:** - Non-CMDB tables receive detailed Azure Container Registry inventory data, including administrative status, encryption, identity, location, provisioning state, network access, subscription and tenant IDs, and service tier. - CMDB tables are populated with core Cloud Resource data such as install status, operational status, resource type (microsoft.containerregistry/registries), location, and unique identifiers. * **Configuration Item Relationships:** The discovery pattern automatically establishes relationships linking Azure Container Registries to resource groups, hosting datacenters, and corresponding Cloud Resources, supporting accurate service mapping. * **Tag Discovery:** Azure tags associated with container registries are collected and stored in the Key Value table, allowing tag-based filtering and reporting within ServiceNow. ## Practical Benefits for ServiceNow Customers * Gain detailed and up-to-date insights into Azure Container Registries, including security and configuration attributes, directly within the ServiceNow CMDB. * Automate discovery and service mapping of Azure Container Registries, reducing manual effort and ensuring accurate dependency management. * Support compliance and operational monitoring by tracking encryption status, provisioning states, network access settings, and other critical resource details. * Utilize tag data for enhanced organization, governance, and reporting on Azure Container Registry resources. * Maintain discovery patterns with seamless updates and no risk of losing configuration after upgrades. 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-container-registry__section_ipy_53n_jfc} Verify the Microsoft Azure discovery prerequisites{#azure-container-registry__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-container-registry__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-container-registry__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud{#azure-container-registry__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-container-registry__configure-govcloud-azure-dd} {#azure-container-registry__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-container-registry__section_aq4_qkq_hfc} Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Container Registry - 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-container-registry__section_aq4_qkq_hfc__entry__2} | Field | Description | |-|-| | Admin User Enabled \[admin_user_enabled\] | Indicates whether the administrator user account is enabled for the resource. | | Encryption Status \[encryption_status\] | The current encryption status of the resource, specifying if data is encrypted. | | Identity \[identity\] | The identity information for the resource, used for authentication and authorization. | | Kind \[kind\] | The specific kind or subtype of the resource, if applicable. | | Location \[location\] | The geographical region where the resource is deployed. | | Object Id \[object_id\] | The unique identifier for the resource. | | Provisioning State \[provisioning_state\] | The current provisioning state of the resource. | | Public Network Access \[public_network_access\] | Indicates whether public network access is allowed for the resource. | | Resource Group \[resource_group\] | Name of the resource group. | | Subscription ID \[subscription_id\] | The subscription ID. | | Tenant ID \[tenant_id\] | The Azure Active Directory tenant ID associated with the resource. | | Tier \[tier\] | The service or resource tier, indicating the level of performance or cost. | | Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. | [Table 1. Azure Container Registry \[cmdb_azure_container_registry_registry\]] ## Data stored in CMDB tables Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Container Registry - Extended Inventory(LP) pattern. {#azure-container-registry__entry__30} | Field | Description | |-|-| | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | | Location \[location\] | The geographical region where the resource is deployed. | | Name \[name\] | The name of the resource. | | Object ID \[object_id\] | The unique identifier for 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.containerregistry/registries. | [Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]] ## CI relationships The pattern creates these relationships to support discovery. {#azure-container-registry__entry__45} | 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 Container Registry \[cmdb_azure_container_registry_registry\] | References | Cloud Resource \[cmdb_ci_cmp_resource\] | [ ] ## Azure tag discovery {#azure-container-registry__section_ezc_jwt_jfc} The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-container-registry__table_axq_spc_y2c__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | [Table 3. Key Value \[cmdb_key_value\]] {#azure-container-registry__table_axq_spc_y2c} *[\>]: and then