Skip to main content

Single sign-on with Microsoft Entra ID

Gate treats your enterprise identity provider as core platform, not a bolt-on. Connecting Microsoft Entra ID (formerly Azure AD) means your team signs in to Kilimanjaro with their corporate Microsoft identity — and the Conditional Access policies, MFA, and device-compliance rules you already enforce in Entra travel with them. Federation is native to the Identity-Aware Kernel; there's nothing to install.

You configure this once at the org level, under Org scope → Identity provider. Changing which identity providers your org trusts routes through Maker-Checker approval by default.

1. Prerequisites​

In the Entra admin center, create an app registration for Kilimanjaro:

  • Note the Application (client) ID, your Directory (tenant) ID, and create either a client secret or a client certificate.
  • For SAML, configure the app as an Enterprise Application with SAML-based sign-on instead.

You'll need an org-admin role in Kilimanjaro to add the provider.

2. Create the identity-provider config​

In Org scope → Identity provider, add a provider and choose Microsoft Entra ID. Pick the protocol:

  • OIDC via the native Microsoft provider (recommended) — supply the issuer (https://login.microsoftonline.com/{tenantId}/v2.0), the client ID, and either the client secret or the client certificate. Gate resolves the authorize and token endpoints under your tenant automatically.
  • SAML — supply Entra's SSO URL and signing certificate; the audience is Gate's entity ID.

Secrets and certificates are pasted once and stored in the Vault — referenced thereafter, never displayed again.

3. Exchange metadata​

Paste Gate's redirect URI (OIDC) or ACS URL and entity ID (SAML), shown on the config screen, into your Entra app registration's redirect/SP settings.

4. Map attributes and groups to roles​

Entra claimMaps to
preferred_usernameemail
given_namefirst name
family_namelast name
groups (object ID)cached group membership (drives role assignment)

Map Entra group object IDs to Kilimanjaro roles. Gate also records the acr and amr claims on each sign-in, so the audit trail captures how the user authenticated (MFA method, authentication-context class) — useful evidence that your Conditional Access policy was satisfied.

5. Conditional Access is honored upstream​

You don't reconfigure your Conditional Access rules in Kilimanjaro, and Gate doesn't try to re-implement them. Entra enforces MFA, device compliance, and location policy during the redirect — Gate only receives a token if Conditional Access passed. The amr/acr claims Gate records are your audit evidence that it did. This is the point of federation: your existing policy engine stays authoritative.

UserGateMicrosoft Entra IDopen the start URLredirect to EntraConditional AccessMFA, device, locationtoken, only if it passedredirect URI or ACS URLmap groups to rolesrecord acr / amr, JITsigned in with mapped roles
Entra enforces Conditional Access during the redirect, so Gate only ever receives a token for a sign-in that passed it.

6. Enable lifecycle sync (optional)​

Enable SCIM for proactive provisioning and deactivation — Entra pushes user lifecycle events to Gate so a disabled Entra account loses Kilimanjaro access immediately. Without SCIM, access reconciles from group membership on next sign-in.

7. Availability​

OIDC sign-in via the native Microsoft provider, SAML federation and SCIM lifecycle provisioning are all available on every plan.

8. Test and verify​

Sign in through the config's start URL (or your org's normal entry point, where Entra now appears as an option). Gate provisions the user just-in-time on first sign-in. Confirm the role mapping landed and that the audit log shows the sign-in with its amr/acr context.

See also​