{"id":73421,"date":"2026-08-05T22:34:51","date_gmt":"2026-08-05T20:34:51","guid":{"rendered":"http:\/\/adiumento.local\/?page_id=73421"},"modified":"2026-08-05T22:34:51","modified_gmt":"2026-08-05T20:34:51","slug":"datenklassifizierung-microsoft-purview","status":"publish","type":"page","link":"https:\/\/adiumento.de\/en\/themen\/regulatorik-sicher-umsetzen\/datenschutz-informationsschutz\/datenklassifizierung-microsoft-purview\/","title":{"rendered":"Data classification and Microsoft Purview"},"content":{"rendered":"
\"Datenschutz<\/span>

\u2190 Data protection & information protection<\/a><\/p>

Data classification and Microsoft Purview<\/h1>

Translate protection needs into understandable rules, labels, protection controls and retention.<\/strong><\/p><\/div><\/div>\n\n\n\n

Data classification begins with a technically responsible model for protection needs and permitted use. Microsoft Purview can technically support this model with sensitivity labels, data loss prevention (DLP), and retention features. The sensible order is: understand data and risks, define classes and rules, publish labels, use DLP in a targeted manner and control retention for each specialist process. Purview is not GDPR compliant.<\/p>\n<\/div>\n\n\n

Relationship to services and technologies<\/h2>\n\n
\"Datenschutz<\/figure>
\n

Microsoft Purview is a possible means of implementing a previously defined protection requirement. Product features, licensing and implementation services are below Technologies<\/a> and Solutions<\/a> described.<\/p>\n<\/div><\/div>\n\n\n<\/div>\n\n\n

Background<\/h2>\n\n

In Microsoft 365, information is often distributed across Exchange, Teams, SharePoint and OneDrive. Without a common classification model, employees are left to their own devices when it comes to approvals, protection rules are inconsistent and sensitive data may be shared too widely. Conversely, too many or unclear label levels create acceptance problems and incorrect assignments.<\/p>\n\n\n\n

The task is therefore primarily governance, not product configuration: departments, data protection, information security and IT must determine which information should be treated, shared, retained and deleted and how. Only then can Purview map rules consistently in the supported workloads.<\/p>\n<\/div>\n\n\n

Technical context<\/h2>\n\n
\"Abstrakte<\/figure>
\n

Classification describes the need for protection of information. Sensitivity labels identify content and, depending on configuration, can apply protective measures such as encryption or content tagging. Retention labels and retention policies, on the other hand, control retention or deletion. Records Management serves the professionally regulated, particularly controlled management of records. A piece of content can have a sensitivity label and a retention label; the purposes remain separate.<\/p>\n<\/div><\/div>\n\n\n\n

DLP policies are intended to identify and address unwanted distribution or use based on defined conditions; they are neither classification nor preservation. Sensitivity labels can be a DLP condition in supported scenarios. However, supported workloads, file types, functions and license requirements differ depending on the tenant status and Microsoft documentation and must be checked for the specific scenario before rollout.<\/p>\n<\/div>\n\n\n

What companies need to clarify specifically<\/h2>\n\n