@SteveW Thanks for reaching out.
Can you confirm if the Computer accounts were syncing before and is this something you are facing for new computer objects only ?
There are filtering in connector space to add computer object, so make sure they are checked.
One important thing about syncing a computer object is that unless the device has got a user certificate generated it wont be considered for syncing, this is a automated process and is usually done without any manual intervention unless the device is not able to find the Service Connection point in your local AD and if you have not enabled Hybrid Azure AD join from AAD connect tool.
Here is the process it follows :
- The device queries AD to find the SCP, in order to obtain AAD tenant details.
- The AAD tenant details are returned.
- The device creates a self-signed certificate and updates the userCertificate property on its own computer object with that info.
- AAD Connect after the userCertificate has been populated, up to 30 minutes later) syncs the AD computer object into Azure AD.
- The device (repeatedly) tries to register with AAD.
- When AAD can find a matching device (synced by AAD Connect), the registration will succeed and AAD will provide a device certificate back to the device.