--- 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 Logic App # Azure Logic App 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 Logic App pattern-based discovery Azure Logic App pattern-based discovery is part of ServiceNow's Discovery and Service Mapping Patterns, designed to identify and map Azure Logic Apps within your cloud environment. This process helps populate both CMDB and non-CMDB tables with detailed information about Azure Logic Apps and their associated cloud functions, enabling comprehensive visibility and management of these resources. Show full answer Show less ## Key Features * **Pattern Activation:** The Azure Logic App discovery pattern is disabled by default and requires activation. From Visibility Content version 6.28.0 onwards, enabling or disabling patterns does not count as customization, ensuring patterns remain up-to-date after upgrades. * **Prerequisites:** Microsoft Azure discovery prerequisites must be met, including proper setup of Azure service accounts and configuration for GovCloud environments using the appropriate datacenter URLs. * **Data Population:** The discovery populates detailed attributes in two types of tables: * **Non-CMDB Tables:** The *cmdbazurelogicapplogicapp* table captures data such as access endpoints, identity, resource kind, location, provisioning and operational states, resource group, subscription and tenant IDs, and resource type. * **CMDB Tables:** The *cmdbcicloudfunction* table records cloud function details including install status, location, name, object ID, and operational status. * **CI Relationships:** The pattern establishes relationships between Azure Logic Apps, cloud functions, resource groups, and Azure datacenters to form a connected configuration item (CI) model. * **Tag Discovery:** Azure tags are collected during discovery and stored in the *cmdbkeyvalue* table, allowing tagging metadata to be leveraged for filtering and management. ## Key Outcomes * **Comprehensive Visibility:** Customers gain detailed inventory and operational status of Azure Logic Apps and related cloud functions within ServiceNow's CMDB and associated tables. * **Up-to-Date Patterns:** Automatic updates to discovery patterns ensure ongoing accuracy and compatibility with Azure services without manual intervention. * **Governance and Compliance:** Mapping resources with their operational states and tags supports governance, auditing, and compliance activities. * **Improved Cloud Management:** The established CI relationships provide a clear topology of Azure Logic Apps and their dependencies, facilitating impact analysis and change management. 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-logic-app__section_ipy_53n_jfc} Verify the Microsoft Azure discovery prerequisites{#azure-logic-app__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-logic-app__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-logic-app__activating-disabled-pattern-not-customization} Configure the Discovery schedule to support GovCloud{#azure-logic-app__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-logic-app__configure-govcloud-azure-dd} {#azure-logic-app__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-logic-app__section_aq4_qkq_hfc} Discovery and Service Mapping Patterns application populates data in the non-CMDB table when running the Azure - Logic App - 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-logic-app__section_aq4_qkq_hfc__entry__2} | Field | Description | |-|-| | Access Endpoint \[access_endpoint\] | The endpoint URL used for accessing the resource. | | Identity \[identity\] | The identity associated with the resource for access and security purposes. | | Kind \[kind\] | The specific subcategory or variant of the resource. | | Location \[location\] | The geographical region where the resource is deployed. | | Object Id \[object_id\] | The unique identifier of the resource. | | Provisioning State \[provisioning_state\] | The current provisioning state of the resource. | | Resource Group \[resource_group\] | Name of the resource group. | | State \[state\] | The overall current operational state of the resource. | | Subscription Id \[subscription_id\] | The subscription ID. | | Tenant Id \[tenant_id\] | The identifier of the tenant that owns the resource. | | Type \[type\] | The type or category of the resource. | | Configuration Item \[configuration_item\] | References the Cloud Function \[cmdb_ci_cloud_function\] table. | [Table 1. Azure Logic App \[cmdb_azure_logic_app_logic_app\]] ## Data stored in CMDB tables Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Logic App - Extended Inventory(LP) pattern. {#azure-logic-app__entry__28} | Field | Description | |-|-| | Install Status \[install_status\] | Install status of the resource. Default value is Installed. | | Location \[location\] | The geographical region where the resource is deployed. | | Name \[name\] | The name assigned to the resource. | | Object ID \[object_id\] | The unique identifier of the resource in the following format: /subscriptions/{subscriptionId}/resourceGroups/{resouceGroupName}/providers/Microsoft.logic/workflows/{workflowName}. | | Operational status \[operational_status\] | Operational status of the resource. Default value is Operational. | [Table 2. Cloud Function \[cmdb_ci_cloud_function\]] ## CI relationships The pattern creates these relationships to support discovery. {#azure-logic-app__entry__41} | CI | Relationship | CI | |-|-|-| | Resource Group \[cmdb_ci_resource_group\] | Contains::Contained by | Cloud Function \[cmdb_ci_cloud_function\] | | Cloud Function \[cmdb_ci_cloud_function\] | Hosted on::Hosts | Azure Datacenter \[cmdb_ci_azure_datacenter\] | | Azure Logic App \[cmdb_azure_logic_app_logic_app\] | References | Cloud Function \[cmdb_ci_cloud_function\] | [ ] ## Azure tag discovery {#azure-logic-app__section_ezc_jwt_jfc} The pattern collects tags and populates them in the Key Value \[cmdb_key_value\] table. {#azure-logic-app__table_axq_spc_y2c__entry__2} | Field | Description | |-|-| | Key \[key\] | Tag name. | | Value \[value\] | Tag value. | [Table 3. Key Value \[cmdb_key_value\]] {#azure-logic-app__table_axq_spc_y2c} *[\>]: and then