Microsoft Purview Encryption on Third Party Apps
Hello Community, I’m working with a desktop-based correspondence management system (CMS) application and would like to apply encryption to the documents that are being created, handled, or stored by this application. Specifically, I’m looking to use Microsoft Purview Information Protection to classify and encrypt these documents. Could someone please guide me on: The steps or best practices to integrate Microsoft Purview labels (with encryption) into a third-party or in-house desktop application? Whether Microsoft Purview SDK or API can be used in such scenarios, and if so, what the implementation flow looks like? Any prerequisites or limitations I should be aware of (e.g., licensing, file formats, offline handling)? How to ensure persistent encryption when files are exported from the application (e.g., to network drives or shared folders)?
Sharepoint IRM
I am trying to implement IRM on a sharepoint online site. I have enabled unified labelling on the azure portal as we have previously used the classic client. i have enabled Use the IRM service specified in your configuration, then Refresh your settings in the sharepoint admin portal about a week ago. However i am not able to view Information Rights Management under the permissions section as outlined by a few tech articles from Microsoft and other blogs. I have the relevant P1 ( Office 365) licenses assigned to my account. Also the library tab is missing on sharepoint online. Will be helpful if i can get this going and apply the RMS for this site.
Azure Information Protection labels being overrided
I recently implemented the Azure Information Protection P1 in my tennant. When I label a document as "Confidential - All Employees" it becomes available to all employees. If I share the document by rightclicking the document and using the "Azure information Protection" Client - and then I classify the Document as "Confidential - All Employees" - and check the "Protect with custom permissions" and choose an email from outside my organisation, it will then override that label and not allow Employees to open the document. Is this intended? Does the "Custom Permissions" override these labels on purpose, or is this a mistake on my part? Thanks in advanced.
