Troubleshooting: Control 1.22 - Information Barriers for AI Agents
Last Updated: January 2026
Common Issues
| Issue | Cause | Resolution |
|---|---|---|
| User not in segment | Department attribute missing | Populate Entra ID attribute |
| Policy not applying | Application not started | Run Start-InformationBarrierPoliciesApplication |
| Barrier not enforcing | User without segment | Ensure all users have segments |
| SharePoint access despite barrier | Site permissions override | Align SharePoint permissions |
Detailed Troubleshooting
Issue: User Not Assigned to Segment
Symptoms: User can access content they shouldn't
Resolution:
- Verify user's Department attribute in Entra ID
- Check segment filter matches attribute value
- Run policy application after fixing
- Wait for propagation (can take hours)
Issue: Policy Application Stuck
Symptoms: Status shows "InProgress" for extended period
Resolution:
- Check for conflicting policies
- Verify all segments have valid filters
- Contact Microsoft Support if stuck > 24 hours
Escalation Path
- Purview Compliance Admin - Segment and policy configuration
- SharePoint Admin - Site permission alignment
- Entra Admin - User attribute population
- Microsoft Support - Policy application issues
Known Limitations
| Limitation | Impact | Workaround |
|---|---|---|
| Application can take hours | Delays after changes | Plan ahead |
| Users without segments bypass | Security gap | Ensure 100% coverage |
| Complex hierarchies | Difficult to model | Simplify segment structure |
| Teams/SharePoint sync delay | May see temporary access | Wait for full propagation |
Back to Control 1.22 | Portal Walkthrough | PowerShell Setup | Verification Testing