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
Right now the SPOTenantSettings still has a dependency on the PnP module that requires the "Sites.FullControl.All" permission even if you just need to read the conf.
Would it be possible to remove this dependency and only get data from Get-MgAdminSharepointSetting or provide another resource that would only rely on this cmdlet?
The problem is that we are using M365DSC to audit tenants config and we are not allowed to have write permissions like "Sites.FullControl.All" meaning that we could for now not audit the SPO config.
Would it also be possible to include all properties from the Get-MgAdminSharepointSetting cmdlet.
For example right now all the property related to Sharing config are not included.
Microsoft 365 DSC Version
1.24.424.1
Which workloads are affected
SharePoint Online
The DSC configuration
No response
Verbose logs showing the problem
No response
Environment Information + PowerShell Version
No response
The text was updated successfully, but these errors were encountered:
Description of the issue
Right now the SPOTenantSettings still has a dependency on the PnP module that requires the "Sites.FullControl.All" permission even if you just need to read the conf.
Would it be possible to remove this dependency and only get data from Get-MgAdminSharepointSetting or provide another resource that would only rely on this cmdlet?
The problem is that we are using M365DSC to audit tenants config and we are not allowed to have write permissions like "Sites.FullControl.All" meaning that we could for now not audit the SPO config.
Would it also be possible to include all properties from the Get-MgAdminSharepointSetting cmdlet.
For example right now all the property related to Sharing config are not included.
Microsoft 365 DSC Version
1.24.424.1
Which workloads are affected
SharePoint Online
The DSC configuration
No response
Verbose logs showing the problem
No response
Environment Information + PowerShell Version
No response
The text was updated successfully, but these errors were encountered: