> For the complete documentation index, see [llms.txt](https://docs.amitysolutions.com/amity-solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amitysolutions.com/amity-solutions/amity-bots-platform/users/setup-microsoft-entra-id-integration.md).

# Setup Microsoft Entra ID Integration

### Step 1: Configure Enterprise Applications in Microsoft Azure

1. Access Enterprise Applications : Log in to the Microsoft Azure portal and navigate to the ***Enterprise Applications*** section.
2. Create a New Application
   1. Click on the ***+ New Application*** button.
   2. Select ***+ Create your own application***.
3. Application Setup
   1. Enter a name for your application.
   2. Choose **Integrate any other application you don't find in the gallery (Non-gallery).**
   3. Finally, click on ***Create*** to complete the process

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

### Step 2: Set Up Single Sign-On (SSO)

1. Initiate Single Sign-On Configuration: In the application settings, click on ***Set up single sign-on***.
2. Basic SAML Configuration
   1. Add Identifier (Entity ID): Enter the Entity ID provided by the ASOL team (format: \`urn:amazon:cognito:sp:{cognito pool}\`).
   2. Add Reply URL: Enter the URL sent by the ASOL team (format: \`{cognate domain}/saml2/idpresponse\`).

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

### Step 3: Set up Attributes & Claims

1. \[Required] emailaddress = user.userprincipalname
2. \[Required] roles = user.assignedroles

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

### Step 4: Role Mapping

Set up the app roles value and provide the expected [user roles in amity bots plus](https://docs.amitysolutions.com/amity-solutions/amity-bots-platform/users#user-roles-and-permissions) to ASOL team

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

### Step 5: Provide Metadata to ASOL Team via Support Team

Once the above steps are completed, send the App Federation Metadata URL to the [ASOL supper team](https://ekoapp.atlassian.net/servicedesk/customer/portal/5/group/11) for further integration and testing.

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

1. Open the service request to ASOL support team [LINK](https://ekoapp.atlassian.net/servicedesk/customer/portal/5/group/11)
2. Select Service Request
3. Provide required information to the ASOL team
   1. App Federation Metadata Url
   2. Organization name (use for create the organization id in Amity Bot+)
   3. Attach the files of role mapping (download template [here](https://docs.google.com/spreadsheets/d/1f3wdY_EVdq4fgYvLlxjVlYLfpgNa8pp3Sj-oAKELvmw/edit?gid=0#gid=0))

{% hint style="info" %}
For any assistance during this process, feel free to reach out to our support team. We are here to help ensure a smooth integration experience!
{% endhint %}


---

# 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://docs.amitysolutions.com/amity-solutions/amity-bots-platform/users/setup-microsoft-entra-id-integration.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.