Microsoft Azure resource inventory discovery
Summarize
Summary of Microsoft Azure resource inventory discovery
The ServiceNow Discovery application uses the Azure Resource Inventory (LP) pattern to identify Azure resources that lack dedicated discovery patterns. This enables ServiceNow customers to discover up to 10,000 Azure resources efficiently, enhancing visibility into their cloud infrastructure. To ensure accurate discovery, customers may need to update to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
Show less
Prerequisites
- Azure Service Principal: Must be configured to allow discovery access.
- Azure Privileges: For versions 1.3.0 and later, assign a user the API Management Service Reader role with permission to run a specific REST POST request to query resources via Azure Resource Graph. For versions 1.0.99 and earlier, assign permissions for a REST GET request to list subscription resources.
Configuration and Usage
- Create a Cloud Discovery Schedule: Set up a schedule for Azure service accounts to automate resource discovery.
- Resource Inclusion List: To avoid duplicate discovery when custom Azure patterns exist, configure the Cloud Inventory Resource Inclusion List by removing resource types covered by custom patterns. Leaving this list empty causes all resources to be discovered, which may degrade performance.
- Customize Inclusion List: Add additional Azure resource types following vendor naming conventions to extend discovery scope. Note that customizing the list disables automatic updates during application upgrades and requires manual maintenance.
- Modify Related Entries: Ensure the identifier “cmdbcicmpresource” and related configuration are set correctly to map discovered Azure resources into the CMDB.
Data Collected During Discovery
- Cloud Resource [cmdbcicmpresource]: Stores descriptive names, resource types (e.g., network, load balancer), object IDs, and descriptions of Azure resources.
- Key Value [cmdbkeyvalue]: Captures Azure tag key-value pairs associated with resources.
- CI Relationships: Establishes relationships such as “Hosted on” linking cloud resources to Azure datacenters, supporting accurate infrastructure mapping.
Benefits for ServiceNow Customers
This pattern expands ServiceNow’s discovery capabilities to include a broad range of Azure resources not covered by specific patterns, ensuring comprehensive cloud asset visibility. It supports efficient inventory management at scale and integrates discovered data into your CMDB with meaningful relationships, facilitating better governance and operational insight into your Azure environment.
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 may 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
Visit the ServiceNow Store website 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.
Prerequisites
- Azure service principal
- Verify the Azure service principal is configured. For more information, see Discovery for Microsoft Azure Cloud
- 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.<resource url>/providers/microsoft.resourcegraph/resources?api-version=2022-10-01"<resource url> – The URL varies based on the Azure account type, like "azure.com" or government site address.
- Create a Cloud Discovery schedule
- Create a schedule for the relevant Azure service account as described in Create Discovery schedules for cloud resources
- 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.
- Ensure that the application scope is Discovery and Service Mapping Patterns:
- Navigate to .
- Select Discovery and Service Mapping Patterns from the Application list.
- Navigate to .
- Open the Cloud Inventory Resource Inclusion List [sa_cloud_inventory_resource_whitelist] table.
- Under Related Links, click Show List.
- Select resource types for which you have custom patterns, and select Delete from the Actions on selected rows list.
- Ensure that the application scope is Discovery and Service Mapping Patterns:
- Modify the ServiceNow related entries
- Navigate to Related Entries.
- Click New.
- For the identifier, enter cmdb_ci_cmp_resource.
- For the related table, select Key Value [cmdb_key_value].
- For the referenced field, select Configuration Item.
- For the criterion attributes, add Key and Value.
You may need to click the lock icon
to view and change the criterion attributes.
Data collected by Discovery during horizontal discovery
| 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. |
CI relationships
| CI | Relationship | CI |
|---|---|---|
| Cloud Resource [cmdb_ci_cmp_resource] | Hosted on:Hosts |
Azure datacenter [cmdb_ci_azure_datacenter] |