Unable to create Communication site via PnP PowerShell

[mag210]

Reporting an Issue or Missing Feature

When trying to create a new communication site via PnP Powershell I receive an error noting that the site url is blank. I include the error below under actual behaviour. Note this always use to work and I have not changed any of my code. I include a code sample below. Interestingly, we have a dev tenancy and the same command ran against this tenancy does work as expected. The issue appears to be confined to our production tenancy: uob.sharepoint.com. However, to my knowledge nothing has changed which could results in this error. We have checked with multiple Global admin accounts on different machines and with services running on Azure. In all cases we get the below error when attempting to create sites in the Production tenancy. Has anyone come across this before?

-Max

Expected behavior

Communication site created and url returned.

Actual behavior

Following error:
New-PnPSite : {"d":{"Create":{"__metadata":{"type":"SP.Publishing.CommunicationSiteCreationResponse"},"SiteStatus":3,"SiteUrl":""}}}

Steps to reproduce behavior

$title = "Sandpit site"
$descritpion = "test"
$classification = "Confidential"
$site_url = "https://uob.sharepoint.com/sites/uob-sandpit4"

$communicationSiteUrl = New-PnPSite -Type CommunicationSite -Title $title -Description $description -Url $site_url -Classification $classification -SiteDesign Topic

Which version of the PnP-PowerShell Cmdlets are you using?

• PnP PowerShell for SharePoint Online

What is the version of the Cmdlet module you are running?

2.24.18

How did you install the PnP-PowerShell Cmdlets?

• Installed through the PowerShell Gallery with Install-Module

[FitzDbA]

$descritpion = "test"
description is not well typed so it can´t be used?

[andreasblueher]

Hey,
I'm running into the same SiteStatus 3 error message, when trying to use New-PnPSite. For me it happens during deploy.ps1 of sp-starter-kit. I've installed pnp PowerShell using the standalone installer.

[andreasblueher]

@mag210 can you confirm that this issue appeared for an url you have used before and deleted the site to recreate it? This seems to be related to it.

[mag210]

Hi all, I raised this ticket with Microsoft Support and apparently the issue was down to a Microsoft problem which effected the creation of site collections on certain tenancies. This has now been resolved in my tenancy and my PnP provisioning engine is now working correctly.

[timcreancu]

@mag210 - I think we are experiencing the same issue. Do you have a Microsoft case # we can reference on that tenant setting to allow site collection provisioning?