Skip to main content

Using sensitivity labels for self-service labelling & automation-driven governance

By: Mbulelo Nyosi

Implementing information protection doesn’t have to slow your organization down. Discover how sensitivity labels enable self-service data classification, drive accountability, and support automation-driven governance in Microsoft 365 without compromising usability or control.

28 March 2025

Implementing information protection in an organisation can be a daunting task. It requires a clear understanding of privacy, security, and usability concerns across the board, and this can often delay data security projects or, worse, frustrate user adoption.

Nedscaper recommends employing a proactive yet secure method of self-service labels, where they view the information protection sensitivity labels as more than just technology that runs it, but for the visual identification it provides and the ease with which it allows users to take accountability and drives a culture of good governance around sensitive information sharing. Sensitivity labels are best utilised when the organization understands them as a feature that is owned by the business, and supported and kept up-to-date by the IT Security Admins.

Sensitivity labels provide a visible indicator at both the file, email, and workspace levels, helping users recognize the sensitivity of the data they’re handling. Beyond classification, this fosters a culture of accountability and ensures security measures align with privacy and regulatory requirements.

Labels should be descriptive yet self-explanatory, reducing reliance on IT administrators for clarification. A well-structured and clear framework follows the recommended four-label approach for M365 files, emails, and containers:

  • Highly Confidential: Most critical information that should only be shared with named recipients.
  • Confidential: Information that is core to organizational goals in a need-to-know context.
  • General: Primarily internal communications and way of work, information we should keep within the organisation.
  • Public / Private*: (depending on use case) – this is information that has minimal to no impact on the business, and is used for public-focused communications.

In some cases, there’s a benefit of adding a “private” classification when users share their personal information, depending on fair usage.

These labels are not just names; they come with clear descriptions that support technological and compliance policy implementations, ensuring a consistent approach beyond security settings. Users understand what’s expected, and IT teams know exactly how to enforce the right security controls.

Sensitivity Labels don’t just protect individual files; they extend to workspaces like Teams and SharePoint sites, enabling:

  • Privacy levels that are clear and intuitive
  • External sharing policies that prevent unintended access
  • Guidance on when and how data can be shared outside the organization
  • Conditional access enforcement for identity and device security

With automated enforcement, sensitivity labels provide governance-by-default, enhancing compliance and security while keeping productivity intact.

To follow more of Mbulelo’s blogs, reach out to him on LinkedIn.

Stay updated with the latest news and insights.

 

Subscribe to our newsletter.

Relevant posts