Configure Microsoft Entra ID single sign-on

This page explains how to set up single sign-on (SSO) between your Microsoft Entra ID (formerly Azure AD) and Smart Placement. SSO integration enables your users to access Smart Placement through their existing Microsoft credentials, with centralised access management and built-in multi-factor authentication. When you remove a user from your Microsoft environment, they automatically lose access to Smart Placement, giving you complete control over user access.

Once configured, sign in to Smart Placement using the following authentication flow:

  1. Navigate to your Artificial instance. For example, foo.artificial.app.

  2. Enter your organisation name. For example, artificial or company-name. You are redirected automatically to Microsoft login.

  3. Authenticate using your Microsoft credentials.

  4. Microsoft handles multi-factor authentication (MFA).

How to configure Microsoft Entra ID SSO

Prerequisites

Before you begin, ensure you have:

  • Administrative access to your Microsoft Entra ID tenant.

  • Permission to register applications in Entra ID.

Provide Artificial’s callback URL to Entra ID

Register your application in Microsoft’s platform, taking care to configure the redirect URI correctly:

  1. Navigate to the "Redirect URI (optional)" section in the registration form.

  2. Set the platform to Web (not SPA).

    You must select "Web" as the platform. Do not select "SPA" (Single Page Application).

  3. Enter the following redirect URI (callback URL) exactly as shown:

    https://auth.artificialos.com/login/callback

Gather required information

After registering your Entra ID application, collect the following information and provide it to your client success manager. We require all of these details to complete the configuration:

  1. Domain information

    • Your Microsoft Entra ID domain.

    • Tenant domain (if different from your Entra ID domain).

  2. Specify which Identity API version your organisation uses:

    • Microsoft Identity Platform (v2) – most common.

    • Azure Active Directory (v1).

    • OpenID Connect (alternative naming).

  3. Your application’s Client ID, which appears as a UUID in this format:

    abc123def-abc23def-abc123def-abc23def
    If your Client ID doesn’t match this UUID format, please verify your application registration.

  4. The Client secret generated for your application.

Getting help

If you encounter any issues during configuration or need clarification on any step, please contact your client success manager directly, or email client.success@artificial.io.