> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clearpolicy.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Sign in with Microsoft (SSO)

> Let team members sign in to ClearPolicy with their Microsoft Entra ID work or school account using OpenID Connect (OIDC).

Team members can sign in to ClearPolicy with their Microsoft Entra ID work or school account (or a personal Microsoft account) using OpenID Connect (OIDC).

Microsoft sign-in is for **team members** who manage documents, people, and requests in ClearPolicy. People who are asked to sign a document do not need a ClearPolicy account or Microsoft sign-in—they use [email links or one-time codes](https://docs.clearpolicy.app/guides/sign-document.md).

## Supported capabilities and licensing

* **Protocol:** OpenID Connect (OIDC) and OAuth 2.0 authorization code flow on the Microsoft identity platform v2.0 endpoint.
* **Supported accounts:** Multitenant Microsoft Entra ID work or school accounts and personal Microsoft accounts.
* **Availability and licensing:** Included in every ClearPolicy trial and standard subscription (\$29/month per organization). No separate SSO add-on or enterprise plan is required.
* **Not included in this integration:** SAML 2.0 and SCIM user provisioning are not used by Microsoft sign-in. To sync people from your Microsoft directory into ClearPolicy, see [Microsoft Entra directory sync](https://docs.clearpolicy.app/integrations/entra.md).

## Roles and permissions

Most team members can sign in with Microsoft without IT configuration. If your Microsoft Entra tenant restricts user consent for third-party applications, a Microsoft administrator—such as a **Cloud Application Administrator**, **Application Administrator**, or **Global Administrator**—must approve ClearPolicy for your tenant.

ClearPolicy requests only the following **delegated** permissions for sign-in:

| Permission | Type | Why ClearPolicy requests it |
| - | - | - |
| `openid` | Delegated | Sign the team member in with OpenID Connect and verify their Microsoft identity. |
| `profile` | Delegated | Read the team member’s display name to populate their ClearPolicy profile. |
| `User.Read` | Delegated | Read the signed-in team member’s basic profile (unique ID, name, and email address) from Microsoft Graph. |
| `offline_access` | Delegated | Maintain the Microsoft sign-in connection without repeated permission prompts. |

These permissions do not grant access to other users in your directory, OneDrive files, or mailboxes.

## Set up and test with a pilot team member

### Sign in or create a new ClearPolicy account

1. Open [app.clearpolicy.app/login](https://app.clearpolicy.app/login) (or [app.clearpolicy.app/register](https://app.clearpolicy.app/register) to start a new trial).
2. Click **Microsoft**.
3. Sign in with your Microsoft Entra ID work or school account.
4. Review and approve the requested permissions (or complete your organization’s Microsoft admin approval workflow if prompted).
5. Confirm that you arrive in your ClearPolicy organization dashboard.

If a ClearPolicy team member account already uses the same email address, ClearPolicy links Microsoft sign-in to that account and records your Microsoft account ID for future sign-ins.

### Connect Microsoft to an existing ClearPolicy account

1. Sign in to ClearPolicy with your current sign-in method.
2. Open **Settings → Account → Profile**.
3. Under **Sign-in providers**, find **Microsoft** and click **Connect**.
4. Complete the Microsoft sign-in prompt and return to ClearPolicy.
5. Sign out, then return to [app.clearpolicy.app/login](https://app.clearpolicy.app/login) and click **Microsoft** to verify your pilot sign-in works end to end.

### Add ClearPolicy from the Microsoft Entra admin center

If your IT team prefers to pre-approve ClearPolicy for your organization before team members sign in:

1. Sign in to the Microsoft Entra admin center as an administrator.
2. Add **ClearPolicy** to your tenant’s enterprise applications and grant tenant-wide admin consent for the delegated permissions listed above if your consent policy requires it.
3. Have a pilot team member sign in at [app.clearpolicy.app/login](https://app.clearpolicy.app/login) using **Microsoft** to verify access.

## Microsoft sign-in, OneDrive, and directory sync

ClearPolicy keeps Microsoft connections separate so your organization only grants what it needs:

* **Microsoft sign-in (this page):** Lets individual team members sign in to ClearPolicy.
* **[Microsoft OneDrive](https://docs.clearpolicy.app/integrations/microsoft.md):** Lets a team member import Word documents and PDFs from OneDrive (requests file access separately).
* **[Microsoft Entra directory sync](https://docs.clearpolicy.app/integrations/entra.md):** Organization-level connection approved by a Microsoft administrator to keep your ClearPolicy people list and groups aligned with your Microsoft directory.

## Disconnect Microsoft sign-in

1. Open **Settings → Account → Profile**.
2. Under **Sign-in providers**, click **Disconnect** next to **Microsoft**.

Before disconnecting, make sure you have another way to sign in—such as a password, passkey, or Google sign-in—under [Account and security](https://docs.clearpolicy.app/guides/account-security.md). Disconnecting in ClearPolicy does not remove the enterprise application from your Microsoft Entra tenant; a Microsoft administrator can revoke consent or remove the app in the Microsoft Entra admin center.

## Troubleshooting

> [accordion] Microsoft says “Need admin approval”
>
> Your Microsoft Entra tenant restricts users from approving new apps on their
> own. Ask a Microsoft **Global Administrator**, **Cloud Application
> Administrator**, or **Application Administrator** to approve ClearPolicy’s
> sign-in permissions for your tenant, then retry signing in.

> [accordion] “Your login session expired. Please try again.”
>
> The sign-in state expired or was interrupted before returning from
> Microsoft. Return to
> [app.clearpolicy.app/login](https://app.clearpolicy.app/login), click
> **Microsoft**, and complete sign-in in a single browser tab with cookies
> enabled.

> [accordion] “Authentication with Microsoft failed.”
>
> You may have canceled the Microsoft prompt, declined permissions, or been
> blocked by a Microsoft Conditional Access policy. Retry from
> [app.clearpolicy.app/login](https://app.clearpolicy.app/login), or ask your
> Microsoft administrator to check Entra sign-in logs for Conditional Access
> or consent blocks.

> [accordion] Signed in with the wrong Microsoft account
>
> Sign out of ClearPolicy, then click **Microsoft** again on the login page
> and choose your work or school account. If your browser automatically picks
> another Microsoft session, use an InPrivate or incognito window or sign out
> of the other Microsoft account first.

> [accordion] Your organization requires two-factor authentication
>
> If an organization owner turned on **Require two-factor authentication** in
> ClearPolicy, team members may also be prompted to set up an authenticator
> app or passkey inside ClearPolicy. See [Account and
> security](https://docs.clearpolicy.app/guides/account-security.md).

## Support

For setup help or troubleshooting, open **Support** inside ClearPolicy or email [support@clearpolicy.app](mailto:support@clearpolicy.app). Include your organization name, the approximate time of the sign-in attempt, and any error message shown. Do not send passwords or tokens.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.