So one critical part of any successful Autopilot process is targeting, we need a way of pointing our Autopilot Devices to the correct profiles. Now I always try to keep these down to a single profile for traditional AAD or even Hybrid if you have no choice, but you may want to dabble in auto deploy scenarios which will require another profile, and well we can't just do a one size fits all.. So Dynamic Device AAD Groups and Grout Tags are our focus on this blog article.

So this is something I wrote quite some time ago, many folks configure OneDrive using the Administrative Templates in Intune, but old habits Die Hard. Below you will learn how to build a One Drive Profile to Auto Configure OneDrive under the current Logged on user using a Custom CSP and ADMX ingestion, very slick Process.

There are a lot of guides out there for Microsoft Intune, this one is going to be focused at Windows Management primarily around Azure AD Join, replacing much of the on-premise functionality to provide a Modern approach to Windows Management.

I always start at the Windows Enrollment you can find this section under Devices > Device enrollment > Enroll devices > Windows enrollment. This section of the Endpoint Manager portal connects to other sections around the Azure Resource Manager Portal like Automatic Enrollment which will take you to the Mobility section in Azure Active Directory.

The ESP gives use the ability to hold the user as a designated screen, until our configurations are complete then allow the user access to their desktop once all configurations are complete. Below is an example on how I configure this with customers.

So a common misconfiguration I see is how customers configure the Mobility (MDM and MAM) in the Azure Resource Manager Portal. Where Azure AD join will still operate without this being configured, you will have inconsistent results leveraging Intune or other 3rd party MDM if this is not configured correctly.

So I have been asked a few times to walk through a customer's environment ensuring everything is in place for Azure AD join Scenarios. Most Azure AD Tenants come pre-configured for Azure AD Join, but Here are a few of the configurations to what out for and why they are important.

So this has been an interesting debate for the past few years as I have worked with various customer working towards a modern approach to Windows 10. Whether modern means Hybrid or Full Azure AD Join. In this Blog I will talk about rational of Azure AD vs Hybrid and in future Blogs on how I achieve an Enterprise Ready Azure AD Join Configuration.