Software-only installation checklist for Microsoft Azure

Last Updated : Jun 10, 2026 |

The following checklist outlines the tasks that you must perform when deploying Avaya Aura® Device Services as a software-only application in a Microsoft Azure environment.

No.

Task

Notes

1

Ensure that the virtual machines that you plan to use to deploy Avaya Aura® Device Services comply with the requirements for software-only installation.

For information about the Microsoft Azure virtual machine size that is required for each Avaya Aura® Device Services profile, see Resource profile specifications for Microsoft Azure virtual machines.

2

Download the Avaya Aura® Device Services software-only installation package from PLDS.

The software-only installation package includes the following files:

  • Software-only system layer installer.

  • Avaya Aura® Device Services application installer.

The package file name has the aads-swonly-AADS_VERSION.tgz format.

For more information about the software downloading process, see Downloading software from PLDS.

3

Prepare your Microsoft Azure instance for software-only installation.

See Prerequisites for software-only deployment on Microsoft Azure.

4

Deploy a virtual machine and install RHEL 8.4 or RHEL 8.10 on Microsoft Azure.

Avaya Aura® Device Services requires the RHEL 8.4 or RHEL 8.10 operating system. For information about installing Linux operating systems on Microsoft Azure virtual machines, see the official documentation at Create a Linux virtual machine in Azure. For the settings, specific for Avaya Aura® Device Services, see Red Hat Enterprise Linux virtual machine deployment in Microsoft Azure.

By default, the size of the primary disk of your virtual machine is not equal to 125 Gb. You must resize the disk to 125 Gb during or after virtual machine deployment.

Avaya also recommends that you install the latest security updates on RHEL.

Note:

During the RHEL installation process, you create primary network interface eth0. Do not modify the ifcfg-eth0 configuration file before installing the system layer. Avaya Aura® Device Services deployment might fail if you modify this file before installing the system layer. You can freely modify this file after you install the system layer.

5

If you are planning to use the Utility Server, configure the eth1 secondary network interface.

See Configuring the secondary network interface on a Microsoft Azure virtual machine.

Note:

Do not modify secondary network interface configuration file ifcfg-eth1 configuration file before installing the system layer. Avaya Aura® Device Services deployment might fail if you modify this file before installing the system layer. You can freely modify this file after you install the system layer.

6

Add the required virtual hard disks to your virtual machine.

See Creating required virtual hard disks for a virtual machine.

7

Enable root access to RHEL.

RHEL deployed on Microsoft Azure does not have the root user enabled by default. For more information, see Enabling root access.

8

Create disk partitioning on RHEL.

Avaya Aura® Device Services requires specific disk partitioning to organize data storage. For more information about creating disk partitioning, see Creating disk partitioning for a Microsoft Azure virtual machine and Disk partitions for software-only deployments.

9

Configure security groups on Microsoft Azure.

See Configuring security groups and Assigning security groups to network interfaces.

10

Create a non-root Linux user.

The installation and administration of the Avaya Aura® Device Services server is more secure when performed by non-root users with sudo privileges. For more information, see Creating an administrative user.

11

Enable the YUM package manager on RHEL.

The YUM package manager is used to install the required packages. For more information about enabling YUM, see the Red Hat YUM documentation.

12

Install additional packages required by Avaya Aura® Device Services.

By default, RHEL 8.4 or RHEL 8.10 does not contain certain packages that Avaya Aura® Device Services requires. You must install these packages manually. For more information, see Additional packages required by Avaya Aura Device Services and Installing additional RHEL 8.4 or RHEL 8.10 packages manually.

13

Enable the Haveged service.

See Enabling the Haveged service.

14

Enable FIPS mode (optional).

For software-only deployments, you can only enable FIPS mode before installing the system layer. For more information about enabling FIPS, see Enabling FIPS for software-only systems.

15
Do one of the following to manage additional RHEL packages:

  • Register your RHEL instance to the Red Hat subscription.

  • Create a local repository for RPM installation or updates.

For more information, see RHEL packages management and Enabling required RHEL repositories.

Registering your RHEL instance to the Red Hat subscription is the preferred option.

16

Prepare you RHEL system for installing the software-only system layer.

See Prerequisites for installing the system layer on Microsoft Azure.

17

Install the software-only system layer on your RHEL.

The system layer is low-level software that forms the required operational environment for Avaya Aura® Device Services.

For more information, see Installing the system layer.

18

Ensure that:

  • The chronyd service is up and running.

  • System Manager and Session Manager are reachable from your virtual machine. This is only required if you deploy Avaya Aura® Device Services in Avaya Aura® environment.

Perform these checks to ensure that the system layer is installed successfully so you can install the Avaya Aura® Device Services application.

For more information, see Checking the Chrony service status and Checking the connection to System Manager and Session Manager.

22

In cluster deployments, configure the Microsoft Azure load balancer.

See Creating a Microsoft Azure load balancer and Configuring a Microsoft Azure load balancer.

After deploying a virtual machine, do the following: