Hideez Server as an External Authentication Method for Microsoft Entra ID via OIDC

The Hideez + Microsoft Entra ID

Configure OIDC for Entra ID

This guide provides step-by-step instructions to configure Hideez Identity Cloud as an External Authentication Method (EAM) for Microsoft Entra ID using OIDC (OpenID Connect). This setup facilitates seamless external authentication and ensures secure user login through an additional MFA (Multifactor Authentication) step.

Important Notes

  • Hideez Server as an External Authentication Method (EAM) does not enable direct login to Microsoft Entra ID. It serves solely as an additional MFA verification method.

  • To enable this feature, an Entra ID P1 license is required.

Additional Resources

For further setup guidance, refer to the following articles:

Step 1: Register the App in Microsoft Entra

  1. Navigate to Identity → Applications → App Registrations.

  2. Click + New registration.

  1. Define a name for the app.

  2. Set Supported account type to:

    • Accounts in any organizational directory (Any Entra ID directory - Multitenant).

  3. Under the Redirect URI section:

  • Select Web platform.

  • Enter: https://<hideez server name>/connect/authorize

    • Example: https://dev.hideez.com/connect/authorize

  1. Click Register.

After registering, keep the Application ID from the Essentials section. You'll need it later to configure your EAM in Hideez Enterprise Server.

Step 2: Configure Integration in Hideez Enterprise Server

  1. Go to Hideez Enterprise Server.

  2. Go to Integrations → OIDC.

  3. Click Create App Integration and set the following parameters:

    • App Type: Entra ID External Authentication Method (EAM).

  4. Fill in the following:

    • Tenant ID

    • Application ID

  5. Click Create.

Keep the tab Add openid connect client with values Client ID, Discovery Endpoint, and Entra Application ID ready for the next step.

Step 3: Add External Method in Entra ID

  1. Go back to Microsoft Entra Admin Center.

  2. Navigate to Protection → Authentication Methods → Policies.

  3. Click + Add external method (Preview).

  4. Set the following parameters:

    • Name: The name users will see during Entra ID login when choosing their authentication method.

    • Client ID: Paste from the app integration in Hideez Enterprise Server.

    • Discovery Endpoint: Paste from the app integration in the Hideez Enterprise Server.

    • App ID: Paste from the app integration in Hideez Enterprise Server.

  5. Click Request permission to grant admin consent for the app to read user information.

  6. Click Enable.

  1. Review the Included and Excluded Targets (all users are included by default).

  2. Click Save.

Step 4: Configure Conditional Access Policy in Entra ID (Optional)

During migration, administrators are advised to create parallel Conditional Access Policies to test new configurations with a subset of users. This ensures minimal disruption and allows admins to verify the functionality of the custom controls.

  1. Navigate to Protection → Conditional Access → Policies.

  2. Click + New Policy (or edit an existing policy).

  1. Configure the policy:

  • Specify Users: Define the users who will be affected by this policy.

  • Target Applications: Specify the applications covered by this policy.

  • Access Requirements:

    • Choose Require multifactor authentication so that the EAM (Hideez Enterprise Server) is used as the MFA step.

  1. Click on Save.

More information from Microsoft can be found here Using Custom Control and EAM in parallel.

Last updated