Azure Classic Load Balancer pattern-based discovery

  • Release version: Yokohama
  • Updated December 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 Azure Classic Load Balancer pattern-based discovery

    The Azure Classic Load Balancer pattern-based discovery enables ServiceNow customers to automatically identify and populate Configuration Items (CIs) related to Azure Classic Load Balancers within their cloud environments. This discovery enhances the Configuration Management Database (CMDB) with accurate and detailed information on load balancers, their IP addresses, services, and backend pools.

    Show full answer Show less

    To ensure successful discovery, customers should verify they meet the Azure discovery prerequisites and may need to update to the latest Discovery and Service Mapping Patterns application from the ServiceNow Store.

    Key Features

    • Discovery of Cloud Load Balancer CIs: The pattern identifies Azure Classic Load Balancers and populates key CI fields such as object ID, name, state, and install status.
    • Identification of Load Balancer IP Addresses: Captures IP details including unique object ID, IP address, IP address type (public/private), FQDN, and install status.
    • Load Balancer Services: Discovers load balancing rules or inbound NAT rules, including port numbers and unique identifiers.
    • Load Balancer Pools: Discovers backend address pools associated with the load balancer, capturing their object IDs and names.
    • CI Relationships: Establishes relationships between CIs such as ownership, hosting, and containment to accurately represent the Azure Classic Load Balancer ecosystem.
    • Service Mapping Integration: The Azure LoadBalancer TD pattern performs top-down discovery to map connections from load balancer services to backend pool member IP addresses, using load balancing rules or inbound NAT rules.

    Key Outcomes

    • Enhanced visibility into Azure Classic Load Balancer configurations within the CMDB, supporting more accurate asset and service management.
    • Improved understanding of load balancer topology, including services, IPs, and backend pools, facilitating troubleshooting and change impact analysis.
    • Automatic establishment of CI relationships ensures a comprehensive and connected representation of Azure networking components in ServiceNow.
    • Supports effective service mapping and dependency visualization through discovery of load balancer connections.

    Discovery and Service Mapping Patterns finds Azure Classic Load Balancers 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 Azure discovery prerequisites section in Microsoft Azure Cloud components discovery using patterns.

    Data collected by Discovery during horizontal discovery

    Discovery populates the data in the CMDB when running the Azure - Classic LB (LP) pattern.

    Table 1. Cloud Load Balancer [cmdb_ci_cloud_load_balancer]
    Field Description
    Object ID [object_id] A unique identifier, allocated by Azure for this resource.
    Name [name] The name of the load balancer.
    State [state] The current state of the load balancer.
    Install Status [install_status] Install status of the resource. Default value is Installed.
    Table 2. Cloud LB IP Address [cmdb_ci_cloud_lb_ipaddress]
    Field Description
    Object ID [object_id] A unique identifier, allocated by Azure for this resource.
    Name [name] IP address of the load balancer.
    IP Address [ip_address] IP address of the load balancer.
    IPAddress Type [ipaddress_type] The type of the IP address, which can be private or public.
    Fully qualified domain name [fqdn] The fully qualified domain name (FQDN) of the load balancer.
    Install Status [install_status] Install status of the resource. Default value is Installed.
    Table 3. Load Balancer Service [cmdb_ci_lb_service]
    Field Description
    Object ID [object_id] A unique identifier, allocated by Azure for this resource.
    Name [name] The name of the load balancing rule or inbound NAT rule.
    Port [port] The TCP port that the load balancer service listens to.
    Install Status [install_status] Install status of the resource. Default value is Installed.
    Table 4. Load Balancer Pool [cmdb_ci_lb_pool]
    Field Description
    Object ID [object_id] A unique identifier, allocated by Azure for this resource.
    Name [name] The name of the backend address pool.
    Install Status [install_status] Install status of the resource. Default value is Installed.

    CI relationships

    The Azure - Classic LB (LP) pattern creates these relationships to support Azure Classic Load Balancer discovery.

    CI Relationship CI
    Cloud Load Balancer [cmdb_ci_cloud_load_balancer] Owns::Owned by Cloud LB IP Address [cmdb_ci_cloud_lb_ipaddress]
    Cloud Load Balancer [cmdb_ci_cloud_load_balancer] Hosted on::Hosts Azure Datacenter [cmdb_ci_azure_datacenter]
    Load Balancer Service [cmdb_ci_lb_service] Hosted on::Hosts Cloud Load Balancer [cmdb_ci_cloud_load_balancer]
    Load Balancer Pool [cmdb_ci_lb_pool] Hosted on::Hosts Cloud Load Balancer [cmdb_ci_cloud_load_balancer]
    Load Balancer Pool [cmdb_ci_lb_pool] Hosted on::Hosts Load Balancer Service [cmdb_ci_lb_service]
    Resource Group [cmdb_ci_resource_group] Contains::Contained by Cloud Load Balancer [cmdb_ci_cloud_load_balancer]

    Connections discovered by Service Mapping during top-down discovery

    The Azure LoadBalancer TD pattern performs top-down discovery of Azure Classic Load Balancers. Service Mapping discovers cluster connections from the load balancer service to backend pool member IP addresses using either load balancing rules or inbound NAT rules.