Setting Name does not export properly on some tables

[DesmondBellingerSolvus]

Setting Name does not export properly on some tables

[Micke-K]

Hello!

I had a look at this. I cannot reproduce this. I tried with both built in Administrative Template settings policy and a policy form an imported ADMX file.

Something is wrong because there is no Category row. Not sure how that would happen either.

What Output Properties and Output Level do you use?

Is it the same result if you do a HTML output? I'm trying to figure out if the problem is the collector or the output provider.

Cheers!

[DesmondBellingerSolvus]

Thanks for the quick reply. The output is identical no matter what format I select. Where would I be able to see the output level and properties?

Settings file.json
I've attached an export of the application settings as well as an image of the Output settings tab.

[Micke-K]

Hello,

If you get the same issue on HTML etc. then there is an issue when collecting information. Do you document from Intune or from an exported folder. If you document from exported folder, are you logged in to the same tenant as the export?

Do you only get this on Administrative Templates or other policies as well?

Output level and Properties is only available for the Word Output provider.

Cheers!

[Micke-K]

Hello,

Can you try this? Documentation would not work when swapping between tenants. If that is what you did.

Cheers!

Documentation.zip

[DesmondBellingerSolvus]

Hi just to answer your questions: we are documenting directly from Intune.
The issue does only seem to affect Administrative Templates profiles.
I placed the file above in the extensions folder but it seems like I'm still getting the same results.

We're only working in a single tenant and I've been logged into the same one for the entirety of this process.

[Micke-K]

Hello!

That is very strange. I kind of know what's happening but can't explain it. The script uses an API to get settings information for ADMX policies and for some reason that is not working in your environment. Any hints in the log file? There should be graph errors if an API call fails.

Cheers!

[DesmondBellingerSolvus]

Looking at the logs I see a few errors:

This one as a log in:
Missing scopes: User.ReadWrite.All,Policy.Read.All,Policy.ReadWrite.ConditionalAccess,Application.Read.All,Agreement.ReadWrite.All,Organization.ReadWrite.All,CloudPC.ReadWrite.All

And one as documentation is attempted:
Failed to invoke MS Graph with URL https://graph.microsoft.com/beta/deviceManagement/groupPolicyDefinitions('5efa5eff-a8f6-46ba-a7cb-4e6d77631754') (Request ID: eee22664-dec8-4972-92b9-4c53e1b61f8f). Status code: Unauthorized. Response message: Access token validation failure. Invalid audience. Exception: The remote server returned an error: (401) Unauthorized.

The above error occurs 3 times followed by this:
Could not find definition for definition id ''. Values might be documented in the wrong order!

The section documented was the same one that I originally attached.

[Micke-K]

Hello,

Thank you for that. It explains the issue and I think I found the reason behind it. It's hard for me to test and verify since this would only happen in GCC environments (+ all other non-public environments).

Can you try this version?

Cheers!

Documentation.zip

[DesmondBellingerSolvus]

That worked, thank you very much!

[DesmondBellingerSolvus]

Just following up on the issue, after making a successful export of all of our Intune information, I checked the logs again and noticed that there were still quite a few Graph errors being thrown. Given the fact that it's probably hard to test outside of commercial, I figured you might be interested in the snippet of log file from that export.
Log11-20.txt