Microsoft Azure Functions discovery with Patterns

  • Release version: Yokohama
  • Updated January 30, 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 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 Azure Function apps and their relationships. To discover some Azure Functions resources, updating to the latest version of this application from the ServiceNow Store may be necessary.

    Show full answer Show less

    Prerequisites

    • Azure Service Account: Configure an Azure service account with appropriate credentials for discovery.
    • Azure Principal Credentials: Create a service account on the ServiceNow AI Platform and set the account ID to match the Azure Service Principal from Microsoft Azure Console.
    • Privileges: Assign the API Management Service Reader role to the Azure user account on the Microsoft Azure Console.

    Discovery Process

    • Run Azure Cloud discovery via Cloud Discovery Workspace.
    • Create a discovery schedule to automate the process.

    Data Collected

    The discovery process collects detailed information about Azure Functions apps, including:

    • Function app name, Object ID
    • IP address, Fully Qualified Domain Name (FQDN)
    • Source code URL
    • Function app state, operational and installation status

    Configuration Item (CI) Relationships

    The discovery creates relationships such as:

    • Hosted on: Links Azure Functions CI to the hosting Azure datacenter CI

    Service Mapping Capabilities

    Service Mapping identifies connections associated with Azure Functions, including:

    • Connections to databases like MSSQL, MySQL, MongoDB, and Documentum
    • HTTP connections within the Azure Functions environment

    Note: Outgoing HTTP connections discovered solely through Java classes/jars or binary files are not detected by Service Mapping.

    Additional Tasks

    Customers can define Cloud REST Queries for cloud computing devices to enhance discovery capabilities.

    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.