As of version 19, the connection to Microsoft's cloud directory is called Entra ID in the Server Manager (in version 18 it was still called "Azure AD"). Imported Entra ID users log on to the Enterprise Server with their Microsoft credentials. This article describes the requirements, the setup in version 19, and the approach recommended by our support team via OpenID Connect (OIDC).
Key requirement: WebView2 Runtime
The Entra login dialog in the Server Manager requires the Microsoft Edge WebView2 Runtime on the server system. If it is missing, only a white/blank window opens when signing in – by far the most common cause of failed Entra connections. In this case, install the WebView2 Runtime (Evergreen) from Microsoft. If login errors persist afterwards, delete the EBWebView cache in the %temp% directory and try again.
Setting up the connection (version 19)
In the Server Manager, open Manage → Server settings → Entra ID and click New... in the Tenants area (alternatively via Tools → Import from Entra ID).
Sign in with the administrator account of your Microsoft organization – a regular user account is not sufficient; the two-factor authentication required by Microsoft cannot be bypassed. On the first successful admin login, the application registers itself in your tenant; it does not have to be added from the Entra gallery.
Then, in Microsoft Entra ID, use Assign users and groups to assign the administrators who are to perform the synchronization.
Import users and groups via Tools → Import from Entra ID (select the organization, search, check the desired entries, Import). Entra ID users can only be added to the server via import. Configure automatic synchronization under Manage → Server settings → Entra ID → Synchronization.
Note: In early 2026, Microsoft tightened the validation of redirect URLs; the previous Entra connection failed as a result. The issue is fixed as of version 19.1.0 – if you encounter login errors, update Enterprise Server and Server Manager first.
Recommended approach: OIDC with your own app registration
Our support team recommends connecting via OpenID Connect with your own app registration in your Entra tenant – it is more independent of changes to the standard connection. Under Manage → Server settings → OpenID Connect (or Tools → Import from OIDC), click New... to create an identity provider of type Entra ID and enter: the Discovery endpoint (https://{Provider}/{TenantId}/.well-known/openid-configuration), the Application (client) ID of your app registration, and the Redirect URL – it must match the redirect URI stored in the app registration exactly. For Entra ID, the Management API tab (API Base URL, Client Secret) is additionally available. Verify the configuration using Test client login and Test server login.
Migrating from Active Directory to Entra ID
Since version 18.0.4, the authentication type can be switched per user; this requires the user's object ID at the identity provider (visible for imported users in the user properties, Entra ID tab). Switching is not possible for groups – import Entra groups anew instead.
Related topics:
Active Directory import and synchronization
Setting up Single Sign-On (SSO) login to the Enterprise Server