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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Azure Data Factory

# Azure Data Factory pattern-based discovery {#ariaid-title1}

Release version: Australia  
Updated March 12, 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 Azure Data Factory pattern-based discovery

The Azure Data Factory pattern-based discovery enables ServiceNow customers to identify and map Azure Data Factory services within their cloud environment using Discovery and Service Mapping Patterns.
This process helps populate both CMDB and non-CMDB tables with detailed information about Azure Data Factory resources, supporting accurate configuration management and cloud resource visibility.
Show full answer Show less  

## Prerequisites and Setup

* **REST API Permissions:** Customers must verify and grant necessary REST API permissions using the downloadable Cloud Discovery patterns spreadsheet, which also provides pattern details and vendor documentation.
* **Azure Discovery Prerequisites:** Follow Microsoft Azure Cloud discovery prerequisites to ensure a successful discovery process.
* **Resource Inclusion List:** Remove any relevant Azure Data Factory resources from the Resource Inclusion List table to prevent duplicate discoveries.
* **Enable Patterns:** The Azure Data Factory discovery pattern is disabled by default and must be enabled. Pattern status changes are preserved across updates starting with Visibility Content version 6.28.0.
* **GovCloud Discovery:** When discovering Azure GovCloud (US) accounts, configure the discovery schedule with the appropriate datacenter URL and Azure service account setup.

## Data Population and Tables

The discovery pattern populates data into both non-CMDB and CMDB tables:

* **Non-CMDB Table (cmdbazuredatafactorydatafactory):** Stores detailed Azure Data Factory resource properties such as identity, kind (SKU), location, object ID, provisioning state, public network access status, resource group, subscription ID, tenant ID, version, and references to the Cloud Resource table.
* **CMDB Table (cmdbcicmpresource):** Contains resource metadata including install status (default "Installed"), location, name, object ID, operational status (default "Operational"), resource type (set to microsoft.datafactory/factories), description, and version.

## Configuration Item (CI) Relationships

The pattern establishes relationships critical for discovery and mapping, such as:

* Cloud Resource contained by a CI Resource Group
* Cloud Resource hosted on an Azure Datacenter
* Azure Data Factory references a Cloud Resource

## Azure Tag Discovery

The pattern also collects Azure tags associated with the discovered resources, storing tag names and values in the Key Value (cmdbkeyvalue) table. This tagging enables enhanced resource categorization and filtering within the CMDB.

## Practical Impact for ServiceNow Customers

By enabling and properly configuring the Azure Data Factory discovery pattern, customers gain automated, up-to-date visibility into their Azure Data Factory resources within ServiceNow's CMDB. This supports improved cloud asset management, accurate service mapping, and better operational decision-making. Regular updates to patterns and permissions ensure ongoing discovery accuracy aligned with Azure environment changes.  
Discovery and Service Mapping Patterns finds Azure services on 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-data-factory__section_ipy_53n_jfc}

Verify the REST API permissions
:   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-data-factory__cloud-discovery-api-ph-short-prereq}

Verify the Microsoft Azure discovery prerequisites{#azure-data-factory__verify-azure-discovery-prerequisites-dlentry}
:   For more information, see the prerequisites section in [Microsoft Azure Cloud discovery using patterns](https://www.servicenow.com/docs/e2521~KHAw8EO7j1nC9QMA "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.").

Remove resources from the Resource Inclusion List table{#azure-data-factory__remove-resource-inclusion-list-azure}
:   Verify that the relevant resource isn't listed in the Resource Inclusion List \[sa_cloud_inventory_resource_whitelist\] table to avoid duplicate discovery. For more information on removing resources from the Resource
    Inclusion List, see [Microsoft Azure resource inventory discovery](https://www.servicenow.com/docs/tO3nNqXv4zOe7q99krvAnA "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.").

Enable the relevant pattern{#azure-data-factory__enable-pattern-reuse-dlentry}
:   The pattern for this service is disabled by default. Starting with Visibility Content version 6.28.0, activating or deactivating a pattern won't be considered a customization, and it will continue to receive updates. Patterns that were previously activated or deactivated will reset to the latest predefined version after upgrading while retaining the last active field value. For more information on enabling patterns, see [Activate a disabled pattern](https://www.servicenow.com/docs/aypCYVQdO8oFebLMLEI89g "If you want to use a pattern for discovery that's disabled by default, activate it manually.").{#azure-data-factory__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud{#azure-data-factory__configure-govcloud-azure-dlentry}
:   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/XKQpJvxWTKNL58XCkRHVxA "Create and configure cloud service accounts at ServiceNow AI Platform for the corresponding Microsoft Azure accounts.").{#azure-data-factory__configure-govcloud-azure-dd}
{#azure-data-factory__configure-govcloud-azure-dd} Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables.

## Data stored in non-CMDB tables {#azure-data-factory__section_aq4_qkq_hfc}

Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Data Factory - Extended Inventory(LP) pattern.

You can review the non-CMDB
Azure tables by navigating to AllConfigurationAzure. You can also search the navigation filter for the specific pattern name.  
{#azure-data-factory__section_aq4_qkq_hfc__entry__2}

| Field | Description |
|-|-|
| Identity \[identity\] | Information about the identity associated with the resource. |
| Kind \[kind\] | The specific kind or stock keeping unit (SKU) of the resource. |
| Location \[location\] | The geographical location where the resource is deployed. |
| Object Id \[object_id\] | The unique identifier of the resource. |
| Provisioning State \[provisioning_state\] | The current provisioning status of the resource. |
| Public Network Access \[public_network_access\] | The status of public network accessibility for the resource. |
| Resource Group \[resource_group\] | Name of the resource group. |
| Subscription ID \[subscription_id\] | The subscription ID. |
| Tenant ID \[tenant_id\] | The unique identifier of the tenant containing the resource. |
| Version \[version\] | The version of the resource. |
| Configuration Item \[configuration_item\] | References the Cloud Resource \[cmdb_ci_cmp_resource\] table. |
[Table 1. Azure Data Factory \[cmdb_azure_data_factory_data_factory\]]

## Data stored in CMDB tables

Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Data Factory - Extended Inventory(LP) pattern.  
{#azure-data-factory__entry__26}

| Field | Description |
|-|-|
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Location \[location\] | The geographical location where the resource is deployed. |
| Name \[name\] | The name assigned to the resource. |
| Object ID \[object_id\] | The unique identifier of the resource. |
| Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. |
| Resource type \[resource_type\] | Type of resource. The value is set to microsoft.datafactory/factories. |
| Description \[short_description\] | Description of the resource or service. |
| Version \[version\] | The version of the resource. |
[Table 2. Cloud Resource \[cmdb_ci_cmp_resource\]]

## CI relationships

The pattern creates these relationships to support discovery.
{#azure-data-factory__entry__45}

| CI | Relationship | CI |
|-|-|-|
| Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud Resource \[cmdb_ci_cmp_resource\] |
| Cloud Resource \[cmdb_ci_cmp_resource\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| Azure Data Factory \[cmdb_azure_data_factory_data_factory\] | References | Cloud Resource \[cmdb_ci_cmp_resource\] |
[ ]

## Azure tag discovery {#azure-data-factory__section_ezc_jwt_jfc}

The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-data-factory__table_axq_spc_y2c__entry__2}

| Field | Description |
|-|-|
| Key \[key\] | Tag name. |
| Value \[value\] | Tag value. |
[Table 3. Key Value \[cmdb_key_value\]]

{#azure-data-factory__table_axq_spc_y2c}

*[\>]: and then