--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Azure Classic Load Balancer # Azure Classic Load Balancer pattern-based discovery {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 in ServiceNow enables automated identification and mapping of Azure Classic Load Balancer resources within your cloud environment. This functionality requires the latest Discovery and Service Mapping Patterns application to ensure comprehensive and accurate data collection. Show full answer Show less Prior to discovery, ensure that Azure discovery prerequisites are met as specified in the Microsoft Azure Cloud discovery using patterns documentation. ## Key Features * **Discovery of Azure Classic Load Balancer components:** The Azure - Classic LB (LP) pattern collects and populates configuration items (CIs) into the CMDB, including Cloud Load Balancers, Cloud LB IP Addresses, Load Balancer Services, and Load Balancer Pools. * **Detailed CI attributes:** Each CI type includes key Azure-specific attributes such as unique Azure object IDs, names, IP addresses, ports, and installation status to maintain accurate records. * **CI relationships:** The discovery pattern automatically establishes relationships among discovered CIs, illustrating ownership, hosting, and containment hierarchy---for example, linking load balancers to IP addresses, backend pools, services, Azure datacenters, and resource groups. * **Top-down Service Mapping discovery:** The Azure LoadBalancer TD pattern enriches discovery by mapping load balancer service connections to backend pool member IP addresses, including load balancing rules and inbound NAT rules, supporting comprehensive service topologies. ## Practical Benefits for ServiceNow Customers * **Automated CMDB population:** Facilitates accurate and up-to-date visibility of Azure Classic Load Balancer infrastructure without manual input. * **Improved service mapping:** Enhances understanding of load balancer configurations and their network relationships, aiding impact analysis and troubleshooting. * **Supports cloud governance:** Enables better control and management of Azure load balancing resources through detailed CI attributes and relationships. Discovery and Service Mapping Patterns finds Azure Classic Load Balancers on your cloud environment. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store. ## Pattern-based discovery and mapping requirements {#azure-classic-load-balancer-pattern__section_rpj_fj2_bgc} Verify the Azure discovery prerequisites section in [Microsoft Azure Cloud discovery using patterns](https://www.servicenow.com/docs/e2521~KHAw8EO7j1nC9QMA "Discovery uses multiple patterns to discover components of the Microsoft Azure Cloud deployment during horizontal discovery. Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store."). ## Data collected by Discovery during horizontal discovery {#azure-classic-load-balancer-pattern__section_ggp_ql2_bgc} Discovery populates the data in the CMDB when running the Azure - Classic LB (LP) pattern. {#azure-classic-load-balancer-pattern__table_cloud_load_balancer__entry__2} | 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 1. Cloud Load Balancer \[cmdb_ci_cloud_load_balancer\]] {#azure-classic-load-balancer-pattern__table_cloud_load_balancer} {#azure-classic-load-balancer-pattern__table_cloud_lb_ipaddress__entry__2} | 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 2. Cloud LB IP Address \[cmdb_ci_cloud_lb_ipaddress\]] {#azure-classic-load-balancer-pattern__table_cloud_lb_ipaddress} {#azure-classic-load-balancer-pattern__table_lb_service__entry__2} | 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 3. Load Balancer Service \[cmdb_ci_lb_service\]] {#azure-classic-load-balancer-pattern__table_lb_service} {#azure-classic-load-balancer-pattern__table_lb_pool__entry__2} | 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. | [Table 4. Load Balancer Pool \[cmdb_ci_lb_pool\]] {#azure-classic-load-balancer-pattern__table_lb_pool} ## CI relationships {#azure-classic-load-balancer-pattern__section_dc4_ghc_dgc} The Azure - Classic LB (LP) pattern creates these relationships to support Azure Classic Load Balancer discovery. {#azure-classic-load-balancer-pattern__table_relationships_classic_lb__entry__3} | 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\] | [ ] {#azure-classic-load-balancer-pattern__table_relationships_classic_lb} ## Connections discovered by Service Mapping during top-down discovery {#azure-classic-load-balancer-pattern__section_connections_td} 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.