Forum Discussion
Azure AD Connect computer object sync delays?
RobinCM :
There could be a few reasons why the newly joined computer object is not showing up in Azure AD after running a delta sync. Here are some steps you can take to troubleshoot the issue and get the computer object to appear in Azure AD faster:
Verify that the computer object is synchronized to Azure AD Connect. You can check this by running the following command on the server running Azure AD Connect:
Get-ADObject -Filter {ObjectClass -eq 'computer' -and ObjectGUID -eq '<GUID>'}Replace <GUID> with the GUID of the computer object that you want to check. This command will confirm if the computer object is synchronized with Azure AD Connect.
Check the synchronization logs for any errors or warnings related to the computer object synchronization. The logs are located in the following directory: C:\ProgramData\AADConnect\SyncEngine\SyncRulesEditor\SyncService\UIShell\SyncCycleLogs.
Ensure that the computer object has the required attributes populated in on-premises AD. Specifically, the msDS-Device object attribute should be set to TRUE for hybrid Azure AD join to work correctly.
Check if the computer object has been added to any exclusion rules in Azure AD Connect. If the object is excluded, it won't be synchronized to Azure AD.
Verify that the computer object has a valid DNS entry and that the DNS server used by the computer is the same as the one used by Azure AD Connect.
Ensure that the computer has an internet connection and can communicate with Azure AD.
Finally, you can try forcing a full synchronization instead of a delta sync to see if the computer object appears in Azure AD. You can do this by running the following command on the server running Azure AD Connect:
Start-ADSyncSyncCycle -PolicyType InitialThis will perform a full synchronization of all objects from on-premises AD to Azure AD.
By following these steps, you should be able to troubleshoot the issue and get the newly joined computer object to appear in Azure AD faster.