3.2.1. Windows Profiles: Settings Catalog, ADMX Import, and Group Policy Analytics
💡 First Principle: Group Policy and Intune configure the same Windows settings through different plumbing — Group Policy writes registry values from a domain controller, Intune sets Configuration Service Providers (CSPs) over the internet. Migration is therefore a translation problem: for each setting in a GPO, is there a CSP that does the same job? Group Policy analytics answers that question for you, and the settings catalog is where the answer lands.
The settings catalog lists every available setting in one place. You start from an empty policy and add only what you need, which keeps policies small and their intent obvious. Windows settings in the catalog are generated from CSPs, including ADMX-backed settings, so many settings you know from Group Policy are already there. Templates still exist as logical groupings, but to see every setting in an area or find one specific setting, the catalog is the tool. A few behaviors come up repeatedly:
- Removing a setting with the minus sign makes it Not configured: Intune stops managing it, and users or other policies can change it.
- Device-scoped settings write to HKLM; user-scoped settings write to HKCU. If the same setting is assigned in both scopes, user scope wins.
- A user-scoped policy assigned to a device group applies to every user on that device, much like loopback processing in Group Policy.
- Windows profiles can carry applicability rules (OS version or edition) as well as assignment filters.
Custom profiles cover anything the catalog doesn't. You enter an OMA-URI — which is case-sensitive — and a data type (String, Integer, Boolean, Base64, XML and so on). The CSP must support Add, Replace and Get; if the value Intune reads back doesn't match what it set, Intune reports an error.
Importing custom ADMX brings third-party administrative templates (a browser, a line-of-business app) into Intune. The feature is in public preview at Devices > Manage devices > Configuration > Import ADMX. Its limits are specific: at most 20 ADMX files, each up to 1 MB, one ADML per ADMX, and en-us ADML only. Import dependencies first — mozilla.admx before firefox.admx — and delete in the reverse order. Some files need Windows.admx uploaded first, and a file containing a combo box setting fails to import. After importing, you build the profile from Templates > Imported Administrative templates (Preview). Don't import Windows' own built-in ADMX files to configure Windows; those settings are already in the settings catalog.
Group Policy analytics shows how much of your existing Group Policy can move to Intune. Export a GPO from the Group Policy Management Console with Save report as XML (under 4 MB), then import it at Devices > Manage devices > Group Policy analytics. For each GPO you see the MDM Support percentage — the share of its settings that have an Intune equivalent — plus unknown settings and the OU it targets in Active Directory. Each setting shows its CSP name and a CSP mapping, an OMA-URI you could use in a custom profile.
Worked example: a GPO with 120 settings shows 85% MDM support. That's 0.85 × 120 = 102 settings with an Intune equivalent and 18 without one, which you'll need to replace, drop or handle another way.
The migration readiness report (Reports > Device management > Group policy analytics) labels each setting Ready for migration, Not supported or Deprecated. When you're ready, tick Migrate on one or more GPOs, choose the settings, and Intune creates a settings catalog policy with the values carried over. Migration is "best effort": where two GPOs set conflicting values you must pick one, and for AppLocker and Firewall rules the Migrate option is disabled — use Endpoint security policies instead. Imported GPOs take a scope tag, so only admins with that tag can see or migrate them.
⚠️ Exam Trap: Group Policy analytics doesn't deploy anything on its own. Its output is a percentage, a readiness report and, if you choose Migrate, a settings catalog policy that you still have to assign. And Migrate is disabled for firewall and AppLocker rules, so "migrate the firewall GPO with Group Policy analytics" is a wrong answer.
Reflection Question: A team wants to configure a third-party browser that isn't in the settings catalog. Its ADMX file depends on a vendor "parent" ADMX and includes one combo box setting. What order do you import the files in, and what happens to the import?