From bold-on to build-in
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.
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?
What’s the Authenticated Users setting in sensitivity labels and what does or doesn’t work?
DId you know that there’s some advanced CA configurations possible for accessing SharePoint Online/OneDrive for Business? Now you do 😉
Microsoft has released some great new and build-in sensitive information types or SIT’s. And these are directly related to privacy sensitive information.
Co-authoring and autosave for encrypted documents are great enhancements for Microsoft Information Protection. But what’s this about metadata changes? In this blog I try to find out.
What’s the Authenticated Users setting in sensitivity labels and what does or doesn’t work?