Comments on: PnP PowerShell Changes Its Entra ID App

By: Auke P

Auke P — Wed, 11 Sep 2024 14:55:29 +0000

we discovered
firstly :: david.a was right “After using a non-corporative workstation (no Intune, no vpn, no corporate AV…), i was able to register the app successfully. Just in the case, someone else has a similar issue.. Thanks.”
secondly :: using the -SkipCertCreation in Register-PnPEntraIDApp also did the job on a corporate machine (so creating a certificate seems to be the issue)

By: R

Tue, 10 Sep 2024 11:56:32 +0000

you’ll need to do this as well:
https://learn.microsoft.com/en-us/sharepoint/dev/solution-guidance/security-apponly-azureacs

By: neogeonz

neogeonz — Tue, 10 Sep 2024 00:24:08 +0000

In reply to David A..

I am having the same problem. I am running: Register-PnPAzureADApp -ApplicationName “PnP PowerShell App” -Tenant {tenant-name}.onmicrosoft.com -Interactive – and am getting the error: Register-PnPAzureADApp: {“error”:{“code”:”Request_BadRequest”,”message”:”A null value was found with the expected type ‘Edm.String[Nullable=False]’. The expected type ‘Edm.String[Nullable=False]’ does not allow null values.”,”innerError”:{“date”:”2024-09-10T00:21:51″,”request-id”:”0d72d114-3c23-41ee-ae44-2eb610ed5d5b”,”client-request-id”:”0d72d114-3c23-41ee-ae44-2eb610ed5d5b”}}}

By: Tony Redmond

Tony Redmond — Mon, 02 Sep 2024 09:04:57 +0000

In reply to Harsh Damania. I don't think so, but you should test this on a trial tenant.

By: Harsh Damania

Harsh Damania — Mon, 02 Sep 2024 08:19:47 +0000

any automation done using app registration having appropriate SharePoint permission , uisng client id and certificate will not be impacted right ?

By: David A.

David A. — Fri, 30 Aug 2024 11:52:24 +0000

After using a non-corporative workstation (no Intune, no vpn, no corporate AV…), i was able to register the app successfully. Just in the case, someone else has a similar issue.. Thanks.

By: Tony Redmond

Tony Redmond — Fri, 30 Aug 2024 07:26:41 +0000

In reply to David A.. I used PS 7.4.5 signed into a GA account and everything worked without a problem. Creating the app and consenting to permissions needs at least the Entra ID Application Administrator role and I was unsure about what else might be required, so I fired on all cylinders...

By: David A.

David A. — Fri, 30 Aug 2024 07:05:32 +0000

In reply to Tony Redmond. Yes, I'm running Powershell 7.4.5 (also tried with 7.4.4 in a different machine) as Administrator, with a Global Administrator user. I will try with a colleague's global account, just in the case there is an issue with mine.

By: Tony Redmond

Tony Redmond — Thu, 29 Aug 2024 17:54:53 +0000

In reply to David A.. Are you signed into PowerShell as an administrator (run as administrator). That might make a difference...

By: David A.

David A. — Thu, 29 Aug 2024 17:45:40 +0000

Hi, just trying to use the cmdlet Register-PnPEntraIDAppForInteractiveLogin to create the interactive alternative to the current PnP, something like

Register-PnPEntraIDAppForInteractiveLogin -ApplicationName “New PnP Interactive” -Tenant [….].onmicrosoft.com -Interactive

but the cmdlet is not registering nothing. Nothing happens beyond the warning. Using PowerShell 7.4.5 and PnP 2.10.0
Just wondering if it is an issue with my workstation.., because Register-PnPEntraIDApp also fails in the same point:

WARNING:
No permissions specified, using default permissions