> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.stacktrack.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Map Azure AD Groups

Once you have set up the Identity Provider, we can begin mapping groups to assign permissions to your users automatically.

![](https://storage.crisp.chat/users/helpdesk/website/-/a/c/b/b/acbb4f3b55f24800/8417a6c5-7029-44b9-8563-f0b771_1b7dc3o.png)

Step 1 In the Servana Identity Service, click through to Mappers and Create Mappers.

![](https://storage.crisp.chat/users/helpdesk/website/-/e/6/2/4/e6242a53bfdbd000/192bda09-bc3d-42d0-bb90-f8542a_3ggepa.png)
From Azure, ensure Groups are added for token claims.

![](https://storage.crisp.chat/users/helpdesk/website/-/a/3/0/d/a30d03a92492c80/e9163b95-ea07-45d8-9c62-dc81d5_1vnw47h.png)

Copy the Object ID for the Group.

![](https://storage.crisp.chat/users/helpdesk/website/-/9/d/e/6/9de6f6d4ce18f000/49f9ab5c-693f-4909-bf7f-24de9d_891nzp.png)

Step 3

![](https://storage.crisp.chat/users/helpdesk/website/-/7/d/6/2/7d62c68642f92c00/7c24673f-595f-448d-a465-d251f7_tflqsv.png)

1. Enter the **Name** for the mapper; this setup uses a 1 to 1 configuration of Azure AD group to Servana Identity Service Group.
2. Change **Sync Mode Override** to Force.
3. Change **Mapper Type** to Advanced Claim to Group.
4. In **Claims,** enter the claim name and Group Object Id.
5. **Select Group** and choose the local mapping Group.