Provision user accounts from Azure Active Directory to local Active Directory

Tor André Solbakken 45 Reputation points
2023-03-09T14:04:35.5933333+00:00

Hi All,

I have been banging my head for many days now and can't find a solution.

What we want to achieve is the possibility to provision users from Azure AD to local Active Directory.

We need a tool/service/App or whatever that can take all the user accounts that exist in our tenant and provision those users to the local Active Directory, new users will never be created locally (but we will soft match those who already exist).

Azure AD Connect, Azure AD Cloud sync will not work for the provisioning part, maybe we will use those later to delete the cloud user, but if Azure AD can be the big boss that is the preferred approach.

The reason why we need local AD is because we already have a lot of apps/files etc that is not in scope for the project, maybe it can be in another project later.

I had a look at https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/sync-scim , maybe this can work, but I am not sure, and it is time consuming to read a lot and find out that this is the wrong approach.

What about MIM 2016 (extended support to 2029) can that software achieve this?

Windows for business | Windows Client for IT Pros | Directory services | Active Directory
Microsoft Security | Microsoft Entra | Microsoft Entra External ID
Microsoft Security | Microsoft Entra | Microsoft Entra ID
{count} votes

1 answer

Sort by: Most helpful
  1. Danny Zollner 10,801 Reputation points Microsoft Employee Moderator
    2023-03-09T17:58:21.8933333+00:00

    There isn't a Microsoft-provided solution to this at this time. It is recommended to create accounts in on-premises AD first and have them sync to Azure AD. For the current set of users you have, I'd recommend using PowerShell or some other scripting language to pull the list of them and then use that data as a seed to create any accounts missing in on-prem AD.

    Standing up MIM to do this sort of backsync from AAD -> AD also is not recommended.

    Another alternative, depending on the exact footprint of your tech that is reliant on on-prem AD, would be to use Azure AD Domain Services, which is a managed ADDS instance where user objects are synced from AAD -> AADDS. AADDS can be joined by servers requiring legacy/on-prem auth protocols like LDAP, NTLM and Kerberos, and potentially to file servers as well. I'm not as familiar with the file server scenario with AADDS, so I'd recommend looking into documentation on that one.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.