SharePoint powers content collaboration in Office 365. At work, it is important for every team member to streamline efforts and stay on the same page. Group-connected SharePoint team sites provide a ...
Updated Jun 07, 2018
Version 2.0
Blog Post
5 MIN READ
Modernize your SharePoint team sites by connecting them to new Office 365 groups
Hi,
I know a lot of customers who have O365 Groups and heavily use the sharepoint site and are not using MS Teams, they want to control access to the MS planner / mailbox (hence a private a O365 group) but they would like to give the organisation read access in general to the whole sharepoint site. What used to be a simple case of adding "everyone but external" in the visitor group now is no longer the case and MS have a batch job that removes it!? Ive tested this and yes its removed as per the KB article https://support.microsoft.com/en-us/help/4492201/everyone-except-external-users-group-is-removed
Q1. Id like to know the rationale behind this decision? Why was it done?
Q2. It would have been better if this was configurable at tenant or even better at the Group setting i.e. do you want to allow the everyone except external in the SP visitor group for the private O365 Group (or something a bit shorter and succinct!)
Q2. It would have been better if this was configurable at tenant or even better at the Group setting i.e. do you want to allow the everyone except external in the SP visitor group for the private O365 Group (or something a bit shorter and succinct!)
I now have to either create a new security group that mimics the "everyone but external" in Azure AD, or create a new SP visitor group with visitor permissions and hope the MS batch job doesn't scan my custom group, and then do this for every new / existing O365 Group Sharepoint site... It is hard enough to keep up with all the changes and explain these things to simply to clients and now even i struggle to explain this decision