@@ -1,85 +1,99 @@ ----title: Scenario - Using directory extensions with group provisioning to Active Directory-description: This topic describes how to extend the schema of a group with a new attribute. Then use the new attribute to filter groups for provisioning to Active Directory.+title: Use directory extensions when provisioning to Active Directory+description: Learn how to use directory extension attributes when provisioning users and groups from Microsoft Entra ID to Active Directory.+author: dhanyahk+ms.author: dhanyahk+ms.service: entra-id ms.topic: tutorial-ms.date: 06/26/2026+ms.date: 08/21/2026 ms.subservice: hybrid-cloud-sync-ms.custom: sfi-image-nochange+ms.custom: sfi-image-nochange, msecd-doc-authoring-1023+ai-usage: ai-assisted+#customer intent: As a hybrid identity administrator, I want to use directory extensions when provisioning users and groups so that required attributes flow to Active Directory. --- -# Scenario - Using directory extensions with group provisioning to Active Directory+# Use directory extensions when provisioning to Active Directory -Scenario: You have hundreds of groups in Microsoft Entra ID. You want to provision some of these groups but not all back to Active Directory. You would like a quick filter that can be applied to groups without having to make a more complicated scoping filter.+A directory extension adds an attribute to the Microsoft Entra schema that Microsoft Entra ID owns. When you provision from Microsoft Entra ID to Active Directory, you can put that attribute to two uses: decide *which* objects are provisioned, or carry a *value* into an Active Directory attribute. Both uses work for users and for groups. - :::image type="content" source="../media/common-scenarios/group-writeback-1.png" alt-text="Diagram of group writeback with cloud sync." lightbox="../media/common-scenarios/group-writeback-1.png":::+This article walks through one example of each. Select the **Groups** or **Users** tab in each step to follow the example you want. Your selection carries through the rest of the article. -You can use the environment you create in this scenario for testing or for getting more familiar with cloud sync.+| Tab | Example | Use |+| --- | --- | --- |+| **Groups** | `WritebackEnabled` | Provision only the groups whose extension value is true. |+| **Users** | `EmployeeCode` | Write the extension value into an Active Directory user attribute. | -## Assumptions+For background on directory extensions, see [Directory extensions for provisioning Microsoft Entra ID to Active Directory](custom-attribute-mapping-entra-to-active-directory.md). For the general mapping interface and expression syntax, see [Configure provisioning to Active Directory](how-to-configure-entra-to-active-directory.md#configure-attribute-mapping). -- This scenario assumes that you already have a working environment that is synchronizing users to Microsoft Entra ID.-- We have 4 users that are synchronized. Britta Simon, Lola Jacobson, Anna Ringdahl, and John Smith.-- Three organizational Units have been created in Active Directory - Sales, Marketing, and Groups-- The Britta Simon and Anna Ringdahl user accounts reside in the Sales OU.-- The Lola Jacobson and John Smith user accounts reside in the Marketing OU.-- The Groups OU is where our groups from Microsoft Entra ID are provisioned.+> [!NOTE]+> Microsoft Entra ID provides a built-in `isWritebackEnabled` property on groups that you can set through Microsoft Graph. You can filter on that property directly by using [attribute value filtering](how-to-configure-entra-to-active-directory.md#attribute-value-filtering), so you don't need a custom extension attribute to control which groups are written back. Use the steps in this article when you need to scope on a value that the built-in property doesn't cover. -> [!TIP]-> For a better experience executing Microsoft Graph PowerShell SDK cmdlets, use Visual Studio Code with `ms-vscode.powershell` extension in [ISE Mode](/powershell/scripting/dev-cross-plat/vscode/how-to-replicate-the-ise-experience-in-vscode).+Groups support attribute mapping as well. For a group whose Source of Authority is converted to Microsoft Entra ID, the `GroupDN` extension preserves the original organizational unit and common name. To create that extension, see [Preserve a group's organizational unit and name](how-to-preserve-group-organizational-unit-entra-to-active-directory.md). For the expression that reads it, see [Preserve a group's original organizational unit](how-to-configure-entra-to-active-directory.md#preserve-a-groups-original-organizational-unit). -## Create two groups in Microsoft Entra ID+## Before you begin -To begin, create two groups in Microsoft Entra ID. One group is Sales and the Other is Marketing.+Both examples need the same starting point: -To create two groups, follow these steps.+- A working environment that synchronizes users to Microsoft Entra ID.+- A healthy provisioning agent connected to the target Active Directory domain.+- A Microsoft Entra ID to Active Directory configuration, or permission to create one. -1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Hybrid Identity Administrator](~/identity/role-based-access-control/permissions-reference.md#hybrid-identity-administrator).-2. Browse to **Entra ID** > **Groups** > **All groups**.-3. At the top, select **New group**.-4. Make sure the **Group type** is set to **security**.-5. For the **Group Name** enter **Sales**-6. For **Membership type** keep it at assigned.-7. Select **Create**.-8. Repeat this process using **Marketing** as the **Group Name.**+Each example then needs its own objects. +# [Groups](#tab/groups) -## Add users to the newly created groups+This example uses the following environment: -1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Hybrid Identity Administrator](~/identity/role-based-access-control/permissions-reference.md#hybrid-identity-administrator).-2. Browse to **Entra ID** > **Groups** > **All groups**.-3. At the top, in the search box, enter **Sales**.-4. Select the new **Sales** group.-5. On the left, select **Members**.-6. At the top, select **Add members**.-7. At the top, in the search box, enter **Britta Simon**.-8. Put a check next to **Britta Simon** and **Anna Ringdahl** and select **Select**.-9. It should successfully add her to the group.-10. On the far left, select **All groups** and repeat this process using the **Marketing** group and adding **Lola Jacobson** and **John Smith** to that group.+- Four synchronized users: Britta Simon, Lola Jacobson, Anna Ringdahl, and John Smith.+- Three organizational units in Active Directory: Sales, Marketing, and Groups.+- The Britta Simon and Anna Ringdahl user accounts reside in the Sales OU.+- The Lola Jacobson and John Smith user accounts reside in the Marketing OU.+- The Groups OU is where groups from Microsoft Entra ID are provisioned. ->[!NOTE]-> When adding users to the Marketing group, make note of the group ID on the overview page. This ID is used later to add our newly created property to the group.+:::image type="content" source="../media/common-scenarios/group-writeback-1.png" alt-text="Diagram of group writeback with cloud sync." lightbox="../media/common-scenarios/group-writeback-1.png":::++# [Users](#tab/users)++This example uses the following environment:++- A cloud-managed test user in Microsoft Entra ID.+- A target organizational unit, for example `OU=test,DC=Contoso,DC=com`.+- A writable target Active Directory user attribute, such as `extensionAttribute1`.++---++You can use the environment you create in this article for testing or for getting more familiar with cloud sync.++> [!TIP]+> For a better experience executing Microsoft Graph PowerShell SDK cmdlets, use Visual Studio Code with `ms-vscode.powershell` extension in [ISE Mode](/powershell/scripting/dev-cross-plat/vscode/how-to-replicate-the-ise-experience-in-vscode).  ## Install and connect Microsoft Graph PowerShell SDK  1. If not yet installed, follow [Microsoft Graph PowerShell SDK](/powershell/microsoftgraph/installation) documentation to install the main modules of Microsoft Graph PowerShell SDK:  `Microsoft.Graph`. -1. Open PowerShell with Administrative privileges+1. Open PowerShell with Administrative privileges.  1. To set the execution policy, run (press [A] Yes to all when prompted):     ```powershell    Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser    ```-1. Connect to your tenant (Be sure to accept on-behalf of when signing in):++1. Connect to your tenant (be sure to accept on-behalf of when signing in):     ```powershell-   Connect-MgGraph -Scopes "Directory.ReadWrite.All", "Application.ReadWrite.All", "User.ReadWrite.All, Group.ReadWrite.All"+   Connect-MgGraph -Scopes "Directory.ReadWrite.All", "Application.ReadWrite.All", "User.ReadWrite.All", "Group.ReadWrite.All"    ``` -## Create our CloudSyncCustomExtensionApp application and service principal+   > [!IMPORTANT]+   > Authenticate interactively. Don't put account passwords in scripts.++## Create the CloudSyncCustomExtensionsApp application and service principal++Both examples store their extension on the same application, so you only need to do this once.  >[!Important]-> Directory extension for Microsoft Entra Cloud Sync is only supported for applications with the identifier URI `api://<tenantId>/CloudSyncCustomExtensionsApp` and the [Tenant Schema Extension App](../connect/how-to-connect-sync-feature-directory-extensions.md#configuration-changes-in-azure-ad-made-by-the-wizard) created by Microsoft Entra Connect. +> Directory extension for Microsoft Entra Cloud Sync is only supported for applications with the identifier URI `api://<tenantId>/CloudSyncCustomExtensionsApp` and the [Tenant Schema Extension App](../connect/how-to-connect-sync-feature-directory-extensions.md#configuration-changes-in-azure-ad-made-by-the-wizard) created by Microsoft Entra Connect.  1. Get the Tenant ID: @@ -88,189 +102,358 @@ To create two groups, follow these steps.    $tenantId    ``` -> [!NOTE] -> This will output our current Tenant ID. You can confirm this Tenant ID by navigating to [Microsoft Entra admin center](https://entra.microsoft.com/) > **Entra ID** > **Overview**.+   > [!NOTE]+   > This outputs your current Tenant ID. You can confirm this Tenant ID by navigating to [Microsoft Entra admin center](https://entra.microsoft.com/) > **Entra ID** > **Overview**. -1. Using the `$tenantId` variable from the previous step, check to see if the CloudSyncCustomExtensionApp exists.+1. Using the `$tenantId` variable from the previous step, check to see if the CloudSyncCustomExtensionsApp exists. -      ```powershell+   ```powershell    $cloudSyncCustomExtApp = Get-MgApplication -Filter "identifierUris/any(uri:uri eq 'api://$tenantId/CloudSyncCustomExtensionsApp')"    $cloudSyncCustomExtApp-      ```-1. If a CloudSyncCustomExtensionApp exists, skip to the next step. Otherwise, create the new CloudSyncCustomExtensionApp app:+   ```++1. If a CloudSyncCustomExtensionsApp exists, skip to the next step. Otherwise, create the new CloudSyncCustomExtensionsApp app:     ```powershell    $cloudSyncCustomExtApp = New-MgApplication -DisplayName "CloudSyncCustomExtensionsApp" -IdentifierUris "api://$tenantId/CloudSyncCustomExtensionsApp"-   $cloudSyncCustomExtApp +   $cloudSyncCustomExtApp    ```-   -1. Check if CloudSyncCustomExtensionsApp application has a security principal associated. If you just created a new app, skip to the next step.++1. Check if the CloudSyncCustomExtensionsApp application has a service principal associated. If you just created a new app, skip to the next step.     ```powershell    Get-MgServicePrincipal -Filter "AppId eq '$($cloudSyncCustomExtApp.AppId)'"    ```-   -1. If you just created a new app or a security principal is not returned, create a security principal for CloudSyncCustomExtensionsApp:++1. If you just created a new app, or a service principal isn't returned, create a service principal for CloudSyncCustomExtensionsApp:     ```powershell    New-MgServicePrincipal -AppId $cloudSyncCustomExtApp.AppId    ```-   -## Create our custom extension attribute -> [!TIP]-> In this scenario we are going to create a custom extension attribute called `WritebackEnabled` to be used in Microsoft Entra Cloud Sync scoping filter, so that only groups with WritebackEnabled set to True are written back to On-premises Active Directory, similarly to the [Writeback enabled flag in Microsoft Entra admin center](../../users/groups-write-back-portal.md).+> [!NOTE]+> Creating a directory extension in Microsoft Entra ID doesn't require a provisioning agent restart. Restart the agent only when it needs to discover a newly added Active Directory schema attribute. -1. Get the Tenant ID:+## Prepare the objects to provision -   ```powershell-   $tenantId = (Get-MgOrganization).Id-   $tenantId-   ```+# [Groups](#tab/groups) -1. Get the CloudSyncCustomExtensionsApp application:+Create two groups in Microsoft Entra ID. One group is Sales and the other is Marketing. -      ```powershell-   $cloudSyncCustomExtApp = Get-MgApplication -Filter "identifierUris/any(uri:uri eq 'api://$tenantId/CloudSyncCustomExtensionsApp')"-   ```+1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Hybrid Identity Administrator](~/identity/role-based-access-control/permissions-reference.md#hybrid-identity-administrator).+1. Browse to **Entra ID** > **Groups** > **All groups**.+1. At the top, select **New group**.+1. Make sure the **Group type** is set to **security**.+1. For the **Group Name**, enter **Sales**.+1. For **Membership type**, keep it at assigned.+1. Select **Create**.+1. Repeat this process using **Marketing** as the **Group Name**. -1. Now, under the CloudSyncCustomExtensionApp, create the custom extension attribute called "WritebackEnabled" and assign it to Group objects:+Now add users to the groups you created. -   ```powershell-   New-MgApplicationExtensionProperty -ApplicationId $cloudSyncCustomExtApp.Id -Name 'WritebackEnabled' -DataType 'Boolean' -TargetObjects 'Group'-   ```- -1. This cmdlet creates an extension attribute that looks like extension_&lt;guid&gt;_WritebackEnabled.+1. Browse to **Entra ID** > **Groups** > **All groups**.+1. At the top, in the search box, enter **Sales**.+1. Select the new **Sales** group.+1. On the left, select **Members**.+1. At the top, select **Add members**.+1. Put a check next to **Britta Simon** and **Anna Ringdahl**, and then select **Select**.+1. On the far left, select **All groups** and repeat this process using the **Marketing** group, adding **Lola Jacobson** and **John Smith**. -## Create our cloud sync configuration+> [!NOTE]+> When adding users to the Marketing group, make note of the group ID on the overview page. This ID is used later to add the newly created property to the group. -1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Hybrid Identity Administrator](~/identity/role-based-access-control/permissions-reference.md#hybrid-identity-administrator).+# [Users](#tab/users) -2. Browse to **Entra ID** > **Entra Connect** > **Cloud sync**.+Identify the cloud-managed user you want to provision to Active Directory, and confirm you can retrieve it: -3. Select **New configuration**.+```powershell+$testUser = Get-MgUser -Filter "userPrincipalName eq '<test-user-UPN>'"+$testUser+``` -4. Select **Microsoft Entra ID to AD sync**.+You can optionally bring the user into scope through a group instead of selecting the user directly: -  :::image type="content" source="media/how-to-configure-entra-to-active-directory/entra-to-ad-1.png" alt-text="Screenshot of configuration selection." lightbox="media/how-to-configure-entra-to-active-directory/entra-to-ad-1.png":::+1. Create an assigned Microsoft Entra security group, such as **AD-Provisioning-Test**.+1. Add the cloud-managed test user to the group.+1. Select that group when you configure user scope in cloud sync. -5. On the configuration screen, select your domain and whether to enable password hash sync. Select **Create**. +> [!IMPORTANT]+> The extension value stays on each user. Group membership only brings the user into provisioning scope; it doesn't carry the value. -  :::image type="content" source="media/how-to-configure/new-ux-configure-2.png" alt-text="Screenshot of a new configuration." lightbox="media/how-to-configure/new-ux-configure-2.png":::+--- -6. The **Get started** screen opens. From here, you can continue configuring cloud sync+## Create the directory extension -7. On the left, select **Scoping filters**, then select **Group scope** > **All groups**.+# [Groups](#tab/groups) -8. Select **Edit attribute mapping** and change the **Target Container** to `OU=Groups,DC=Contoso,DC=com`. Select **Save**.+> [!TIP]+> This example creates a custom extension attribute called `WritebackEnabled` to use in a Microsoft Entra Cloud Sync scoping filter, so that only groups with `WritebackEnabled` set to true are written back to on-premises Active Directory. It works similarly to the built-in `isWritebackEnabled` property described earlier in this article. -9. Select **Add Attribute scoping filter**.+Under the CloudSyncCustomExtensionsApp, create the extension attribute and assign it to Group objects: -10. Type a name for the scoping filter: `Filter groups with Writeback Enabled`+```powershell+New-MgApplicationExtensionProperty -ApplicationId $cloudSyncCustomExtApp.Id -Name 'WritebackEnabled' -DataType 'Boolean' -TargetObjects 'Group'+``` -11. Under **Target Attribute** select the newly created attribute that looks like extension_&lt;guid&gt;_WritebackEnabled.+This cmdlet creates an extension attribute that looks like `extension_<AppIdWithoutHyphens>_WritebackEnabled`. -> [!IMPORTANT]-> Some of the target attributes displayed in the dropdown list might not be usable as a scoping filter because not all properties can be managed in Entra ID, for example extensionAttribute[1-15], hence the recommendation is to create a custom extension property for this specific purpose.+# [Users](#tab/users) -:::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-4.png" alt-text="Screenshot of available attributes." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-4.png":::+Under the CloudSyncCustomExtensionsApp, create the extension attribute and assign it to User objects: -13. Under **Operator** select **IS TRUE**.-14. Select **Save**, and then select **Save**.-15. Leave the configuration disabled and come back to it.+```powershell+New-MgApplicationExtensionProperty -ApplicationId $cloudSyncCustomExtApp.Id -Name 'EmployeeCode' -DataType 'String' -TargetObjects 'User'+``` -## Add new extension property to one of our groups+This cmdlet creates an extension attribute that looks like `extension_<AppIdWithoutHyphens>_EmployeeCode`. Retrieve the generated name, because you need it when you add the attribute mapping: -For this portion, we're going add a value on our newly created property to one of our existing groups, Marketing.+```powershell+$userExtension = Get-MgApplicationExtensionProperty -ApplicationId $cloudSyncCustomExtApp.Id |+    Where-Object Name -Like '*_EmployeeCode' | Select-Object -First 1 -### Set the extension property value using Microsoft Graph PowerShell SDK+$userExtensionName = $userExtension.Name+$userExtensionName+``` -1. Get the Tenant ID:+--- -   ```powershell-   $tenantId = (Get-MgOrganization).Id-   $tenantId-   ```+## Set the extension value -1. Get the CloudSyncCustomExtensionsApp application:+# [Groups](#tab/groups) -      ```powershell-   $cloudSyncCustomExtApp = Get-MgApplication -Filter "identifierUris/any(uri:uri eq 'api://$tenantId/CloudSyncCustomExtensionsApp')"-   ```+Set a value on the newly created property for the Marketing group. -1. Get our extension property:+1. Get the extension property:     ```powershell-   $gwbEnabledExtAttrib = Get-MgApplicationExtensionProperty -ApplicationId $cloudSyncCustomExtApp.Id | +   $gwbEnabledExtAttrib = Get-MgApplicationExtensionProperty -ApplicationId $cloudSyncCustomExtApp.Id |        Where-Object {$_.Name -Like '*WritebackEnabled'} | Select-Object -First 1-   $gwbEnabledExtAttrib     $gwbEnabledExtName = $gwbEnabledExtAttrib.Name    ``` -2. Now, get the `Marketing` group:+1. Get the `Marketing` group:     ```powershell    $marketingGrp = Get-MgGroup -ConsistencyLevel eventual -Filter "DisplayName eq 'Marketing'"-   $marketingGrp     ``` -3. Then, with the variable `$gwbEnabledExtName` containing `extension_<guid>_WritebackEnabled`, set the value `True` for the Marketing group:+1. Set the value `True` for the Marketing group:     ```powershell    Update-MgGroup -GroupId $marketingGrp.Id -AdditionalProperties @{$gwbEnabledExtName = $true}    ``` -4. To confirm, you can read the `extension_<guid>_WritebackEnabled` property value with:+1. To confirm, read the property value:     ```powershell    $marketingGrp = Get-MgGroup -ConsistencyLevel eventual -Filter "DisplayName eq 'Marketing'" -Property Id,$gwbEnabledExtName    $marketingGrp.AdditionalProperties.$gwbEnabledExtName    ``` -### Set the extension property value using Microsoft Graph Explorer+# [Users](#tab/users)++1. Set the value on the test user:++   ```powershell+   Update-MgUser -UserId $testUser.Id -AdditionalProperties @{ $userExtensionName = "EMP-1001" }+   ```++1. To confirm, read the property value:++   ```powershell+   $testUser = Get-MgUser -UserId $testUser.Id -Property "id,displayName,$userExtensionName"+   $testUser.AdditionalProperties[$userExtensionName]+   ```++---++### Set the extension value by using Microsoft Graph Explorer++You can set the value through [Microsoft Graph Explorer](https://developer.microsoft.com/graph/graph-explorer) instead of PowerShell. Make sure you consented to the required permission by selecting **Modify permissions**.++# [Groups](#tab/groups)++1. Navigate to [Microsoft Graph Explorer](https://developer.microsoft.com/graph/graph-explorer) and consent to `Group.ReadWrite.All`.+1. Sign in using your tenant administrator account. A Hybrid Identity Administrator account was used to create this scenario and might be sufficient.+1. At the top, change **GET** to **PATCH**.+1. In the address box, enter `https://graph.microsoft.com/v1.0/groups/<Group Id>`.+1. In the request body, enter:++   ```json+   {+     "extension_<AppIdWithoutHyphens>_WritebackEnabled": true+   }+   ```++1. Select **Run query**.++   :::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-1.png" alt-text="Screenshot of running the graph query." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-1.png":::++1. If done correctly, you see `[]`.+1. At the top, change **PATCH** to **GET** and look at the properties of the Marketing group. Select **Run query**. You should see the newly created attribute. -You need to make sure that you have consented to `Group.ReadWrite.All`. You can do this by selecting **Modify permissions**.+   :::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-2.png" alt-text="Screenshot of group properties." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-2.png":::++# [Users](#tab/users)++1. Navigate to [Microsoft Graph Explorer](https://developer.microsoft.com/graph/graph-explorer) and consent to `User.ReadWrite.All`.+1. Sign in using your tenant administrator account.+1. At the top, change **GET** to **PATCH**.+1. In the address box, enter `https://graph.microsoft.com/v1.0/users/<User Id>`.+1. In the request body, enter: -1. Navigate to [Microsoft Graph Explorer](https://developer.microsoft.com/graph/graph-explorer)-2. Sign in using your tenant administrator account. A Hybrid Identity Administrator account was used to create this scenario and might be sufficient.-3. At the top, change the **GET** to **PATCH**-4. In the address box enter: `https://graph.microsoft.com/v1.0/groups/<Group Id>`-5. In the Request body enter:    ```json    {-     "extension_<guid>_WritebackEnabled": true+     "extension_<AppIdWithoutHyphens>_EmployeeCode": "EMP-1001"    }    ```-6. Select **Run query**.-  :::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-1.png" alt-text="Screenshot of running the graph query." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-1.png"::: -7. If done correctly, you see [].-8. Now at the top, change **PATCH** to **GET** and look at the properties of the marketing group. -9. Select **Run query**. You should see the newly created attribute. -  :::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-2.png" alt-text="Screenshot of group properties." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-2.png":::+1. Select **Run query**.+1. At the top, change **PATCH** to **GET** and look at the properties of the user. Select **Run query**. You should see the newly created attribute.++---++## Use the extension in your cloud sync configuration++# [Groups](#tab/groups)++1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Hybrid Identity Administrator](~/identity/role-based-access-control/permissions-reference.md#hybrid-identity-administrator).++1. Browse to **Entra ID** > **Entra Connect** > **Cloud sync**.++1. Select **New configuration**.++1. Select **Microsoft Entra ID to AD sync**.++   :::image type="content" source="media/how-to-configure-entra-to-active-directory/entra-to-ad-1.png" alt-text="Screenshot of configuration selection." lightbox="media/how-to-configure-entra-to-active-directory/entra-to-ad-1.png":::++1. On the configuration screen, select your domain. Select **Create**.++   :::image type="content" source="media/how-to-configure/new-ux-configure-2.png" alt-text="Screenshot of a new configuration." lightbox="media/how-to-configure/new-ux-configure-2.png":::++1. The **Get started** screen opens. From here, you can continue configuring cloud sync.++1. On the left, select **Scoping filters**, then select **Group scope** > **All groups**.++1. Select **Edit attribute mapping** and change the **Target Container** to `OU=Groups,DC=Contoso,DC=com`. Select **Save**.++1. Select **Add Attribute scoping filter**.++1. Type a name for the scoping filter: `Filter groups with Writeback Enabled`.++1. Under **Target Attribute**, select the newly created attribute that looks like `extension_<AppIdWithoutHyphens>_WritebackEnabled`.++   > [!IMPORTANT]+   > Some of the target attributes displayed in the dropdown list might not be usable as a scoping filter because not all properties can be managed in Microsoft Entra ID, for example `extensionAttribute[1-15]`. That's why we recommend creating a custom extension property for this purpose.++   :::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-4.png" alt-text="Screenshot of available attributes." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-4.png":::++1. Under **Operator**, select **IS TRUE**.++1. Select **Save**, and then select **Save**.++1. Leave the configuration disabled and come back to it.++# [Users](#tab/users)++1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least a [Hybrid Identity Administrator](~/identity/role-based-access-control/permissions-reference.md#hybrid-identity-administrator).++1. Browse to **Entra ID** > **Entra Connect** > **Cloud sync**. +1. Select **New configuration** and select **Microsoft Entra ID to AD sync**, or open an existing configuration.++1. Select the Active Directory domain and a healthy provisioning agent.++1. On the left, select **Scoping filters**, and configure **User scope**. Select the test user directly, or select the group that contains the user.++1. Select **Edit attribute mapping** for users and set the **Target Container** to the complete Active Directory distinguished name, for example `OU=test,DC=Contoso,DC=com`.++1. Add the attribute mapping:++   | Setting | Value |+   | --- | --- |+   | Mapping type | Direct |+   | Source attribute | `extension_<AppIdWithoutHyphens>_EmployeeCode` |+   | Target attribute | `extensionAttribute1`, or another writable Active Directory user attribute |++1. Select **Save**.++1. Leave the configuration disabled until you review the scope, target container, and mappings.++---++## Test and verify++# [Groups](#tab/groups) -## Test our configuration >[!NOTE]->When using on-demand provisioning, members aren't automatically provisioned. You need to select which members you wish to test on and there's a 5 member limit.+>When using on-demand provisioning, members aren't automatically provisioned. You need to select which members you wish to test on, and there's a five member limit. -  [!INCLUDE [sign in](../../../includes/cloud-sync-sign-in.md)]+ [!INCLUDE [sign in](../../../includes/cloud-sync-sign-in.md)]  3. Under **Configuration**, select your configuration. 4. On the left, select **Provision on demand**.-5. Enter **Marketing** in the **Selected group** box-6. From the **Selected users** section, select some users to test. Select **Lola Jacobson** and **John Smith**.+5. Enter **Marketing** in the **Selected group** box.+6. From the **Selected users** section, select **Lola Jacobson** and **John Smith**. 7. Select **Provision**. It should successfully provision.-  :::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-5.png" alt-text="Screenshot of successful provision." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-5.png":::-8. Now try with the **Sales** group and add **Britta Simon** and **Anna Ringdahl**. This shouldn't provision.-  :::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-6.png" alt-text="Screenshot of provisioning being blocked." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-6.png":::++   :::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-5.png" alt-text="Screenshot of successful provision." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-5.png":::++8. Now try with the **Sales** group and add **Britta Simon** and **Anna Ringdahl**. This shouldn't provision, because the Sales group doesn't have the extension value set.++   :::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-6.png" alt-text="Screenshot of provisioning being blocked." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-6.png":::+ 9. In Active Directory, you should see the newly created Marketing group.-  :::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-7.png" alt-text="Screenshot of new group in active directory users and computers." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-7.png":::-1. You can now browse to **Entra ID** > **Entra Connect** > **Cloud sync > Overview** page to Review and Enable our configuration to start synchronizing. -## Next steps -- [Use Group writeback with Microsoft Entra Cloud Sync ](../group-writeback-cloud-sync.md)-- [Govern on-premises Active Directory based apps (Kerberos) using Microsoft Entra ID Governance](govern-on-premises-groups.md)+   :::image type="content" source="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-7.png" alt-text="Screenshot of new group in active directory users and computers." lightbox="media/tutorial-directory-extension-group-provision/directory-extension-group-provision-7.png":::++10. You can now browse to **Entra ID** > **Entra Connect** > **Cloud sync** > **Overview** to review and enable your configuration and start synchronizing.++# [Users](#tab/users)++ [!INCLUDE [sign in](../../../includes/cloud-sync-sign-in.md)]++3. Under **Configuration**, select your configuration.+4. On the left, select **Provision on demand**.+5. Select the test user. If you used group scope, select the group and then explicitly select the test user.+6. Select **Provision**.+7. Review the import, scope evaluation, matching, and export steps.++Confirm the value landed in Active Directory:++```powershell+Get-ADUser -Filter "UserPrincipalName -eq '<test-user-UPN>'" -SearchBase "OU=test,DC=Contoso,DC=com" -Properties extensionAttribute1 |+    Select-Object DistinguishedName,extensionAttribute1+```++The expected value is `extensionAttribute1 = EMP-1001`.++To review the result in the provisioning logs, browse to **Entra ID** > **Monitoring & health** > **Provisioning logs** and filter by the test user and your cloud sync configuration. Confirm that:++- Scope evaluation passed.+- The user was created or matched in Active Directory.+- Under **Modified properties**, the directory extension was mapped to `extensionAttribute1`.+- The export operation succeeded.++---++## Directory extensions on users converted from Active Directory++When you convert a user's Source of Authority to Microsoft Entra ID, the attributes that Active Directory previously owned must already be visible in Microsoft Entra ID, either as directory attributes or as directory schema extensions. For the full list of preconditions, see [Prepare your environment to convert user Source of Authority](../prepare-user-source-of-authority-environment.md).++That means a converted user usually already has the extension values it needs, so you don't create new extensions for those attributes. Instead, you map from the extensions that already hold the values.++Extensions created by Microsoft Entra Connect live on the [Tenant Schema Extension App](../connect/how-to-connect-sync-feature-directory-extensions.md#configuration-changes-in-azure-ad-made-by-the-wizard), which is supported as a mapping source alongside CloudSyncCustomExtensionsApp. Add the mapping the same way as in the **Users** tab, selecting the existing extension as the source attribute. Converting Source of Authority doesn't require you to re-register or recreate the extension.++## Next step++> [!div class="nextstepaction"]+> [Test and enable provisioning](how-to-test-and-enable-provisioning-entra-to-active-directory.md) -- [Migrate Microsoft Entra Connect Sync group writeback V2 to Microsoft Entra Cloud Sync](migrate-group-writeback.md)+## Related content +- [Directory extensions for provisioning Microsoft Entra ID to Active Directory](custom-attribute-mapping-entra-to-active-directory.md)+- [Configure scoping filters and attribute mappings](how-to-configure-entra-to-active-directory.md#configure-scoping-filters)+- [Configure provisioning to Active Directory](how-to-configure-entra-to-active-directory.md)+- [Overview of provisioning from Microsoft Entra ID to Active Directory](overview-provision-entra-id-to-active-directory.md)+- [How provisioning to Active Directory works](how-provisioning-to-active-directory-works.md)