M365 Playbooks1. Plan
Design your segments and barrier policies
The rules that justify each barrier, the attribute that defines segments, the organization's mode, and a signed matrix of who can't talk to whom.
- Duration
- 4 to 6 weeks
- Complexity
- High
Program · Security Management
Information barriers
Keep apart the groups a rule says must not communicate, in Teams, SharePoint and OneDrive, without breaking everyone else's collaboration.
Written for Microsoft 365 E5
Essential path
Start with these. Go further, below, covers specific workloads and needs to complete your approach.
2. Prepare
Test barriers and get ready to apply them
Clean directory data, required tenant settings, a test of every way people communicate, a rollback plan and a go/no-go before policies apply.
- Duration
- 3 to 6 weeks
- Complexity
- Medium
3. Deploy
Apply barriers across Teams, SharePoint and OneDrive
Segments and policies created inactive, then activated barrier by barrier, with teams moved to Implicit and SharePoint and OneDrive barriers turned on.
- Duration
- 4 to 8 weeks
- Complexity
- High
4. Maintain
Keep barriers accurate as people move
Owners, mover handling, exception requests, checks after every change, and a yearly review of each barrier against its rule.
- Duration
- Ongoing
- Complexity
- Medium
↻ Refine feeds what you learn back into Plan.
Go further
Show 1 more playbook for specific workloads and needs
Deploy · Exchange email
Restrict email between segments with mail flow rules
Mail flow rules that reject email between segments a rule keeps apart, built from groups that match the segments and tested before enforcement.