'/%3E%3Cpath%20fill='%23b2b2b2'%20d='M241%20382q0%2016%2017%2026%2017%2011%2042%2011t42-11q16-11%2017-26V269H241'/%3E%3Cpath%20fill='%239f7e00'%20d='M241%20379q0%2014%208%2023%209%209%2021%209%2014%200%2021-9%209-9%209-23V269h-59'/%3E%3Cpath%20d='M241%20339v-70h59v110q0%2014-9%2023l-6%205v-68h-15v72q-8%200-14-4v-68zm59%2040c0%2022%2015%2032%2029%2032%2021%200%2030-18%2030-32v-40h-59'/%3E%3Cpath%20fill='%239f7e00'%20d='M266%20277v5h2v12h-3v-5h2v-5h-9v5h2v5h-4v9h3v18h-5v10h34v-10h-5v-18h3v-9h-4v-5h2v-5h-9v5h2v5h-3v-12h2v-5zm42%20101q0%2010%206%2017%206%206%2015%207%2010-1%2016-7%206-7%206-17v-29h-43'/%3E%3Ccircle%20fill='%230044ad'%20cx='329.5'%20cy='372'%20r='6'/%3E%3Cellipse%20fill='%230044ad'%20cx='300'%20cy='340'%20rx='16'%20ry='21'/%3E%3C/svg%3E){kind=small}
Microsoft Purview and information protection
We design and implement classification, sensitivity labels, DLP and retention with Microsoft Purview, based on your organization’s information and requirements.
Protection rules that fit your information
A sales proposal, a contract and an internal case file may need different access and retention conditions. Implementation starts by identifying those requirements and agreeing who makes decisions for each information type.
MSAdvance turns the agreed model into Microsoft Purview configurations. We prepare the labels and policies included in the project and test them with representative documents and users. Information owners help refine controls and exceptions before deployment extends to more teams.
- Classification that users and owners can understand.
- Tests covering protection, sharing and retention.
- Responsibilities and procedures for maintaining policies.
When we can help with Purview
Inconsistent handling of sensitive documents
Your organization needs to distinguish documents that can be shared from information requiring specific access conditions.
Too many DLP alerts
Policies generate too many warnings or blocks, and your team needs to review rules, testing and exceptions.
Unclear retention practices
Retention practices vary, without a clear relationship between requirements, information owners and technical policies.
Information protection and governance services
Information assessment
We review information types, owners and the places where data is stored or shared. We identify requirements and available capabilities to define a workable initial set of policies.
Classification model
We design categories and usage criteria with information owners. The rules should help users classify documents consistently and understand the protection required in each case.
Sensitivity labels
We configure the agreed labels and protection settings. We check how they are applied, the user experience and document access for the profiles involved in everyday work.
Data loss prevention
We design and test DLP rules for the defined locations and scenarios. We review matches, warnings and exceptions before applying restrictions that could affect business activities.
Retention and preservation
We configure retention policies agreed with your organization and verify their scope. The relevant owners must supply or validate retention periods, obligations and preservation decisions.
Operations and AI readiness
We document policies, ownership and incident handling. Where the project relates to Copilot, we review protection and access dependencies for the sources included in that deployment.
Clear classification, protection and retention
Each control serves a different decision
Classification identifies the type of information being handled. A label can apply particular protection conditions; DLP acts on configured scenarios; retention implements preservation decisions. The design establishes the purpose and scope of each control.
We work with sample documents and real collaboration practices. This helps avoid categories that are difficult to apply and identifies exceptions needing approval or a specific procedure.
Test the effect on everyday work
The pilot covers opening and editing documents, sharing and access for the included user groups. Where external collaborators are involved, we include their tests in the plan from the design stage.
We refine rules using the incidents and matches observed. Usage instructions, notifications and exception handling are prepared with the team that will administer the policies.
Requirements, testing and policy rollout
Requirements
Identify information types, owners and protection and retention needs.
Design
Define the classification model, labels and project policies.
Testing
Validate with representative documents, users and scenarios.
Rollout
Activate progressively with communications and exception handling.
Operations
Document ownership and review incidents and policies.
Project documentation and handover
- Register of included requirements and information types.
- Classification model with application criteria.
- Design and configuration of agreed labels and policies.
- Test plan and access and collaboration results.
- Incident, exception and maintenance procedures.
- Administration documentation and instructions for the agreed user groups.
Scope, requirements and ongoing support
Do we need to define information classification first?
We can help design it with information owners. We use sample documents and collaboration requirements to agree categories and criteria that can then be translated into configurations.
Do labels always include encryption?
The options depend on the design and available capabilities. We define which labels classify information and which require protection conditions. Their behavior is tested before deployment.
Can we start DLP with a pilot?
Yes. We define locations, rules and users, review matches and assess the effects of warnings and planned actions. The findings determine adjustments and any scope expansion.
Who decides retention periods?
Your organization supplies or validates requirements with the relevant owners. MSAdvance designs and configures their technical application within the agreed scope and documents the tests performed.
Can protected documents be shared externally?
That depends on the protection settings, recipients and applications involved. The project needs to include those scenarios so access can be validated and usage and support guidance prepared.
Which licenses do we need?
We review required capabilities and available licenses before finalizing the scope. The proposal details requirements for labels, DLP policies, retention and any other included features.
Related services
SharePoint Online: intranets and document managementExplore this service →
Microsoft 365 Copilot for businessesExplore this service →
Microsoft Entra ID: identity and access for businessesExplore this service →Microsoft CybersecurityExplore the service area →Microsoft project experienceExplore our case studies →Administration and ongoing supportExplore Managed Services →Let’s define how your information needs to be protected
Tell us which documents concern you, where they are stored and how they are shared. With IT and information owners, we will define an initial scope for classification, protection or retention.
