---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Azure Container Registry

# Azure Container Registry pattern-based discovery {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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

The Azure Container Registry pattern-based discovery helps ServiceNow customers identify and map Azure Container Registry services within their cloud environments using Discovery and Service Mapping Patterns.
This process enables accurate inventory and configuration management by populating data into both CMDB and non-CMDB tables.
Show full answer Show less  

## Key Features

* **Pattern Activation:** The Azure Container Registry discovery pattern is disabled by default and requires activation. Starting with Visibility Content version 6.28.0, enabling or disabling patterns does not count as customization and patterns receive ongoing updates.
* **Permissions and Prerequisites:** Users must grant appropriate REST API permissions and meet Microsoft Azure discovery prerequisites to ensure successful discovery. A Cloud Discovery patterns spreadsheet provides necessary permissions, pattern details, CI classes, and vendor documentation links.
* **Resource Inclusion List Management:** To avoid duplicate discovery, ensure Azure Container Registry resources are not listed in the Resource Inclusion List (sacloudinventoryresourcewhitelist) table.
* **GovCloud Support:** Discovery of Azure GovCloud (US) accounts requires configuring the discovery schedule with a datacenter URL when setting up Azure service accounts.
* **Data Population:** The pattern populates detailed Azure Container Registry data in two areas:
  * **Non-CMDB tables:** Includes fields such as admin user enabled status, encryption status, identity, location, provisioning state, public network access, resource group, subscription and tenant IDs, tier, and references to configuration items.
  * **CMDB tables:** Populates standard cloud resource fields including install and operational status, location, name, object ID, and resource type (set as microsoft.containerregistry/registries).
* **Configuration Item (CI) Relationships:** The pattern creates relationships linking container registries with resource groups, cloud resources, and Azure datacenters to support comprehensive discovery mapping.
* **Tag Discovery:** Azure tags associated with container registries are collected and stored in the Key Value table, capturing tag names and values for enhanced resource classification.

## Practical Benefits

By implementing the Azure Container Registry pattern-based discovery, ServiceNow customers can achieve:

* Automated and accurate discovery of Azure Container Registry resources, ensuring up-to-date CMDB data.
* Clear visibility into resource configurations, statuses, and relationships within Azure environments.
* Support for compliance and governance through detailed inventory and tag management.
* Efficient management of discovery schedules and permission configurations to accommodate different Azure environments including GovCloud.  
Discovery and Service Mapping Patterns finds Azure services on your cloud environment. Discovering some of these resources might 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 REST API permissions
:   Download the [Cloud Discovery patterns spreadsheet](https://downloads.docs.servicenow.com/resource/enus/api/servicenow-discovery-patterns-api-details.xlsx) so you can grant user permissions required for running the Discovery patterns. In addition to permissions, the spreadsheet also includes useful information such as pattern names, types, CI Classes, and links to vendor documentation. New patterns are available quarterly, so check periodically to be sure you have the latest version of the spreadsheet.{#azure-container-registry__cloud-discovery-api-ph-short-prereq}

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 discovery using patterns](https://www.servicenow.com/docs/e2521~KHAw8EO7j1nC9QMA "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.").

Remove resources from the Resource Inclusion List table{#azure-container-registry__remove-resource-inclusion-list-azure}
:   Verify that the relevant resource isn't listed in the Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table to avoid duplicate discovery. For more information on removing resources from the Resource
    Inclusion List, see [Microsoft Azure resource inventory discovery](https://www.servicenow.com/docs/tO3nNqXv4zOe7q99krvAnA "The ServiceNow Discovery application uses the Azure Resource Inventory (LP) pattern to find resources available through Azure that don’t have a dedicated pattern. Discovering some of these resources might 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://www.servicenow.com/docs/aypCYVQdO8oFebLMLEI89g "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://www.servicenow.com/docs/XKQpJvxWTKNL58XCkRHVxA "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