Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not importing some setting catalog policies #209

Open
royklo opened this issue Apr 2, 2024 · 2 comments
Open

Not importing some setting catalog policies #209

royklo opened this issue Apr 2, 2024 · 2 comments

Comments

@royklo
Copy link

royklo commented Apr 2, 2024

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
Copy link
Author

royklo commented Apr 2, 2024

Some for conditional access.

image

@Micke-K
Copy link
Owner

Micke-K commented Apr 3, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants