Azure AD Connect to new OU

Anonymous
2024-09-04T13:18:58+00:00

Hello

currently using on prem AD and Azure AD connect to talk to Azure

doing a tidy up of our local AD

Users currently in 2 different OU Groups - and working

i have created a new OU under the domain like the 2 working ones

when i move 2 test users to the new OU i have made - the user accounts get deleted from Azure

When i add them back from where they came from - they are restored

How do i get my new OU to sync properly to Azure?

Windows for business | Windows Server | Directory services | Active Directory

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  1. Anonymous
    2024-09-04T13:47:21+00:00

    Hello Simon Gibson3,

    Thank you for posting in Microsoft Community forum.

    It sounds like the new OU you created is not included in the synchronization scope of Azure AD Connect. To resolve this issue, you need to update the sync scope to include your new OU. Here's how you can do that:

    1.Open Azure AD Connect: On the server where Azure AD Connect is installed, open the Azure AD Connect application.

    2.Configure Directory Partitions: In the Azure AD Connect wizard, you'll want to select the option to customize synchronization options. Specifically, look for an option like 'Configure directory partitions'.

    3.Select OUs: You'll find a section where you can configure the Organizational Units (OUs) to be synced. Ensure that your new OU is checked in this list.

    4.Save and Sync: Save your changes and run a full synchronization to ensure all objects in the new OU are synced to Azure AD.

    Here's step-by-step:

    1.Launch the Azure AD Connect tool:

    On the server running Azure AD Connect, open the Start menu and search for Azure AD Connect. Launch the program.

    1. Configuration:

    In the Azure AD Connect interface, click on 'Configure'.

    3.Select 'Customize Synchronization Options':

    Choose the 'Customize Synchronization Options' and click 'Next'.

    1. Connect to Azure AD:

    Enter your Azure AD credentials to connect to Azure AD and click 'Next'.

    5.Select Active Directory Forest:

    You might need to enter your credentials for your on-premises AD as well.

    Click 'Next' once authenticated.

    6.Select OUs:

    You'll reach a screen where you can select which OUs in your on-premises AD will be synchronized with Azure AD.

    Ensure that the new OU you created is checked. Also, verify that any other relevant OUs are checked.

    7.Finish:

    Once you’ve made the necessary selections, proceed through the remaining steps and finish the setup.

    8.Force a Synchronization:

    Open PowerShell as an administrator on the server where Azure AD Connect is installed.

    Run the following commands to force a synchronization:

    Import-Module ADSync Start-ADSyncSyncCycle -PolicyType Initial

    After completing these steps, the users in your new OU should sync properly to Azure AD.

    If they still don't appear, you might need to check if there are any additional filtering rules or synchronization issues by checking the Azure AD Connect logs.

    I hope the information above is helpful.

    If you have any question or concern, please feel free to let us know.

    Best Regards,

    Daisy Zhou

    1 person found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2024-11-18T10:38:00+00:00

    Hello Daisy Zhou123,

    Can we done it with powershell ?

    I would like to update the list of OUs synchronized on my staging platform with an export of list of OUs synced in production plateform.

    Thanks

    Regards

    Cyrille C

    0 comments No comments
  2. Anonymous
    2024-12-09T15:33:20+00:00

    Hi Daisy

    I have followed the steps and synchronization show successful on M365 and and Entra ID but identities/users are not showing on M365.

    0 comments No comments