![Itunes download for windows 10 for gpo](https://kumkoniak.com/77.jpg)
![itunes download for windows 10 for gpo itunes download for windows 10 for gpo](https://practicalsbs.files.wordpress.com/2013/06/excludedirectoriesinroamingprofile001.jpg)
Remember that in this scenario the devices are managed by Microsoft Intune and enrolled using the Intune Client Software. Navigate to >Azure>Azure Active Directory>Devices>All devices. You can also verify this in the Azure portal This means the device is Hybrid Azure AD Joined. Further below you will also see that the value for DomainJoined is YES. On the test device run dsregcmd /status from the command line. You can check successful joined devices using dsregcmd.exe. Read the documentation and make sure your devices register with Azure AD. Microsoft already has a written an article about this so I won’t go into details. This can be accomplished by configuring Hybrid Azure AD joined devices. We have an on-premises Active Directory environment and want to join our domain-joined devices to Azure AD. One of the requirements to make this all work, is that devices are Azure AD joined.
![itunes download for windows 10 for gpo itunes download for windows 10 for gpo](https://i.ytimg.com/vi/e8kRoizHL1k/maxresdefault.jpg)
- Active Directory integrated with Azure AD.
- Active Directory joined devices running Windows 10, version 1709.
- Devices are automatically MDM enrolled and managed by Intune using the MDM channel (as mobile devices).
- Devices are automatically Azure AD joined.
- Devices are retired/removed from the old Intune portal.
- Devices are managed by Microsoft Intune as computers using the PC Client Software.
-
I want to share my own experience migrating from Microsoft Intune Enrolled devices using the PC Client Software (Agent) to re-enrolling these devices using the MDM channel. In this topic we’ll be setting up Winddevices to Azure AD join and automatically MDM enroll to Microsoft Intune.