← All connectors
Auth
Microsoft Entra ID
Signs an application’s end users in against the customer’s own Entra tenant, so accounts, password policy and MFA remain theirs and nobody maintains a second user list. Your application receives the tenant, the client id, a secret and its redirect URI. What it does not receive is a login screen: the variables configure an OIDC client, whether that’s an oauth2-proxy sidecar or your framework’s own, and that piece still has to exist in the application.
Before you connect it
01
Create an app registration in the customer’s Entra tenant. This needs Application Administrator plus admin consent, usually from the client’s IT rather than the consultant.
02
Add the redirect URI your application will use.
03
Generate a client secret and hand it to the platform once. It is never shown again.
What your application receives
An admin enters these once, and the platform injects them as environment variables at deploy time. Your code reads them. It never sees a login screen or an SDK for this.
ENTRA_TENANT_IDENTRA_CLIENT_IDENTRA_CLIENT_SECRETENTRA_REDIRECT_URIWe use cookies
We use essential cookies to run the site and optional ones to understand usage. See our Privacy Policy.