Working with Azure AD/ Microsoft Entra Identity

Integrating AVEVA Integration Service with a Microsoft Entra Identity environment involves three key aspects:

• Installation and configuration of AIS

• Communication with the AIS Data API

• AIS communication with back-end data sources

While AIS can be installed in a Microsoft Entra Identity environment, the local AIS Data API only supports NTLM authentication.

AIS continues to use standard Active Directory (Windows Authentication) to access back-end data sources. Examples include:

• Communication with SQL Server using Windows Authentication

• Accessing AVEVA ERM on-premises systems using NTLM authentication

Using AIS in a MS Entra Identity Environment/Azure AD Machine – User Addition Format

Requirements

While adding a user to the AIS Administrators group from the Configurator on an Azure AD machine, the username must be entered in the following format:

AzureAD\<username/serviceaccount>@Domain.com

For configuring the Application Pool Identity, the format must be:

AVEVA\<username/serviceaccount>

When the above formats are followed, the configuration completes successfully.