Open Zerg00s opened 5 years ago
Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.
We can use the old New-PnPTenantSite commandled. It seems to work fine. But I'm not sure if it causes any issues when creating modern Communication sites with it:
New-PnPTenantSite -Title $currentSite.SiteTitle -Url $fullSiteUrl -Owner $SiteOwner -Template 'SITEPAGEPUBLISHING#0' -TimeZone 10 -Wait
Same issue here. Also, new version of pnp-powershell present issues with the new-pnpSite ... it takes ages to complete
still the same :/
updating the current pnp-powershell version may help
Reporting a Missing Feature
There seems to be no way to create a modern communucation site when using Azure AD App authentication with a certificate.
Expected behavior
New-PnPSite -Type **CommunicationSite**
should allow us specify -Owners parameter. Similar toNew-PnPSite -Type **TeamSite** -Owners
Actual behavior
When using New-PnPSite -Type CommunicationSite , there is no way to specify an Owner.
Steps to reproduce behavior
Type
New-PnPSite -Type CommunicationSite
and then try to specify an OwnerWhich version of the PnP-PowerShell Cmdlets are you using?
What is the version of the Cmdlet module you are running?
3.13.1909.0
How did you install the PnP-PowerShell Cmdlets?