Why Entra Connect Stops Syncing New Users
New users may be missing from Microsoft 365 because Microsoft Entra Connect can't import them, excludes them during synchronization, or encounters an error exporting them to Microsoft Entra ID. The fastest fix is to find where the user stops before changing accounts or sync settings.
Start with the user's organizational unit and the scheduler. Then follow the object through Synchronization Service Manager to identify the failed stage.
Key Takeaways
A new user outside the selected domain or organizational unit won't enter the sync pipeline. If the user is in scope, check the scheduler and the latest connector runs before changing attributes.
Duplicate sign-in names and email addresses can block or alter provisioning. After fixing the specific issue, run the appropriate sync cycle and confirm the user appears in the correct tenant.
Check the User's Domain and OU First
Microsoft Entra Connect only imports users in its configured domain and organizational unit (OU) scope. A new account placed in the wrong OU can remain invisible even when existing employees sync normally.
Find the Account in Active Directory
On a computer with the Active Directory PowerShell module, prompt for the user's account name:
$user = Read-Host "Enter the user's AD account name"
Then retrieve the account's location and key identity attributes:
Get-ADUser -Identity $user -Properties userPrincipalName,proxyAddresses | Select-Object Name,DistinguishedName,UserPrincipalName,Enabled,proxyAddresses
The DistinguishedName
shows the account's domain and location in Active Directory. Compare that location with the OU where your organization normally creates synchronized users. A disabled account is still a separate issue: don't assume its enabled status alone explains why it's missing.
If the account was created on a different domain controller, replication delay can also affect what Entra Connect sees. Query the domain controller used by the AD connector:
$dc = Read-Host "Enter the connector's domain controller"
Get-ADUser -Server $dc -Identity $user | Select-Object Name,DistinguishedName
If the account appears on one domain controller but not the other, address AD replication before changing sync rules.
Review the Selected OUs
On the Entra Connect server, open the Microsoft Entra Connect wizard and review domain and OU filtering . Confirm that the user's domain and OU are selected.
If the user belongs in an existing synchronized OU, move the account there according to your organization's provisioning process. If the OU itself should be included, update the selection carefully. A filtering change can affect every object in that OU, including accounts you didn't intend to synchronize.
Check the Sync Scheduler and Server
If the user is in scope, check whether the sync engine is running and whether the server is meant to export changes. Run these commands on the Entra Connect server in an elevated PowerShell session:
Import-Module ADSync
Get-ADSyncScheduler | Select-Object SyncCycleEnabled,SyncCycleInProgress,StagingModeEnabled,NextSyncCycleStartTimeInUTC
Read the Scheduler Results
SyncCycleEnabled
shows whether scheduled synchronization is enabled. SyncCycleInProgress
indicates whether a cycle is underway. The next start time is in UTC, so compare it with the server time accordingly.
If StagingModeEnabled
is True
, that server is in staging mode. It can process changes but doesn't export them to Microsoft Entra ID. Find the active server rather than switching staging mode off as a quick fix.
A scheduled cycle doesn't prove that each connector completed successfully. Use the run history to identify the last completed operation and any errors.
Check the Windows Service
The sync engine also depends on the Microsoft Entra Connect Sync service. Check its status with:
Get-Service ADSync
A stopped service prevents normal processing. If it won't start, record the error and review the server's event logs before making wider changes. When many users are affected, also review Health > Service health in the Microsoft 365 admin center for a related Microsoft incident.
Avoid resetting employee passwords or changing tenant-wide settings while the sync failure is still unidentified. Those actions can interrupt staff without repairing the connector.
Trace the User in Synchronization Service Manager
Open Synchronization Service Manager on the Entra Connect server. Its Operations tab shows run history for the Active Directory and Microsoft Entra connectors.
Select recent runs and inspect their status and error details. Record the connector name, operation type, time, and exact error before changing anything.
Follow Import, Synchronization, and Export
The pipeline has three main stages. Import reads changes from a connected directory. Synchronization applies rules and joins or projects objects into the metaverse. Export sends pending changes to the target directory.
An import error points you toward the source connector, its connection, or its access to the directory. A synchronization error points toward processing rules or object matching. An export error means the object reached a later stage, so an OU exclusion alone doesn't explain that error.
Select a failed operation, then open the listed error and its details. The error text matters: a duplicate attribute calls for a different fix than a connector authentication or network failure.
Find Where the Object Disappears
In the Connectors tab, select the Active Directory connector and search its connector space for the user's distinguished name. If the object isn't there, revisit scope, AD replication, and the latest import.
If it is present, open its properties and inspect its synchronization status. Search the metaverse for the user and review the connected objects. A user in the AD connector space but absent from the metaverse may be excluded by a synchronization rule or have a processing error.
If the user reaches the metaverse, inspect the Microsoft Entra connector and its export history. This narrows the investigation to the stage that needs attention.
Inspect Filtering and Required Attributes
OU selection is only one part of sync scope. Custom synchronization rules and attribute-based filtering can also exclude an individual account while other users in the same OU sync successfully.
Look for Rules That Exclude the User
Review the user's properties in the connector space and compare them with the configured rules. A custom rule may depend on an attribute or group membership that hasn't been populated on the new account.
The Connect wizard also includes an object-sync troubleshooting task in supported versions. Use its findings alongside the run history rather than changing a rule based only on an assumption.
Don't disable filtering broadly to test one user. That can bring unintended objects into scope or cause unexpected changes to accounts already in the cloud.
Check the Sign-In and Mail Attributes
Review userPrincipalName
and proxyAddresses
in the AD output. The user principal name is the sign-in name; proxy addresses identify email addresses associated with the object.
Look for a missing value, a typing error, or an address assigned to someone else. Also compare the affected account with a working account created through the same process. If your organization uses custom rules, the relevant missing attribute may be one of your own provisioning fields.
Make corrections in the authoritative source for that attribute. For an on-premises synchronized user, that often means Active Directory or the organization's Exchange management tools.
Resolve Duplicate and Matching Errors
An account can pass the earlier stages and still encounter a conflict in Microsoft Entra ID. The error details will help distinguish a duplicate value from an attempt to match the wrong objects.
Duplicate UPN or Proxy Address
Errors such as AttributeValueMustBeUnique
can point to a user principal name or proxy address already in use. Search for the conflicting value in both on-premises AD and Microsoft Entra ID, including relevant existing or deleted objects where applicable.
Microsoft Entra's duplicate-attribute resiliency can quarantine a duplicate value rather than fail the entire provisioning operation. As a result, finding an account in the cloud doesn't always mean every intended address or sign-in name arrived correctly.
Identify which object should own the value, correct the authoritative record, and allow a new export. Don't remove an address from another employee's account without understanding the effect on mail delivery.
Invalid Soft Match
InvalidSoftMatch
can occur when a new on-premises object attempts to match a cloud object using a UPN or proxy address, but their source anchors don't agree.
That distinction matters when a cloud account already exists for the employee. Creating another account or changing identifiers at random can make the situation harder to resolve. Inspect both objects and determine which one should be linked before making an identity-matching change.
For complex conflicts, keep the error details and object information together for the administrator responsible for identity synchronization.
Run the Right Sync Cycle
After an ordinary user or attribute change, start a delta cycle on the active Entra Connect server:
Start-ADSyncSyncCycle -PolicyType Delta
A successful command starts the requested cycle; it doesn't prove the user exported successfully. If a cycle is already running, let it finish before requesting another.
For a domain or OU filtering change, Microsoft calls for a Full Import followed by Delta Synchronization on the relevant connector. In Synchronization Service Manager, select that connector, choose Run , and select the appropriate operation in that order.
After those operations finish, run a delta cycle if needed to process and export pending changes. Review the operation results rather than relying on the command response alone.
Verify the User and Microsoft 365 Access
Return to Synchronization Service Manager and inspect the latest AD import, synchronization, and Microsoft Entra export. A successful export is an important milestone, but check the account in the destination as well.
Confirm the Cloud Object
In the Microsoft Entra admin center, find the user under Users . Confirm the account appears in the intended tenant with the expected sign-in name and on-premises synchronization status.
If the account is present but a value is wrong, return to the export details and inspect any duplicate-attribute errors. If it's absent, continue tracing the object rather than repeatedly starting the same cycle.
Check Access Separately
A synchronized identity doesn't guarantee a Microsoft 365 license, mailbox, or access to every group. Review the user's license assignment and required group membership after the identity issue is resolved.
For ongoing access, a process for Microsoft 365 group lifecycle management helps teams keep ownership and membership organized as employees join or change roles.
Restore Sync Without Guesswork
When Entra Connect stops syncing new users, start with scope and follow the object through each stage. The first failed operation usually gives you a more useful direction than a broad reset.
Once you've corrected the cause, confirm both the export and the cloud account. At SJC Technology, we help businesses with Microsoft 365 setup and managed IT support when identity issues need a closer review.

