--- sourceDocument: Brazil IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Azure resource inventory # Microsoft Azure resource inventory discovery {#ariaid-title1} Release version: Brazil Updated September 10, 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 Microsoft Azure resource inventory discovery The ServiceNow Discovery application leverages the Azure Resource Inventory (LP) pattern to identify Azure resources that lack dedicated discovery patterns. This enables customers to discover up to 10,000 Azure resources, helping maintain an accurate and comprehensive configuration management database (CMDB) of their Azure environment. Show full answer Show less ## Prerequisites and Setup * **Azure Service Principal:** Confirm configuration to allow Discovery to access Azure resources. * **Privileges:** For versions 1.3.0 and later, assign the API Management Service Reader role with permissions to execute a REST POST request against the Azure Resource Graph API. For earlier versions, permissions to run a REST GET request on subscription resources are needed. * **Discovery Schedule:** Create a discovery schedule for the Azure service account following standard cloud resource discovery procedures. ## Fine-Tuning Discovery with Resource Inclusion List To avoid duplicate discovery when custom Azure patterns are in use, customers should manage the Cloud Inventory Resource Inclusion List. This list controls which Azure resource types the Azure Resource Inventory pattern will discover. * By default, the inclusion list contains common Azure services but can be expanded with additional resource types following Azure naming conventions. * Modifications disable automatic updates to the list during application upgrades, so manual maintenance is required. * When leaving the inclusion list empty, the pattern discovers all resources, which may impact performance negatively. ## Application Scope and Configuration The Discovery and Service Mapping Patterns application scope must be active to manage resource inclusion. Adjustments to related ServiceNow entries include linking Azure resource discovery to the **cmdbcicmpresource** table and configuring key-value pairs for Azure tags in the **cmdbkeyvalue** table. ## Data Collected During Discovery * **Cloud Resource \[cmdbcicmpresource\]:** Captures resource name, type (e.g., network, load balancer), Azure Object ID, and descriptive information indicating Azure origin. * **Key Value \[cmdbkeyvalue\]:** Stores Azure tag key-value pairs to enrich resource context. * **CI Relationships:** Establishes relationships such as "Hosted on" between the Azure resource and Azure datacenter CI (**cmdbciazuredatacenter**), supporting the CMDB's relational structure. ## Practical Benefits for ServiceNow Customers Using the Azure Resource Inventory (LP) pattern allows customers to efficiently discover and maintain a broad inventory of Azure resources, including those without dedicated patterns. This comprehensive visibility supports better asset management, governance, and decision-making within the ServiceNow platform. 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. You can discover up to 10 thousand resources using the Azure Resource Inventory (LP) pattern. ## Request apps on the Store {#azure-resource-inventory-pattern__section_lp4_mnf_fjb} Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#azure-resource-inventory-pattern__inline-send-to-store} ## Prerequisites {#azure-resource-inventory-pattern__section_lf75wdhjwk_m2b} Azure service principal : Verify the Azure service principal is configured. For more information, see [Discovery for Microsoft Azure](https://www.servicenow.com/docs/tyS76oBWPcV9nWT~V2y4_w "If your cloud resources are in an Azure cloud, you must create a user identity called a service principal that grants permissions to the MID Server to access selected resources.") Privileges : For versions 1.3.0 and later: On the Microsoft Azure Console, provide a user with the API Management Service Reader role with permissions to run the following REST POST request: `"https://management./providers/microsoft.resourcegraph/resources?api-version=2022-10-01"` \ -- The URL varies based on the Azure account type, like "azure.com" or government site address. : For versions 1.0.99 and earlier: On the Microsoft Azure Console, provide a user with the API Management Service Reader role with permissions to run the following REST GET request: `"https://management.azure.com/subscriptions//resources"` Create a Cloud Discovery schedule : Create a schedule for the relevant Azure service account as described in [Create Discovery schedules for cloud resources](https://www.servicenow.com/docs/75D1RA0uUfz0uQupZOga5Q#discovery-manager "Create schedules for discovering cloud resources using service accounts or IP ranges.") Fine-tune Azure inventory discovery using the Resource Inclusion List : If your deployment has custom patterns for Azure discovery, ensure that you don't discover Azure resources twice. Note: Leaving the \[pre_resource_whitelist\] table empty causes the Pattern to populate all resources and it might cause performance issues. 1. Ensure that the application scope is Discovery and Service Mapping Patterns: 1. Navigate to SettingsDeveloper. 2. Select Discovery and Service Mapping Patterns from the Application list. {#azure-resource-inventory-pattern__ol_nfr_g2l_d3b} 2. Navigate to System DefinitionsTables. 3. Open the Cloud Inventory Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table. 4. Under Related Links, click Show List. 5. Select resource types for which you have custom patterns, and select Delete from the Actions on selected rows list. {#azure-resource-inventory-pattern__ol_d1v_kb2_d3b} : The Cloud Inventory Resource Inclusion List is predefined with common services. You can expand the inclusion list with additional resource types that you want the pattern to discover. The names of these resource types must conform to the appropriate vendor naming conventions. Note: When you modify the out-of-the-box inclusion list, it is no longer updated automatically in application updates. You must maintain the customized list on your own. 1. Open the Cloud Inventory Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table. 2. Click New. 3. Fill in the form, and then click Submit.{#azure-resource-inventory-pattern__table_usx_krd_fkb__entry__2} | Field | Description | |-|-| | Cloud Vendor | The vendor of the resource type: Azure. | | Resource Type | The Azure resource type value. | | Application | The application scope: Discovery and Service Mapping Patterns. | [ ] {#azure-resource-inventory-pattern__table_usx_krd_fkb} {#azure-resource-inventory-pattern__ol_osj_vvc_fkb} : The changes are applied the next time you run the pattern. Modify the ServiceNow related entries : 1. Navigate to Related Entries. 2. Click New. 3. For the identifier, enter cmdb_ci_cmp_resource. 4. For the related table, select Key Value \[cmdb_key_value\]. 5. For the referenced field, select Configuration Item. 6. For the criterion attributes, add Key and Value. You may need to click the lock icon ![Lock icon]() to view and change the criterion attributes. {#azure-resource-inventory-pattern__ol_ttm_ljl_rjb}
## Data collected by Discovery during horizontal discovery {#azure-resource-inventory-pattern__section_fgew238798_j3q_fdb} {#azure-resource-inventory-pattern__table_olk_1pq_f56b__entry__2} | Table and field | Additional information | |-|-| | Cloud Resource \[cmdb_ci_cmp_resource\] || | Name | A descriptive name used to identify the Azure resource. | | Resource type | The type of the resource, for example network, load balancer. | | Object ID | The ID of the Azure resource. | | Description | The text populated during discovery that specifies that this resource is available from Azure. | | Key Value \[cmdb_key_value\] || | Key | The Azure tag key name. | | Value | The Azure tag value name. | [ ] {#azure-resource-inventory-pattern__table_olk_1pq_f56b} ## CI relationships {#azure-resource-inventory-pattern__section_g13_tp4_m2b} These relationships are created to support Azure resource inventory discovery:{#azure-resource-inventory-pattern__table_ysf_fpq_f987b__entry__3} | CI | Relationship | CI | |-|-|-| | Cloud Resource \[cmdb_ci_cmp_resource\] | Hosted on:Hosts | Azure datacenter \[cmdb_ci_azure_datacenter\] | [ ] {#azure-resource-inventory-pattern__table_ysf_fpq_f987b} **Related topics** * *[\>]: and then