--- 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 --- # Azure Dev Center # Azure Dev Center pattern-based discovery {#ariaid-title1} * Release version: Yokohama * * Updated August 11, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 you to automatically find and map Azure Dev Center services within your cloud environment. This discovery uses patterns that identify Azure resources and populate data into both CMDB and non-CMDB tables, helping you maintain an accurate and comprehensive Configuration Management Database (CMDB) for your Azure infrastructure. Show full answer Show less ## Key Features * **Pattern Activation:** The Azure Dev Center discovery pattern is disabled by default. Enabling it from Visibility Content version 6.28.0 onward does not count as customization, allowing you to receive automatic updates without losing your active settings. * **Prerequisites:** You must meet Microsoft Azure discovery prerequisites and configure Azure service accounts correctly, especially when discovering Azure GovCloud (US) accounts, which require specific datacenter URLs. * **Data Population:** The discovery populates detailed Azure Dev Center data into: * **Non-CMDB tables:** Contains detailed resource metadata such as Object ID, kind, location, resource group, subscription and tenant IDs, provisioning state, and Dev Center URI. * **CMDB tables (Cloud App Server):** Stores key configuration items with fields like Object ID, resource name, type (set to microsoft.devcenter/devcenters), location, install status, and operational status. * **CI Relationships:** The pattern establishes relationships between Azure Dev Centers, Cloud App Servers, Resource Groups, and Azure Datacenters, enabling accurate topology mapping. * **Azure Tag Discovery:** Tags assigned to Azure resources are collected and stored in the Key Value table, facilitating tag-based filtering and management within ServiceNow. ## Practical Application for ServiceNow Customers By enabling and configuring the Azure Dev Center discovery pattern, you can integrate your Azure Dev Center resources into your ServiceNow CMDB with up-to-date and detailed information. This supports improved asset management, operational visibility, and governance of your Azure cloud environment. Ensuring prerequisites and pattern activation are correctly handled will lead to comprehensive mapping and reliable data synchronization, aiding in effective cloud service 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 {#azure-dev-center__selection_ipy_53n_jfc} 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 components discovery using patterns](https://servicenow-prod.fluidtopics.net/JeDZ0tlC9eLF5fei5qSv3w "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."). 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://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "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://servicenow-prod.fluidtopics.net/wA59_lRoV_0PzpuODHnNjA "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