New in Avaya Aura Device Services Release 10.2

Last Updated : Jun 10, 2026 |

The following is a summary of new functionalities added to Avaya Aura® Device Services in Release 10.2:

Enable/Disable logging

  • Before Release 10.2, AADS supported extended logging at the system level only. With AADS Release 10.2, you can enable or disable logging at an individual user level.

  • LOG_VERBOSITY property is added in the AADS dynamic configuration at a user level.

Support for VMware 8.0

With Release 10.2, Avaya Aura® applications support the VMware® vSphere ESXi 8.0 and VMware® vCenter Server 8.0 in a VMware virtualized environment.

Client ID configuration

Before Release 10.2, client ID used by J100 phones was hard-coded in AADS and couldn’t be configurable. With Release 10.2, you can configure the client-id in AADS, which enables IAM to apply customer-specific requirements in the access token when the client authenticates.

Dynamic configuration for telecommuter number

Using AADS auto-config service API, the administrator can configure the telecommuter number and associate it with agents using Workplace. With this release, only one telecommuter number is supported.

Upgraded Keycloak version

Upgraded Keycloak version from Release 6.0.1 to Release 22.0.4.

Added MS Graph API support

AADS now supports MS Graph API as a replacement for MS Azure API, which Microsoft retired this year.

For more information on MS Graph API replacing MS Azure API, see PSN at https://download.avaya.com/css/public/documents/101086282 for details.

Note:

Microsoft announced EoS for Azure AD Graph API. MS Graph API will replace Azure AD Graph API.