Yes, there are GPOs in Intune
When I have the standard “you don’t need domain join and SCCM if you use Intune” conversation, the first push-back from the uninitiated is that Intune does not have full parity with on-premise GPO (Group Policy Objects). This hasn’t been true for sometime, but now with the official release of Administrative Templates, it is even more ludicrous.
Types of Intune policy
Policy from Intune can be divided into three categories: Configuration profiles, custom CSP, and Administrative Templates.
Configuration profiles
These are the easy ones; profiles that are nothing more than GUI toggles in the console just like any standard MDM (Mobile Device Management) solution. Want to disable Cortana? Just hit the ‘block’ button in the console. Require CTRL + ALT + DEL to unlock a PC? Click away, my friend.
Custom CSP
So what happens when you want to set a policy that’s nowhere to be found in the Intune console? That’s when you head over to the holy grail of modern management, the Policy CSP page. Here you’ll find every policy that can be configured to Windows 10 through Intune. The one catch is you have to put them together yourself.
Let’s say for example you want to disable the consumer features of Windows that business love so much (that was sarcasm). First step is to find that policy on the Microsoft CSP page. As you can see below, the AreaName is “Experience” and the Policy is “AllowWindowsConsumerFeatures”. Our options are represented by the values 0 (Not Allowed) and 1 (Allowed).
The basic construction of the policy is usually ./<Scope>/Vendor/MSFT/Policy/Config/<AreaName>/<Policy>.
Scope can also be found on the page with the policy documentation. So in this case, our policy will read as ./Device/Vendor/MSFT/Policy/Config/Experience/AllowWindowsConsumerFeatures. Intune has an option when creating configuration profiles to choose “custom”. Simply apply the values we aggregated from the CSP page to set and assign:
Administrative templates
Ah yes- this is the long awaited feature that was keeping so many of us nerds in suspense. Actual, GPOs in the Intune console. Simply add a configuration profile with the type “Administrative Templates”. From there, you will find an embarrassingly disorganized list of every ADMX policy available.
Let’s go ahead and set a configuration for OneDrive policy. After creating the Administrative Templates profile, open the settings and search for “OneDrive”. Everything available in that node should populate. Select the settings you want to configure, and just like traditional GPO, you’ll be presented with the options. That’s it. You can make as many of these profiles as you’d like as they pertain to different areas of Windows.
There we have it; three different ways to add policy through Intune. Again, let me emphasize that this provides us complete control over a non-domain joined PC. And the advantage of these policies through Intune is unlike the local domain, these can be configured and enforced anywhere, regardless of the machines location.
Coming up next, I will tell you why you don’t need SCCM either.