Azure Container Registry pattern-based discovery

  • Release version: Zurich
  • Updated July 31, 2025
  • 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 enables ServiceNow customers to detect and map Azure Container Registry services within their cloud environment using Discovery and Service Mapping Patterns. This process helps populate critical configuration data into both CMDB and non-CMDB tables, providing comprehensive visibility into Azure Container Registry resources and their relationships.

    Show full answer Show less

    Key Features

    • Pattern Activation: The Azure Container Registry discovery pattern is disabled by default. Customers must enable it to start discovery. Since version 6.28.0 of Visibility Content, activating or deactivating patterns is no longer considered a customization and patterns reset to the latest predefined versions upon upgrades.
    • Prerequisites and Setup: Azure discovery requires meeting Microsoft Azure discovery prerequisites and configuring the discovery schedule properly, especially when discovering Azure GovCloud (US) accounts, which need a datacenter URL in the Azure service account setup.
    • Data Population: The discovery pattern populates data into non-CMDB tables (such as cmdbazurecontainerregistryregistry) and CMDB tables (such as cmdbcicmpresource), capturing detailed attributes of Azure Container Registry resources.
    • CI Relationships: The pattern automatically creates relationships between configuration items to reflect resource group containment, hosting on Azure datacenters, and references between Azure Container Registry and cloud resource records.
    • Tag Collection: Azure tags are collected and stored in the cmdbkeyvalue table, enabling customers to manage metadata associated with their Azure resources.

    Key Outcomes

    • Comprehensive Resource Visibility: Customers gain detailed insights into their Azure Container Registry resources, including encryption status, network access, provisioning state, identity details, geographic location, and subscription information.
    • Accurate CMDB Population: The discovery pattern ensures relevant Azure Container Registry resources are accurately represented in the CMDB with essential operational and installation statuses, facilitating better service management and compliance.
    • Improved Cloud Resource Management: By capturing relationships and tags, customers can better understand dependencies and metadata, enhancing cloud governance, auditing, and operational decision-making.

    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 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.