Azure Container Registry pattern-based discovery

  • Release version: Yokohama
  • 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

    The Azure Container Registry pattern-based discovery in ServiceNow enables automated identification and mapping of Azure Container Registry resources within your cloud environment. This functionality is part of the Discovery and Service Mapping Patterns application, which requires activation of specific patterns and meeting Azure discovery prerequisites. It supports extended inventory collection and populates both CMDB and non-CMDB tables with detailed resource information.

    Show full answer Show less

    Key Features

    • Pattern Activation and Updates: The Azure Container Registry discovery pattern is disabled by default and must be enabled manually. Starting with Visibility Content version 6.28.0, enabling or disabling patterns does not count as customization, ensuring patterns continue to receive updates and reset to predefined versions after upgrades.
    • Discovery Schedule Configuration for GovCloud: Supports discovery of Azure GovCloud (US) accounts by requiring datacenter-specific URLs during Azure service account setup.
    • Data Population: Runs the Azure - Container Registry - Extended Inventory (LP) pattern to populate:
      • Non-CMDB tables with detailed registry attributes such as admin user status, encryption, identity, provisioning state, public network access, subscription, tenant, and tier.
      • CMDB tables with standard cloud resource records including install and operational status, location, name, object ID, and resource type.
    • CI Relationships: Automatically builds relationships between Azure Container Registry CIs and related resource groups, cloud resources, and Azure datacenters to maintain an accurate service map.
    • Tag Discovery: Collects and stores Azure tags in the Key Value table, enabling enhanced filtering and categorization based on tag keys and values.

    Practical Benefits for ServiceNow Customers

    By implementing this discovery pattern, ServiceNow customers can efficiently automate the detection and inventory of Azure Container Registry resources, resulting in:

    • Improved accuracy and completeness of CMDB data regarding Azure container registries.
    • Enhanced visibility into Azure container resource configurations, security settings, and operational status.
    • Streamlined compliance and governance through detailed resource attributes and tag management.
    • Robust service mapping that supports impact analysis and change management by establishing CI relationships.
    • Support for Azure GovCloud environments, extending discovery coverage in regulated or government-specific cloud regions.

    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.