---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/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


---

# Microsoft Azure Cloud components

# Microsoft Azure Cloud components discovery using patterns {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 17 minutes to read

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.

## Request new or enhanced Patterns on the ServiceNow® Store {#azure-cloud-discovery-patterns__id_ztn_lkb_5yb}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/application/06a71b1367e4130051c9027e2685ef1e/1.6.0?referer=/store/search?listingtype=allintegrations%253Bancillary_app%253Bcertified_apps%253Bcontent%253Bindustry_solution%253Boem%253Butility%253Btemplate&q=Patterns&sl=sh) to view all the available updates 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-cloud-discovery-patterns__p_d21_nfg_h1c}

## Prerequisites {#azure-cloud-discovery-patterns__section_gwn_lwv_pnb}

Verify that the applications are up to date.
:
    * Discovery and Service Mapping Patterns
    * CMDB CI Class Models
    * Visibility Content
    {#azure-cloud-discovery-patterns__ul_aln_qlb_5yb}

Activate the cloud-related CI relationships
:   To include discovered components into service instances, enable CI relationships used in tag-based discovery by Service Mapping. These CI relationships are available from the 1.0.68 release on the ServiceNow Store. For operational steps, see [Tag-based discovery configuration](https://servicenow-prod.fluidtopics.net/WMqYQ9cztLwkmoyPJWnmIw "You can refine the default configuration to control which CIs Service Mapping includes in application services during the tag-based discovery process.").

Azure Availability Set
:   Wait for the Clean-Up job for Availability zone to clear availability set record schedule job to delete all the pre-populated availability set's Configuration Items (CI) in the
    cmdb_ci_azure_availability_set table.

Azure Availability Zone

:   To run a discovery with Azure Availability Zone, register the subscription ID to the AvailabilityZonePeering feature with AZ CLI using `az feature register -n AvailabilityZonePeering
    --namespace Microsoft.Resources` to use the Check Zone Peering API. Check the status with `az feature show -n AvailabilityZonePeering --namespace Microsoft.Resources` before running
    discovery.

Set up Azure service accounts
:   Enable Cloud Discovery to access your Azure environment. For more information, see [Set up Azure service accounts](https://servicenow-prod.fluidtopics.net/wA59_lRoV_0PzpuODHnNjA "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-cloud-discovery-patterns__set-up-service-account-azure-ph}

Create an Azure cloud discovery schedule
:   For more information, see [Create an Azure Discovery schedule in Discovery Admin Workspace](https://servicenow-prod.fluidtopics.net/Anu8TAbvH~Y2JYJPHfEacg "Use the Discovery Admin Workspace dashboard to create an Azure Discovery schedule.").

(Optional) Populate Service Account and Logical Datacenter fields in cloud CIs
:   Starting with Discovery and Service Mapping Patterns version 1.30.2, you can improve query performance by populating Service Account and Logical Datacenter fields directly in cloud CIs. For more information, see [Improved query performance with direct field population in CI tables](https://servicenow-prod.fluidtopics.net/H_wfVmrRA2K_BT9VRkb6iQ "The Populate Service Account and LDC IN CMDB scheduled job populates the Service Account and Logical Datacenter fields in cloud configuration item (CI) tables, and the Virtual Machine Object field in the Hardware [cmdb_ci_hardware] table. This direct population reduces query complexity and improves query performance.").

## Verify the REST API Permissions {#azure-cloud-discovery-patterns__id_ej5_btw_1dc}

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-cloud-discovery-patterns__cloud-discovery-api-paragraph}

## Azure resources discovery by datacenters {#azure-cloud-discovery-patterns__section_ifx_fkg_cbc}

Azure has multiple datacenters around the world, but resources like load balancers and virtual machines are typically deployed in only some of them. The Azure Datacenter Discovery
pattern executes before all other Azure patterns to identify the datacenters that have resources related to your service account ("active") and the datacenters that don't have your resources ("passive"). This model improves the performance
of the Azure discovery. This execution model is more efficient than the
previous one, in which all datacenters were discovered regardless of having relevant resources in them.

After identifying the "active" and "passive" datacenters, the Discovery schedule continues to execute all Azure patterns only for the "active" datacenters, to discover your Azure cloud resources. The "passive" datacenters are ignored while running the schedule.

You might notice differences in Azure discovery log, in discovery time and in the CMDB, depending on the service account and MID Server property settings.

Datacenters that have already been discovered before the upgrade to
Discovery and Service Mapping Patterns version 1.15.0, remain in the Azure Datacenters
table. However, the discovery runtime behavior is now
determined by the value of the MID Server property mid.cloud.discovery.sonar.discover_all_azure_datacenters. The property is set to false by default, to limit the discovery
execution to the "active" datacenters, rather than all datacenters. You can discover all datacenters for a service account, including "passive" ones, by setting the property to true. For more information,
see: [Create a MID Server property](https://www.servicenow.com/docs/access?context=r_MIDServerProperties&version=yokohama&pubname=yokohama-servicenow-platform&section=t_SetMIDServerProperties&ft:locale=en-US).

If the MID Server property is set to false, the Azure Datacenters table shows only active datacenters. All other behaviors remain unchanged from previous Discovery and Service Mapping Patterns versions.  
{#azure-cloud-discovery-patterns__table_wzt_31d_dhc__entry__5}

| Discovery and Service Mapping Patterns version | MID Server property setting | Discovered datacenters | Datacenters contained in Azure Datacenters table | Datacenters displayed in discovery log |
|-|-|-|-|-|
| Discovery and Service Mapping Patterns starting with version 1.15.0 | False (default) | Active only | Active only | Active only |
| Discovery and Service Mapping Patterns starting with version 1.15.0 | True | All datacenters | All datacenters | All datacenters |
| Discovery and Service Mapping Patterns before version 1.15.0 | False (default) | Active only | All datacenters | Active only |
| Discovery and Service Mapping Patterns before version 1.15.0 | True | All datacenters | All datacenters | All datacenters |
[Table 1. Differences in datacenter discovery by Discovery and Service Mapping Patterns version]

{#azure-cloud-discovery-patterns__table_wzt_31d_dhc}

For management groups, Azure
Cloud Discovery discovers all Azure datacenters.

Starting with Discovery and Service Mapping Patterns version 1.29.0, the Refresh Datacenters flow displays all regions, not just active ones. You don't need to create another schedule when a resource is added
or a datacenter switches from passive to active.

## Azure Hardware Type discovery {#azure-cloud-discovery-patterns__section_jmd_5bv_1bc}

Hardware Type discovery has undergone three model changes in recent years. The 1.15.0 model triggers the Hardware Type pattern and the Virtual Machine pattern after the Azure Datacenter Discovery pattern. Starting Discovery and Service Mapping Patterns plugin version 1.15.0, Cloud Discovery identifies which Hardware Type model is used, and launches only one of the two patterns: Hardware Type (LP) or Cloud Hardware Type (LP).{#azure-cloud-discovery-patterns__table_gml_tkv_1bc__entry__4}

| Discovery and Service Mapping Patterns version | Hardware Type Migration status | Which pattern executes | Discovery result |
|-|-|-|-|
| Prior to 1.0.75 | Haven't migrated to the new model | Hardware Type (LP) pattern | The CI type created: \[cmdb_ci_compute_template\] |
| Discovery and Service Mapping Patterns version 1.0.75 | The migration to the new model is done by migration script. See [KB0955939](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0955939) | Hardware Type (LP) pattern | The CI type created: \[cmdb_ci_cloud_hardware_type\] |
| Discovery and Service Mapping Patterns version 1.6.0 | The Hardware Type new model is provided OOB, enabled with the system property: sn_itom_pattern.use a single hardware type for cloud datacenters. For more information, see[KB1285337](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1285337). | According to [KB1285337](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1285337) Flow Diagram | The CI type created: According to [KB1285337](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1285337) |
| Discovery and Service Mapping Patterns 1.15.0 | The Hardware Type new model is provided OOB enabled with the system property: sn_itom_pattern.use a single hardware type for cloud datacenters. For more information, see[KB1285337](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1285337). | The flow is as described in [KB1285337](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1285337). However, only one pattern executes. The pattern that used to gracefully terminate doesn't execute. | Either Hardware Type (LP) pattern or Cloud Hardware Type (LP) pattern executes. |
[Table 2. Migration to the Azure Hardware Type discovery model- Use cases]

{#azure-cloud-discovery-patterns__table_gml_tkv_1bc}

## Azure SQL Managed Instance license discovery {#azure-cloud-discovery-patterns__section_ulz_51b_wbc}

The Azure DataBase (LP) pattern extension Azure SQL Managed Instance license discovers Azure SQL Managed Instance license information and populates the license type in the Key Value \[cmdb_key_value\] table of Cloud Database CI \[cmdb_ci_cloud_database\].

Required plugins and applications
:
    * Software Asset Management Professional for Microsoft
    * Visibility Content
    {#azure-cloud-discovery-patterns__ul_sw3_1db_wbc}

Discovered resources and relationships
:   [Resources discovered using the Azure DataBase (LP) pattern extension: Azure SQL Managed Instance license](https://servicenow-prod.fluidtopics.net/JeDZ0tlC9eLF5fei5qSv3w#azure-cloud-discovery-patterns__resources-azure-sql-managed-instance-license)
:   [Relationships discovered using the Azure DataBase (LP) pattern extension: Azure SQL Managed Instance license](https://servicenow-prod.fluidtopics.net/JeDZ0tlC9eLF5fei5qSv3w#azure-cloud-discovery-patterns__relationships-azure-sql-managed-instance-license)

## Azure Marketplace discovery {#azure-cloud-discovery-patterns__section_g5b_gdg_xcc}

The Azure - Marketplace LB (LP) pattern discovers the following Azure Marketplace products:

* SaaS
* Azure Application
* Virtual Machine  
  Note:  
  The pattern discovers only virtual machines (VMs) created from third-party or commercial marketplace images.
{#azure-cloud-discovery-patterns__ul_iz3_d2g_xcc}

Discovered resources and relationships
:   [Resources discovered by the Azure - Marketplace LB (LP) pattern](https://servicenow-prod.fluidtopics.net/JeDZ0tlC9eLF5fei5qSv3w#azure-cloud-discovery-patterns__resources-azure-marketplace)
:   [Relationships discovered using the Azure - Marketplace LB (LP) pattern](https://servicenow-prod.fluidtopics.net/JeDZ0tlC9eLF5fei5qSv3w#azure-cloud-discovery-patterns__relationships-azure-marketplace)

## Data collected by Discovery during horizontal discovery {#azure-cloud-discovery-patterns__section_rjp_pcl_rnb}

Resources discovered by the Microsoft Azure - Resource Group (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_esx_pdl_rnb__entry__2}

    | Field | Description |
    |-|-|
    | Object ID \[object_id\] | A unique identifier, allocated by Microsoft Azure for this resource. |
    | Name \[name\] | The Name or ID if no Name is specified for the resource group. |
    | Location \[location\] | Path of the resource group. |
    | State \[state\] | The current state of the resource group. |
    | Install Status \[install_status\] | Resource provisioning status. |
    [Table 3. Resource Group \[cmdb_ci_resource_group\]]

    {#azure-cloud-discovery-patterns__table_esx_pdl_rnb}

Resources discovered by the Microsoft Azure - Route Table (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_mxj_qdl_rnb__entry__2}

    | Field | Description |
    |-|-|
    | Object ID \[object_id\] | A unique identifier, allocated by Microsoft Azure for this resource. |
    | Name \[name\] | The Name or ID if no Name is specified for the route table. |
    | Location \[location\] | Path of the route table. |
    | Install Status \[install_status\] | Resource provisioning status. |
    | State \[state\] | The current state of the route table. |
    [Table 4. Route Table \[cmdb_ci_route_table\]]

    {#azure-cloud-discovery-patterns__table_mxj_qdl_rnb}

Resources discovered by the Microsoft Azure - Security Group (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_dyq_qdl_rnb__entry__2}

    | Field | Description |
    |-|-|
    | Object ID \[object_id\] | A unique identifier, allocated by Microsoft Azure for this resource. |
    | Name \[name\] | The Name or ID if no Name is specified for the security group. |
    | Location \[location\] | Path of the security group. |
    | State \[state\] | The current state of the security group. |
    | Install Status \[install_status\] | Resource provisioning status. |
    [Table 5. Compute Security Group \[cmdb_ci_compute_security_group\]]

    {#azure-cloud-discovery-patterns__table_dyq_qdl_rnb}

Resources discovered by the Microsoft Azure - SQL Server (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_eh3_3pt_vnb__entry__2}

    | Field | Description |
    |-|-|
    | Object ID \[object_id\] | A unique identifier, allocated by Microsoft Azure for this resource. |
    | Location \[location\] | Path of the VM instance. |
    [Table 6. Virtual Machine Instance \[cmdb_ci_vm_instance\]]

    {#azure-cloud-discovery-patterns__table_eh3_3pt_vnb}

    {#azure-cloud-discovery-patterns__table_x1d_tw1_23c__entry__2}

    | Field | Description |
    |-|-|
    | Key \[key\] | Server_License_Type_automatic |
    | Value \[value\] | The value is one of the following options: * Azure Hybrid Benefit: BYOL * Pay-as-you-go licensing: License Included {#azure-cloud-discovery-patterns__ul_value_options} |
    | Configuration item \[configuration_item\] | References the Virtual Machine Instance \[cmdb_ci_vm_instance\] table. |
    [Table 7. Key Value \[cmdb_key_value\]]

    {#azure-cloud-discovery-patterns__table_x1d_tw1_23c}

Resources discovered by the Microsoft Azure - Storage Account (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_ppy_qdl_rnb__entry__2}

    | Field | Description |
    |-|-|
    | Object ID \[object_id\] | A unique identifier, allocated by Microsoft Azure for this resource. |
    | Name \[name\] | The Name or ID if no Name is specified for the storage account. |
    | Location \[location\] | Path of the storage account. |
    | Sku Name \[sku_name\] | The name of the stock keeping unit (SKU) for backup frequency. |
    | Install Status \[install_status\] | Resource provisioning status. |
    | State \[state\] | The current state of the storage account. |
    [Table 8. Cloud Storage Account \[cmdb_ci_cloud_storage_account\]]

    {#azure-cloud-discovery-patterns__table_ppy_qdl_rnb}

Resources discovered by the Microsoft Azure - Storage Containers (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_gll_rdl_rnb__entry__2}

    | Field | Description |
    |-|-|
    | Name \[name\] | The name of the storage container. |
    | Object ID \[object_id\] | A unique identifier for the storage container. |
    | Comments \[comments\] | Identifier for internal usage (deletion strategy). |
    | Install Status \[install_status\] | Resource provisioning status. |
    [Table 9. Storage Container \[cmdb_ci_storage_container\]]

    {#azure-cloud-discovery-patterns__table_gll_rdl_rnb}

Resources discovered by the Microsoft Azure - Storage Volume (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_nps_rdl_rnb__entry__2}

    | Field | Description |
    |-|-|
    | Object ID \[object_id\] | A unique identifier, allocated by Microsoft Azure for this resource. |
    | Name \[name\] | The Name or ID if no Name is specified for the storage volume. |
    | Volume ID \[volume_id\] | The volume type. For example: * <kbd class="ph userinput">gp2</kbd> for General Purpose SSD * <kbd class="ph userinput">io1</kbd> for Provisioned IOPS SSD * <kbd class="ph userinput">st1</kbd> for Throughput Optimized HDD * <kbd class="ph userinput">sc1</kbd> for Cold HDD * <kbd class="ph userinput">standard</kbd> for Magnetic volumes {#azure-cloud-discovery-patterns__ul_rjg_jfp_xnb} |
    | Location \[location\] | Path of the storage volume. |
    | State \[state\] | The current state of the storage volume. |
    | Install Status \[install_status\] | Resource provisioning status. |
    | Size \[size\] | The size of the volume. |
    | Size bytes \[size_bytes\] | The size of the volume in bytes. |
    | Storage type \[storage_type\] | For example, hard-coded value "block". |
    | Comments \[comments\] | Identifier for internal usage (deletion strategy). |
    [Table 10. Storage Volume \[cmdb_ci_storage_volume\]]

    {#azure-cloud-discovery-patterns__table_nps_rdl_rnb}

Resources discovered by the Microsoft Azure - Sub Account (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_dmy_rdl_rnb__entry__2}

    | Field | Description |
    |-|-|
    | Object ID \[object_id\] | A unique identifier, allocated by Microsoft Azure for this resource. |
    | Account Id \[account_id\] | The unique identifier (ID) of the account. |
    | Name \[name\] | The Name or ID if no Name is specified for the service account. |
    | Datacenter Type \[datacenter_type\] | cmdb_ci_azure_datacenter |
    | Discovery credentials \[discovery_credentials\] | Reference field to the related Microsoft Azure credentials. |
    | Datacenter URL \[datacenter_url\] | The URL of the datacenter. |
    | Parent account \[parent_account\] | Reference to the primary account, if it exists. |
    | Is management account \[is_master_account\] | The Boolean attribute indicating if this is the primary account or not. |
    [Table 11. Cloud Service Account \[cmdb_ci_cloud_service_account\]]

    {#azure-cloud-discovery-patterns__table_dmy_rdl_rnb}

Resources discovered by the Microsoft Azure WebSite (LP) pattern and Microsoft Azure WebSite pattern
:
    {#azure-cloud-discovery-patterns__table_zgm_xdc_zwb__entry__2}

    | Field | Description |
    |-|-|
    | Name \[name\] | The name of the Azure web server. |
    | Object ID \[object_id\] | The ID of the Azure web server. |
    | IP Address \[ip_address\] | The IP address of the web server. |
    | Fully qualified domain name \[fqdn\] | The fully qualified domain name (FQDN) of the web server. |
    | Vendor \[vendor\] | The vendor is Microsoft. |
    | Install Status \[install_status\] | The install status of the web server. |
    | State \[state\] | The operational state of the web server. |
    | Operational status \[operational_status\] | The operational status of the web server. |
    [Table 12. Cloud WebServer \[cmdb_ci_cloud_webserver\]]

    {#azure-cloud-discovery-patterns__table_zgm_xdc_zwb}

    {#azure-cloud-discovery-patterns__table_zgm_xdc_zwb_ip__entry__2}

    | Field | Description |
    |-|-|
    | Name \[name\] | The IP address of the web server. |
    | IP Address \[ip_address\] | The IP address of the web server. |
    | Fully qualified domain name \[fqdn\] | The fully qualified domain name (FQDN). |
    | Vendor \[vendor\] | The vendor is Microsoft. |
    | Install Status \[install_status\] | The install status. |
    | Operational status \[operational_status\] | The operational status. |
    [Table 13. IP Address \[cmdb_ci_ip_address\]]

    {#azure-cloud-discovery-patterns__table_zgm_xdc_zwb_ip}

Resources discovered using the Azure DataBase (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_ikx_tgf_xcc__entry__2}

    | Field | Description |
    |-|-|
    | Fully qualified domain name \[fqdn\] | The FQDN that Microsoft Azure assigned to your database. |
    | Name \[name\] | The name of the database that you created in Microsoft Azure. |
    | Object ID \[object_id\] | The identification name of the database. |
    | Operational Status \[operational_status\] | The operational status of the database. |
    | Type \[type\] | The type of database you created. |
    | State \[state\] | The state of the database: Whether it's Available or Terminated. |
    | Vendor \[vendor\] | The vendor name is Azure. |
    | Version \[version\] | The version of the database. |
    | Category \[category\]\* | The stock keeping unit (SKU) family. |
    [Table 14. Cloud DataBase \[cmdb_ci_cloud_database\]]

    {#azure-cloud-discovery-patterns__table_ikx_tgf_xcc}\* Populated only by the Azure SQL Managed Instance license pattern extension. For more information, see the "Azure SQL Managed Instance license discovery" section.

    {#azure-cloud-discovery-patterns__table_tx2_xhf_xcc__entry__2}

    | Field | Description |
    |-|-|
    | Object ID \[object_id\] | A unique identifier for the hardware type. |
    | Name \[name\] | Name for the hardware type. |
    | vCPUs \[vcpus\] | Number of virtual CPU cores. |
    | Provider \[provider\] | Provider for the hardware type: Azure. |
    [Table 15. Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\]]

    {#azure-cloud-discovery-patterns__table_tx2_xhf_xcc}

    {#azure-cloud-discovery-patterns__table_wzj_jjf_xcc__entry__2}

    | Field | Description |
    |-|-|
    | Netmask \[netmask\] | Netmask of the Azure database. |
    [Table 16. IP Address \[cmdb_ci_ip_address\]]

    {#azure-cloud-discovery-patterns__table_wzj_jjf_xcc}

Resources discovered using the Azure DataBase (LP) pattern extension: Azure SQL Managed Instance license{#azure-cloud-discovery-patterns__resources-azure-sql-managed-instance-license}
:
    {#azure-cloud-discovery-patterns__table_jbc_kwd_zbc__entry__2}

    | Field | Description |
    |-|-|
    | Key \[key\] | SQL_Server_PaaS_Managed_Instance_License_Type_automatic |
    | Value \[value\] | License type. The following maps the Azure portal license to ServiceNow values: * Azure Hybrid Benefit: BYOL * Pay as you go: License Included * Hybrid Failover rights: Hybrid Failover {#azure-cloud-discovery-patterns__ul_kbc_kwd_zbc} |
    | Configuration item \[configuration_item\] | References the Cloud DataBase \[cmdb_ci_cloud_database\] table. |
    [Table 17. Key Value \[cmdb_key_value\]]

    {#azure-cloud-discovery-patterns__table_jbc_kwd_zbc}

    {#azure-cloud-discovery-patterns__table_kwc_wh2_xbc__entry__2}

    | Field | Description |
    |-|-|
    | Object ID \[object_id\] | Object ID of the Azure cloud database. |
    | Name \[name\] | SKU name. |
    | Cloud Vendor \[cloud_vendor\] | Cloud vendor of the serverless hardware: MS Azure. |
    | CPU core count \[cpu_core_count\] | Number of virtual cores (vCores). |
    | CPU core thread \[cpu_core_thread\] | Number of vCores. |
    | CPU count \[cpu_count\] | Number of vCores. |
    | Category \[category\] | vCore purchasing model. |
    | Subcategory \[subcategory\] | SKU tier. |
    | Host Type \[host_type\] | Host type: PaaS. |
    [Table 18. Serverless Hardware \[cmdb_ci_serverless_hardware\]]

    {#azure-cloud-discovery-patterns__table_kwc_wh2_xbc}

Resources discovered by the Azure - Marketplace LB (LP) pattern{#azure-cloud-discovery-patterns__resources-azure-marketplace}

:   The Azure - Marketplace LB (LP) pattern introduces the following CI class that extends an existing CMDB class.

    {#azure-cloud-discovery-patterns__table_extends_marketplace__entry__2}

    | CI class | Extends from |
    |-|-|
    | Deployed Marketplace Product \[cmdb_ci_deployed_marketplace_product\] | Virtual Machine Object \[cmdb_ci_vm_object\] |
    [Table 19. CI class introduced by this pattern]

    {#azure-cloud-discovery-patterns__table_extends_marketplace}  
    {#azure-cloud-discovery-patterns__table_os5_tgg_xcc__entry__2}

    | Field | Description |
    |-|-|
    | Name \[name\] | Name of the Cloud resource, usually the marketplace offering or SKU name. |
    | Object ID \[object_id\] | A unique resource ID of the Cloud resource. |
    | Resource Type \[resource_type\] | Service in Cloud Marketplace. For example: microsoft.compute/virtualmachines. |
    | Plan Name \[plan_name\] | Billing or SKU plan for a resource from the Cloud Marketplace. For example: Pay as You Go. |
    | Market \[market\] | International Organization for Standardization (ISO) code of the geographical market where the resource is sold. For example: US or EU. |
    | Organization Id \[organization_id\] | A unique identifier for the organization or publisher that owns the marketplace resource. |
    [Table 20. Deployed Marketplace Product \[cmdb_ci_deployed_marketplace_product\]]

    {#azure-cloud-discovery-patterns__table_os5_tgg_xcc}  
    {#azure-cloud-discovery-patterns__table_phz_qgg_xcc__entry__2}

    | Field | Description |
    |-|-|
    | Product Code \[product_code\] | A unique product code of the resource within the Cloud Marketplace. |
    | Publisher Name \[publisher_name\] | Organization or individual responsible for creating and offering the product or service. |
    | Version \[version\] | Release number or iteration of the product. |
    | Deployed On \[deployed_on\] | References the Deployed Marketplace Product \[cmdb_ci_deployed_marketplace_product\] table. |
    [Table 21. Marketplace Product Details \[marketplace_product_details\]]

    {#azure-cloud-discovery-patterns__table_phz_qgg_xcc}

Resources discovered by the Azure - Sub Account (LP) pattern extension: Azure Management Groups

:   The Azure - Sub Account (LP) pattern extension introduces the following CI class that extends an existing CMDB class.

    {#azure-cloud-discovery-patterns__table_extends_mgmt_group__entry__2}

    | CI class | Extends from |
    |-|-|
    | Azure Management Group \[cmdb_ci_azure_management_group\] | Cloud Account Group \[cmdb_ci_cloud_account_group\] |
    [Table 22. CI class introduced by this pattern]

    {#azure-cloud-discovery-patterns__table_extends_mgmt_group}  
    {#azure-cloud-discovery-patterns__table_rwt_pws_p2c__entry__2}

    | Field | Description |
    |-|-|
    | Name \[name\] | Tenant ID or name. * Tenant ID: When using management-level credentials * Tenant name: When using tenant-level credentials {#azure-cloud-discovery-patterns__ul_a54_dkm_s2c} |
    | Object ID \[object_id\] | Tenant ID. |
    | DNS Domain \[dns_domain\] | Domain name entered during registration. For example: <kbd class="ph userinput">servicenow.com</kbd>. This field is only populated when using tenant-level credentials. |
    [Table 23. Cloud Organizations \[cmdb_ci_cloud_org\]]

    {#azure-cloud-discovery-patterns__table_rwt_pws_p2c}  
    {#azure-cloud-discovery-patterns__table_f3n_vws_p2c__entry__2}

    | Field | Description |
    |-|-|
    | Name \[name\] | Management group name. |
    | Object ID \[object_id\] | Management group name and tenant ID in the following format: <kbd class="ph userinput">name+@+tenantId</kbd>. For example: <kbd class="ph userinput">itomMgmtGroup@8bcff-vdc-btrv</kbd>. |
    | Parent \[parent\] | References the direct parent Azure Management Group \[cmdb_ci_azure_management_group\] table. |
    [Table 24. Azure Management Group \[cmdb_ci_azure_management_group\]]

    {#azure-cloud-discovery-patterns__table_f3n_vws_p2c}

## CI relationships {#azure-cloud-discovery-patterns__section_ulx_mh2_tnb}

The Microsoft Azure patterns create the following relationships and references to support Microsoft Azure discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table.

Relationships discovered using the Microsoft Azure - Resource Group (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_fxb_qj2_tnb__entry__3}

    | CI | Relationship | CI |
    |-|-|-|
    | Azure Datacenter \[cmdb_ci_azure_datacenter\] | Contains::Contained by | Resource Group \[cmdb_ci_resource_group\] |
    [Table 25. CI relationships]

    {#azure-cloud-discovery-patterns__table_fxb_qj2_tnb}

Relationships discovered using the Microsoft Azure - Route Table (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_hsd_qj2_tnb__entry__3}

    | CI | Relationship | CI |
    |-|-|-|
    | Route Table \[cmdb_ci_route_table\] | Contains::Contained by | Route \[cmdb_ci_route\] |
    | Route Table \[cmdb_ci_route_table\] | Contains::Contained by | Cloud Network \[cmdb_ci_network\] |
    | Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Route Table \[cmdb_ci_route_table\] |
    | Azure Datacenter \[cmdb_ci_azure_datacenter\] | Contains::Contained by | Route Table \[cmdb_ci_route_table\] |
    [Table 26. CI relationships]

    {#azure-cloud-discovery-patterns__table_hsd_qj2_tnb}

Relationships discovered using the Microsoft Azure - Security Group (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_v3f_qj2_tnb__entry__3}

    | CI | Relationship | CI |
    |-|-|-|
    | Cloud Subnet \[cmdb_ci_cloud_subnet\] | Uses::Used by | Compute Security Group \[cmdb_ci_compute_security_group\] |
    | Cloud Network \[cmdb_ci_network\] | Contains::Contained by | Compute Security Group \[cmdb_ci_compute_security_group\] |
    | Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Compute Security Group \[cmdb_ci_compute_security_group\] |
    | Compute Security Group \[cmdb_ci_compute_security_group\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
    [Table 27. CI relationships]

    {#azure-cloud-discovery-patterns__table_v3f_qj2_tnb}

Relationships discovered using the Microsoft Azure - Storage Account (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_t1h_qj2_tnb__entry__3}

    | CI | Relationship | CI |
    |-|-|-|
    | Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud Storage Account \[cmdb_ci_cloud_storage_account\] |
    | Cloud Storage Account \[cmdb_ci_cloud_storage_account\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
    [Table 28. CI relationships]

    {#azure-cloud-discovery-patterns__table_t1h_qj2_tnb}

Relationships discovered using the Microsoft Azure - Storage Containers (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_rq3_qj2_tnb__entry__3}

    | CI | Relationship | CI |
    |-|-|-|
    | Block Endpoint \[cmdb_ci_endpoint_block\] | Implement End Point To::Implement End Point From | Storage Volume \[cmdb_ci_storage_volume\] |
    | Cloud Storage Account \[cmdb_ci_cloud_storage_account\] | Contains::Contained by | Storage Volume \[cmdb_ci_storage_volume\] |
    | Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Storage Volume \[cmdb_ci_storage_volume\] |
    | Storage Volume \[cmdb_ci_storage_volume\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
    [Table 29. CI relationships]

    {#azure-cloud-discovery-patterns__table_rq3_qj2_tnb}

Relationships discovered using the Microsoft Azure - Storage Volume (LP) pattern
:
    {#azure-cloud-discovery-patterns__table_g2k_qj2_tnb__entry__3}

    | CI | Relationship | CI |
    |-|-|-|
    | Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Storage Volume \[cmdb_ci_storage_volume\] |
    | Storage Volume \[cmdb_ci_storage_volume\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
    [Table 30. CI relationships]

    {#azure-cloud-discovery-patterns__table_g2k_qj2_tnb}

Relationships discovered using the Microsoft Azure - Sub Account (LP) pattern
:   The Microsoft Azure - Sub Account (LP) pattern does not discover any relationships.

Relationships discovered using the Microsoft Azure WebSite (LP) and Microsoft Azure WebSite patterns
:
    {#azure-cloud-discovery-patterns__table_bkb_mhc_zwb__entry__3}

    | CI | Relationship | CI |
    |-|-|-|
    | Cloud WebServer \[cmdb_ci_cloud_webserver\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
    | Cloud WebServer \[cmdb_ci_cloud_webserver\] | Owns::Owned by | IP Address \[cmdb_ci_ip_address\] |
    [Table 31. CI relationships]

    {#azure-cloud-discovery-patterns__table_bkb_mhc_zwb}
    {#azure-cloud-discovery-patterns__table_ci_references_website__entry__3}

    | CI | Field | Referenced CI |
    |-|-|-|
    | Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | Cloud WebServer \[cmdb_ci_cloud_webserver\] |
    [Table 32. CI references]

    {#azure-cloud-discovery-patterns__table_ci_references_website}

Relationships discovered using the Azure DataBase (LP) Pattern.
:
    {#azure-cloud-discovery-patterns__table_ipf_hgf_xcc__entry__3}

    | CI | Relationship | CI |
    |-|-|-|
    | Cloud DataBase \[cmdb_ci_cloud_database\] | Owns::Owned by | IP Address \[cmdb_ci_ip_address\] |
    | Cloud DataBase \[cmdb_ci_cloud_database\] | Contains::Contained by | Database \[cmdb_ci_database\] |
    | Cloud DataBase \[cmdb_ci_cloud_database\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
    | Database \[cmdb_ci_database\] | Provisioned From::Provisioned | Compute Template \[cmdb_ci_compute_template\] |
    | Database \[cmdb_ci_database\] | Provisioned From::Provisioned | Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] |
    | Compute Template \[cmdb_ci_compute_template\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
    | Compute Template \[cmdb_ci_compute_template\] | Hosted on::Hosts | Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] |
    [Table 33. CI relationships]

    {#azure-cloud-discovery-patterns__table_ipf_hgf_xcc}

Relationships discovered using the Azure DataBase (LP) pattern extension: Azure SQL Managed Instance license{#azure-cloud-discovery-patterns__relationships-azure-sql-managed-instance-license}
:
    {#azure-cloud-discovery-patterns__table_zk5_tgb_wbc__entry__3}

    | CI | Relationship | CI |
    |-|-|-|
    | Cloud DataBase \[cmdb_ci_cloud_database\] | Runs on::Runs | Serverless Hardware \[cmdb_ci_serverless_hardware\] |
    | Serverless Hardware \[cmdb_ci_serverless_hardware\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
    [Table 34. CI relationships]

    {#azure-cloud-discovery-patterns__table_zk5_tgb_wbc}

    {#azure-cloud-discovery-patterns__table_ci_references_sql_managed__entry__3}

    | CI | Field | Referenced CI |
    |-|-|-|
    | Key Value \[cmdb_key_value\] | Configuration item \[configuration_item\] | Cloud DataBase \[cmdb_ci_cloud_database\] |
    [Table 35. CI references]

    {#azure-cloud-discovery-patterns__table_ci_references_sql_managed}

Relationships discovered using the Azure - Marketplace LB (LP) pattern{#azure-cloud-discovery-patterns__relationships-azure-marketplace}
:
    {#azure-cloud-discovery-patterns__table_tby_t2g_xcc__entry__3}

    | CI | Relationship | CI |
    |-|-|-|
    | Deployed Marketplace Product \[cmdb_ci_deployed_marketplace_product\] | Hosted on::Hosts | Cloud Service Account \[cmdb_ci_cloud_service_account\] |
    | Deployed Marketplace Product \[cmdb_ci_deployed_marketplace_product\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
    | Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Deployed Marketplace Product \[cmdb_ci_deployed_marketplace_product\] |
    [Table 36. CI relationships]

    {#azure-cloud-discovery-patterns__table_tby_t2g_xcc}

    {#azure-cloud-discovery-patterns__table_ci_references_marketplace__entry__3}

    | CI | Field | Referenced CI |
    |-|-|-|
    | Marketplace Product Details \[marketplace_product_details\] | Deployed On \[deployed_on\] | Deployed Marketplace Product \[cmdb_ci_deployed_marketplace_product\] |
    [Table 37. CI references]

    {#azure-cloud-discovery-patterns__table_ci_references_marketplace}

Relationships discovered using the Azure - Sub Account (LP) pattern extension: Azure Management Groups
:
    {#azure-cloud-discovery-patterns__table_ypx_3xs_p2c__entry__3}

    | CI | Relationship | CI |
    |-|-|-|
    | Azure Management Group \[cmdb_ci_azure_management_group\] | Contains::Contained by | Cloud Service Account \[cmdb_ci_cloud_service_account\] |
    | Cloud Organizations \[cmdb_ci_cloud_org\] | Contains::Contained by | Azure Management Group \[cmdb_ci_azure_management_group\] |
    | Azure Management Group \[cmdb_ci_azure_management_group\] | Contains::Contained by | Azure Management Group \[cmdb_ci_azure_management_group\] |
    [Table 38. CI relationships]

    {#azure-cloud-discovery-patterns__table_ypx_3xs_p2c}

    {#azure-cloud-discovery-patterns__table_ci_references_mgmt_groups__entry__3}

    | CI | Field | Referenced CI |
    |-|-|-|
    | Azure Management Group \[cmdb_ci_azure_management_group\]\* | Parent \[parent\] | Azure Management Group \[cmdb_ci_azure_management_group\] |
    [Table 39. CI references]

    {#azure-cloud-discovery-patterns__table_ci_references_mgmt_groups}\*Only references the direct parent-child management group relationship.

## Events discovered by Discovery during horizontal discovery {#azure-cloud-discovery-patterns__section_dkp_pld_tnb}

Discovery uses patterns to find events created for Microsoft Azure components. If there are events that indicate the change of state in one of the Microsoft Azure components, it triggers the discovery of Microsoft Azure components using the patterns.
{#azure-cloud-discovery-patterns__table_gg2_ymd_tnb__entry__2}

| Pattern | CI Class |
|-|-|
| Azure Application LB Event | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] |
| Azure Availability Set Event | Availability Set \[cmdb_ci_availability_set\] |
| Azure Classic LB Event | Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\] |
| Azure DataBase Event | Cloud DataBase \[cmdb_ci_cloud_database\] |
| Azure Express Route Circuit Event | Cloud Direct Connect \[cmdb_ci_cloud_direct_connect\] |
| Azure Functions Event | Cloud Function \[cmdb_ci_cloud_function\] |
| Azure Local Network Gateway Event | Virtual Private Gateway \[cmdb_ci_virtual_pvt_gateway\] |
| Azure NAT Gateway Event | NAT Gateway \[cmdb_ci_nat_gateway\] |
| Azure Network Event | Cloud Network \[cmdb_ci_network\] |
| Azure NIC Event | Cloud Mgmt Network Interface \[cmdb_ci_nic\] |
| Azure Private DNS Zone Event | DNS Zone \[cmdb_ci_dns_zone\] |
| Azure Public IP Event | Cloud Public IP Address \[cmdb_ci_cloud_public_ipaddress\] |
| Azure Resource Group Event | Resource Group \[cmdb_ci_resource_group\] |
| Azure Security Group Event | Compute Security Group \[cmdb_ci_compute_security_group\] |
| Azure Storage Account Event | Cloud Storage Account \[cmdb_ci_cloud_storage_account\] |
| Azure Virtual Machine Event | Virtual Machine Instance \[cmdb_ci_vm_instance\] |
| Azure Virtual Network Gateway Connection Event | Virtual Network Gateway Connection \[cmdb_ci_vpc_gateway_connection\] |
| Azure Virtual Network Peerings Event | Virtual Network Peering \[cmdb_ci_vnet_peering\] |
| Azure VM Scale Set Event | Instance Scale Set \[cmdb_ci_instance_scale_set\] |
[Table 40. Patterns used for event discovery]

{#azure-cloud-discovery-patterns__table_gg2_ymd_tnb}

## Tag information collected by Discovery during horizontal discovery {#azure-cloud-discovery-patterns__section_lv5_14d_tpb}

When running the patterns, tag information is collected to populate the cmdb_key_value table.​ Each tag is related to a CI that was discovered during the discovery.​ Tag discovery is done in the extension section of each
pattern.

## Data collected by Service Mapping during tag-based discovery {#azure-cloud-discovery-patterns__section_dsx_jty_qpb}

Service Mapping uses tag-based discovery to create service instance maps including the Cloud components. The Service Mapping application comes with the following preconfigured CI relationships used for tag-based discovery. These CI relationships are available from the 1.0.68 release on the ServiceNow Store. {#azure-cloud-discovery-patterns__id_yqp_xhy_qpb__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Configuration Item \[cmdb_ci\] | Hosted on::Hosts | Logical Datacenter \[cmdb_ci_logical_datacenter\] |
| Logical Datacenter \[cmdb_ci_logical_datacenter\] | Hosted on::Hosts | Cloud Service Account \[cmdb_ci_cloud_service_account\] |
[ ]

{#azure-cloud-discovery-patterns__id_yqp_xhy_qpb}
**Related concepts**   

* [Kubernetes discovery using patterns](https://servicenow-prod.fluidtopics.net/Nq0fHYmeSm4QYmSRUrjWJA "The ServiceNow ITOM Visibility finds Kubernetes and OpenShift components using patterns and creates application services containing them. Discovery also finds Kubernetes events and frequently updates the CMDB to reflect the dynamic Kubernetes environment.")  
**Related reference**   

* [Azure Key Vault certificate discovery](https://servicenow-prod.fluidtopics.net/fb6YnFnagvVlfI81Mznzvg "Cloud Discovery uses Patterns to discover Azure Key Vault certificates. Discovering this data requires installing and updating Discovery and Service Mapping Patterns and Certificate Inventory and Management.")
* [Microsoft Foundry (Classic) pattern-based discovery](https://servicenow-prod.fluidtopics.net/qncj27mBSZbQvGrW0CWy_g "AI Agent Topology Mapping discovers Microsoft Foundry (Classic) services, agents, and models during horizontal discovery.")