Azure Logic App pattern-based discovery

  • Release version: Australia
  • Updated March 12, 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 Logic App Pattern-Based Discovery

    The Azure Logic App pattern-based discovery enables customers to identify and map Azure services within their cloud environment. This process may require the latest version of the Discovery and Service Mapping Patterns application available in the ServiceNow Store.

    Show full answer Show less

    Key Features

    • Microsoft Azure Discovery Prerequisites: Ensure that the prerequisites for Azure discovery are met as outlined in the Microsoft documentation.
    • Pattern Activation: The Azure service pattern is disabled by default. From version 6.28.0 onwards, activating or deactivating this pattern is not considered a customization, allowing for seamless updates.
    • GovCloud Support: For Azure GovCloud accounts, a specific datacenter URL must be used when setting up the Azure service account.
    • Data Population: The application populates both CMDB and non-CMDB tables with discovery data. For non-CMDB data, users can navigate to Azure-specific tables in the configuration section.
    • CI Relationships: The pattern establishes relationships between various configuration items to enhance the discovery process.
    • Tag Collection: Tags associated with Azure resources are collected and stored in the Key Value table for easier management and reference.

    Key Outcomes

    By utilizing the Azure Logic App pattern-based discovery, customers can effectively manage their Azure resources, ensuring accurate data representation in both CMDB and non-CMDB tables. This capability leads to improved visibility and operational efficiency within their cloud environment.

    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 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 - Logic App - 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 Logic App [cmdb_azure_logic_app_logic_app]
    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.

    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.

    Table 2. Cloud Function [cmdb_ci_cloud_function]
    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.

    CI relationships

    The pattern creates these relationships to support discovery.

    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

    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.