---
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 Database

# Azure Database pattern-based discovery {#ariaid-title1}

Release version: Brazil  
Updated June 18, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read  
Discovery and Service Mapping Patterns finds Azure databases, including SQL Server, MySQL, PostgreSQL, Redis, and Azure Cosmos DB, in 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-database-pattern__section_rpj_fj2_bgc}

Verify the Microsoft Azure discovery prerequisites
:   For more information, see the prerequisites section in [Microsoft Azure Cloud discovery using patterns](https://www.servicenow.com/docs/s9SHZxzsnOR4TZKkvmJG9A "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.").

Configure the Discovery schedule to support GovCloud
:   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/_5QfXcWcH8tWf~lcyLEaIg "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-database-pattern__configure-govcloud-azure-dd}
{#azure-database-pattern__configure-govcloud-azure-dd}

Verify requirements for Azure SQL Managed Instance license discovery
:
    Required plugins and applications:

    * Software Asset Management Professional for Microsoft
    * Visibility Content
    {#azure-database-pattern__ul_required_apps}

## Data collected by Discovery during horizontal discovery {#azure-database-pattern__section_ggp_ql2_bgc}

Discovery populates the data in the CMDB when running the Azure DataBase (LP) pattern.  
{#azure-database-pattern__table_cloud_database__entry__2}

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

{#azure-database-pattern__table_cloud_database}\* Populated only by the Azure SQL Managed Instance license pattern extension.  
{#azure-database-pattern__table_ip_address__entry__2}

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

{#azure-database-pattern__table_ip_address}  
{#azure-database-pattern__table_database__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the database in the following format: <kbd class="ph userinput">&lt;database name&gt;@&lt;server name&gt;</kbd>. |
| Type \[type\] | Database engine type. Possible values: * Microsoft SQL Server * MySQL * Postgres SQL * Redis * DocumentDB {#azure-database-pattern__ul_db_type} |
| Serial number \[serial_number\] | Unique identifier of the database. |
| Life Cycle Stage \[life_cycle_stage\] | Life cycle stage of the database, derived from its Azure status. For example: Operational or End of Life. |
| Life Cycle Stage Status \[life_cycle_stage_status\] | Life cycle stage status of the database, derived from its Azure status. For example: In Use or Retired. |
[Table 3. Database \[cmdb_ci_database\]]

{#azure-database-pattern__table_database}  
{#azure-database-pattern__table_hardware_type__entry__2}

| Field | Description |
|-|-|
| Name \[name\] | Name of the hardware type, based on the database SKU. |
| Object ID \[object_id\] | Unique identifier for the hardware type, based on the database SKU name. |
| vCPUs \[vcpus\] | Number of virtual CPUs, extracted from the SKU name. |
| Provider \[provider\] | Cloud provider of the hardware type. The value is set to AZURE. This field is only populated in the Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] table. |
[Table 4. Hardware Type \[cmdb_ci_compute_template\] or Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\]]

{#azure-database-pattern__table_hardware_type}  
Note:  
When using the Hardware Type \[cmdb_ci_compute_template\] table to store the hardware types, you may notice an unusually large number of records. To avoid this issue, you can store the discovered hardware types in the Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] table. For more information, see [Enable the Cloud Hardware Type class extension](https://www.servicenow.com/docs/HNx6VTgkXGQ9fjYQbrQchw "Enable the Cloud Hardware Type [cmdb_ci_cloud_hardware_type] table to store the predefined virtual machine (VM) hardware type records for Amazon AWS Cloud Microsoft Azure Cloud and Google Cloud Platform (GCP). This class extension helps prevent duplication of the VM hardware type records in the Hardware Type [cmdb_ci_compute_template] table, which improves performance for Discovery and related flows.").  
Discovery populates the data in the CMDB when running the Azure SQL Managed Instance license pattern extension.{#azure-database-pattern__table_serverless_hardware__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 5. Serverless Hardware \[cmdb_ci_serverless_hardware\]]

{#azure-database-pattern__table_serverless_hardware}

## CI relationships and references {#azure-database-pattern__section_dc4_ghc_dgc}

The Azure DataBase (LP) pattern creates the following relationships and references to support Azure database discovery. References link to records in other tables and don't appear in the CI Relationship \[cmdb_rel_ci\] table.  
{#azure-database-pattern__table_bkg_jhc_dgc__entry__3}

| CI | Relationship | CI |
|-|-|-|
| Cloud DataBase \[cmdb_ci_cloud_database\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| 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\] |
| Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud DataBase \[cmdb_ci_cloud_database\] |
| Hardware Type \[cmdb_ci_compute_template\] or Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| Database \[cmdb_ci_database\] | Provisioned From::Provisioned | Hardware Type \[cmdb_ci_compute_template\] or Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] |
[Table 6. CI relationships]

{#azure-database-pattern__table_bkg_jhc_dgc}  
{#azure-database-pattern__table_ci_references__entry__3}

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

{#azure-database-pattern__table_ci_references}  
The Azure SQL Managed Instance license pattern extension creates the following relationships.{#azure-database-pattern__table_license_relationships__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 8. CI relationships]

{#azure-database-pattern__table_license_relationships}  
{#azure-database-pattern__table_license_references__entry__3}

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

{#azure-database-pattern__table_license_references}

## Azure Tag discovery {#azure-database-pattern__section_lyw_zhc_dgc}

The Collect Azure DataBase Tags (LP) pattern extension collects tags from database servers and databases, and populates them in the Key Value \[cmdb_key_value\] table.  
{#azure-database-pattern__table_ojy_vss_5hc__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | Tag name. |
| Value \[value\] | Tag value. |
| Configuration item \[configuration_item\] | References the Cloud DataBase \[cmdb_ci_cloud_database\] table (for server-level tags) or the Database \[cmdb_ci_database\] table (for database-level tags). |
[Table 10. Key Value \[cmdb_key_value\]]

{#azure-database-pattern__table_ojy_vss_5hc}

## Azure SQL Managed Instance license discovery {#azure-database-pattern__section_sql_managed_instance}

The Azure SQL Managed Instance license pattern extension populates the license type in the Key Value \[cmdb_key_value\] table.  
{#azure-database-pattern__table_key_value_license__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-database-pattern__ul_license_values} |
| Configuration item \[configuration_item\] | References the Cloud DataBase \[cmdb_ci_cloud_database\] table. |
[Table 11. Key Value \[cmdb_key_value\]]

{#azure-database-pattern__table_key_value_license}

## Connections found by Service Mapping during top-down discovery {#azure-database-pattern__section_dzz_jz4_skc}

The Azure DataBase TD pattern discovers the following connections during top-down discovery: SQL Server, MySQL, PostgreSQL, Redis, and Cosmos DB (DocumentDB).