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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Azure Managed Identity User Assigned Identity

# Azure Managed Identity User Assigned Identity pattern-based discovery {#ariaid-title1}

* Release version: Yokohama
* 
* Updated August 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Managed Identity User Assigned Identity pattern-based discovery

The Azure Managed Identity User Assigned Identity pattern-based discovery enables ServiceNow customers to identify and map Azure Managed Identity User Assigned Identity resources in their cloud environment.
This discovery is part of the Discovery and Service Mapping Patterns application and populates relevant data into both CMDB and non-CMDB tables, providing detailed visibility into Azure managed identities.
Show full answer Show less  

## Key Features

* **Pattern Activation:** The Azure Managed Identity User Assigned Identity pattern is disabled by default. Starting with Visibility Content version 6.28.0, enabling or disabling patterns is no longer considered a customization, allowing updates without losing configuration.
* **Prerequisites:** Customers must verify Microsoft Azure discovery prerequisites and ensure proper configuration of Azure service accounts. Special configuration is required for discovering Azure GovCloud (US) accounts using a datacenter URL.
* **Data Population:** The pattern populates data in:
  * **Non-CMDB Table:** The `cmdbazuremanagedidentityuserassignedidentity` table stores details such as Client ID, Location, Object ID, Principal ID, Resource Group, Tenant ID, and references a configuration item.
  * **CMDB Table:** The `cmdbcicmpresource` table stores core resource information including install status, location, name, object ID, operational status, and identifies the resource type specifically as `microsoft.managedidentity/userassignedidentities`.
  * **Tag Discovery:** Tags associated with the discovered resources are collected and stored in the `cmdbkeyvalue` table, enabling tag-based management.
* **CI Relationships:** The pattern establishes important relationships between discovered Configuration Items such as:
  * Cloud Resource contained by a Resource Group
  * Cloud Resource hosted on an Azure Datacenter
  * Azure Managed Identity User Assigned Identity referencing the Cloud Resource

## Practical Benefits for ServiceNow Customers

* Gain accurate and comprehensive visibility into Azure Managed Identity User Assigned Identity resources, supporting better cloud asset management.
* Ensure data integrity by automatically linking discovered resources with appropriate resource groups and datacenters.
* Leverage tag data for enhanced classification, filtering, and reporting within the CMDB.
* Maintain easy updates and management of discovery patterns without losing custom configurations, ensuring up-to-date visibility as Azure environments evolve.  
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 {#azure-managed-id-user-assigned-id__section_ipy_53n_jfc}

Verify the Microsoft Azure discovery prerequisites{#azure-managed-id-user-assigned-id__verify-azure-discovery-prerequisites-dlentry}
:   For more information, see the prerequisites section in [Microsoft Azure Cloud components discovery using patterns](https://www.servicenow.com/docs/JeDZ0tlC9eLF5fei5qSv3w "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.").

Enable the relevant pattern{#azure-managed-id-user-assigned-id__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/R5W5GP640V_5uNIhVNRPCw "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#azure-managed-id-user-assigned-id__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud{#azure-managed-id-user-assigned-id__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/wA59_lRoV_0PzpuODHnNjA "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-managed-id-user-assigned-id__configure-govcloud-azure-dd}
{#azure-managed-id-user-assigned-id__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-managed-id-user-assigned-id__section_aq4_qkq_hfc}

Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Managed Identity User Assigned Identity - 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-managed-id-user-assigned-id__section_aq4_qkq_hfc__entry__2}

| Field | Description |
|-|-|
| Client ID \[client_id\] | The unique identifier for an Azure Active Directory (Azure AD) application, also known as a client. |
| Location \[location\] | The geographical region where the resource is deployed. |
| Object Id \[object_id\] | The unique identifier of the resource. |
| Principal ID \[principal_id\] | The unique identifier of the principal service or user associated with the resource. |
| Resource Group \[resource_group\] | Name of the resource group. |
| Tenant ID \[tenant_id\] | The unique identifier of the Azure AD tenant. |
| Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. |
[Table 1. Azure Managed Identity - User Assigned Identity \[cmdb_azure_managed_identity_user_assigned_identity\]]

## Data stored in CMDB tables

Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Managed Identity User Assigned Identity - Extended Inventory(LP) pattern.  
{#azure-managed-id-user-assigned-id__entry__18}

| 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 of 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.managedidentity/userassignedidentities. |
[Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]]

## CI relationships

The pattern creates these relationships to support discovery.
{#azure-managed-id-user-assigned-id__entry__33}

| 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 Managed Identity - User Assigned Identity \[cmdb_azure_managed_identity_user_assigned_identity\] | References | Cloud Resource \[cmdb_ci_cmp_resource\] |
[ ]

## Azure tag discovery {#azure-managed-id-user-assigned-id__section_ezc_jwt_jfc}

The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-managed-id-user-assigned-id__table_axq_spc_y2c__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | Tag name. |
| Value \[value\] | Tag value. |
[Table 3. Key Value \[cmdb_key_value\]]

{#azure-managed-id-user-assigned-id__table_axq_spc_y2c}

*[\>]: and then