Set up single sign-on with Microsoft Entra ID
2 min read · Updated Jul 21, 2026
Current signs your team in with Microsoft Entra ID, so access follows your existing identity policies — conditional access, MFA, and offboarding included.
Before you start

- +A Microsoft Entra tenant and an account that can create app registrations (Application Administrator or Global Admin).
- +Tenant Admin role in Current.
Register the app in Entra

- 1Create an app registrationEntra admin center → App registrations → New registration. Name it "Current" and choose single-tenant unless you have multiple Entra tenants.
- 2Add the redirect URICopy it from Current's Settings → Authentication → Entra ID panel and paste it as a Web redirect URI. Current validates redirect URIs against an allowlist, so it must match exactly.
- 3Create a client secretCertificates & secrets → New client secret. Copy the value immediately — Azure only shows it once.
- 4Note the IDsYou'll need the Application (client) ID and the Directory (tenant) ID from the app's Overview page.
Configure Current
- 1Enter the three valuesSettings → Authentication → Entra ID: client ID, tenant ID, and the client secret. The secret is encrypted at rest and never returned to the browser.
- 2Test with your own accountUse the Test sign-in button before enforcing anything. The flow uses a CSRF nonce and validates the redirect — if the URI doesn't match the allowlist, the test fails with a clear error.
- 3Enforce SSO (optional)Once the test passes, flip Require SSO for all members. Password sign-in is disabled for everyone except break-glass admins.
Note
Claiming your email domain needs proof of ownership
Claiming an email domain for single sign-on — so sign-ins from that domain belong to your workspace — now requires you to prove you own it before the claim takes effect: add a DNS TXT record Current gives you, or reply from the domain's postmaster address. This stops one workspace from claiming a domain that isn't theirs and catching other people's sign-ins. Domains you've already claimed keep working; this only gates new claims.
Common errors
| Error | Fix |
|---|---|
| AADSTS50011 (redirect mismatch) | The redirect URI in Azure doesn't exactly match the one Current shows. Copy-paste it again — trailing slashes count. |
| AADSTS700016 (app not found) | Wrong tenant ID, or the registration is in a different Entra tenant than the signing-in user. |
| Secret expired | Entra secrets expire (6–24 months). Create a new secret and update it in Current. |
Heads up
Don't lock yourself out
Keep at least one Tenant Admin able to sign in before enforcing SSO-only, and calendar a reminder for the client-secret expiry date.
Was this helpful?
