SkipToTheEndpoint
Native Intune policy import failing
Hello,
I am trying to import one of the settings catalog (JSON files). I keep getting an error message as shown in the attached screenshot. I would like to test this with native import first.
Hey @devearoux
Unfortunately the UI doesn't allow the import of configurations into the Endpoint Security blade, and the format of the JSON files exported by the IntuneManagement tool are different enough for the UI to throw an error if you try and import them.
I've been deliberating whether to make just the Settings Catalog policies available in UI-importable versions, but then you'd be missing a bunch of settings.
Is there a reason you're not able to import them using IntuneManagement?
Hi @SkipToTheEndpoint ,
Thank you for the response. Aren't the Microsoft Office - U - Security settings located under Devices > Configuration blade? I am trying to import the policies from the Settings Catalog folder. I have tried different JSONs and every one of them have failed to import.
Example Path: OpenIntuneBaseline-windows-v3.6\OpenIntuneBaseline-windows-v3.6\WINDOWS\IntuneManagement\SettingsCatalog
Regarding IntuneManagement, it is not always feasible to have an app registration created for import as sometimes the customer does not allow more permissions than Intune Administrator role. Hence, I wanted to test the settings catalog import directly. That should still work though, correct?
@VinceThompson , @SkipToTheEndpoint Also, may be it is just me using IntuneManagement for the first time, however, I felt that the documentation for IntuneManagement is not beginner friendly. There is a lot of trial and error when trying to test it. I have not been able to use it efficiently yet. Although the tool looks really promising. May be once I know how to use it, it would be great. However, as mentioned above, I would like to see if I can just import the JSONs from the Settings Catalog folder.
Thank you again for this response. I would really like to move away from Microsoft Security Baselines and point customers to this Open Intune Baseline solution.
There is a painful option of popping over to https://github.com/SkipToTheEndpoint/OpenIntuneBaseline/blob/main/WINDOWS/SETTINGSOUTPUT.md finding the policy and manually loading it in if you're not confident or able to use the IntuneManagement. If you have a test tenant and CIPP is a separate way you may be able to side load things too.
