# Configure your sign-in provider

Agent Mission Control user guide > Administration

> Connect Microsoft Entra or Auth0, map new users, and test changes before they go live.

**Who can do this:** Tenant Admin, Super Admin

Go to **Settings > Identity**. AMC supports **Microsoft Entra** and **Auth0**.

## Enter the connection

- **Authority:** for Entra, `https://login.microsoftonline.com/<tenant ID>/v2.0`. For Auth0, your domain including `https://`.
- **Client ID** and **Client secret** (write-only).
- **Audience:** for Entra, the same value as the Client ID.
- **Scopes:** must include `openid`. Usually `openid, profile, email`.
- **Redirect URIs:** register `<your AMC address>/api/auth/callback` as the callback and your AMC address as the sign-out URL in your provider.

## Map new users

Under **New users**, add **Claim mappings** from a provider group to an AMC base role and, optionally, a department. Mappings apply at a person's first sign-in and only set how they're listed. Access still comes from roles granted under **Settings > Users**.

## Test, then activate

1. Select **Save Changes**. Changes that affect sign-in become a pending change; people keep signing in with the current settings.
2. Select **Test sign-in** and sign in with an admin account in the window that opens.
3. Within 15 minutes of a passing test, select **Activate**.

Select **Discard changes** to drop a pending change. If the test fails, the result names the reason, such as no matching AMC user or an unverified email.

## Related

- [Add users, departments, and roles](https://www.agentmissioncontrol.ai/guide/users-and-departments/)
- [Troubleshooting and FAQ](https://www.agentmissioncontrol.ai/guide/troubleshooting/)

---
Source: https://www.agentmissioncontrol.ai/guide/sign-in-provider/ · Last updated 2026-10-21 · Full guide index: https://www.agentmissioncontrol.ai/llms.txt