Azure Application Insight Component pattern-based discovery

  • Release version: Xanadu
  • 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 Application Insight Component pattern-based discovery

    The Azure Application Insight Component pattern-based discovery in ServiceNow identifies and maps Azure Application Insights resources within your cloud environment using Discovery and Service Mapping Patterns. This capability helps you maintain an accurate and up-to-date Configuration Management Database (CMDB) by integrating detailed Azure resource information.

    Show full answer Show less

    To leverage this discovery, ensure you meet Microsoft Azure prerequisites, enable the appropriate discovery pattern (disabled by default), and configure discovery schedules properly—especially for Azure GovCloud accounts, which require specific datacenter URL settings.

    Key Features

    • Pattern Activation and Updates: Starting from Visibility Content 6.28.0, enabling or disabling patterns is no longer considered a customization, allowing seamless updates while preserving your activation preferences after upgrades.
    • Data Population: The discovery populates detailed data into both CMDB and non-CMDB tables, capturing comprehensive attributes of Azure Application Insight components.
    • Non-CMDB Data: Includes application-specific fields such as App ID, Application Type, Connection String, Instrumentation Key, resource location, provisioning state, retention period, subscription and tenant IDs, and version information.
    • CMDB Data: Core resource details such as install and operational status, name, object ID, resource type (identified as microsoft.insights/components), description, version, and location are stored in the Cloud Resource [cmdbcicmpresource] table.
    • CI Relationships: The pattern establishes relationships between Application Insight Components, Cloud Resources, Resource Groups, and Azure Datacenters to support service mapping and impact analysis.
    • Tag Collection: The discovery captures Azure tags and stores them in the Key Value [cmdbkeyvalue] table for enhanced resource categorization and management.

    Practical Implications for ServiceNow Customers

    • Enable the Azure Application Insight Component discovery pattern to start populating your CMDB with Azure Application Insights data.
    • Ensure Azure service accounts and discovery schedules are configured correctly, especially for Azure GovCloud environments.
    • Use the populated data and relationships to improve visibility into your Azure environment, enhance service mapping accuracy, and support operational and compliance requirements.
    • Leverage tags captured by discovery to organize and filter resources effectively within ServiceNow.

    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 populate data in the non-CMDB table when running the Azure - Application Insight Component - 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 Application Insight - Component [cmdb_azure_application_insight_component]
    Field Description
    App ID [app_id] The identifier for the application linked to this resource.
    Application Type [application_type] The type of application to which the resource is related.
    Connection String [connection_string] The string used to connect to the resource endpoint.
    Instrumentation Key [instrumentation_key] The key used for application insights to log telemetry data.
    Kind [kind] The specific subtype or variation of the resource.
    Location [location] The geographic region where the resource is deployed.
    Object Id [object_id] The unique identifier for the resource.
    Provisioning State [provisioning_state] The current provision status of the resource.
    Resource Group [resource_group] Name of the resource group.
    Retention In Days [retention_in_days] The number of days that logs or data are retained.
    Subscription ID [subscription_id] The subscription ID.
    Tenant ID [tenant_id] The directory tenant to which the resource belongs.
    Version [version] The version number of the resource or service.
    Configuration Item [configuration_item] References the Cloud Resource [cmdb_ci_cmp_resource] table.

    Data stored in CMDB tables

    Discovery and Service Mapping Patterns application populates data in the CMDB when running the Azure - Application Insight Component - Extended Inventory(LP) pattern.

    Table 2. Cloud Resource [cmdb_ci_cmp_resource]
    Field Description
    Install Status [install_status] Install status of the resource. Default value is Installed.
    Location [location] The geographic region where the resource is deployed.
    Name [name] The name assigned to the resource.
    Object ID [object_id] The unique identifier for the resource.
    Operational status [operational_status] Operational status of the resource. Default value is Operational.
    Resource type [resource_type] Type of resource. The value is set to microsoft.insights/components.
    Description [short_description] Description of the resource or service.
    Version [version] The version number of the resource or service.

    CI relationships

    The pattern creates these relationships to support discovery.

    CI Relationship CI
    Resource Group [cmdb_ci_resource_group] Contains::Contained by Cloud Resource [cmdb_ci_cmp_resource]
    Cloud Resource [cmdb_ci_cmp_resource] Hosted on::Hosts Azure Datacenter [cmdb_ci_azure_datacenter]
    Azure Application Insight - Component [cmdb_azure_application_insight_component] References Cloud Resource [cmdb_ci_cmp_resource]

    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.