One of the most distinct features of Purview is of course sensitivity labeling, which is part of the information protection section in the Purview portal. Before we head off to configuring sensitivity labeling and dive into what it looks like from a users perspective, let’s first talk about what sensitivity labels are.

Introduction

You can think of a sensitivity label like a stamp, which you can apply to content like documents, email and meetings. The cool thing is that the sensitivity label is added in clear text to the metadata of the files, so it travels together with the content (hence the reference to the stamp 😉). Because it’s stored in clear text, applications and services can use the sensitivity label to apply logic to it. Examples of this logic is adding a watermark to a document, protecting content from being openend by unauthorized people or content being protected from being sent outside your organization. This protection part can be done by Microsoft 365 or a third-party application. But a sensitivity label by itself can inform users of the sensitivity level of a certain item.

There are various automatic methods of applying labels to your content, but for this article we’ll focus on manually adding labels to content so we understand how the basic process works before we move on to some form of automatic labeling.

Continue reading “Microsoft Purview 101: How To Implement Sensitivity Labels” →

Records Management in Microsoft Purview can be used to:

• Setup a retention schedule for your files or folders (Just as with Purview Data Lifecycle Management)
• Mark items such as Word, Excel or Powerpoint files as records.

When an item such as a file or folder becomes a record, the item or it’s contents cannot be changed any more. This is often done to comply with legal requirements, such as those that require a certain company to retain their documents for a certain period of time and during that time, the files (that have become records) cannot be altered by anyone. This article will explain how to configure the basics of Records Management, and will show you the end-user experience.

Differences between Records Management (RM) and Data Lifecycle Management (DLM)

Let’s start by looking at the differences between Data Lifecycle Management and Records Management.

Continue reading “Microsoft Purview 101: How to Setup Records Management” →

In the previous post I talked about retention policies and how you can apply them to your environment. To keep things simple, I used static scopes in that article. But since adaptive scopes are the recommended approach for retention policies I want to show you what they can do, and why Microsoft recommends them to be used instead of static scopes.

Continue reading “Microsoft Purview 101: Using Adaptive Scopes” →

One of the core features of Microsoft Purview is Data Lifecycle Management (DLM), formerly known as Microsoft Information Governance. DLM is all about providing you with the tools you need to keep information that you need, and delete the information that you don’t. This process is of great importance for compliance with regulations, risk management en liability management.

Data Lifecycle Management in Microsoft Purview has a great overlap with Records Management, although they also have their differences. However this is something for another article. This article will explain how to configure the basics of Data Lifecycle Management, and will show you the end-user experience.

Continue reading “Microsoft Purview 101: Data Lifecycle Management (DLM)” →