Azure Classic Load Balancer pattern-based discovery

  • Release version: Zurich
  • 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 helps ServiceNow customers automatically identify and map Azure Classic Load Balancer resources within their cloud environments. This discovery populates the Configuration Management Database (CMDB) with detailed load balancer data and establishes relationships between the load balancer components and related Azure infrastructure. To utilize this pattern, customers should ensure they meet Azure discovery prerequisites and have the latest Discovery and Service Mapping Patterns application installed from the ServiceNow Store.

    Show full answer Show less

    Key Features

    • Resource Identification: The pattern discovers key Azure Classic Load Balancer components such as load balancers, IP addresses, load balancer services (including load balancing rules and inbound NAT rules), and backend address pools.
    • CMDB Population: Each discovered component is recorded as a Configuration Item (CI) with attributes including unique Azure object IDs, names, IP addresses, ports, and install status, facilitating accurate asset management.
    • CI Relationships: The discovery pattern automatically creates relationships among load balancer components, such as ownership of IP addresses by load balancers, hosting of services and pools on load balancers, and containment of load balancers within Azure resource groups and datacenters.
    • Service Mapping Integration: The Azure LoadBalancer TD pattern supports top-down discovery, enabling Service Mapping to trace connections from load balancer services to backend pool member IP addresses using load balancing or inbound NAT rules.

    What Customers Can Expect

    • Comprehensive and structured representation of Azure Classic Load Balancer infrastructure in the ServiceNow CMDB, enhancing visibility and management.
    • Improved accuracy in cloud asset tracking through standardized attributes and consistent install status marking.
    • Automatic mapping of component relationships, enabling better impact analysis and operational insights.
    • Seamless integration with Service Mapping for detailed connection discovery and service topology mapping within Azure environments.

    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 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.