Conditional Access policies and encrypted documents
What do conditional access, guest users and information protection have in common? They might frustrate a user. So check this out.
Microsoft Purview and more
What do conditional access, guest users and information protection have in common? They might frustrate a user. So check this out.
How do the newly announced (preview) Azure AD Admin Units work with Microsoft Purview?
How do the newly announced (preview) Azure AD Admin Units work with Microsoft Purview?
How does a mandatory label act within the two different clients?
What if a sensitivity label is configured to expire access to the information? How does this work?
How to combine retention and sensitivity labels? Use auto-labeling.
Microsoft just released a newsletter on Microsoft Purview Information Protection. An important part of this newsletter was the use of the required client. In this blog I want to elaborate on this a bit more.
When people leave the organization, we mostly focus on their user-account in (Azure)AD, information stored in OneDrive and e-mails. But what if the user has been labeling and/or protecting documents using user-defined permissions?
User Defined Permissions for encrypting Office documents sometimes conflict with the OLE functions for embedding documents.
What’s the Authenticated Users setting in sensitivity labels and what does or doesn’t work?