> For the complete documentation index, see [llms.txt](https://docs.trustlogix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlogix.io/attribute-management/importing-user-attributes-and-group-membership-from-microsoft-entra-id-azure-ad.md).

# Importing User Attributes and Group Membership from Microsoft Entra ID (Azure AD)

TrustLogix enables you to import user attributes and group memberships from Microsoft Entra ID into TrustLogix entitlement tables. These attributes and group memberships can then be used to create and enforce data access policies.

### Steps to Import User Attributes and Group Membership

#### 1. Configure Integration with Azure&#x20;

Set up the Azure integration by following the steps described in [Configure Azure AD/Entra as an Attribute Source Connection](https://docs.trustlogix.io/integrations/attribute-source-connection/azure-ad-or-ms-entra-graph-endpoint.md)

#### 2. Configure Attribute Source

Follow the below steps to configure the integration as attribute source

* Go to **Attribute Management**
* Click on **Source Configurations** Tab
* Click on **Add Configuration**
* Enter the source **Configuration Name**
* Select the integration created in step#1 as Data Source&#x20;

Click on **Next** to create attribute definition&#x20;

Alternatively, go to the **Attributes** tab and click **Add Attribute** to create attribute definition(explained in the next step)

#### 3. Define User attributes

Follow the steps mentioned to [Create Attribute with Source Configuration](https://docs.trustlogix.io/attribute-management/attributes-based-on-source.md#creating-an-attribute-with-source-configuration)

In order to create Azure AD attribute definition&#x20;

* Enable **“Map Attribute Value Source”**
* Select the Azure attribute source created in Step 2 as the **Source Configuration**
* Select **Attribute Type** as **Direct**
* Choose the required Azure AD attribute from the **Source Column**
  * To import user group memberships, select **group**
* Review and update additional fields as needed:
  * Display Name
  * Description
  * Group Name
* **Save** the attribute
* **Provision** the attribute

> Please note that **group** is not a standard user attribute in Azure AD. It is a special attribute specifically designed to capture and import group memberships for users.
>
> All user attribute values, including group memberships, are stored directly in the data source. TrustLogix maintains only the metadata; the actual values are not stored within TrustLogix.

#### 4. Import/sync Azure AD attribute values&#x20;

Once the attribute is defined:

* The attribute sync service imports attribute values from Azure into the entitlement tables
* Changes in Azure AD (including group memberships) are automatically synchronized
* Synchronization occurs based on the configured frequency
* The imported attribute values are stored directly in the entitlement tables of the corresponding data sources and are not persisted within TrustLogix.


---

# 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://docs.trustlogix.io/attribute-management/importing-user-attributes-and-group-membership-from-microsoft-entra-id-azure-ad.md?ask=<question>&goal=<user_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.
