search

Micke-K / IntuneManagement

Copy, export, import, delete, document and compare policies and profiles in Intune and Azure with PowerShell script and WPF UI. Import ADMX files and registry settings with ADMX ingestion. View and edit PowerShell script.
MIT License
1.13k stars 201 forks source link

Not importing some setting catalog policies #209

Open royklo opened 7 months ago

royklo commented 7 months ago

I've bulk exported all settings and i've noticed that some policies didn't import in the destination tenant, such as "Microsoft 365 Baseline" and one MacOS configuration policy.

I didn't receive any error, but noticed it didn't land in the destination environment.

Loading Settings Catalog objects WARNING: Could not find migration table Import objects WARNING: Could not find migration table Import Settings Catalog object All Types - Productie - Windows 10/11 - M365 Apps Security Baseline WARNING: Could not find migration table Failed to invoke MS Graph with URL https://graph.microsoft.com/beta/deviceManagement/configurationPolicies (Request ID: 2816229d-9853-409a-aaf9-3aba6974aa6b). Status code: BadRequest. Response message: . Response message: Info Invalid Reference id found in Policy created from Template 90316f12-246d-44c6-a767-f87692e86083_1 PolicyId

TemplateId 90316f12-246d-44c6-a767-f87692e86083_1 InvalidReferenceId 8b15df12-f484-4d30-93e7-14253e25fde9 - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: b8a5f292-5f20-401b-9ec9-93ddebcd3f5b - Url: https://fef.msub07.manage.microsoft.com/DeviceConfigV2/DCV2GraphService/de147310-ffff-2273-0302-033122480958/deviceManagement/configurationPolicies?api-version=5024-01-18 Exception: The remote server returned an error: (400) Bad Request. SCR-20240402-lpd-2

royklo commented 7 months ago

Some for conditional access.

image

Micke-K commented 7 months ago

Hello

The first issue is because the exported policy is the old version.

90316f12-246d-44c6-a767-f87692e86083 is the id of the "Microsoft 365 Apps for Enterprise Security Baseline" template.

90316f12-246d-44c6-a767-f87692e86083_1 is for "Version 2206". This version is now superseded.

This is replaced by 90316f12-246d-44c6-a767-f87692e86083_2 which is for "Version 2306".

So it looks like it is not possible to import a policy for an old version once it is marked superseded.

The second issue seems to be caused by authentication and Conditional Access. This page might be of help. I have not seen this myself.

Cheers!

image