║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║

---

title: Add Microsoft as an EASIE connection description: Learn how to allow users to sign up and sign in to your Clerk app with their Microsoft account using EASIE SSO.

<TutorialHero beforeYouStart={[ { title: "Add the Enhanced authentication add-on to your Pro plan", link: "/pricing", icon: "plus-circle", }, { title: "Enable email for your app.", link: "/docs/guides/configure/auth-strategies/sign-up-sign-in-options", icon: "key", }, { title: "A Microsoft Azure account is required.", link: "https://azure.microsoft.com/en-us/free/", icon: "user-circle", } ]} />

Enabling EASIE SSO with Microsoft (formerly Active Directory) allows your users to sign up and sign in to your Clerk application with their Microsoft account.

Configure for your development instance

For development instances, Clerk uses preconfigured shared credentials and redirect URIs—no other configuration is needed.

1. In the Clerk Dashboard, navigate to the SSO connections page.
2. Select Add connection and select For specific domains or organizations.
3. Under EASIE, select Microsoft.
4. Enter the Domain. This is the email domain of the users you want to allow to sign in to your application. Optionally, select an Organization.
5. Select Add connection.

Configure for your production instance

For production instances, you must provide custom credentials. If you already configured Microsoft as a social provider, you can skip this step. EASIE SSO will automatically use the credentials you configured for your social connection.

To make the setup process easier, it's recommended to keep two browser tabs open: one for the Clerk Dashboard and one for your Microsoft Azure portal.

<Steps> ### Enable Microsoft as an EASIE connection

1. In the Clerk Dashboard, navigate to the SSO connections page.
2. Select Add connection and select For specific domains or organizations.
3. Under EASIE, select Microsoft.
4. Enter the Domain. This is the email domain of the users you want to allow to sign in to your application. Optionally, select an Organization.
5. Save the Redirect URI somewhere secure. Keep this modal and page open.

Create a Microsoft Entra ID app

<Include src="_partials/authentication/microsoft/create-app" />

Get your Client ID and Client Secret

<Include src="_partials/authentication/microsoft/get-client-id-secret" />

Enable OpenID

<Include src="_partials/authentication/microsoft/enable-openid" />

Secure your app against the nOAuth vulnerability

<Include src="_partials/authentication/microsoft/noauth" />

Set the Client ID and Client Secret in the Clerk Dashboard

<Include src="_partials/authentication/social-connections/set-client-id-secret" />

Test your connection

<Include src="_partials/authentication/social-connections/test-your-connection" /> </Steps>

║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║
║