Control 2.4: Information Barriers for Copilot (Chinese Wall) — Portal Walkthrough
Step-by-step portal configuration for implementing Information Barriers and validating ethical-wall restrictions for approved Copilot interactions.
Prerequisites
- Purview Compliance Admin role
- Microsoft 365 E5 or E5 Compliance license
- Entra ID user attributes populated (department, segment identifiers)
- Ethical-wall / Chinese Wall policy requirements documented by Legal/Compliance
Steps
Step 1: Define Information Barrier Segments
Portal: Microsoft Purview Path: Purview > Information Barriers > Segments
Create segments based on organizational units that require information separation. For FSI environments, typical segments include: - Investment Banking - Research / Equity Analysis - Trading / Sales - Retail Banking / Wealth Management - Corporate Treasury - Compliance / Legal
Legal/Compliance should determine whether SEC Rule 10b-5, FINRA Rule 5280, FINRA Rule 2241, FINRA Rule 2242, or firm policy require these or other segments before the playbook is treated as a control requirement.
Define each segment using Entra ID user attributes (department, custom attribute, or group membership).
Step 2: Create Information Barrier Policies
Portal: Microsoft Purview Path: Purview > Information Barriers > Policies > Create
Create barrier policies that define which segments cannot communicate or share data: - Policy 1: Block communication between Investment Banking and Research - Policy 2: Block communication between Investment Banking and Trading - Policy 3: Block communication between Research and Sales
For each policy, define the segment pair and the restriction type (Block or Allow).
Step 3: Apply Information Barrier Policies
Portal: Microsoft Purview Path: Purview > Information Barriers > Policy application
After creating all policies, apply them to activate enforcement. Policy application may take 24-48 hours to fully propagate across all workloads including: - Microsoft Teams (chat, channels, meetings) - SharePoint Online and OneDrive - Microsoft 365 Copilot (content grounding and response generation)
Step 4: Verify Copilot Compliance with Barriers
Portal: Microsoft Purview Path: Purview > Information barriers > Status
Verify that approved Copilot scenarios respect the underlying workload boundaries: - Users in the Investment Banking segment should not receive Copilot responses grounded on Research segment SharePoint/OneDrive or Teams content used for the test - Outlook/email scenarios require separate controls because Microsoft Learn states Information Barriers do not restrict Exchange Online email communication - Copilot Pages, Copilot Notebooks, and embedded-file agent knowledge require separate controls because Information Barriers are not supported for SharePoint Embedded content - Note: Channel Agent in Teams does NOT support Information Barriers — see Step 6 for required actions
Step 5: Configure Barrier Exception Handling
Document and configure any approved exceptions to barrier policies: - Compliance and Legal may need cross-barrier access for supervisory purposes - Specific deal teams may need temporary barrier exceptions with governance approval - Document all exceptions with business justification and expiration dates
Step 6: Manage Channel Agent IB Gap
Channel Agent in Teams does not enforce Information Barriers. Before deploying any Channel Agent, complete the following:
- Audit channel membership for the target Teams channel. Navigate to Microsoft Teams Admin Center or review the Teams channel members list.
- Confirm the channel is homogeneous — all members must belong to a single IB segment, or the channel must contain only non-IB-restricted users.
- Do not deploy Channel Agent in any channel with members from IB-separated segments (e.g., a channel containing both Investment Banking and Research members).
- Do not rely on sensitivity-label DLP as an IB substitute. Microsoft Learn states DLP cannot prevent Channel Agent from summarizing labeled files; use app restriction, channel membership controls, and removal from mixed-segment channels instead.
- Document the Channel Agent IB limitation in the firm's supervisory procedures and information barrier policy where Legal/Compliance determines ethical-wall controls apply.
Portal path for channel membership review: Microsoft Teams Admin Center > Teams > [team] > Channels > [channel] > Members; also verify Microsoft 365 admin center > Agents / agent registry views where available in your tenant.
FSI Recommendations
| Tier | Recommendation |
|---|---|
| Baseline | Define segments for primary ethical-wall divisions approved by Legal/Compliance; implement core barrier policies; disable Channel Agent in IB-affected Teams channels |
| Recommended | Full approved segment coverage with exception management process; verify Copilot scenarios through tenant functional tests; deploy Channel Agent only in homogeneous-segment channels with documented membership audits; document that sensitivity-label DLP is not an IB substitute for Channel Agent |
| Regulated | Comprehensive barrier policies per firm-approved requirements; documented exception process with time-limited approvals; continuous monitoring of barrier effectiveness where telemetry supports it; Channel Agent IB limitation documented in supervisory procedures; Channel Agent prohibited in any channel with mixed IB-segment membership |
Next Steps
- Proceed to PowerShell Setup for barrier management automation
- See Verification & Testing to validate barrier enforcement
- Review Control 2.1 for DLP integration with Information Barriers
- Back to Control 2.4