Forum Discussion
rholland
Mar 03, 2021Copper Contributor
2 Azure machines
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 deploymen...
- Mar 06, 2021It'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.
Thijs Lecomte
Mar 06, 2021Bronze Contributor
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.
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.
rholland
Mar 08, 2021Copper Contributor
Thanks!
Appreciate the response as I thought it was meant to work slightly different. All is working as it should do then 🙂
Appreciate the response as I thought it was meant to work slightly different. All is working as it should do then 🙂