SOLVED

Hybrid identity and device ownership inconsistency

%3CLINGO-SUB%20id%3D%22lingo-sub-1334361%22%20slang%3D%22en-US%22%3EHybrid%20identity%20and%20device%20ownership%20inconsistency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1334361%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20in%20the%20process%20of%20rolling%20out%20Intune.%20Today%20we%20noticed%20several%20windows%20devices%20didn't%20show%20up%20in%20%3CSTRONG%3EDevices%3C%2FSTRONG%3E%20in%20Azure%20AD%20under%20their%20User.%20Some%20windows%20devices%20were%20marked%20as%20%3CSTRONG%3EAzure%20AD%20registered%3C%2FSTRONG%3E%20for%20join%20type%2C%20others%20still%20have%20%3CSTRONG%3EHybrid%20Azure%20Joined.%20%3C%2FSTRONG%3EIn%20both%20cases%2C%20Owner%20is%20marked%26nbsp%3B%20N%2FA%3C%2FP%3E%3CP%3EAt%20Intune%20portal%20these%20device%20show%20up%20as%20%3CSTRONG%3Emanaged%20by%3C%2FSTRONG%3E%20Intune%20with%20the%20correct%20user%20for%3CSTRONG%3E%20enrolled%20by%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20see%20this%3F%20Is%20this%20an%20expected%20behavior%3F%3C%2FP%3E%3CP%3EAny%20reason%20these%20devices%20are%20changing%20their%20join%20type%3F%20why%20would%20the%20user%20owner%20disappear%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1334361%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EEMS%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ehybrid%20identity%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1335651%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20identity%20and%20device%20ownership%20inconsistency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1335651%22%20slang%3D%22en-US%22%3ECould%20you%20tell%20us%20more%20about%20your%20current%20environment%3F%3CBR%20%2F%3E%3CBR%20%2F%3EAre%20your%20devices%20joined%20to%20an%20on-prem%20AD%20and%20then%20hybrid%20joined%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1335790%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20identity%20and%20device%20ownership%20inconsistency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1335790%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F551905%22%20target%3D%22_blank%22%3E%40bec064%3C%2FA%3EThanks%20for%20clarifying!%20It's%20still%20frustrating%20since%20the%20devices%20show%20up%20in%20Intune%20but%20not%20Azure%20AD%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F186539%22%20target%3D%22_blank%22%3E%40Thijs%20Lecomte%3C%2FA%3Eyes%2C%20devices%20are%20joined%20on-prem%20and%20then%20hybrid-joined%20by%20pushing%20a%20group%20policy%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1338785%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20identity%20and%20device%20ownership%20inconsistency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1338785%22%20slang%3D%22en-US%22%3EIf%20they%20are%20on-prem%20joined.%3CBR%20%2F%3EAll%20of%20your%20devices%20should%20sync%20as%20'hybrid%20azure%20ad%20joined'%20in%20the%20end.%3CBR%20%2F%3EI%20assume%20you%20have%20configured%20AAD%20connect%20to%20enable%20hybrid%20azure%20ad%20join%3F%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-plan%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-plan%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20a%20device%20is%20aad%20registered%2C%20starting%20from%20Windows%201803%20the%20registered%20device%20should%20automtically%20be%20cleanup%20and%20it%20should%20Hybrid%20join.%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-plan%23handling-devices-with-azure-ad-registered-state%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fhybrid-azuread-join-plan%23handling-devices-with-azure-ad-registered-state%3C%2FA%3E).%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20your%20devices%20are%20not%201803%2C%20you%20might%20need%20a%20manual%20cleanup%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1334979%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20identity%20and%20device%20ownership%20inconsistency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1334979%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F527244%22%20target%3D%22_blank%22%3E%40aghi234%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHello%2C%20%22%3CSPAN%3EHybrid%20Azure%20AD%20Joined%20Windows%2010%20devices%20do%20not%20have%20an%20owner.%20So%2C%20if%20you%20are%20looking%20for%20a%20device%20by%20owner%20and%20didn't%20find%20it%2C%20search%20by%20the%20device%20ID.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fdevice-management-azure-portal%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fdevices%2Fdevice-management-azure-portal%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAlso%2C%20take%20a%20look%20at%20this%20for%20more%20info%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fsv-se%2Fazure%2Factive-directory%2Fdevices%2Foverview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fsv-se%2Fazure%2Factive-directory%2Fdevices%2Foverview%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2110621%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20identity%20and%20device%20ownership%20inconsistency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2110621%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F527244%22%20target%3D%22_blank%22%3E%40aghi234%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20working%20on%20BitLocker%20management%20with%20Intune%20policy%20on%20hybrid%20Azure%20join%20device.%20We%20have%20on-prem%20AD%20that%20is%20connected%20to%20Azure%20AD%20and%20sync%20the%20device%20using%20AD%20connect.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAccording%20to%20MS%20that%20hybrid%20join%20device%20doesn't%20have%20ownership.%20But%20we%20saw%20in%20some%20situations%20that%20the%20ownership%20transfer%20to%20hybrid%20dedvice%20after%20we%20click%20Fix%20It%20button%20when%20MS%20Account%20shared%20experienced%20error%20message%20popped%20up.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20this%20is%20an%20expected%20behavior%20is%20there%20a%20way%20to%20automate%20the%20verification%20rather%20than%20ask%20user%20to%20click%20Fix%20it%20button.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20also%20noticed%20that%20the%20recovery%20key%20process%20tried%20to%20backup%20the%20key%20to%20on-prem%20AD%20which%20sometime%20created%20challenge%20because%20some%20user%20are%20working%20remotely%20and%20not%20connected%20through%20vpn%20all%20the%20time.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3CP%3Ecjsanto%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

We're in the process of rolling out Intune. Today we noticed several windows devices didn't show up in Devices in Azure AD under their User. Some windows devices were marked as Azure AD registered for join type, others still have Hybrid Azure Joined. In both cases, Owner is marked  N/A

At Intune portal these device show up as managed by Intune with the correct user for enrolled by

 

Anyone see this? Is this an expected behavior?

Any reason these devices are changing their join type? why would the user owner disappear?

5 Replies
best response confirmed by aghi234 (New Contributor)
Solution

@aghi234 

Let me get back to you (old info in MS docs).

*edit*

 

The first info I attached didn't have the correct information. I will report it to MS.

 

But this do have the correct info so take a look here and it will explain the behavior:

"Windows 10 devices that are hybrid Azure AD joined don't show up under USER devices. Use the All devices view in the Azure portal"

https://docs.microsoft.com/en-us/azure/active-directory/devices/faq

 

Also, take a look at this for general information https://docs.microsoft.com/sv-se/azure/active-directory/devices/overview

 

Could you tell us more about your current environment?

Are your devices joined to an on-prem AD and then hybrid joined?

@ChristianBergstromThanks for clarifying! It's still frustrating since the devices show up in Intune but not Azure AD

 

@Thijs Lecomteyes, devices are joined on-prem and then hybrid-joined by pushing a group policy  

If they are on-prem joined.
All of your devices should sync as 'hybrid azure ad joined' in the end.
I assume you have configured AAD connect to enable hybrid azure ad join?
https://docs.microsoft.com/en-us/azure/active-directory/devices/hybrid-azuread-join-plan

If a device is aad registered, starting from Windows 1803 the registered device should automtically be cleanup and it should Hybrid join. (https://docs.microsoft.com/en-us/azure/active-directory/devices/hybrid-azuread-join-plan#handling-de...).

If your devices are not 1803, you might need a manual cleanup

Hi @aghi234 

 

I am working on BitLocker management with Intune policy on hybrid Azure join device. We have on-prem AD that is connected to Azure AD and sync the device using AD connect.

 

According to MS that hybrid join device doesn't have ownership. But we saw in some situations that the ownership transfer to hybrid dedvice after we click Fix It button when MS Account shared experienced error message popped up.

 

If this is an expected behavior is there a way to automate the verification rather than ask user to click Fix it button. 

 

We also noticed that the recovery key process tried to backup the key to on-prem AD which sometime created challenge because some user are working remotely and not connected through vpn all the time. 

 

Thanks.

cjsanto