New-PnPMicrosoft365Group - prefix / suffix

[stefwanders]

Hello everyone,

recently started to use the new PnP PowerShell module; mind you, I'm still pretty much a beginner in PowerShell. I do hope the question Im about to ask is allowed here; if not, my apologies!

I've been using the command New-PnPMicrosoft365Group to provide new Groups in our test Tenant, working like a charm. However, Im not using the command in our live environment which has a naming Policy in Azure, a prefix.

Now when I try to invoke the command it will give me back the statement: "Message: The property is missing a required prefix/suffix per your organization's Group naming requirements."

In the "old" PnP PowerShell this was never the case; we like to create Groups without the prefix in order to "distinguish" Groups created by personnel and the IT department (no prefix)

Is there a solution for this or a solution coming in future updates to force over the naming policy?

Many thanks in advance!

[stefwanders]

A little more background:

I've been doing a bit more research, and it seems that the following users are exempted from these policies:

• Global administrator (my current role)
• User administrator

However, the way I connect to PnPOnline has changed;
Previous method Connect-PnPOnline -Scopes "Group.ReadWrite.All" -SPOManagementShell
(Doesn't work anymore with new PnPPowerShell version

Current method Connect-PnPOnline -Url $targetURL -ClientId $ClientID -Tenant $Tenant -CertificatePath $Certificate
This connects with an App, and now I understand, that an App is neither User administrator or User administrator, thus it falls under the policy.

Maybe someone has an idea on how to differently connect to PnPOnline?

Possible workaround
A Possible workaround would be to disable the naming Policy in Azure while the script is running and turning it back on when the script has finished. However, we have a rather big organisation where a lot of groups are made; so I really don't wish Groups to created without the prefix.

(more information here: https://docs.microsoft.com/en-us/azure/active-directory/enterprise-users/groups-naming-policy?WT.mc_id=Portal-Microsoft_AAD_IAM

Help is appreciated, I feel a little stuck here ;)

[stefwanders]

Using the new "Interactive" signin method seems to fix the problem ;) Always good to read other topics as well!

Yet to be tested, but for those that are interested, I'll let you know the results.