> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/platform/organizations/single-sign-on/microsoft-azure-ad.md).

# Microsoft Azure AD

## In Azure AD Admin: Create an App Registration

An administrator for your company's Microsoft Azure AD needs to log in to the portal and follow the steps below to create an App Registration.

Navigate to the `App Registrations` section of the portal. You can find this section by searching for `App Registrations` or as part of the `Azure Active Directory` section of the portal.

<figure><img src="/files/wiCDTOcEB2xEaANwWbtL" alt=""><figcaption></figcaption></figure>

Select `+ New Registration`

Enter `Pushly` for the Name and choose the appropriate Account Type that should have access to log in.

Under `Redirect URI` choose "Web" and enter the following value:

```
https://identity.pushly.com/login/callback
```

<figure><img src="/files/Eaq9tzFaksMeOBnq6PBY" alt=""><figcaption></figcaption></figure>

Click the `Register` button

On the next page copy the `Client ID` and then click the `Certificates and Secrets` item in the left menu bar.

On this page ensure the `Client Secrets` tab is selected and then click the `+ New client secret` button. Enter a description, choose the expiration length (we recommend 24 months) and then click the `Add` button.

{% hint style="warning" %}
You will need to generate a new Client Secret and upload it to the platform every time the secret expires. For example, if you choose 24 months for the expiration length you will need to generate a new secret and add it to the platform every 2 years.
{% endhint %}

<figure><img src="/files/DgiF6NHt24gaqXuqqWye" alt=""><figcaption></figcaption></figure>

After clicking the `Add` button make sure you copy the newly generated `Value` on the resulting page as it will only show once. This value will be used as the `Client Secret` along with the `Client ID` when setting up the integration in the platform.

Next, click the `Token configuration` item in the left menu bar.&#x20;

On this resulting page click the `+ Add optional claim` button and then choose the `ID Token` radio button.

From the list of claims add the `email` and `upn` claims and then click the `Add` button.&#x20;

<figure><img src="/files/SLv36nrE1M8twGqhcK4i" alt=""><figcaption></figcaption></figure>

An additional modal will be shown at the top of the slide-out that asks you to confirm adding the email and profile permission to the Microsoft graph. Click the checkbox to confirm adding these permissions and then click the `Add` button to complete the App Registration set up.

## Pushly: Create the Microsoft Azure AD Provider

Now that you have your `Client ID` and `Client Secret` you can log into the platform and [navigate to your Organization Settings](/platform/organizations.md#accessing-organization-context) page.

Next, click the `Security` tab and then click the `Add Provider` button.

Choose `Microsoft Azure AD` from the `Provider Type` dropdown.

Enter the `Azure AD Domain` and then fill in the  `Client ID`, and `Client Secret` that was generated in the first section of this documentation.

Within the `Associated Domains` text area enter each domain name that your organization will be using to to log in via Azure AD on a separate line. For example, if your email address is `example@yourdomain.com` then you would enter `yourdomain.com`

<figure><img src="/files/GNdA225JqOcb1MZ1sJYd" alt=""><figcaption></figcaption></figure>

Once the provider has been successfully created you can begin [inviting users](/platform/user-management.md#creating-a-user) to the platform. Any user invited that has an email address that matches one of the emails provided in `Email Domains` will be sent through Azure AD for authentication.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.pushly.com/platform/organizations/single-sign-on/microsoft-azure-ad.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
