> For the complete documentation index, see [llms.txt](https://missiveapp.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://missiveapp.com/docs/administration/saml-and-sso/configuring-azure-active-directory.md).
# Microsoft Entra ID (Formerly Azure AD)
Set up Microsoft Entra ID SSO with Missive step by step.
### Step 1
Log in to [Azure portal](https://portal.azure.com/), navigate to **Microsoft Entra ID** and select **Enterprise applications** in the left sidebar.
### Step 2
Click **+ New application**.
### Step 3
Click **+ Create your own application**, name it “Missive”, select “**Integrate any other application you don't find in the gallery**” and click **Create**.
### Step 4
Click **Single sign-on** in the left sidebar, then select the **SAML** method.
### Step 5
Logged in as an admin in Missive, open your **Organizations** settings, then the **SSO** tab, copy the required fields and paste them in the Azure **Basic SAML Configuration** form as shown below.
### Step 6
Copy the **Login URL** field and paste it in your Missive SSO settings in the **Entry point** field.
### Step 7
Download the **Certificate (Base64)**, copy its text content, and paste it in your Missive SSO settings in the **Signing certificate** field. You may need to rename the downloaded file to a **.txt** extension in order to easily copy the content.
### Step 8
Click **Users and groups** in the left sidebar, then add all users who should log in to Missive.
### Step 9
In your Missive SSO settings, enable Single Sign-On.
---
# 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://missiveapp.com/docs/administration/saml-and-sso/configuring-azure-active-directory.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.
