Implementing Microsoft Purview to secure a cloud migration.
A foundation moved 100% of its confidential data to Microsoft 365 in 60 days, with Microsoft Purview sensitivity labels, data loss prevention and auditing live on day one.
data migrated
days start to finish
workshop phases
The challenge
The foundation needed to move confidential on-premises files into Microsoft 365 without losing control of who could see what. Collaboration had to feel easier after the migration, and protections had to be in place before the first file landed in SharePoint.
- Migrate confidential on-premises files to Microsoft 365 without compromising security
- Maintain data protection and compliance during the transition
- Enable secure collaboration in SharePoint and OneDrive for internal and external stakeholders
- Establish data protection and compliance with Microsoft Purview: sensitivity labels, data loss prevention policies and auditing
- Balance technical execution with organizational policy-making
Our approach
Site structure and data mapping
Inventoried on-premises folders, identified confidential data and planned SharePoint site equivalents.
External collaboration and access
Refined Microsoft Entra ID groups and defined external sharing policies to balance collaboration with security.
Microsoft Purview sensitivity labels, data loss prevention policies and auditing
Established a sensitivity label taxonomy, label policies and encryption settings.
Testing, deployment and training
Sandbox testing, production rollout and user training.
What we configured
- Sensitivity labels (Public, Internal, Confidential) with label policies, default labels for confidential SharePoint libraries, and encryption settings.
- Data loss prevention policies for Exchange, SharePoint and OneDrive to flag and restrict sharing of confidential content.
- Microsoft Purview Audit confirmed on and reviewed so activity on confidential data can be traced.
- SharePoint site permissions aligned with Microsoft Entra ID groups, for granular access control and separation of duties.
- Tenant-wide external sharing settings with allowlists for approved domains.
- Ongoing policy adjustments during migration so labels were applied correctly to migrated content.
Outcomes
100% migration complete
All on-premises files moved to SharePoint and OneDrive with security labeling.
Consistent labeling
Confidential content is labeled more consistently, with clear guidance for staff.
Streamlined access
Microsoft Entra ID groups integrated with SharePoint permissions for consistent access control.
Compliance readiness
Clear data protection policies, with audit records that show how confidential data is handled.
Trained staff
Staff trained on data classification and secure sharing.
Key takeaways
- 01
Policy clarity drives adoption: engage leadership early on classification.
- 02
Iterative testing prevents rework: sandbox first.
- 03
Data protection is ongoing: monitoring, refinement and user education continue after launch.
Continuing work
Gyan-i continues to support the organization by monitoring and refining its Microsoft Purview labels, data loss prevention policies and audit configuration.
Find out what to fix first in your environment.
A 30-minute scoping call with the team behind these engagements. We'll show you your biggest risk and where to start. No obligation.
