SOLVED

2 Azure machines

%3CLINGO-SUB%20id%3D%22lingo-sub-2181843%22%20slang%3D%22en-US%22%3E2%20Azure%20machines%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2181843%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20just%20started%20to%20implement%20Intune%20for%20our%20azure%20AD%20network.%20I%20have%20added%20a%20new%20machine%20into%20the%20autopilot%20section%20which%20default%20creates%20a%20machine%20in%20Azure%20AD%20as%20Azure%20AD%20Joined.%20Upon%20deployment%20profile%20with%20Hybid%20Azure%20AD%20join%2C%20the%20machine%20joins%20the%20on%20site%20domain%20and%20then%20Azure%20refreshes%20to%202%20machines%20of%20the%20same%20name.%20One%20with%20Azure%20AD%20Joined%20and%20one%20Hybrid%20Azure%20Domain%20Joined.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehow%20do%20you%20get%20it%20so%20the%20autopilot%20machine%2C%20deploys%20as%20a%20Hybrid%20Azure%20Machine%20so%20there%20isn't%202%20duplicates%20in%20Azure%20AD%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2181843%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

We have just started to implement Intune for our azure AD network. I have added a new machine into the autopilot section which default creates a machine in Azure AD as Azure AD Joined. Upon deployment profile with Hybid Azure AD join, the machine joins the on site domain and then Azure refreshes to 2 machines of the same name. One with Azure AD Joined and one Hybrid Azure Domain Joined. 

 

how do you get it so the autopilot machine, deploys as a Hybrid Azure Machine so there isn't 2 duplicates in Azure AD?

2 Replies
best response confirmed by rholland (New Contributor)
Solution
It's by design and there isn't much you can do about it.
Check out more information here: https://oofhours.com/2019/07/15/inside-windows-autopilot-user-driven-hybrid-azure-ad-join/

I quote:
Yes, you will end up seeing two devices in Azure AD when this process completes: The pre-created Azure AD Join device objects (which ends up getting enabled and renamed as part of this process) and the synced Hybrid Azure AD Join device object. Keep both of these objects around – never delete the original pre-created Azure AD device object.
Thanks!
Appreciate the response as I thought it was meant to work slightly different. All is working as it should do then :)