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
The resource returns information that is available through Get-PnPTenant. The corresponding Graph-cmdlet Get-MgAdminSharepointSetting returns quite a number of the same properties and additionally TenantDefaultTimezone. The latter would be very nice to set first thing in order to not having to do it from every SPO-site being created.
I'm not sure if any other resources mix permissions/cmdlets like this - ie calling New-M365DSCConnection twice with different workloads - but I'd think that this would be the easy way. The PNP-module could be used to provide validation for the timezone via 'Get-PnpWeb -Includes RegionalSettings.TimeZones' (see https://www.sharepointdiary.com/2017/06/sharepoint-online-change-time-zone-using-powershell.html) - but another option is to just let the Update-cmdlet throw an error (and log it).
Microsoft 365 DSC Version
DEV
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
The resource returns information that is available through Get-PnPTenant. The corresponding Graph-cmdlet Get-MgAdminSharepointSetting returns quite a number of the same properties and additionally TenantDefaultTimezone. The latter would be very nice to set first thing in order to not having to do it from every SPO-site being created.
I'm not sure if any other resources mix permissions/cmdlets like this - ie calling New-M365DSCConnection twice with different workloads - but I'd think that this would be the easy way. The PNP-module could be used to provide validation for the timezone via 'Get-PnpWeb -Includes RegionalSettings.TimeZones' (see https://www.sharepointdiary.com/2017/06/sharepoint-online-change-time-zone-using-powershell.html) - but another option is to just let the Update-cmdlet throw an error (and log it).
Microsoft 365 DSC Version
DEV
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: