Forum Discussion

Copper Contributor

Mar 26, 2019

Pnp provisoning issue with permissions for Everyone except external users

Basically, I've setup a Pnp powershell script that is triggered by a site design (site design/script -> flow -> azure queue -> azure function ...) to provision a newly created public Team site in my ...

Iron Contributor

Apr 25, 2019

Auren10 this is what I've been told by the escalation team regarding permissions reverting back from read to edit for "Everyone Except External Users" on public group site (which does not makes any sense to me):

Hello Martin,

I just had a discussion with Escalation Team and got to know that this is a known behavior globally. This has been confirmed that this is how a Public Group Site collection should work. In order to get this resolved we can follow either of the following step.

Remove the Members Group from Public Group Site collection

Rename the Members Group and then change the permission.

If we explicitly wants all users not to have EDIT permission then we can create new SPO Site Collection and make required changes.

Your patience is highly appreciated

Auren10

Copper Contributor

Apr 29, 2019

Martin-Coupal thanks for the reply !

I finally get to a similar solution but on a private team site:

Create a new group with the desired permissions (Read" permission in my case)
Add "Everyone Except External Users" on this group

For info:

Adding "Everyone Except External Users" in the "Visitors" group on a private site has a similar behavior as on public site. After some time "Everyone Except External Users" is removed from the "Visitors" group ...

Martin-Coupal
Iron Contributor
Apr 29, 2019
Auren10 , For private group site, this is a "By Design" behavior. Personnaly I think this is causing confusion as site owner are allowed to add EEEU and set the permission but a background process "play" with permission. IMO, this is not good.
https://support.microsoft.com/en-us/help/4492201/everyone-except-external-users-group-is-removed

But for public group site I never saw this was a "By design" behavior (And It would not make sense if it was). I'm still in discussion with Microsoft on this. I'm waiting for an answer. Apparently it's not happening on all tenants but surely other people are having the issue (on my side I have the problems with my customers tenants in Canada and my tenant in the US).