Microsoft
Microsoft
Sesha_Mani Tony Themelis Thanks for the information. I have come across a problem when testing out the new container labels to Teams and SharePoint sites.
The issue arises as there is a common process to manage container and content labels. Any MIP labels you set up to specifically manage Teams sites to control guest access are visible when you apply labels to content e.g. on Work or Outlook.
For example for a client I was testing out two MIP labels to manage their content Public and Private. Public was a just a label with a footer and Private had encryption with a footer. These were added to a label policy where the default label was Private.
I then created two new labels to manage the guest access in Teams Internal and External. Internal would block guest access and External would allow guest access. I did not want to provide any controls to manage content. These two labels were created was under a separate label policy so I could set the default label to Internal.
When I created a new Team all was well as the Internal MIP label was set as default and I could only see the two options Internal and External.
However when I went to apply an MIP label in a Office Doc or Outlook when I selected the sensitivity icon I was presented with 4 labels, Public, Private , Internal & External. Internal & Externa had nor controls and were set up just to manage Teams guest access yet the users could inadvertently select the label Internal and think that the system would provide relevant controls on the content which it would not do,
It is possible to combine the labels sets and reduce to three :
This still increases the choices for an end user from 2 to 3 when labeling content and if the client already have existing labelling in place then this an additional change the client will need to make.
I have heard that Microsoft are looking to split content and container MIP labeling to mitigate this issue. Any ideas on timelines or any other advice we can use in the short term