Previously I provided instructions on how to create a sensitivity label scoped to your sites and groups. In this short post, I’ll demonstrate how one apply sensitivity labels to sites, Groups, and Teams in Microsoft 365. I’ll present the before and after effects that applying the sensitivity label has on your sites. I’ll also show you how site sensitivity labels can help ensure content that isn’t supposed to be within the site is flagged automatically for you.
To test the ability of sensitivity labels to affect change within these platforms, I created a new modern SharePoint Site and a new Microsoft Team. Both were set to public (allowing anyone to have access), and both were set to allow guest access. You can see in the following screenshots how users outside the organization can access the site and Team.
- The site is wide open to the org:
- Adding guests to the site:
- Guest added to the site:
- Guest receiving email and able to access the site:
- Adding guests to the team:
- Guest receiving email and able to access the team:
Apply Sensitivity Labels to Sites, Groups, and Teams
Applying sensitivity labels to sites, Groups, and Teams is pretty straight forward actually. The process is very similar between the different locations.
- Click on the site settings cog and then click “Site information.“
- On the site information blade, select the desired sensitivity for the site.
- Click Save
Important: Any existing guests will still have access after the label is applied. Any future guests cannot be added:
- Click on the Team’s ellipsis in the selection pane and click on “Edit Team.”
- Set the desired sensitivity label. Notice in the example below that the team is changed from Public to Private.
- Click Save.
Important: Any existing guests will still have access after the label is applied. Any future guests cannot be added.
One last item you should be well aware of. A site sensitivity label will not apply a default label to your content. It can, however, let you know when content that is too sensitive is added to your site. I’ll discuss that in my next post.
Thanks for reading!