Microsoft Azure Functions discovery with Patterns

  • Release version: Zurich
  • Updated July 31, 2025
  • 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 Microsoft Azure Functions discovery with Patterns

    The Discovery and Service Mapping Patterns application in ServiceNow enables automated discovery and mapping of Microsoft Azure Functions apps within the context of application services. It leverages the Azure - Functions (LP) and Azure - Functions TD Patterns to identify and document Azure Functions in your environment, supporting enhanced visibility and management.

    Show full answer Show less

    To discover these resources effectively, customers may need to update to the latest version of the Discovery and Service Mapping Patterns application available on the ServiceNow Store.

    Prerequisites

    • Azure Service Account: Configure an Azure service account with appropriate permissions following ServiceNow’s guidelines for setting up a cloud account for Azure.
    • Azure Principal Credentials: Create a service account on the ServiceNow AI Platform linked to the Azure Service Principal ID as registered in the Microsoft Azure Console.
    • Privileges: Assign the API Management Service Reader role to the user in the Microsoft Azure Console to enable necessary API access for discovery.

    Discovery Process

    • Run Azure Cloud discovery using ServiceNow’s Cloud Discovery Workspace to schedule and execute discovery jobs.
    • The discovery process collects detailed information about Azure Functions apps, including name, object ID, IP address, fully qualified domain name (FQDN), source code URL, function state, operational status, and installation status.

    Configuration Data and Relationships

    Discovered Azure Functions are stored in the cmdbcicloudfunction table with key attributes that aid in identification and management.

    Service Mapping establishes relationships between Azure Functions and their hosting Azure datacenters (cmdbciazuredatacenter) to provide context and improve service mapping accuracy.

    Service Mapping Capabilities

    • Service Mapping identifies connections from Azure Functions to various databases such as MSSql, MySql, MongoDB, and Documentum.
    • It detects HTTP connections within the Azure Functions environment (e.g., URLs like https://scenario4-hop1-azure-function.azurewebsites.net).
    • Note that Service Mapping does not analyze Java classes, JARs, or binary files for outgoing HTTP connections. Hence, if these are the sole source of such connection information, those connections will not be discovered.

    Additional Guidance

    For more advanced discovery needs, customers can define Cloud REST Queries to extend cloud computing device discovery.

    The Discovery and Service Mapping Patterns application uses the Azure - Functions (LP) and Azure - Functions TD Patterns to discover Azure Functions apps and map them in the context of application services. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.

    Request apps on the Store

    Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.

    Prerequisites

    Azure Functions detailed information
    Detailed information on products discovered by ITOM Visibility
    Azure service account
    Configure the Azure service account. For more information, see Set up a cloud account for Azure
    Azure Principal credentials
    On the ServiceNow AI Platform, create a service account for cloud discovery. Set the account Id to the Azure Service Principal as it appears at the Microsoft Azure Console. For more information see: Create Azure cloud credentials
    Privileges
    On the Microsoft Azure Console, provide a user with the API Management Service Reader role.
    Run Azure Cloud discovery
    For detailed information, see: Discovery for Microsoft Azure Cloud
    Create discovery schedule
    Create a discovery schedule in Cloud Discovery Workspace

    Data collected by Discovery during horizontal discovery

    Table and field Description
    Azure Function [cmdb_ci_cloud_function]
    name The name of the Function app.
    Object_id The ID of the Function app.
    ip_address The IP Address of the Function app.
    fqdn The Fully Qualified Domain Name (FQDN) of the Function app.
    code_location_url The URL of the Function app source code.
    app_function_state The state of the Function app.
    operational_status The operational status of the Function app.
    install_status The installation status of the Function app.

    CI relationships

    These relationships are created to support Azure Functions discovery:
    CI Relationship CI
    Azure Functions [cmdb_ci_cloud_function] Hosted on::Hosts Azure datacenter [cmdb_ci_azure_datacenter]

    Connections found by Service Mapping during top-down discovery

    Service Mapping can discover the following connections:
    • Connections to the following databases: MSSql, MySql, MongoDB, and Documentum.
    • HTTP connections belonging to Azure Functions environment, for example, https://scenario4-hop1-azure-function.azurewebsites.net.
      Note:
      Service Mapping does not scan java classes/jars and binary files for possible information about outgoing HTTP connections of Azure Functions. If java classes/jars and binary files are the only source of information about some outgoing HTTP connections, Service Mapping does not find such HTTP connections.