![]() They also don't like the idea of copying the document and changing the label on that copy to send it in email.įrom what I can tell, option two will only work for external users who also use Office/Microsoft 365 which may present an issue for some of our partners who may not use Office.Īre there any other options we are missing? Are the concerns raised about option one unfounded? How do your organizations navigate this scenario? I'm getting pushback from stake holders on option number one because they would prefer that documents remain encrypted at rest, so they don't like the idea of changing the document's label to one that does not include encryption. ![]() ![]() Work with the content owner to determine which external users need this access, add those users as "Guests" in Azure AD, and add them to that group. Set up a label that includes permissions for a group of external users to be able to co-author the document. Any ideas on the best way to accomplish this?įrom my reading, it looks like there are two options:Ĭhange the label of the document to a label that removes encryption, then share the document with the external users in an encrypted email. I'm implementing Azure Information Protection (AIP) in my company's Office365 deployment and I have a sticking point about how to maintain encryption on documents that are labeled with a label that enables encryption, but still may need to be shared with external vendors/partners for collaboration or information sharing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |