Azure Container Registry pattern-based discovery

  • Release version: Xanadu
  • Updated June 16, 2026
  • 2 minutes to read
    • Summarize
    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 in ServiceNow enables automated identification and mapping of Azure Container Registry resources within your cloud environment. This capability is part of the Discovery and Service Mapping Patterns application, which helps populate both Configuration Management Database (CMDB) and non-CMDB tables with detailed information about Azure services. It requires specific prerequisites and configuration steps to ensure accurate discovery, especially when working with Azure GovCloud accounts.

    Show full answer Show less

    Key Features

    • Pattern Activation: The Azure Container Registry pattern is disabled by default. Starting with Visibility Content version 6.28.0, enabling or disabling patterns does not count as customization, ensuring smooth updates without losing your activation preferences.
    • Discovery Scheduling: For Azure GovCloud environments, discovery requires configuring the service account with a datacenter URL to properly access resources.
    • Data Population: The discovery runs the Azure - Container Registry - Extended Inventory (LP) pattern, which populates detailed Azure Container Registry data into both CMDB and non-CMDB tables.
    • Comprehensive Data Fields: The discovery captures critical attributes such as admin user status, encryption status, identity, location, provisioning state, public network access, resource group, subscription ID, tenant ID, and service tier.
    • Configuration Item (CI) Relationships: The pattern automatically establishes relationships among Azure Container Registry resources, resource groups, cloud resources, and Azure datacenters to provide context and support dependency mapping.
    • Tag Discovery: Tags associated with Azure Container Registry resources are collected and stored in the Key Value table, enabling better classification and filtering of discovered resources.

    Practical Application for ServiceNow Customers

    By implementing this pattern-based discovery, ServiceNow customers can efficiently discover Azure Container Registry resources with detailed attributes and relationships automatically captured in the CMDB. This facilitates improved visibility, operational management, and governance of Azure container services within their environments. Customers should ensure they meet Azure discovery prerequisites, enable the pattern, configure discovery schedules appropriately, and understand how discovered data is structured across CMDB and non-CMDB tables for effective use in asset and configuration management.

    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

    Verify the Microsoft Azure discovery prerequisites
    For more information, see the prerequisites section in Microsoft Azure Cloud components discovery using patterns.
    Enable the relevant pattern
    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.
    Configure the Discovery schedule to support GovCloud
    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.

    Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables.

    Data stored in non-CMDB tables

    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 All > Configuration > Azure. You can also search the navigation filter for the specific pattern name.

    Table 1. Azure Container Registry [cmdb_azure_container_registry_registry]
    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.

    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.

    Table 2. Cloud Resource [cmdb_ci_cmp_resource]
    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.

    CI relationships

    The pattern creates these relationships to support discovery.

    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

    The pattern collects tags and populates them in the Key Value [cmdb_key_value] table.
    Table 3. Key Value [cmdb_key_value]
    Field Description
    Key [key] Tag name.
    Value [value] Tag value.