---
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 Managed Identity User Assigned Identity

# Azure Managed Identity User Assigned Identity 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 Managed Identity User Assigned Identity pattern-based discovery

This pattern-based discovery in ServiceNow identifies Azure Managed Identity User Assigned Identities within your cloud environment.
It is part of the Discovery and Service Mapping Patterns application, which requires periodic updates from the ServiceNow Store to access the latest Azure service patterns.
The discovery populates data into both CMDB and non-CMDB tables, enabling comprehensive asset and configuration management for Azure resources.
Show full answer Show less  

## Key Requirements and Configuration

* **REST API Permissions:** Download the Cloud Discovery patterns spreadsheet to grant necessary user permissions. The spreadsheet also provides pattern details, CI classes, and vendor documentation links.
* **Azure Discovery Prerequisites:** Ensure all prerequisites listed in Microsoft Azure Cloud discovery using patterns are met.
* **Resource Inclusion List:** Verify the relevant Azure resource is not on the Resource Inclusion List to avoid duplicate discovery.
* **Pattern Activation:** The Azure Managed Identity User Assigned Identity pattern is disabled by default. From Visibility Content version 6.28.0 onward, enabling or disabling patterns is not treated as customization and patterns will automatically update upon upgrading.
* **Discovery Schedule for GovCloud:** Azure GovCloud (US) discovery requires configuring the Azure service account with the appropriate datacenter URL.

## Data Storage and Configuration Item (CI) Details

The discovery stores data in two main areas:

* **Non-CMDB Tables:** Includes detailed inventory data such as Client ID, Object ID, Principal ID, Tenant ID, Location, and Resource Group. These can be reviewed under the Azure configuration section in ServiceNow.
* **CMDB Tables:** Core resource information is stored in the *Cloud Resource \[cmdbcicmpresource\]* table with fields like Install Status, Operational Status, Resource Type (set as microsoft.managedidentity/userassignedidentities), Location, Name, and Object ID.

## CI Relationships and Tag Discovery

* The pattern establishes relationships connecting the User Assigned Identity to its Azure Resource Group and Azure Datacenter, supporting accurate dependency mapping.
* Tags associated with the Azure resources are collected and stored in the Key Value \[cmdbkeyvalue\] table, capturing both tag names and values for enhanced resource metadata management.

## Practical Impact for ServiceNow Customers

By enabling this pattern, customers gain automated, up-to-date visibility into Azure Managed Identity User Assigned Identities within their cloud environment. This improves the accuracy of the CMDB, supports compliance and governance efforts, and enhances service mapping for better operational insights.  
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-managed-id-user-assigned-id__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-managed-id-user-assigned-id__cloud-discovery-api-ph-short-prereq}

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 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-managed-id-user-assigned-id__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-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/aypCYVQdO8oFebLMLEI89g "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/XKQpJvxWTKNL58XCkRHVxA "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