Closed ColinHJ closed 2 weeks ago
@ColinHJ For now, please use Windows PowerShell 5.1 instead of PowerShell 7. There are a number of issues that are still present because Microsoft365DS doesn't properly support Windows PowerShell and PowerShell 7 at the same time... I am working on it though.
Thank you for the feedback, @FabienTschanz. I am experiencing better results with PowerShell 5.1.
Description of the issue
I have been trying to test M365DSCBlueprint. My tests included ODSettings and AADConditionalAccessPolicy. An error occurs at line 1106 of M365DSCReport.psm1. Upon debugging, I discovered that Get-M365ResourceKey returns null to $Key at line 1104. Get-M365DSCResourceKey seems to be filtering $DSCResourceInfo for properties of $_.IsMandatory. All nested property values of $DSCResourceInfo are strings of "Microsoft.PowerShell.DesiredStateConfiguration.DSCResourcePropertyInfo". I suspect the issue arises when GET-DSCResource -Module 'Microsoft365DSC' is executed on line 739.
Microsoft 365 DSC Version
1.24.724.1
Which workloads are affected
Azure Active Directory (Entra ID), OneDrive for Business
The DSC configuration
No response
Verbose logs showing the problem
Environment Information + PowerShell Version