Resolved - Group Policy Objects from past releases of Group Policy analytics are excluded

[Intune_Support_Team]

Updated 05/05/22: This issue was resolved with the November (2111) Intune service release. See the updates at the end of the post for more details. We're also excited to share that with the April (2204) service release, you can now analyze your on-premises group policy objects (GPO) using Group Policy analytics (in public preview). See: Create a Settings Catalog policy using your imported GPOs in Microsoft Endpoint Manager (public prev... to learn more.

Group Policy analytics has gone into public preview with the 2009 release, you can learn more here. There is a known issue with the new “Migration readiness report” where Group Policy Objects (GPOs) that you have uploaded in past releases of Group Policy analytics will be excluded in calculations done in the graphic at the top of the workload, Summary blade and Migration Readiness report.

Below are two workarounds for this issue:

1. Force a re-compute of calculations by manually taking GPOs through the “Import” workflow again.
2. Use the PowerShell script that was provided to help automatically re-compute the calculations. Follow the instructions hosted on our GitHub repository.
   
   

Upcoming feature improvements

We're excited to share that with the April (2204) service release, you can now analyze your on-premises group policy objects (GPO) using Group Policy analytics (in public preview). See: Create a Settings Catalog policy using your imported GPOs in Microsoft Endpoint Manager (public prev... to learn more.

Let us know if you have any additional questions on this by replying to this post or tagging @IntuneSuppTeam out on Twitter.

Post updates:

05/24/21: We previously noted that in Q4 of 2020 that we would be doing an automatic re-compute for all GPOs across all tenants. This is still under investigation, and we’ll keep this post updated as we receive additional information.

02/01/22: This known issue was resolved with the November (2111) service release: MDM support data to refresh automatically in Group Policy analytics tool. We also added updates on Group Policy settings migration: we no longer support migration to administrative templates, but we do support migration to setting catalog.

05/05/22: We previously noted a private preview for support on a "Migrate" workflow. We're excited to share that this is now available in public preview! Week of April 25, 2022 (Service release 2204) | Create a Settings Catalog policy using your imported....

[Cristopher Alaya]

We tried this out as soon as it came to public preview and I have to say it's shaping up to be an awesome tool to help move things out of legacy GPO and into cloud management.  I left feedback w/ the tool and look forward to improvements as they come out. 

This post mentions a future release coming out Q4 of this calendar year.  Is there a way to be notified when that will be available besides following announcements here and on Twitter?

Thanks!

[Michael Cherry]

Is this the evolution of the former MMAT tool, which is still available at GitHub, but appears to be an abandoned or stale project? See: https://github.com/WindowsDeviceManagement/MMAT.

Thanks, 

Michael Cherry

[Nick Wiley]

Any news on the Migrate to MDM bit?

[Intune_Support_Team]

Hi @Cristopher Alaya and @Michael Cherry, thanks for the feedback! This known issue was resolved with the November (2111) service release: MDM support data to refresh automatically in Group Policy analytics tool. We also added updates on Group Policy settings migration: we no longer support migration to administrative templates, but we do support migration to setting catalog.

@Nick Wiley, please reach out to the email address in our post with your tenant ID to get flighted on the “Migrate” workflow!

05/05/22 Edit: We previously noted an email address where customers could get flighted in our private preview. We're excited to share that we've taken the private preview tag off, and this workflow is now available in public preview! For more information, please see the updated post above.