Duplicate Profiles Created During Import – Existing Policies Not Recognised Until All Items Loaded

[SasStu]

Hi,

I am currently importing newer profiles from a different tenant and want to replace the existing versions. While testing with single Settings Catalog profiles, I noticed that duplicates were created.

I checked whether the “Skip if object exists” option would detect the existing policy and whether this was only an issue with the preview replace feature, but I got the same result.

After further investigation, I realised the configuration profile in question was not listed in the GUI because it only loads the first 20 objects by default. When I used the “Load All Items” button and tried again, it worked – the existing policy was recognised and skipped or replaced as expected.

Assumption:
Before any import action is carried out, all existing policies should be loaded to ensure accurate detection and avoid duplicates.

Thank you for your excellent work!

Sascha

[Micke-K]

Hello,

Ah another great pickup.... I have to look into this. Feels like paging caused more headaches that it solved.

Easy solution for now is to turn paging off in Settings. You do this by select Graph API Default or All. First one default back to API default paging size, the other one will always load all values.

Cheers!