Back to Blog

    SharePoint

    How do you set up sensitivity labels for SharePoint?

    What sensitivity labels control for files and sites, how to publish them through policies, and how to test auto-labelling and Copilot.

    February 13, 20262 min read
    Joël Kuhn

    Joël Kuhn

    Solution Engineer

    joel.kuhn@cnext.ch
    CNEXT SharePoint
    In this article

    Microsoft Purview sensitivity labels can classify content and, when configured accordingly, apply protection such as encryption, usage rights or markings. Their actual effect depends on scope, published policy, supported apps, permissions and the protection options chosen.

    Files and sites are different scopes

    File labels can, for example, control markings or access protection. With encryption, administrators determine who can open content and which actions they may perform. A SharePoint site or Microsoft 365 group can receive a container label that affects selected site or group settings such as external sharing. These container settings are not the same as encrypting an individual document.

    First define a taxonomy that fits your types of information and your workflows. The names and number of levels, such as “Internal” or “Confidential”, are for your organisation to decide. Create labels with the required scope, configure protection options and publish them through label policies to the right people. Automatic labelling requires its own policies and supported file types; validate it with a simulation and representative data.

    Test Copilot and access rights

    Microsoft 365 Copilot accesses content according to existing permissions; sensitivity labels do not replace a permission review or the clean-up of overly broad sharing. Microsoft documents label inheritance from referenced content for certain Copilot experiences. Which rules apply depends on the surface and the scenario. Test with ordinary user accounts, approved sample files and the specific Copilot features in your tenant.

    Swiss data protection law requires appropriate technical and organisational security measures. Whether a configuration meets this duty in a given case depends on, among other things, the personal data processed, the risks, access and complementary controls. Have your data protection and security officers make this assessment; a product label alone does not demonstrate compliance with the Swiss Federal Act on Data Protection (FADP).

    Sources: Microsoft: Create and publish sensitivity labels, Microsoft: Labels for groups and sites, Microsoft: Labels and Copilot data protection, Swiss FDPIC: Information security.

    SharePointMicrosoft PurviewComplianceDatenschutzSchweiz
    Teilen:

    AI tools may have supported the creation of this article. CNEXT is responsible for the published content. Product features and prices can change; check the linked primary sources for current details.

    Joël Kuhn

    Joël Kuhn

    Solution Engineer

    Discuss a labelling concept

    We develop a label taxonomy with you and test it before rollout.