> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/access-and-sharing/authentication-and-sso/sign-in-sign-up/auth0-sso-oauth-2.0-1.md).
# Azure AD SSO OAuth 2.0
In this section you will learn about Azure AD SSO OAuth 2.0
### 1. Go to Sign In & Sign Up -> Authentication
### 2. Create a new External SSO
Specify **Name** and **New members team** for newly created **External SSO**
### 3. Go to Azure Active Directory -> App registrations and create new new Application
In **Redirect URI (optional)** section fill the following fields
* Platform: Web
* URL: copy **REDIRECT URL** from **Jet Admin -> External SSO** -> **Application parameters** section**.**
### 4. Copy credentials to Jet Admin
* Copy **Application (client) ID** and **Directory (tenant) ID** from **App Registration** page in **Azure portal** to Jet Admin **External SSO**
* Then open **Certificates & secrets** page, create new **Client secret** and copy it's **Value** to Jet Admin **Client Secret**
* You should also set **Scope** to **openid,profile,email,offline\_access**.
### 5. You are all set
**SSO** button should appear automatically on the login and register pages when visiting **Jet Admin** from your **custom domain**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.jetadmin.io/access-and-sharing/authentication-and-sso/sign-in-sign-up/auth0-sso-oauth-2.0-1.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
