Sensitivity labeling now built into Office apps for Windows to help protect sensitive information

I use sensitivity labels on a number of set of documents and run into a number of issues.

• I just had a document with custom sensitivity protections to 187 users.  After about 160 I got an error message that the rms sizedefinitions was too large and no suggestion how to fix.  I'm guessing this relates to the number of users but I have had another label with 200 users.  (Diagnostic information: {Version:17.00.7971.004,Environment:CUSPROD,DeploymentId:326b150198174bdf98ef8cad64c99971,InstanceId:WebRole_IN_5,SID:4e9c8e21-5052-41b0-831e-c007982cc9bf,CID:1955a250-e9e1-4bd3-a740-8599ecd21fce} Time: Tue, 15 Feb 2022 18:50:58 GMT)
• I have old sensitivity labels that are no longer in use.  It sounds like if I delete the label, the document is unprotected.  Is there a way to archive them so that the list is shorter?
• When adding a number of users authorized for a label, is there a way to bulk load?

Overall, the labels have worked but have been clunky.  The older format/interface under Azure was easier, I thought, to create a label & add users, but more cumbersome to publish labels.  

Any help on those questions would be greatly appreciated.  Particularly, I am stuck on the RMS error and can't complete the label. 

Thank you!

What is exactly applied from existing labels? I mean, we are underway to implement the UL client and have some labels and policies defined and assigned to a few pilot user groups. Now other people are in the process of the Office upgrade (version 2002 or newer) and find the new labels, although they are not member of any of the pilot groups for our information protection pilot. Hence, I wasn't expecting them to see any labels.

Also, what is the MS strategy/roadmap. Should we focus on the built-in client, or stay with the UL client? To me the UL client is more feature rich, especially when using powershell to manage labels and policies. And we already moved from AIP to UL client, should we now prepare for another switch? Seems like this project will never end, because we can't keep up with the changes...

Mike Paer thanks so much For the quick response! That’s exactly the info I needed. 🙂

JeffJubach yes, 1910 was the first version to introduce the Sensitivity button in the Office applications on Windows. This document explains the minimum versions for each sensitivity labeling capability on each platform.

I don't see a version listed in the article. What Office version was this where we can see the Sensitivity button? 1910 or thereabouts?

For me the sensitivity part is missing from all desktop applications. It show up online though, but not on desktop (windows). Any ideas what might cause this? I tried installing O365 again, but that did not do the trick.

I've created several Sensitivity Labels and marked them as requiring justification to send to untrusted domains.

Now I want to define the domains which ARE trusted and so bypass the justification prompt using Set-LabelPolicy -Identity "Global" -AdvancedSettings @{OutlookJustifyTrustedDomains=" ..."}

Does this option imply subdomains are also trusted? In other words would -

Set-LabelPolicy -Identity "Global" -AdvancedSettings @{OutlookJustifyTrustedDomains="contoso.com"}

mean that emails to sales.contoso.com, finance.contoso.com etc. would NOT generate a justification prompt?

Fantastic news, highly anticipated change, hopefully soon it will come out of the beta stage and we could use it in all Office apps on all platforms without to use any clients or agents. I'm an agentless admin, I don't do clients, agents, things that need to be installed via GPO or sitting in the tray and crashing or need to be signed in to work properly.

Thijs Lecomte I believe UL client takes priority. I've just tested it on my devices and I needed to disable AIP add-in in Office desktop apps, (one by one... unfortunately, or you can do it via policies of course) and after reopening, the sensitivity button showed up again but now it's located after "Dictate". Android labels are showing up properly, Office web apps don't work yet 😞 I've noticed that in desktop apps the policy tips are not showing? Or is it only me?

Thijs Lecomte The Azure Information Protection unified labeling client can't run at the same time as the built-in labeling experience. More info at the bottom of this article. Scroll down to:

Will the built-in Sensitivity feature run alongside the Azure Information Protection client in Office for Windows?

No. The built-in Sensitivity feature is turned off if the Azure Information Protection client is loaded in Office for Windows. If you have the Azure Information Protection client installed, but you want to use the built-in Sensitivity feature instead, you can: