> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/administration/sso-and-single-sign-on/scim-azure.md).

# SCIM - Azure

### Supported Features

* **Push Users** Users created in Azure will also be created in Couchdrop
* **Push User Updates** User updates in Azure will be pushed to the corresponding users in Couchdrop
* **User deactivation** Users deactivated in Azure will be deactivated in Couchdrop
* **Push Groups** Groups created in Azure will also be created in Couchdrop
* **Push Group updates** Group updates in Azure will be pushed to the corresponding users in Couchdrop
* **Group deactivation** Groups deactivated in Azure will be deactivated in Couchdrop

### Configuration Steps

#### Create User Provisioning Token in Couchdrop

Navigate to [User Provisioning](https://my.couchdrop.io/manage/settings/userProvisioning) in Couchdrop’s interface and **create a new Provisioning Token**. This will be used in the Azure Active Directory provisioning process.

<figure><img src="/files/2w3fYIal6j1moT4gdZ2x" alt=""><figcaption></figcaption></figure>

#### Configure Enterprise Application in Azure Active Directory

Navigate to your [Administration dashboard](https://aad.portal.azure.com/#blade/Microsoft_AAD_IAM/AppGalleryBladeV2) in Microsoft’s admin portal and **create an enterprise application.**

![](https://community.couchdrop.io/hc/article_attachments/5598072976143/mceclip1.png)

Provide a name for the application and select “Integrate any other application you don’t find in the gallery (Non-gallery)<br>

<figure><img src="https://community.couchdrop.io/hc/article_attachments/5598073126287/mceclip2.png" alt=""><figcaption></figcaption></figure>

Next assign users and groups to the newly created application that you would like to have provisioned in Couchdrop.<br>

<figure><img src="https://community.couchdrop.io/hc/article_attachments/5598073216399/mceclip3.png" alt=""><figcaption></figcaption></figure>

Select **Add user/group**

<figure><img src="https://community.couchdrop.io/hc/article_attachments/5598029468943/mceclip4.png" alt=""><figcaption></figcaption></figure>

Select the desired users or groups that should be provisioned through to Couchdrop then **Select** and **Assign**.<br>

![](https://community.couchdrop.io/hc/article_attachments/5598029580303/mceclip5.png)

#### Configure SCIM provisioning between Azure Active Directory and Couchdrop

Navigate to the **Provisioning Tab** on the left hand side. Next select **Get started** to configure the tenant URL and the User Provisioning Token that was created in **Step 1**. Provisioning mode should be set to automatic. The Tenant URL is: <https://api.couchdrop.io/scim/v2>.

&#x20;

Select **Test Connection** and Azure will attempt to connect as well and vwill retrieve schema information needed for the user and group mapping. If tested successfully then select **Save**.

![](https://community.couchdrop.io/hc/article_attachments/5598029772687/mceclip6.png)

#### &#x20;Configure user mapping

Select **Provision Azure Active Directory Users** as required.

Couchdrop requires the following user SCIM attributes for the SCIM system to be mapped, all others should be removed.

| **Custom Application SSO Attribute** |
| ------------------------------------ |
| userName                             |
| active                               |
| emails\[type eq "work"].value        |
| name.givenName                       |
| name.familyName                      |
| externalId                           |

![](https://community.couchdrop.io/hc/article_attachments/5598074193295/mceclip7.png)

The **externalId** attribute may need to be remapped from **mailNickname** to **objectId** on the Azure Active Directory attribute side depending on your settings.

![](https://community.couchdrop.io/hc/article_attachments/5598074565263/mceclip8.png)

#### Configure group mapping

Select **Provision Azure Active Directory Groups** as required.

Couchdrop requires the following user SCIM attributes for the SCIM system to be mapped.

| **Custom Application SSO Attribute** |
| ------------------------------------ |
| displayName                          |
| externalId                           |
| members                              |

![](https://community.couchdrop.io/hc/article_attachments/5598030447759/mceclip9.png)

#### Start the user and group provisioning process

Navigate back to the custom application breadcrumb (in this case it’s Couchdrop SCIM) and to **Provisioning**. From here select the **Start provisioning** button.<br>

![](https://community.couchdrop.io/hc/article_attachments/5598030648463/mceclip10.png)

After the provisioning has completed running the first time a status should be required that indicates how many users and groups were provisioned within the Couchdrop product. Further information can be located by selecting **View provisioning logs.**

![](https://community.couchdrop.io/hc/article_attachments/5598031249807/mceclip11.png)

<br>


---

# 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.couchdrop.io/administration/sso-and-single-sign-on/scim-azure.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.
