Right now, M365DSC only supports properties for resources that are made available by the used Set-cmdLets for the resource. PowerShell DSC does support read-only properties that are populated after by the Get-TargetResource function within a resource.
In M365DSC we have the built in Export-TargetResource function. It would add a lot value for documenting a tenant if we could export all available properties and/or even create resources that would export settings for objects in M365 and Azure that cannot be set.
This will be really helpful especially for configuration backups and configuration changes done by Microsoft for a tenant as well as Role Entry parameter for Management Role component.
Right now, M365DSC only supports properties for resources that are made available by the used Set-cmdLets for the resource. PowerShell DSC does support read-only properties that are populated after by the Get-TargetResource function within a resource.
In M365DSC we have the built in Export-TargetResource function. It would add a lot value for documenting a tenant if we could export all available properties and/or even create resources that would export settings for objects in M365 and Azure that cannot be set.
https://learn.microsoft.com/en-us/powershell/dsc/resources/authoringresourceclass?view=dsc-1.1#declare-properties
cc/ @ykuijs and @NikCharlebois What do you think?