Learn how to use the robot
Prevent guest access to Teams with SProbot
Why prevent external access to Teams?
In some instances, Teams and SharePoint team sites may contain information that is very definitely only intended for internal use. To limit data loss and accidental oversharing, Microsoft 365 governance best practice is to prevent team owners and members from adding external users (outside the organizational tenant).
What is needed to prevent external access?
Two configuration settings in tandem achieve the lockdown state described above:
- The AllowToAddGuests setting on Microsoft 365 groups
- The External Sharing setting on a SharePoint site
SProbot enables you to automate the enforcement of these settings to specific Teams and SharePoint sites by enabling a rule to be configured on a pipeline, and then automatically applying it to all workspaces requested via the pipeline.
Define the setting
In the Governance Rules step of a pipeline, use the Prevent guest access checkbox to enable lockdown.
It is important to remember that this setting is in fact two separate settings, one applied to the Microsoft 365 group, the other to the associated team site. This means that it effects both Teams and SharePoint, so serves as an overarching lockdown for both the Teams app and its Files (which reside in SharePoint). Group/site owners cannot change this setting without administrator assistance, so if in future a specific team should not be locked down anymore, both the group and site settings will need to be manually updated.
Learn how to disable standard Team and SharePoint site creation for end-users when switching to request and creation with pipelines.
Use the default sharing settings feature in SProbot to prevent Microsoft 365 group owners and members from accidentally sharing sensitive information.
Use the guest access lockdown feature in SProbot pipelines to prevent external users from being added to teams.