Good job!

Hi Tony,

I managed to get it all working! 🙂

https://github.com/soundguy5566/assignSenLabel/blob/main/label

Let us know when you’ve figured things out… I might have another look at this the next time I get some time.

It appears that the assignSensitivityLabel API is now publicly available as a metered API.

https://learn.microsoft.com/en-us/graph/metered-api-setup?tabs=azurecloudshell

I’ve followed the guide and created the app registration. However, I haven’t quite figured out how to use the API to assign the sensitivity labels yet…

I had an open case with Microsoft, because SharePoint was not displaying the correct sensitivity information for some PDF files. After using the script, the sensitivity information was updated correctly.

I never went back to try the assignSensitivityLabel API. I grew tired of waiting for Microsoft to approve my app (they probably thought it wasn’t a serious app) and other things took precedence…

I’m trying the assignSensitivityLabel API. I enabled the metered API but I’m still getting the following error:
Error: 422, {“error”:{“code”:”notSupported”,”message”:”Sensitivity label cannot be assigned due to unsupported feature.”,”innerError”:{“code”:”unprocessableEntity”}}}

Did you have any luck testing this API?

A document can have multiple sensitivity labels assigned by multiple tenants if those labels do not enforce encryption. Once a label enforces encryption, it becomes the only one assigned to the document.

SharePoint does populate properties with label GUIDs. See https://office365itpros.com/2020/06/30/search-sharepoint-for-sensitivity-labels/

Do you know anything about this, and how robust it may be?

Am I also right in thinking there can be multiple sensitivity labels applied to a file, for example from different tenants? My understanding is the extractSensitivityLabel command produces an array of objects.

Did you look at the script? That’s exactly what it does…