A cloud-based identity and access management service for securing user authentication and resource access
You’ve run into a limitation rather than a misconfiguration. Entra Connect is based on AD being the authoritative source for user objects, not Entra ID. There isn’t a native Microsoft-supported, production-ready tool today that fully creates and manages AD user objects purely from Entra ID as the source of truth. The platform direction has been to move away from AD, not rebuild it from Entra.
So what you’re trying to do is possible, but only with a custom approach. You can script the creation of AD users on your domain controller. This can be done with Microsoft Graph to read users from Entra and PowerShell against AD to create and maintain them.
A simple pattern looks like this: query Entra users via Graph, check if they exist in AD (for example by UPN or a mapped attribute), and create them if not. You’d run this on a scheduled job or automation account that has line of sight to your domain controller.
For example, retrieving users from Entra:
Connect-MgGraph -Scopes "User.Read.All"
$users = Get-MgUser -All
Then for each user, check and create in AD:
Import-Module ActiveDirectory
foreach ($u in $users) {
$existing = Get-ADUser -Filter "UserPrincipalName -eq '$($u.UserPrincipalName)'" -ErrorAction SilentlyContinue
if (-not $existing) {
New-ADUser `
-Name $u.DisplayName `
-GivenName $u.GivenName `
-Surname $u.Surname `
-UserPrincipalName $u.UserPrincipalName `
-SamAccountName ($u.UserPrincipalName.Split("@")[0]) `
-EmailAddress $u.Mail `
-Enabled $true `
-AccountPassword (ConvertTo-SecureString "TempP@ss123!" -AsPlainText -Force)
}
}
You’d then extend this to handle updates, disables, and possibly group membership if your legacy apps depend on that. You also need to think about attribute mapping carefully, especially samAccountName length limits and uniqueness, since Entra doesn’t enforce the same constraints.
An alternative approach is described at https://www.alitajran.com/sync-microsoft-entra-id-user/ - this actually allows you to maintain the relationship between AD users and Entra ID users - so even though a bit more complex, it's worth considering.
Finally, if you want a commercial product that allows you to implement it, there are identity governance or provisioning tools like Microsoft Identity Manager, One Identity, or SailPoint that can do Entra-to-AD provisioning, but those add cost and complexity.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin