Forum Discussion
Entra hybrid join issue caused maybe by 2 M365 accounts
Hello to everyone,
one of my collegue has 2 Microsoft 365 accounts on its notebook when we tried to do the procedure to hybrid join his device; I suppose the other account give us problem in the procedure; now, there is only one account even if I can see in event log, in AAD log, that there is an error and 2 warnings bound to the old account.
However, I tried to repeat the procedure but without any luck; what I see that it is different from the other devices, if I give the cmd dsregcmd /status is in these 2 lines:
DisplayNameUpdated : YES
OsVersionUpdated : YES
while on other devices I see:
DisplayNameUpdated : Managed by MDM
OsVersionUpdated : Managed by MDM
We have all a Microsoft 365 Business subscription and the configuration and steps for the other devices was:
- We have all devices with Entra registered user, we started with this when we have only the Microsoft 365 Basic subscription
- We enrolled all devices, with group policy, in MDE when we upgraded to the business
- Installed the Azure AD Connect
- Users sync
- Devices sync
So, in the Entra portal we have first only the entry for registered, then when we synced the devices we have a second entry with hybrid registered and finally only one entry with Owner, MDM and Settings field filled with correct data; for example, when I make an hybrid join device, initially in the row I see MDE as MDM, then when the hybrid and registered compose one row I see Intune in that field.
For the device that give us problems, I see a row like this in Entra portal
while in Intune
Any help is greatly appreciated.
1 Reply
- lucheteIron Contributor
Hi MarcoMangianteIM,
I think the old Microsoft 365 account is still causing conflicts, even though it’s no longer in use. Since you're seeing errors and warnings tied to the old account, try these steps:
Make sure the device is fully removed from Entra ID and rejoin it from scratch. Run dsregcmd /leave, remove the device from Entra portal, and then reattempt the hybrid join. Also, check if any stale credentials are saved in Windows Credential Manager. If the issue persists, reviewing Azure AD Connect sync logs might help pinpoint the problem.
Regards!