Azure Dev Center pattern-based discovery

  • Release version: Yokohama
  • Updated June 16, 2026
  • 2 minutes to read
    • Summarize
    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 services within your cloud environment. This functionality uses Discovery and Service Mapping Patterns to locate Azure Dev Center resources and related components, populating both CMDB and non-CMDB tables with detailed information. This helps maintain an accurate and comprehensive configuration management database for Azure services.

    Show full answer Show less

    Key Features

    • Pattern Activation: The Azure Dev Center discovery pattern is disabled by default and must be enabled. Activating or deactivating patterns no longer counts as a customization, ensuring updates are retained seamlessly after upgrades.
    • Azure GovCloud Support: Discovery supports Azure GovCloud (US) by configuring the Discovery schedule with the appropriate datacenter URL when setting up Azure service accounts.
    • Data Population: The discovery populates data into:
      • Non-CMDB Tables: Through the Azure - Dev Center - Extended Inventory(LP) pattern, data such as object IDs, resource types, locations, subscription and tenant IDs, provisioning states, and Dev Center URIs are stored.
      • CMDB Tables: Key Azure Dev Center resources are represented as Cloud App Server configuration items, including their operational and install status, location, and resource type.
    • CI Relationships: The pattern creates relationships linking Cloud App Servers to Resource Groups and Azure Datacenters, clarifying the resource hierarchy and dependencies.
    • Tag Discovery: Azure tags are collected and stored in the Key Value table, enabling enhanced classification and filtering of Azure resources.

    Practical Considerations

    • Ensure all Microsoft Azure discovery prerequisites are met before enabling the pattern.
    • Update the Discovery and Service Mapping Patterns application to the latest version from the ServiceNow Store to support Azure Dev Center discovery.
    • Configure the discovery schedule correctly, especially when working with Azure GovCloud accounts, by setting appropriate datacenter URLs.

    Expected Outcomes

    By implementing Azure Dev Center pattern-based discovery, ServiceNow customers gain a reliable and automated method to discover, map, and manage Azure Dev Center resources within their CMDB. This leads to improved visibility of Azure environments, accurate resource relationships, and enriched metadata through tags, supporting better cloud infrastructure management and decision-making.

    Discovery and Service Mapping Patterns finds Azure services on your cloud environment. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

    Pattern-based discovery and mapping requirements

    Verify the Microsoft Azure discovery prerequisites
    For more information, see the prerequisites section in Microsoft Azure Cloud components discovery using patterns.
    Enable the relevant pattern
    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.
    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.

    Discovery and Service Mapping Patterns application populates data in both CMDB and non-CMDB tables.

    Data stored in non-CMDB tables

    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 All > Configuration > Azure. You can also search the navigation filter for the specific pattern name.

    Table 1. Azure Dev Center [cmdb_azure_dev_centers_dev_center]
    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.

    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.

    Table 2. Cloud App Server [cmdb_ci_cloud_appserver]
    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.

    CI relationships

    The Azure - Dev Center - Extended Inventory(LP) pattern creates these relationships to support Azure Dev Center discovery.

    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

    The pattern collects tags and populates them in the Key Value [cmdb_key_value] table.
    Table 3. Key Value [cmdb_key_value]
    Field Description
    Key [key] Tag name.
    Value [value] Tag value.