Skip to content

Commit e6344d3

Browse files
drernieclaude
andauthored
docs(sso): revamp Azure Active Directory section for Microsoft Entra ID (#4772)
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
1 parent 7077590 commit e6344d3

File tree

3 files changed

+24
-29
lines changed

3 files changed

+24
-29
lines changed

docs/imgs/azure_console_1.png

-93.8 KB
Binary file not shown.

docs/imgs/azure_console_2.png

-92.6 KB
Binary file not shown.

docs/technical-reference.md

Lines changed: 24 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -49,35 +49,30 @@ to Google's OAuth 2.0 server.
4949
Copy the `Client ID` and `Client secret` to a safe place.
5050
Add `<QuiltWebHost>/oauth-callback` to *authorized redirect URIs*.
5151

52-
### Active Directory
53-
54-
1. Go to Azure Portal > Active Directory > App Registrations.
55-
1. Click "New Registration".
56-
1. Name the app, select the Supported account types.
57-
1. Click "Add a platform", "Web", and enter the `Redirect URIs` value
58-
`<QuiltWebHost>/oauth-callback`. Click "Save" at the bottom.
59-
1. Once the application has been created you will need both its `Application
60-
(client) ID` and `Directory (tenant) ID`.
61-
62-
![](./imgs/azure_console_1.png)
63-
64-
1. Go to "Client credentials" and create a new client secret. Note you will use
65-
the `Value` (and not the `Secret ID`).
66-
67-
![](./imgs/azure_console_2.png)
68-
69-
1. Your `AzureBaseUrl` will be of the form
70-
`https://ENDPOINT/TENANT_ID`. In most cases `ENDPOINT` is simply
71-
`login.microsoftonline.com`. Reference
72-
[Microsoft identity platform and OpenID Connect protocol](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-protocols-oidc)
73-
and
74-
[National clouds](https://docs.microsoft.com/en-us/azure/active-directory/develop/authentication-national-cloud)
75-
for further details.
76-
> **If `AzureBaseUrl` doesn't end in `/v2.0`
77-
then append `/v2.0` to it.**
78-
1. Click "Save".
79-
1. Copy the `Application (client) ID`, `Client secret Value`, and
80-
`AzureBaseUrl` to a safe place.
52+
### Microsoft Entra ID (Azure Active Directory)
53+
54+
1. Go to [Microsoft Entra admin center](https://entra.microsoft.com)**Microsoft Entra ID → Applications → App registrations → New registration**.
55+
1. Name the app, select the supported account types, and click **Register**.
56+
Note the **Application (client) ID** and **Directory (tenant) ID**.
57+
1. Go to **Authentication → Add a platform → Web**. Add the redirect URI
58+
`<QuiltWebHost>/oauth-callback`. Under **Implicit grant and hybrid flows**,
59+
enable **ID tokens** (required — login will fail without it). Click **Save**.
60+
1. Go to **Certificates & secrets → New client secret**. Copy the **Value**
61+
immediately — it is not shown again. (Do not use the Secret ID.)
62+
1. Go to **API permissions → Add a permission → Microsoft Graph → Delegated**.
63+
Add `openid`, `profile`, `email`, `offline_access`, and `User.Read`, then
64+
click **Grant admin consent**. Without admin consent, each user is typically
65+
prompted to grant these permissions on their first login; granting admin consent
66+
approves them tenant-wide (subject to your org's policies) and avoids end-user prompts.
67+
1. Your `AzureBaseUrl` is `https://login.microsoftonline.com/<TENANT_ID>/v2.0`.
68+
Reference [Microsoft identity platform and OpenID Connect protocol](https://learn.microsoft.com/en-us/entra/identity-platform/v2-protocols-oidc)
69+
and [National clouds](https://learn.microsoft.com/en-us/entra/identity-platform/authentication-national-cloud)
70+
for non-standard endpoints.
71+
> **`AzureBaseUrl` must end in `/v2.0`. Append it if missing.**
72+
1. For SSO Permissions Mapping:
73+
- Create security groups in Entra and assign users.
74+
- In the app registration, go to **Token configuration → Add groups claim** (or **Edit** if it already exists) and configure it to emit **Group IDs** in the **ID token**.
75+
- Create a [configuration file](./advanced-features/sso-permissions.md) to map Entra Group IDs to Quilt roles.
8176
1. Proceed to [Enabling SSO](#enabling-sso).
8277

8378
### Okta

0 commit comments

Comments
 (0)