Azure Container Registry pattern-based discovery

  • Release version: Yokohama
  • Updated August 10, 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 enables ServiceNow customers to detect and map Azure Container Registry resources within their cloud environment. This functionality is part of the Discovery and Service Mapping Patterns application and helps populate both CMDB and non-CMDB tables with detailed information about Azure Container Registries, supporting comprehensive cloud asset management and operational visibility.

    Show full answer Show less

    Key Features

    • Pattern Activation: The Azure Container Registry discovery pattern is disabled by default. Starting with Visibility Content version 6.28.0, enabling or disabling patterns no longer counts as a customization, allowing smooth upgrades while retaining active status.
    • Prerequisites: Proper Microsoft Azure discovery prerequisites must be met, including configuring Azure service accounts and discovery schedules, especially for Azure GovCloud (US) environments which require a datacenter URL.
    • Data Population: The discovery pattern populates data in two locations:
      • Non-CMDB tables: Contains detailed Azure Container Registry-specific attributes such as admin user status, encryption status, identity, location, provisioning state, public network access, subscription, tenant ID, and tier.
      • CMDB tables: The Cloud Resource table stores core resource information including install status, location, name, operational status, resource type, and object ID.
    • CI Relationships: The pattern creates relationships linking container registries to resource groups, cloud resources, and Azure datacenters, enabling a clear hierarchical view of resources.
    • Tag Discovery: Azure tags are collected and stored in the Key Value table, providing metadata management capabilities.

    Practical Implications for ServiceNow Customers

    By enabling this pattern, customers can automate the discovery and mapping of Azure Container Registries, ensuring their CMDB reflects accurate and detailed cloud resource information. This supports better governance, compliance, and operational management of Azure cloud assets. The pattern’s integration with both CMDB and non-CMDB tables allows customers to leverage enriched data for workflows, reporting, and service management processes. Proper configuration of Azure service accounts and discovery schedules, especially for specialized environments like GovCloud, is essential for successful discovery.

    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.