Unable to provision a Communication site using New-PnPSite cmdlet

[BrookZion]

Is the issue related to the cmdlet itself, its parameters, the syntax, or do you suspect it is the code of the cmdlet that is causing the issue? Then please continue reporting the issue in this repo.**
I suspect the cmdlet is not designed to support multiple vanity domains.

Reporting an Issue or Missing Feature

     I am unable to provision a communication site using New-PnPSite cmdlet

Expected behavior

       I should be able to create a communication site 

Actual behavior

Error message

Steps to reproduce behavior

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

• [ ] PnP PowerShell for SharePoint 2013
• [ ] PnP PowerShell for SharePoint 2016
• [x] PnP PowerShell for SharePoint Online

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

       3.12.1908.1

How did you install the PnP-PowerShell Cmdlets?

• [ ] MSI Installed downloaded from GitHub
• [x] Installed through the PowerShell Gallery with Install-Module
• [ ] Other means

[ghost]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[Sup3rlativ3]

When I've had this issue in the past it has been because I was using the admin url instead of the normal url. I've just tested with your example and it works for me.

https://i.imgur.com/0EI8EO1.png

admin url example: https://TenantName-admin.sharepoint.com/Sites/MySiteName

correct url example: https://TenantName.sharepoint.com/Sites/MySiteName

[BrookZion]

@Sup3rlativ3 I can provision a communication site using the default web app, the problem is when i try to create the site using the other web app. Fyi- The environment is configured to use multiple Vanity domains (not "standard" SPO tenant).

[Sup3rlativ3]

The only other thought I have before (if) the ticket gets triaged is that you're not trying to run the cmdlet in pscore (version 6/7). I've found that while it installs okay, there are many things broken due to .net vs .net core.