You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details of the scenario you tried and the problem that is occurring
The New-M365DSCReportFromConfiguration -Type JSON command outputs a .json file with a Depth of 2 (default for ConvertTo-Json).
Any nested objects beyond that level are lost.
Example output of an AADApplication resource with nested Permissions object (MSFT_AADApplicationPermission) being truncated:
For consistency, recommend adding the ConvertTo-Json -Depth 25 parameter in the New-M365DSCConfigurationToJSON function.
See line 165 in M365DSCReport.psm1.
Details of the scenario you tried and the problem that is occurring
The
New-M365DSCReportFromConfiguration -Type JSON
command outputs a .json file with a Depth of 2 (default for ConvertTo-Json).Any nested objects beyond that level are lost.
Example output of an AADApplication resource with nested Permissions object (MSFT_AADApplicationPermission) being truncated:
Verbose logs showing the problem
N/A
Suggested solution to the issue
For consistency, recommend adding the
ConvertTo-Json -Depth 25
parameter in theNew-M365DSCConfigurationToJSON
function.See line 165 in M365DSCReport.psm1.
In function New-M365DSCDeltaReport, the Depth is already specified as 25.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
N/A
Version of the DSC module that was used ('dev' if using current dev branch)
Release 1.23.208.1
The text was updated successfully, but these errors were encountered: