Skip to main content
The Ops Playbook

Migrate Group Policy to Intune With Group Policy Analytics Before Moving Autopilot to Entra Join

Moving Autopilot to Entra join? Export GPOs as XML, import them into Intune Group Policy analytics, migrate supported settings to Settings Catalog and pilot safely.

KBY Technologies11 min readTier L115 min
Migrate Group Policy to Intune With Group Policy Analytics Before Moving Autopilot to Entra Join

Advertising disclosure: this article includes partner links. KBY may earn a commission if you sign up or buy through one, at no extra cost to you. How we make money.

To move Windows configuration off Group Policy before you switch Autopilot to Microsoft Entra join, export each GPO that applies to your Windows clients as an XML report, import it into Group Policy analytics in Intune (Devices > Manage devices > Group Policy analytics), migrate the settings that show MDM Support: Yes into a Settings Catalog profile, and assign that profile to a small pilot of Entra-joined Autopilot devices before anything wider. The constraint that shapes the whole job: Microsoft states that Group Policy isn’t supported on Microsoft Entra joined devices, which can only be managed through MDM. Any GPO setting you don’t move simply stops reaching new devices. Each XML file must be under 4 MB with proper Unicode encoding, and migration is best effort, so you review every setting rather than migrating whole GPOs blind.

#How Windows configuration is usually handled today

In a tenant that still deploys hybrid-joined devices, Windows Autopilot hands the device to Active Directory through the Intune Connector for Active Directory, and the GPOs linked to the workstation OUs do most of the configuration work, often with a smaller set of Intune policies on top. Few teams have a single list of which setting comes from where.

That arrangement starts to hurt when the organisation follows Microsoft’s current guidance. The Autopilot hybrid join documentation says Microsoft recommends deploying new devices as cloud-native using Microsoft Entra join, and that deploying new devices as hybrid joined, including through Windows Autopilot, isn’t recommended. The usual workaround is to flip the Autopilot profile to Entra join and rebuild missing settings in Intune as tickets arrive. Nobody then knows which settings were dropped on purpose.

#A better way to carry GPO settings into Intune

Group Policy analytics reads the GPO reports you export, shows which settings have a matching setting available to MDM, flags deprecated settings and settings with no MDM equivalent, and can create a Settings Catalog policy from the settings you pick. Microsoft’s Entra join planning guide recommends it for checking GPO and MDM policy parity.

The workflow below changes nothing in Active Directory. The GPOs stay linked, hybrid-joined devices keep receiving them, and what reaches devices is one Settings Catalog profile, plus any Endpoint security policies for firewall and AppLocker, assigned to a pilot group. The rollback is an assignment change in Intune, not a GPO restore.

Rendering diagram...

Every imported setting goes through that decision. Settings with no MDM support get a written decision too, so the gap list is something you keep rather than rediscover.

#Setting it up, one GPO at a time

You need an account with the Intune Administrator role, or a role that has the Security baselines permission and the Device configurations Create permission. Work through the steps in order and stop where a step says so.

  1. List the GPOs that apply to your Windows clients. On a machine with the Group Policy Management Console, run Get-GPO -All to list every GPO in the domain with its DisplayName, Id, GpoStatus and ModificationTime. It’s read-only. Keep only the GPOs linked to workstation OUs, and stop if a GPO has no owner who can make the keep-or-drop call on its settings.
  2. Export each GPO as XML. In GPMC, expand your domain, then Group Policy Objects, right-click the GPO and choose Save report, with Save as type set to XML File. From PowerShell, Get-GPOReport -Name "Workstation Baseline" -ReportType XML -Path "C:\GPOReports\Workstation Baseline.xml" writes the same kind of report for one GPO, and it doesn’t change the GPO. Export one GPO per file: Get-GPOReport -All writes every GPO into a single file, and Intune rejects any single GPO file over 4 MB. Check each file’s size before you import. If a file is over 4 MB, Microsoft’s advice is to reduce the number of settings in that GPO.
  3. Import the files. In the Microsoft Intune admin center, go to Devices > Manage devices > Group Policy analytics, select Import, pick one or more XML files and select Next. Choose a scope tag deliberately. If you don’t pick one, the Default scope tag is used, and only admins with the same scope tag can see the imported GPO or migrate it later. Select Next > Create and Intune analyses the file.
  4. Read the analysis. Each GPO shows an MDM Support percentage, Unknown Settings, Targeted in AD (Yes means it’s linked to an OU) and Last imported. Select the percentage to see every setting with its Scope (user or device), Min OS Version, CSP Name and CSP Mapping. Reports > Device management > Group policy analytics groups settings across all imports as Ready for migration, Not supported or Deprecated; it can take about 20 minutes to update after an import.
  5. Decide per setting. Microsoft’s own advice is not to include all your Group Policy settings without reviewing them, because some don’t apply to cloud-native endpoints. Write down every Not supported, Deprecated and Unknown setting with an owner and a decision. AppLocker and Firewall rule settings can’t be migrated from here: the Migrate option is greyed out, and Microsoft directs you to the Endpoint security workload for them.
  6. Migrate the chosen settings. Back in Group Policy analytics, tick Migrate next to one or more GPOs, then select Migrate. On Settings to migrate, tick only the settings you decided to keep and select Next. If two GPOs set the same setting to different values, Intune shows “Conflicts are detected for the following settings: <setting name>. Select only one version with the value you prefer in order to continue.” Untick one of them. Check the values on Configuration, then name the profile clearly, such as Windows: Imported Workstation Baseline, with the source GPOs in the description.
  7. Assign only the pilot. In Assignments, include one small assigned (static) group of Entra-joined Autopilot pilot devices. If you route Autopilot devices with group tags, you can build that group the way the guide to routing Autopilot profiles with group tags and dynamic device groups describes, but Microsoft notes that dynamic device groups take time to populate at enrolment, so a static group or an assignment filter gives a more predictable pilot. Select Create. The profile appears under Devices > Manage devices > Configuration, and assigned devices pick it up at their next check-in.

Some settings won’t land cleanly. Migration is best effort: older Office or Google Chrome administrative template settings may be offered as a newer alternative setting, and settings with an unexpected value format, or a parent setting whose required child is missing from the GPO, show errors in Notifications while the profile is created. Rebuild each of those by hand in the Settings Catalog and add it to the decision list.

Laptop displaying data analytics graph in a modern office setting, symbolizing growth and technology.
Photo by ThisIsEngineering on Pexels

#Who can run the import and who can change the result

Scope tags are the control that matters here. An imported GPO is visible only to admins who share one of the scope tags chosen at import, Give the import and the profile the scope tag of the team that owns Windows configuration.

Device scope and user scope also need a deliberate choice. In the Settings Catalog, a setting tagged (Device) writes to HKEY_LOCAL_MACHINE and a setting tagged (User) writes to HKEY_CURRENT_USER. A device-scope setting assigned to a user applies to every user on that device once that user signs in and Intune syncs, and a user-scope setting assigned to a device applies to all users of the device, much like loopback set to merge.

Leave the original GPOs linked and unchanged during the pilot. Hybrid-joined devices still depend on them.

#Checking it worked on the pilot devices

Give the pilot devices time to sync. Newly enrolled Windows devices check in every 3 minutes for 15 minutes, then every 15 minutes for 2 hours, then around every 8 hours; an assignment change also triggers a notification to online devices, which can arrive immediately or take a few hours.

  1. Open Devices > Manage devices > Configuration, select the profile and read Device and user check-in status. Every pilot device should show Succeeded. Error means the policy failed to apply and usually carries an error code; Conflict means two policies set the same setting.
  2. Select Per setting status to see which individual setting failed.
  3. Open Devices > Monitor > Assignment failures. The new profile shouldn’t be listed.
  4. For a device in Conflict, open Devices > All devices, select the device, then the conflicting row. Intune lists every profile that contains the setting. Check security baselines and endpoint security policies too.
  5. Sign in on a pilot device as a normal user and test the behaviour each migrated setting controls, starting with anything security-related such as BitLocker. The script that lists Windows devices with no BitLocker recovery key in Entra ID is a quick cross-check if the GPO you migrated carried BitLocker settings.

#What goes wrong in a Group Policy migration

  • The import fails. The file is over 4 MB, or it isn’t in the expected Unicode encoding. Re-export that one GPO from GPMC with Save report as XML. If it’s still too large, split the GPO’s settings before exporting again.
  • Another admin can’t see the imported GPO. It was imported with a scope tag they don’t hold, or with Default when they aren’t scoped to Default. Edit the scope tag instead of importing a second copy.
  • MDM Support looks wrong for some settings. Group Policy analytics currently supports non-ADMX settings only in English. A GPO with settings in another language gives an inaccurate percentage, so review those settings by hand.
  • Pilot devices show Conflict. Two Intune policies set the same setting differently. Intune leaves configuration conflicts for you to resolve: remove the setting from one of the profiles.
  • Settings arrive late on brand-new devices. The profile is assigned to a dynamic device group that hadn’t picked up the device during setup. Use a static group, a user group with an assignment filter, or enrolment time grouping, which Microsoft lists for exactly this delay. The guide to configuring the Autopilot Enrollment Status Page covers holding users at setup until required apps are in place.
Person working on a laptop with business analytics displayed on the screen.
Photo by Shoper .pl on Pexels

#Backing out a migrated profile

Because nothing changed in Active Directory, the rollback lives entirely in Intune. Before the pilot, export the Group Policy analytics view to CSV and save the decision list.

  1. To stop one device getting the profile, remove it from the pilot group. To stop the pilot, remove the group from the profile’s assignment. Microsoft notes that removing or unassigning a profile on Windows takes effect once the Entra user signs in and the device syncs with Intune.
  2. Expect some values to stay. Whether a Windows setting is removed or kept (often called tattooing) depends on the setting’s CSP. Where a value stays, assign a profile that sets the value you want instead; setting it to Not configured hands control of that setting back to the user.
  3. Fix the failing setting in the profile, or delete it from the profile, and reassign to one pilot device first. Confirm Succeeded on that device before you add the rest of the pilot back.

#Measuring progress toward Entra join

Set the baseline before the pilot: the number of settings across the workstation GPOs, split into Ready for migration, Not supported and Deprecated from the readiness report. Progress is the share of settings you decided to keep that are delivered by Intune and report Succeeded on every pilot device, plus the share of Not supported and Deprecated settings with a recorded decision. Both should reach 100 percent before you widen the assignment.

Review the profile’s check-in status and the Assignment failures report weekly during the pilot. A reasonable threshold for widening is no Error or Conflict on any pilot device across at least two maintenance check-ins, which Microsoft estimates at about every 8 hours.

#Before you switch the Autopilot profile to Entra join

  • Every workstation GPO is exported, imported and has a named owner.
  • Every Not supported, Deprecated and Unknown setting has a written decision.
  • Firewall and AppLocker settings are rebuilt in Endpoint security and tested on the same pilot.
  • The Settings Catalog profile shows Succeeded on every pilot device, with no Conflict.
  • Scope tags on the import and the profile match the team that owns Windows configuration.
  • The GPOs are still linked for hybrid-joined devices, and the CSV export and decision list are saved with the change record.

Once all six hold, widen the profile to the device group your Entra join Autopilot profile targets, then change the Autopilot deployment profile for new devices. Retiring the GPOs themselves is a separate decision, made only when no hybrid-joined device still depends on them.

About this page

Credited to

Dates

Published

Sources

This page lists no external sources.

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on Migrate Group Policy to Intune With Group Policy Analytics Before Moving Autopilot to Entra Join. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Discover more

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

Operate smarter, with fewer recurring tickets.

Receive new operational playbooks, incident-prevention guidance, automation scripts and recovery runbooks.