> For the complete documentation index, see [llms.txt](https://docs.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryprotege.com/review/enterprise-features/enterprise-sso/azure-ad.md).
# Azure AD
**Overview**
This guide provides instructions on how to create and configure a SAML-based Single Sign-On (SSO) application in Azure Portal. Follow these steps to integrate your application with Protege.
**Step 1: Create a SAML Application in Azure Portal**
1. **Log in to Azure Portal:**
* Sign in to the [Azure portal](https://portal.azure.com) using your administrator credentials.
2. **Register a New Application:**
* Navigate to **Enterprise applications**.
* Click on **New application**.
* Select **Create your own application**.
* Provide a name for the application and choose **Integrate any other application you don't find in the gallery (Non-gallery)**.
3. **Set Up SAML-based SSO:**
* Under the application’s settings, go to **Single sign-on**.
* Choose **SAML** as the single sign-on method.\
4. **Basic SAML Configuration:**
* On the **Basic SAML Configuration** section, click **Edit** and fill in the following fields: replace `{{org-name}}` with your organization name in `kebab-case`
* **Identifier (Entity ID)**: `urn:auth0:protegeai:{{org-name}}-production`
* **Reply URL (Assertion Consumer Service URL)**: [https://protegeai.us.auth0.com/login/callback?connection={{org-name}}-production](https://protegeai.us.auth0.com/login/callback?connection={{CLIENT}}-production)
* **Sign on URL**: Leave this blank.
**Step 2: Provide the required information**
Please collect the information below and share with us.
1. **Primary Domain**
* You can find the Primary domain in Microsoft Entra ID
2. **Application ID**
* The Application ID of the Enterprise Application you created in **Step 1**
3. **Client Secret**
* Visit **App registrations** and open your new Enterprise Application
* Create a new secret and save the **Value**. Please note that the secret have an expiration so we need to renew the secret before it expires
Once we have the required information above, our team will handle the remaining setup. We will inform you shortly once the integration is ready for use.
***Note:*** If you experience any issues during the linking process or have questions related to Single Sign-On (SSO) integration, please reach out to our support team at . We are available to assist you and ensure a seamless integration with your authentication system.
---
# 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.tryprotege.com/review/enterprise-features/enterprise-sso/azure-ad.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.
