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

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Data collected for Azure

# Data collected for Microsoft Azure
Cloud Discovery {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](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 Data collected for Microsoft Azure Cloud Discovery

Microsoft Azure Cloud Discovery in ServiceNow collects detailed information about Azure cloud resources across datacenters.
This discovery process leverages the Cloud Provisioning and Governance API along with Discovery and Service Mapping Patterns to populate the Configuration Management Database (CMDB) with accurate cloud infrastructure data.
Show full answer Show less  
To ensure comprehensive and up-to-date discovery, customers should keep the Discovery and Service Mapping Patterns application current, which can be managed via the ServiceNow Store. Azure cloud credentials with appropriate permissions are required to access Azure accounts and perform discovery.

## Prerequisites and Setup

* Verify that the Discovery and Service Mapping Patterns application and CMDB CI Class Models Visibility Content are up to date.
* Create and configure Microsoft Azure cloud credentials with sufficient access rights.
* Set up a discovery schedule within the Cloud Discovery Workspace to automate discovery runs.
* Grant REST API permissions as outlined in the Cloud Discovery patterns spreadsheet, which also provides pattern details and links to vendor documentation. This spreadsheet is updated quarterly.

## Discovery Process and Patterns

Discovery uses predefined patterns to detect various Azure resources and populate corresponding CMDB tables. Key default patterns include:

* **Azure DataBase (LP):** Discovers SQL servers, managed instances, MySQL, PostgreSQL, Cosmos DB, Redis, and related databases, populating the `cmdbciclouddatabase` table.
* **Azure LoadBalancer TD:** Retrieves Azure load balancers for Service Mapping top-down discovery, populating `cmdbcilbservice`. Note: This is not used for horizontal discovery.
* **Azure WebSite (LP):** Discovers Azure web servers, populating `cmdbcicloudwebserver` and `cmdbciipaddress` tables.

## Data Collected and CMDB Tables

Discovery populates numerous CMDB tables with detailed Azure resource attributes, enabling comprehensive asset and configuration tracking. Important tables and their key fields include:

* **Azure Datacenter (`cmdbciazuredatacenter`):** Name, region, object ID.
* **Availability Zone (`cmdbciavailabilityzone`):** Name.
* **Virtual Machine Instance (`cmdbcivminstance`):** Name, state, CPUs, memory, disks, network adapters, VM instance ID.
* **Compute Security Groups (`cmdbcicomputesecuritygroup`):** Name, state, object ID.
* **Images (`cmdbciostemplate`):** Name, guest OS, image source.
* **Storage Volume (`cmdbcistoragevolume`):** Name, state, type, size.
* **Cloud Networks and VMware vCenter Networks (`cmdbcinetwork`, `cmdbcivcenternetwork`):** Name, state, CIDR (not on vCenter).
* **Cloud Subnets (`cmdbcicloudsubnet`):** Name, status, CIDR.
* **Network Interfaces (`cmdbcinic`):** Name, netmask, MAC address/manufacturer, status.
* **Cloud Load Balancers (`cmdbcicloudloadbalancer`):** Name, object ID, state.
* **Azure Deployments (`cmdbciazuredeployment`):** Name, provisioning state (requires Cloud Provisioning and Governance plugin).
* **Resource Groups (`cmdbciresourcegroup`):** Name, object ID, state, operational status, install status. State and status values track lifecycle events including termination.
* **Public IP Addresses (`cmdbcicloudpublicipaddress`):** Name, public IP, DNS.
* **Storage Accounts (`cmdbcicloudstorageaccount`):** Name, SKU, state.
* **Cloud Databases (`cmdbciclouddatabase`):** Domain name, name, object ID, operational status, type, state, vendor, version (version info may be missing for some databases), with category info for Azure SQL Managed Instances.
* **Cloud Web Servers (`cmdbcicloudwebserver`):** Name, install status, vendor, domain name, operational status, state.
* **IP Addresses (`cmdbciipaddress`):** Domain name, install status, IP address, netmask, operational status, vendor.
* **Database (`cmdbcidatabase`):** Life-cycle stage status, name, status, serial number, type.
* **Compute Template (`cm`**  
Discovery collects information about cloud resources in Microsoft Azure datacenters. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

## Request apps on the Store {#data-collected-azure-discovery__section_y3k_3pl_rlb}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) 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](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#data-collected-azure-discovery__inline-send-to-store}

## Prerequisites {#data-collected-azure-discovery__section_asl_pcm_jzb}

Verify that the applications are up to date
:
    * Discovery and Service Mapping Patterns
    * CMDB CI Class Models
    * Visibility Content
    {#data-collected-azure-discovery__ul_aln_qlb_5yb}

Create Azure cloud credentials
:   Create Microsoft Azure credentials that can access the Microsoft Azure account. For more information, see [Create Azure cloud credentials](https://www.servicenow.com/docs/gdMjiCdRG_AE9pO2aEOACQ "If your cloud resources are in an Azure cloud, create credentials that can access the Azure account. This procedure requires configuration in your Azure account.").

Configure a discovery schedule
:   [Create a discovery schedule in Cloud Discovery Workspace](https://www.servicenow.com/docs/HqOgLUuXYs~qteHC5QcuyA "Create schedules for discovering cloud resources based on the discovery method that you choose: service accounts or IP ranges. The discovery schedule defines the various settings for the cloud discovery.")

## Verify the REST API Permissions {#data-collected-azure-discovery__id_tnc_2bb_f1c}

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.{#data-collected-azure-discovery__cloud-discovery-api-paragraph}

## How Discovery finds Microsoft Azure resources {#data-collected-azure-discovery__section_s3h_1cv_nz}

Discovery uses the Cloud Provisioning and Governance API and Discovery and Service Mapping Patterns to find cloud resources.  
{#data-collected-azure-discovery__table_wwr_rng_gz__entry__2}

| Pattern | Description |
|-|-|
| Azure DataBase (LP) | Discovers database types of: * Microsoft.sql/servers * microsoft.sql/managedInstances * microsoft.dbformysql * microsoft.documentdb/databaseaccounts * microsoft.cache/redis * microsoft.dbforpostgresql/servers * microsoft.dbformysql/servers * microsoft.dbformysql/flexibleservers * microsoft.dbforpostgresql/flexibleservers {#data-collected-azure-discovery__ul_kkx_1zq_2xb} Populates the \[cmdb_ci_cloud_database\] table. |
| Azure LoadBalancer TD | Retrieves Microsoft Azure load balancers and populates the cmdb_ci_lb_service table. This pattern is only used by Service Mapping for top-down discovery, not by the Discovery application for horizontal discovery. |
| Azure WebSite (LP) | Retrieves Microsoft Azure web servers and populates the Cloud WebServers \[cmdb_ci_cloud_webserver\] and IP address \[cmdb_ci_ip_address\] tables. |
[Table 1. Default patterns]

{#data-collected-azure-discovery__table_wwr_rng_gz}

## Data collected by Discovery during horizontal discovery {#data-collected-azure-discovery__section_ivt_pbv_nz}

{#data-collected-azure-discovery__table_hsy_ql3_cy__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Region | region |
| Object ID | object_id |
[Table 2. Azure Datacenter \[cmdb_ci_azure_datacenter\]]

{#data-collected-azure-discovery__table_hsy_ql3_cy}  
{#data-collected-azure-discovery__table_jmt_rtv_cy__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
[Table 3. Availability Zone \[cmdb_ci_availability_zone\]]

{#data-collected-azure-discovery__table_jmt_rtv_cy}  
{#data-collected-azure-discovery__table_igv_rtv_cy__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| State | state |
| Object ID | object_id |
| CPUs | cpus |
| Disks | disks |
| Disks size (GB) | disks_size |
| Memory | memory |
| Network adapters | nics |
| VM Instance ID | vm_inst_id |
[Table 4. Virtual Machine Instance \[cmdb_ci_vm_instance\]]

{#data-collected-azure-discovery__table_igv_rtv_cy}  
{#data-collected-azure-discovery__table_csk_4cv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| State | state |
[Table 5. Compute Security Groups \[cmdb_ci_compute_security_group\]]

{#data-collected-azure-discovery__table_csk_4cv_nz}  
{#data-collected-azure-discovery__table_j1k_pcv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| Guest OS | guest_os |
| Image source | image_source |
[Table 6. Images \[cmdb_ci_os_template\]]

{#data-collected-azure-discovery__table_j1k_pcv_nz}  
{#data-collected-azure-discovery__table_ggz_qcv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| State | state |
| Object ID | object_id |
| Storage type | storage_type |
| Size | size |
[Table 7. Storage Volume \[cmdb_ci_storage_volume\]]

{#data-collected-azure-discovery__table_ggz_qcv_nz}  
{#data-collected-azure-discovery__table_xgb_scv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| State\* | state |
| CIDR\* | cidr |
[Table 8. Cloud Networks \[cmdb_ci_network\] and VMware vCenter Network \[cmdb_ci_vcenter_network\]]

{#data-collected-azure-discovery__table_xgb_scv_nz}\*Not found on VMware vCenter networks.  
{#data-collected-azure-discovery__table_v4h_jfv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Status | status |
| CIDR | cidr |
[Table 9. Cloud Subnets \[cmdb_ci_cloud_subnet\]]

{#data-collected-azure-discovery__table_v4h_jfv_nz}  
{#data-collected-azure-discovery__table_ebc_tcv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Netmask | netmask |
| MAC Address | mac_address |
| MAC Manufacturer | mac_manufacturer |
| Status | install_status |
[Table 10. Cloud Provisioning and Governance Network Interfaces \[cmdb_ci_nic\]]

{#data-collected-azure-discovery__table_ebc_tcv_nz}  
{#data-collected-azure-discovery__table_csh_5cv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| State | state |
[Table 11. Cloud Load Balancers \[cmdb_ci_cloud_load_balancer\]]

{#data-collected-azure-discovery__table_csh_5cv_nz}  
{#data-collected-azure-discovery__table_rbm_xcv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Provisioning state | provisioning_state |
[Table 12. Azure Deployments \[cmdb_ci_azure_deployment\]]

{#data-collected-azure-discovery__table_rbm_xcv_nz}  
Note:  
This table is only available for Discovery when the Cloud Provisioning and Governance plugin is activated.  
{#data-collected-azure-discovery__table_hwb_zcv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| State | state |
| Operational Status | operational_status |
| Install Status | install_status |
[Table 13. Resource Groups \[cmdb_ci_resource_group\]]

{#data-collected-azure-discovery__table_hwb_zcv_nz}  
Note:  
* When a resource group is discovered for the first time, the State field is set to Available, operational_status=Operational, and Status=Installed; based on the response mapping.
* When a resource group is terminated on Microsoft Azure, the CMPReconciler scripts set the State field to Terminated, and operational_status=Non-Operational and Status=Absent.
{#data-collected-azure-discovery__ul_lph_gkv_slb}  
{#data-collected-azure-discovery__table_ljd_1dv_nz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| Public IP address | public_ip_address |
| Public DNS | public_dns |
[Table 14. Public IP Addresses \[cmdb_ci_cloud_public_ipaddress\]]

{#data-collected-azure-discovery__table_ljd_1dv_nz}  
{#data-collected-azure-discovery__table_k4b_wmb_qz__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| Sku Name | sku_name |
| State | state |
[Table 15. Storage Accounts \[cmdb_ci_cloud_storage_account\]]

{#data-collected-azure-discovery__table_k4b_wmb_qz}  
{#data-collected-azure-discovery__table_wbh_k4s_mbb__entry__2}

| Label | Field Name |
|-|-|
| Fully qualified domain name | fqdn |
| Name | name |
| Object ID | object_id |
| Operational Status | operational_status |
| Type | type |
| State | state |
| Vendor | vendor |
| Version | version Note: For NoSQL and MSSQL Managed Instances, the API responses for these databases do not return version data. |
| Category\* | category |
[Table 16. Cloud Databases \[cmdb_ci_cloud_database\]]

{#data-collected-azure-discovery__table_wbh_k4s_mbb}\* Populated only by the Azure SQL Managed Instance license pattern extension. For more information, see the "Azure SQL Managed Instance license discovery" section in [Microsoft Azure Cloud discovery using patterns](https://www.servicenow.com/docs/5NmnHdhD8h3YVHs729mwBw "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.").  
{#data-collected-azure-discovery__table_ar5_2gd_4db__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Install status | install_status |
| Vendor | vendor |
| Fully qualified domain name | fqdn |
| Operational status | operational_status |
| State | state |
[Table 17. Cloud WebServer \[cmdb_ci_cloud_webserver\]]

{#data-collected-azure-discovery__table_ar5_2gd_4db}  
{#data-collected-azure-discovery__table_bdw_x5j_2xb__entry__2}

| Label | Field Name |
|-|-|
| Fully qualified domain name | fqdn |
| Install status | install_status |
| IP Address | ip_address |
| Name | name |
| Netmask | netmask |
| Operational status | operational_status |
| Vendor | vendor |
[Table 18. IP Address \[cmdb_ci_ip_address\]]

{#data-collected-azure-discovery__table_bdw_x5j_2xb}  
{#data-collected-azure-discovery__table_lll_wvj_2xb__entry__2}

| Label | Field Name |
|-|-|
| Life-cycle Stage Status | life_cycle_stage_status |
| Name | name |
| Status | status |
| Serial Number | serial_number |
| Type | type |
[Table 19. Database \[cmdb_ci_database\]]

{#data-collected-azure-discovery__table_lll_wvj_2xb}  
{#data-collected-azure-discovery__table_brd_gxj_2xb__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| VCPUS | vcpus |
[Table 20. Compute Template \[cmdb_ci_compute_template\]]

{#data-collected-azure-discovery__table_brd_gxj_2xb}  
{#data-collected-azure-discovery__table_bzv_sxj_2xb__entry__2}

| Label | Field Name |
|-|-|
| Name | name |
| Object ID | object_id |
| Provider | provider |
| vCPUs | vcpus |
[Table 21. Hardware Type \[cmdb_ci_hardware_type\]]

{#data-collected-azure-discovery__table_bzv_sxj_2xb}
**Related concepts**   

* [Agent Client Collector Discovery](https://www.servicenow.com/docs/edhre6~2pn1oGWgUK2rrGQ "Discover CIs in your environment by using Agent Client Collector for Visibility Content (ACC-VC) Discovery. ACC-VC works with both horizontal IP-based Discovery, and you can also use push-based Discovery.")  
**Related reference**   

* [Microsoft Azure Cloud discovery using patterns](https://www.servicenow.com/docs/5NmnHdhD8h3YVHs729mwBw "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.")  
**Related topics**   

* [Service Graph Connector for Microsoft Azure](https://www.servicenow.com/docs/access?context=cmdb-integration-azure&version=zurich&pubname=zurich-servicenow-platform&ft:locale=en-US)