Erwin van Hunen

The issue is most likely connected to the registration of the PnP Management Shell application that is in place in your Azure AD. Run `Register-PnPManagementShellApplication` again, it will change the...

I just tested and indeed it doesn't work with a bearer token (which is what we use by default). It seems that that is not (more?) supported. We'll investigate that....

To give you an update: this is not an issue with PnP PowerShell but has to do with how SharePoint Online handles authorization. We provided Microsoft with this feedback and...

@waaromikniet : for my understanding: do you have legacy auth set to false in your tenant settings? If so, PnP PowerShell will use the PnP Management Shell multi-tenant application (if...

@waaromikniet You can find the setting by executing Get-SPOTenant or Get-PnPTenant. The setting is called `LegacyAuthProtocolsEnabled`. If set to false it means you're not using classic auth anymore and we...

Added info: setting LegacyAuthProtocolsEnabled to true or false is not instant. That can take a few hours.

right... okay, so for pure auth, PnP PowerShell will use the legacy auth (SharePointOnlineCredentials) option then. I will check what's exactly happening in the engine when it comes to the...

Have you tried the Connect-PnPOnline -PnPManagementShell -Url option? It will go through the consent flow and add the enterprise app to your AD. You can, after you have consented and...

Right. So a change has happened that require this consent to be in place. I'll take it up with the team.

We have identified the issue and have just merged a solution. We are discussing internally if we should release an intermediate build.