search

pnp / PnP-PowerShell

SharePoint PnP PowerShell CmdLets
https://pnp.github.io/powershell
Other
989 stars 663 forks source link

Set-PnPTenant -ShowEveryoneClaim or -ShowAllUsersClaim throws an "Unknown Error" #2191

Open michaelgalyon opened 5 years ago

michaelgalyon commented 5 years ago

Reporting an Issue or Missing Feature

Issue - I'm trying to add the "Everyone" or "All Authenticated Users" groups as options when granting permissions to our Development Tenant. However, the Set-PnPTenant (and Set-SPOTenant) gives me the following error when trying to change either of these options.

PS C:> Set-PnpTenant -ShowEveryoneClaim $true Set-PnpTenant : Unknown Error At line:1 char:1

Expected behavior

When I run this command, it should set the new value to the Tenant.

Actual behavior

See above error. NOTE: This error does not appear for the -ShowEveryoneExceptExternalUsersClaim parameter. I was able to change it to false and back to true without any issue. I am also running this code under the Global Administrator account.

Steps to reproduce behavior

Open a Powershell Window Use "Connect-PnPOnline" to connect to our Tenant (I tried this with both our top level site, and connecting to the Admin page, like with Connect-SPOService) Attempt to run "Set-PnpTenant -ShowEveryoneClaim $true"

Which version of the PnP-PowerShell Cmdlets are you using?

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

3.11.1907.0

How did you install the PnP-PowerShell Cmdlets?

ghost commented 5 years ago

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

michaelgalyon commented 5 years ago

This had something to do with the Global Admin account I was logging in with. Both of these commands work correctly when using a different Global Admin account.

I'm not sure what the difference between the accounts is yet (the one that failed is our service account and the working one was my regular user account granted the Global Admin role), but I'll update once I find out.

I still think this issue should be continued as a bug, but only so we get a not-completely-useless error message when it fails.

Tomikin commented 4 years ago

I've been getting the same issue, is there any further updating on thiss can you add the everyone commend using the PnP-PowerShell Cmdlet, I've played around with the global admin settings and can't seem to find a way to add it get the same error as the original user.

CSART69 commented 4 years ago

Same issue on my tenant. Any news ?

Tomikin commented 4 years ago

@CSART69 No feedback here, but my issue was around an application accessing the term set, so I was provide this https://www.techmikael.com/2018/08/modifying-terms-using-app-only-tokens.html by the vendor not the greatest result and dont know if it will work yet but its what Ive got

NEMA-IT commented 4 years ago

Has anyone found a solution for this error? I tried different Global Administrator accounts and still get the "Unknown Error".

robinmeure commented 4 years ago

Known issue and is dealt with at the moment