Purview Foundation

A label and retention model users actually follow, built on Microsoft Purview.

Information protection that exists only on paper protects nothing. In 3 to 6 weeks, CloudWay designs a pragmatic sensitivity label and retention taxonomy for Microsoft 365, configures the baseline Microsoft Purview policies to match, and plans the rollout, so classification works for users as well as auditors.

Organisations with the foundation in place typically continue with our Data Lifecycle & Records Implementation.

The challenge

In most organisations, information protection exists on paper but not in practice. Users do not know which label to apply, retention rules do not match how teams actually work, and every mismatch generates another policy exception. A classification model that users cannot apply is not protection; it is documentation.

Policies exist on paper

Rules may be documented, but not easy for users to apply in daily work.

Unclear labelling

Users may not know which labels or retention rules apply to different content.

Controls do not fit

Protection and retention controls may not match real business scenarios.

What we do

CloudWay builds a Purview foundation that works for both users and auditors. We review how your teams handle sensitive content, design a pragmatic label and retention taxonomy with as few labels as the business can defend, and configure the baseline Purview policies to match. We finish with a rollout plan and a lightweight change governance process, so the model survives contact with real users. A working classification foundation is also the prerequisite for deploying Microsoft 365 Copilot safely, since Copilot surfaces whatever your permissions and labels allow.

Step 1

Understand scenarios

Review how teams handle sensitive content and where retention rules apply.

Step 2

Design the taxonomy

Define practical labels and retention rules that users can understand.

Step 3

Configure baseline controls

Set up core Microsoft Purview policies aligned to the agreed model.

Step 4

Plan adoption and governance

Create a rollout and change governance plan the business can defend.

You get

Typical outcomes

Label/retention taxonomy

You get a label and retention taxonomy designed around your real content scenarios, small enough that users apply it correctly.

Policies adopted in initial scope

Labels and controls are in real use in the initial scope, not just published.

Baseline policies and configuration

You get baseline Purview policies configured to match the taxonomy, live in your tenant.

Fewer exceptions

Controls fit how teams actually work, which cuts the stream of policy exceptions.

Rollout plan

You get a rollout plan that takes the model from pilot group to the whole organisation at a pace users can absorb.

Clearer ownership

Every policy and label has a named owner.

Change governance

You get a lightweight change governance process, so the model survives new requirements and exceptions.

Ideal for

Teams unsure what to label

For organisations with unclear labels, retention rules, or classification models.

Sensitive content handled differently

For teams applying protection and retention differently across Microsoft 365.

Too many policy exceptions

For leaders managing exceptions, ownership gaps, and governance risk.

Why CloudWay

CloudWay AS is a Norwegian Microsoft consultancy working across Europe, and its governance work is done with your people, not for them: controls are built together and documented in runbooks, so they stay effective and auditable long after the engagement ends. The team includes seven Microsoft MVPs; the customer stories page shows what that looks like in practice.

Ready to improve how your teams work?

Start with a focused workshop to identify priorities and align your organisation.