[BUG] Add-PnPTeamsTab doesnt work with ClientID and ClientSecret

[1nY0urF4c3]

Expected behavior

A powershellrunbook in Azure (Logic-Apps) creates tabs in a Team, using clientID and clientSecret.

Actual behavior

Error cause of lag of permissions for Graph API

Steps to reproduce behavior

Set app-permissions on two ways and start the automation.

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

Add-PnPTeamsTab

I have no idea, where the lag of permissions is comming from. Some ideas?

Best regards

[veronicageek]

@1nY0urF4c3 - On your last screenshot I can see you're using the old module (SharePointPnPPowerShellOnline) v.3.29.2101.0. This module is not maintained anymore.

Can you please try with the PnP PowerShell module (this repo) and try again.
https://pnp.github.io/powershell/articles/installation.html

[1nY0urF4c3]

@1nY0urF4c3 - On your last screenshot I can see you're using the old module (SharePointPnPPowerShellOnline) v.3.29.2101.0. This module is not maintained anymore.

Can you please try with the PnP PowerShell module (this repo) and try again. https://pnp.github.io/powershell/articles/installation.html

@veronicageek thank you for your feedback. I have now uploaded the current module to Azure. Attached is the screenshot. Unfortunately, a different error message now comes up, which refers to ACs.

[gautamdsheth]

@1nY0urF4c3 - this is by design.
This requires you to connect PnPOnline using either a global admin account or a clientid+certificate combination.

https://pnp.github.io/powershell/articles/authentication.html#setting-up-access

or

https://pnp.github.io/powershell/articles/connecting.html#connect-using-a-clientid-and-pfx-certificate-stored-on-your-local-machine

After that you will be able to add a teams tab.

Check the docs here:

https://pnp.github.io/powershell/cmdlets/Add-PnPTeamsTab.html

The permission required for that is Group.ReadWrite.All

Am converting this issue to a discussion since it is a configuration issue and not an issue with the library itself