---
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 Dev Center

# Azure Dev Center 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 Dev Center pattern-based discovery

Azure Dev Center pattern-based discovery in ServiceNow enables automated identification and mapping of Azure Dev Center resources within your cloud environment.
This discovery leverages Discovery and Service Mapping Patterns to populate detailed configuration data into both CMDB and non-CMDB tables, supporting comprehensive cloud asset management and visibility.
Show full answer Show less  

## Key prerequisites and setup

* **REST API permissions:** Ensure appropriate Azure REST API permissions are granted by using the Cloud Discovery patterns spreadsheet, which details necessary permissions, pattern names, CI classes, and vendor documentation. Regularly update this spreadsheet to stay current with quarterly pattern releases.
* **Microsoft Azure discovery prerequisites:** Follow the specific Azure discovery prerequisites as outlined in the ServiceNow documentation to prepare your environment.
* **Resource Inclusion List:** Verify and remove any relevant resources from the Resource Inclusion List table to prevent duplicate discoveries.
* **Pattern activation:** The Azure Dev Center discovery pattern is disabled by default. Starting with Visibility Content version 6.28.0, activating or deactivating patterns is no longer considered a customization and updates will not overwrite your activation status.
* **Discovery schedule configuration:** For Azure GovCloud (US) accounts, configure service accounts using datacenter URLs to ensure successful discovery.

## Data storage and tables

Discovery results are stored in two main table types:

* **Non-CMDB tables:** The pattern populates data in non-CMDB Azure-specific tables when running the Azure - Dev Center - Extended Inventory(LP) pattern. These tables include detailed fields such as Object Id, Kind, Location, Resource Group, Subscription Id, Tenant Id, Provisioning State, Configuration Item reference, and Dev Center URI.
* **CMDB tables:** Key configuration items are created in the Cloud App Server \[cmdbcicloudappserver\] table with fields like Object ID, Name, Type (set to microsoft.devcenter/devcenters), Location, Install Status, and Operational Status.

## CI relationships and tagging

* The pattern establishes relationships linking Cloud App Servers to Resource Groups, Azure Datacenters, and Azure Dev Centers, providing a connected view of your cloud infrastructure.
* Azure tags discovered by the pattern are stored in the Key Value \[cmdbkeyvalue\] table, capturing tag names and corresponding values to aid in resource categorization and management.

## Practical benefits for ServiceNow customers

By implementing Azure Dev Center pattern-based discovery, customers gain automated, up-to-date visibility into Azure Dev Center resources, facilitating accurate CMDB population and improved cloud service management. Configuring permissions, patterns, and discovery schedules correctly ensures comprehensive and duplicate-free discovery results. The resulting data supports better operational insights, governance, and resource optimization within ServiceNow.  
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-dev-center__selection_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-dev-center__cloud-discovery-api-ph-short-prereq}

Verify the Microsoft Azure discovery prerequisites{#azure-dev-center__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-dev-center__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-dev-center__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-dev-center__activating-disabled-pattern-not-customization}

Configure the Discovery schedule to support GovCloud{#azure-dev-center__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-dev-center__configure-govcloud-azure-dd}
{#azure-dev-center__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-dev-center__section_aq4_qkq_hfc}

Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Dev Center - 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-dev-center__section_aq4_qkq_hfc__entry__2}

| Field | Description |
|-|-|
| Object Id \[object_id\] | The unique resource identifier in Azure Resource Manager format. |
| Kind \[kind\] | The specific type or classification of the resource. |
| DC Location \[location\] | The Azure datacenter region where the resource is located. |
| Resource Group \[resource_group\] | The name of the Azure Resource Group containing the resource. |
| Subscription Id \[subscription_id\] | The unique identifier of the Azure subscription. |
| Tenant Id \[tenant_id\] | The unique identifier of the Azure Active Directory tenant. |
| Provisioning State \[provisioning_state\] | The current state of resource provisioning. For example: Succeeded or Failed. |
| Configuration Item \[configuration_item\] | References the Cloud App Server \[cmdb_ci_cloud_appserver\] table. |
| Dev Center URI \[dev_center_uri\] | The Uniform Resource Identifier (URI) endpoint for connecting to the Dev Center resource. |
[Table 1. Azure Dev Center \[cmdb_azure_dev_centers_dev_center\]]

## Data stored in CMDB tables

Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Dev Center - Extended Inventory(LP) pattern.  
{#azure-dev-center__entry__22}

| Field | Description |
|-|-|
| Object ID \[object_id\] | The unique resource identifier in Azure Resource Manager format. |
| Name \[name\] | The name of the resource. |
| Type \[type\] | Type of resource. The value is set to microsoft.devcenter/devcenters. |
| Location \[location\] | The Azure datacenter region where the resource is located. |
| Install Status \[install_status\] | Install status of the resource. Default value is Installed. |
| Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. |
[Table 2. Cloud App Server \[cmdb_ci_cloud_appserver\]]

## CI relationships

The Azure - Dev Center - Extended Inventory(LP) pattern creates these relationships to support Azure Dev Center discovery.  
{#azure-dev-center__entry__37}

| CI | Relationship | CI |
|-|-|-|
| Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud App Server \[cmdb_ci_cloud_appserver\] |
| Cloud App Server \[cmdb_ci_cloud_appserver\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] |
| Azure Dev Center \[cmdb_azure_dev_centers_dev_center\] | References | Cloud App Server \[cmdb_ci_cloud_appserver\] |
[ ]

## Azure tag discovery {#azure-dev-center__section_ezc_jwt_jfc}

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

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

{#azure-dev-center__table_axq_spc_y2c}

*[\>]: and then