Hi,
Hybrid Azure AD join was mistakenly disabled from the AAD Connect configuration. If we re-enable it will it cause any problems, like duplicates or something?
Regards
Robert
Hi,
Hybrid Azure AD join was mistakenly disabled from the AAD Connect configuration. If we re-enable it will it cause any problems, like duplicates or something?
Regards
Robert
If you are syncing devices using Azure AD Connect, hybrid Azure AD joined devices will be automatically re-enabled during the next sync cycle. If the device was disabled in Azure AD, an administrator with sufficient privileges can enable it from the Azure AD portal.
If the device was actually deleted in Azure AD, you will need to re-register the device.
Repeated tries to unjoin and rejoin the same device might cause duplicate entries. If that is the case you should be able to remove the duplicates and keep the one that has the matching Object ID.
See FAQ.
Hi, thank you.
The sort time this has been disabled only new devices are in the onprem AD. Otherwise nothing changed on either side, so we should be good just to turn it on again right?
Sorry for the late reply. I was consulting with my teammate on this. It is possible that there could be duplicates if the sourceAnchor changed on-premises. If devices are not removed from Azure AD or On-prem AD, then there is no other impact than duplicate devices. If a device is removed and then added back any static group membership of the device won't be there for the new one. Intune policies applied to the old device may not work on the new device.
5 people are following this question.