Nik Charlebois

After much investigation, this is caused by the language of the SPO site and has nothing to do with the OS. If you export the permissions from a site that...

Sites.FullControl.All needs to be applied under the SharePoint provider, not Microsoft Graph. Please see: https://github.com/microsoft/Microsoft365DSC/issues/2506

@Timsto have you had a chance to look at the comments? Should we keep this PR open or close it?

Looks like this may be a catch 21. We made a decision a few years back to adopt PnP.PowerShell over SPO PowerShell. On top of this, the latest PnP.PowerShell module...

The recommendation here would be for us to wait for these SPO Admin APIs to be available on Graph.

My understanding is that this has been fixed in recent version of the Microsoft Graph SDK. @ykuijs can you please confirm?

This is not something we are able to reproduce on our end. The resource is looking for a Label match based on display name, not ID.

Essentially, we would need to check in the resource's parameters list (the .psm1 files) to see if $CertificateThumbprint, $ApplicationSecret or $Credential are present and then make the decision based on...

Let's deprecate this parameter from the resource. The documentation seems off for this parameter anyway: 

Can you please update to the latest version by running ``` Update-M365DSCModule ``` And confirm if this fixes your issue. We cannot replicate on our end and the cmdlet is...