Configuring a Microsoft Azure load balancer

Last Updated : Jun 05, 2026 |

About this task

You must do the following to configure a load balancer for your Avaya Aura® Device Services cluster:

  • Configure a front-end IP address for the load balancer.

    If you use the Utility Server in your deployment, you also need another front-end IP address for the Utility Server.

  • Connect all network interfaces of all nodes to the load balancer.

  • Configure health monitoring probes.

  • Configure load balancing rules.

Procedure

  1. On the Microsoft Azure administration portal, navigate to Networking > Load Balancers.
  2. Select your load balancer.
  3. Do the following to create a new front-end IP address for Avaya Aura® Device Services nodes:
    1. In the Settings area, click Frontend IP configuration.
    2. Click Add.
    3. In Name, type a name of your choice.
    4. In Subnet, select an appropriate subnet of your network.
    5. In Assignment, select Dynamic.
    6. Click Add.

      Microsoft Azure displays the new front-end IP address.

  4. If you have the Utility Server in your deployment, repeat step 3 to create an additional front-end IP address for the Utility Server.
  5. In the Network area, click Backend pools.
  6. Do the following to connect the nodes of your cluster to the load balancer:
    1. In the Settings area, click Backend pools.
    2. Click Add.
    3. In Name, type a name of your choice.
    4. In Backend pool configuration, select NIC.
    5. In IP version, select IPv4.
    6. In the Virtual machines area, click Add.
    7. In the Add virtual machines to backend pool window, select IP addresses as follows:
      • For the Avaya Aura® Device Services back-end pool, select IP addresses of all Avaya Aura® Device Services nodes in the cluster. These are the IP addresses of the primary eth0 interface of cluster nodes.

      • For the Utility Server back-end pool, select IP addresses of all Utility Server nodes in the cluster. These are the IP addresses of the secondary eth1 interface of cluster nodes.

    8. Click Add.
    9. Click Add again.
  7. If you are using the Utility Server in your deployment, repeat step 6 to connect the IP addresses of all Utility Server nodes to the load balancer.
  8. In the Settings area, click Health probes and then configure two health probes with the following settings:

    Setting

    First health probe

    Second health probe

    Name

    Any name of your choice

    Any name of your choice

    Protocol

    TCP

    HTTPS

    Path

    Not applicable

    /

    Port

    80

    443

    Interval

    5 seconds

    5 seconds

    Unhealthy threshold

    2 consecutive failures

    2 consecutive failures

  9. Do the following to create six load balancing rules for the Avaya Aura® Device Services nodes and three load balancing rules for the Utility Server nodes:
    1. In the Settings area, click Load balancing rules.
    2. Click Add.
    3. In Name, type a name of your choice.
    4. In IP Version, select IPv4.
    5. In Protocol, select TCP.
    6. In Health Probe, select the health probe that you created that uses the TCP protocol.
    7. In Idle timeout (minutes), type 15.
    8. In Floating IP, select Disabled.
    9. In TCP reset, select Enabled.
    10. Configure the remaining settings as follows:
      Table 1: Load balancing rules for Avaya Aura® Device Services nodes

      Setting

      Rule 1

      Rule 2

      Rule 3

      Rule 4

      Rule 5

      Rule 6

      Frontend IP address

      The front-end IP address for the Avaya Aura® Device Services nodes.

      Port

      80

      443

      8440

      8442

      8443

      8445

      Backend port

      80

      443

      8440

      8442

      8443

      8445

      Session Persistence

      None

      None

      None

      None

      None

      Client IP and protocol

      Backend pool

      The back-end pool for the Avaya Aura® Device Services nodes.

      Table 2: Load balancing rules for Utility Server nodes

      Setting

      Rule 1

      Rule 2

      Rule 3

      Frontend IP address

      The front-end IP address for the Utility Server nodes.

      Port

      80

      443

      8443

      Backend port

      80

      443

      8443

      Session Persistence

      None

      None

      None

      Backend pool

      The back-end pool for the Utility Server nodes.