[BUG] New-PnPMicrosoft365Group Throws Error in PreRelease 1.11.74

[Studermarc]

Reporting an Issue or Missing Feature

New-PnPMicrosoft365Group Cmdlet fails in the new PreRelease with -ErrorAction = "Stop"

Expected behavior

A new Microsoft 365 Group is created

Actual behavior

An Error is thrown

Looking at the codebase, the Error gets thrown when it first checks, if a Microsoft 365 Group with the same alias exists (because none is found, which is to be excepted):

• when executing this line:

  powershell/src/Commands/Microsoft365Groups/NewMicrosoft365Group.cs

  Line 86 in 5dad6d2

  var candidate = Microsoft365GroupsUtility.GetGroupAsync(Connection, MailNickname, AccessToken, false, false).GetAwaiter().GetResult();

• which executes this method:

  powershell/src/Commands/Utilities/Microsoft365GroupsUtility.cs

  Line 118 in 5dad6d2

  internal static async Task<Microsoft365Group> GetGroupAsync(PnPConnection connection, string displayName, string accessToken, bool includeSiteUrl, bool includeOwners)

I believe the error thrown when no teams is found should be suppressed, as we actually check for its non-existance, and not the oposite:

powershell/src/Commands/Microsoft365Groups/NewMicrosoft365Group.cs

Line 86 in 5dad6d2

var candidate = Microsoft365GroupsUtility.GetGroupAsync(Connection, MailNickname, AccessToken, false, false).GetAwaiter().GetResult();

The Error is thrown due to the changes made to the Error Handling Behaviour: #2288 (comment)

Steps to reproduce behavior

1. Run the following Code

New-PnPMicrosoft365Group -DisplayName "TestNewGroup" -Description "TestNewGroup" -MailNickname "TestNewGroup" -Connection $AdminConnection

2. Observe the Error:

New-PnPMicrosoft365Group: No Microsoft 365 group found with id, display name or mail nickname 'TestNewGroup'

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

1.11.74

Which operating system/environment are you running PnP PowerShell on?

• Windows
• Linux
• MacOS
• Azure Cloud Shell
• Azure Functions
• Other : please specify

[gautamdsheth]

Hi @Studermarc , good catch.
Have managed to fix it. The fix will be available in tomorrow's nightly.

Please let me know if the issue still persists.

[Studermarc]

Awesome many thanks 👍