Modern authentication with Azure AD
With Modern Authentication, users authenticate with OpenID Connect against the customer’s own Azure tenant using a browser. This means that user accounts are centralized to the customer’s own Azure and are by definition subject to the already-existing security policies.
Tenant configuration
To enable Azure AD authentication integration to Enreach Voice services, two Enreach Voice enterprise applications must be consented by the customer’s Azure tenant administrator:
EnreachVoice application
Enables the users to sign in via Enreach Identity
EnreachVoice UserSync application
Enables Enreach backend to read and synchronize user information from Azure. This is needed to correlate users in Enreach system to Azure users.
Consent is granted by generating the following two links pointing to the customer tenant.
https://login.microsoftonline.com/<tenant-id>/adminconsent?client_id=36773b1f-bfe6-4cc6-b5d8-cd36a7b740a7
https://login.microsoftonline.com/<tenant-id>/adminconsent?client_id=5717fd23-b335-454d-bb65-af56dca00304
After generating the links by populating the correct tenant id, a tenant Global Global administrator follows the links and grants the consents in Azure.
Classic authentication
In classic modeMore details and step-by-step instructions on how to configure modern authentication with AzureAD are here: Enabling SCIM integration with Azure AD
Classic authentication integration with AzureAD
| Note |
|---|
Classic authentication mode is maintained for backwards compatibility. All new deployments are done using Modern Authentication. |
In classic authentication integration, user credentials are passed through the Enreach backend to Azure for validation. This mode is maintained for backwards compatibility - new deployments focus on Modern Authentication.
To enable classic Azure AD Authentication integration for your organization, an Azure AD application must be registered to the customer Active Directory in Azure management portal.
...