[BUG] New-PnpSite with Managed Identity gives "Object reference not set to an instance of an object. " but still creates the Site

[CGrossNteam]

Reporting an Issue or Missing Feature

I'm using the "New-PnPSite" cmdlet inside of a Runbook, which is used with a Managed Identity.

The Managed Idetity has the following Permissions:

• Microsoft Graph [Directory.ReadWrite.All]
• Microsoft Graph [Team.Create]
• Microsoft Graph [Group.Create]
• Microsoft Graph [TeamMember.ReadWrite.Al]
• Office 365 SharePoint Online [Sites.FullControl.All]

I connect to the SharePoint Admin Site the following way:

$ConnectionAdminCenter = Connect-PnPOnline -Url "https://tenant-admin.sharepoint.com" -ManagedIdentity -ReturnConnection

And then use the "New-PnpSite" cmdlet this way:

New-PnPSite -Type TeamSite -Alias "Site-Alias" -Title "Site-Name" -Description "Description" -Owners "owner@tenant.com" -Lcid 1031 -Wait -Connection $ConnectionAdminCenter

When I try to create a "TeamSiteWithoutMicrosoft365Group" it works without issue.

Expected behavior

The Site will be created with the parameters given. After that the runbook will continue with what comes afterwards.

Actual behavior

The Site is created and after about 10 minutes the Runbook shows the Status "Error" and in the "Exceptions" Tab I see:

Object reference not set to an instance of an object. (Object reference not set to an instance of an object.)

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

I'm running Version 2.5.12-nightly of the PnP.Module.

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

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

[jackpoz]

Could you try passing -ErrorAction:Stop as additional parameter and then logging more exception details with Get-PnPException | Select-Object * ?

[CGrossNteam]

This is the Exception I'm getting:

Message : Object reference not set to an instance of an object. Stacktrace : at PnP.PowerShell.Commands.NewSite.ExecuteCmdlet() in D:\a\powershell\powershell\src\Commands\Admin\NewSite.cs:line 145 at PnP.PowerShell.Commands.Base.PnPConnectedCmdlet.ProcessRecord() in D:\a\powershell\powershell\src\Commands\Base\PnPConnectedCmdlet.cs:line 53 ScriptLineNumber : 160 InvocationInfo : System.Management.Automation.InvocationInfo Exception : System.NullReferenceException: Object reference not set to an instance of an object. at PnP.PowerShell.Commands.NewSite.ExecuteCmdlet() in D:\a\powershell\powershell\src\Commands\Admin\NewSite.cs:line 145 at PnP.PowerShell.Commands.Base.PnPConnectedCmdlet.ProcessRecord() in D:\a\powershell\powershell\src\Commands\Base\PnPConnectedCmdlet.cs:line 53 CorrelationId : 01de3aa1-7025-9000-74f1-529dedd7ac88 TimeStampUtc : 7/10/2024 8:23:19 AM

[jackpoz]

That shows that it's line

powershell/src/Commands/Admin/NewSite.cs

Line 145 in 15497cc

WriteObject(returnedContext.Url);

and it happens because something else went wrong during the creation, with returnedContext being null.
Do you know if the site was created ?

[CGrossNteam]

The site and the coresponding Group are being created.

I can navigate to it. The Owner is set.

But your comment brought me to a possible cause. The SharePoint is almost at its limit space wise. Could that cause the lead to the cmdlet not being able to find the URL after creation?