Skip to content

Control 2.4: Information Barriers for Copilot (Chinese Wall)

Control ID: 2.4 Pillar: Security & Protection Regulatory Reference: SEC Rule 10b-5, FINRA 5280, Chinese Wall Requirements Last Verified: 2026-09-24 Regulatory Applicability: Firm/counsel determination — see Regulatory Applicability Questions Governance Levels: Baseline / Recommended / Regulated


Objective

Deploy Microsoft Purview Information Barriers (IB) to restrict communication and collaboration between organizational segments in the Microsoft 365 workloads where Microsoft documents IB enforcement, and validate that Microsoft Copilot grounding respects those boundaries for the firm's approved use cases. This control is intended for firms whose legal and compliance owners determine that ethical wall / Chinese Wall controls are required for scenarios such as investment banking and research separation, proprietary trading and client advisory separation, or merging entities during M&A transactions.


Why This Matters for FSI

  • SEC Rule 10b-5: Legal/compliance should determine whether a Copilot use case creates MNPI misuse or antifraud risk that requires information barrier controls and testing.
  • FINRA Rule 5280: Broker-dealer compliance should determine whether trading-ahead-of-research controls apply to the firm's Copilot-assisted research or trading workflows.
  • FINRA Rule 2241 (Equity Research) and Rule 2242 (Debt Research): Legal/compliance should determine which research/investment-banking separation requirements apply to the firm's Copilot-enabled workflows.
  • SEC Regulation AC: Legal/compliance should determine whether Copilot-assisted analyst workflows require additional independence, certification, or supervision controls.
  • Chinese Wall / ethical wall policies: Where firm policy requires separation of private-side/public-side information, Copilot's cross-workload retrieval should be included in barrier design and effectiveness testing.

Regulatory applicability

Regulatory citations identify commonly referenced requirements. Applicability, record classification, and retention periods are a firm and counsel determination; this framework does not assert that any regulation applies or is satisfied. See the Regulatory Applicability Questions appendix.


Control Description

Microsoft Purview Information Barriers restrict communication and collaboration between defined user segments in Microsoft Teams, SharePoint, OneDrive, Planner, and related supported collaboration experiences. Microsoft Learn also documents that IB policies cannot restrict email communication in Exchange Online. For Copilot, treat IB as an underlying workload boundary that must be validated in each tenant and surface:

  1. SharePoint and OneDrive: IB policies can prevent unauthorized site/content access, sharing, and search; test Copilot grounding against segment-exclusive test content.
  2. Teams: IB policies prevent unauthorized communication and collaboration activities; test Teams Copilot scenarios only after Teams IB policy application is active.
  3. Exchange Online: IB policies do not restrict email communication; use Exchange mail flow rules or other approved controls where email separation is required.
  4. Unsupported/limited Copilot surfaces: Channel Agent in Teams does not support IB. Copilot Pages and Copilot Notebooks use SharePoint Embedded content where Information Barriers are not supported.

IB Mode and Segment Membership

Microsoft Purview Information Barriers operates in one of three modes that determine how many segments a user may belong to:

IB Mode Segment Limit per User Total Segments Supported Notes
Legacy 1 (exactly one segment) 250 Oldest mode; users cannot be assigned to multiple segments; upgrade path available
SingleSegment (non-Legacy) 1 5,000 Current non-Legacy baseline; supports multi-segment upgrade
MultiSegment (non-Legacy) Up to 10 5,000 Current recommended mode; enables complex organizational scenarios

Multi-segment support (non-Legacy MultiSegment mode) allows users to belong to up to 10 IB segments simultaneously. User compatibility is determined by shared segment membership — if two users share at least one common segment, they are compatible under IB policy. This enables scenarios such as Compliance personnel who span multiple business units, deal team members who temporarily acquire an additional segment during a transaction, or supervisory users who need access across segments without full policy override.

FSI implication: Organizations should verify their current IB mode by running Get-PolicyConfig and checking the InformationBarrierMode property. Legacy-mode organizations should plan an upgrade path, as Legacy mode limits segment count to 250 and restricts each user to one segment — both constraints that create operational challenges for large diversified financial institutions. Organizations should verify that their Copilot-related IB configurations and compensating controls account for their specific IB mode behavior.

FSI Information Barrier Segments

Segment Description Wall Type Separated From
Investment Banking M&A advisory, capital markets, underwriting Permanent Research, Trading
Equity Research Equity analyst coverage Permanent Investment Banking, Trading
Debt/Fixed Income Research Fixed income analyst coverage Permanent Investment Banking
Proprietary Trading Firm proprietary trading desks Permanent Research, Investment Banking
Client Advisory Wealth management, financial advisory Situational Investment Banking (deal-specific)
Compliance/Legal Regulatory, legal, compliance Supervisory None (supervisory override)
Retail Banking Consumer banking operations Permanent Investment Banking
M&A Deal Teams Transaction-specific teams Temporary All non-deal personnel

Barrier Types and Copilot Impact

Barrier Type Duration Copilot Impact Example
Permanent Ongoing Supported workload barriers should prevent cross-segment SharePoint/OneDrive/Teams content access; Copilot grounding must be tenant-tested against those sources Research vs. Investment Banking
Temporary (Deal-Specific) Duration of transaction Additional barrier restricting deal team content from non-deal personnel where the underlying workload supports IB M&A target information
Situational Activated/deactivated as needed Client advisory restricted from specific IB deal information where the underlying workload supports IB Wealth client also an M&A target
Supervisory Ongoing with override Compliance can access all segments for supervisory purposes Compliance monitoring

Microsoft Copilot Chat Cross-Workload Search Implications

Microsoft Copilot Chat performs a cross-workload search when answering user queries. Without information barriers, a single Copilot Chat prompt could retrieve:

Copilot Chat Query: "What's the latest on Acme Corp?"
         │
    ┌────┴────────────────────────────────────┐
    │            Without Barriers              │
    ├──────────────────────────────────────────┤
    │ SharePoint: M&A deal room documents (IB) │
    │ Exchange: Research analyst emails         │
    │ Teams: Trading desk conversations         │
    │ OneDrive: Client advisory presentations   │
    └──────────────────────────────────────────┘
                    ⚠ POTENTIAL WALL BREACH / REVIEW EVENT

    ┌────┴────────────────────────────────────┐
    │            With Barriers                 │
    ├──────────────────────────────────────────┤
    │ SharePoint/OneDrive/Teams content: only  │
    │ segment-accessible + non-restricted data │
    │ Exchange email: separate controls needed │
    └──────────────────────────────────────────┘
                    ✓ TARGET STATE TO TENANT-TEST

Information Barrier Policy Architecture

Segment Definition (Entra ID attributes)
              │
              ▼
    IB Policy (Block/Allow rules)
              │
              ▼
    ┌─────────┴──────────┐
    │                    │
  M365 Workloads    Copilot Service
    │                    │
  ├─ Teams Chat        ├─ Copilot Chat Search
  ├─ SharePoint        ├─ File Grounding
  ├─ OneDrive          ├─ Meeting Summary
  └─ Exchange          └─ Email Drafting

Copilot Surface Coverage

M365 Application Public-source IB posture Tenant validation requirement Notes
Microsoft Copilot Chat Underlying workload controls apply; per-surface IB matrix not verified in public Learn Required Test with segment-exclusive SharePoint/OneDrive, Teams, and Exchange content. Do not assume Exchange email is barriered by IB.
Word Underlying file permissions/SharePoint or OneDrive IB apply to referenced files Required Test file reference, open-document, and generated-content scenarios.
Excel Underlying file permissions/SharePoint or OneDrive IB apply to referenced files Required Test analysis prompts against segment-exclusive files and Work IQ/Agent Mode sources where enabled.
PowerPoint Underlying file permissions/SharePoint or OneDrive IB apply to referenced files Required Test presentation generation, Agent Mode, and referenced email/file sources where enabled.
Outlook IB does not restrict email communication in Exchange Online Required Use Exchange mail flow rules or other approved email controls if the firm's wall design requires email separation.
Teams Copilot (meeting summaries, chat) Teams IB applies to Teams communication/collaboration boundaries Required Test meeting, chat, and transcript scenarios with segment-exclusive users and content.
Channel Agent in Teams Not supported Block or strictly scope Documented limitation: Information Barriers are not supported for Channel Agent. Channel Agent may return content that crosses IB boundaries. See compensating controls below.
OneNote Underlying file/storage controls apply; per-surface IB matrix not verified in public Learn Required Test notebook storage and references before approving use in IB-sensitive workflows.
Loop SharePoint Embedded / Loop capabilities can have IB limitations depending on storage surface Required Verify exact Loop/Copilot Pages/Notebooks storage and policy behavior in tenant.
Copilot Pages Not supported for SharePoint Embedded containers Disable or scope for IB-sensitive populations Microsoft Learn states Information Barriers are not supported for content stored in SharePoint Embedded containers used by Copilot Pages and Notebooks.
Copilot Notebooks Not supported for SharePoint Embedded containers Disable or scope for IB-sensitive populations Use Cloud Policy or approved admin controls where IB-sensitive populations cannot use these surfaces.
SharePoint agents / agents with embedded files Site-backed agents inherit SharePoint access controls; embedded files do not support IB Required For embedded-file knowledge, any user who can access the agent can see responses grounded in the embedded file content.

Channel Agent IB Limitation and Compensating Controls

Channel Agent in Teams does not support Information Barriers. This is a documented platform limitation: unlike standard Copilot Chat and Teams Copilot features, Channel Agent is not subject to IB policy enforcement and may return content that crosses information barrier boundaries.

FSI regulatory impact: If firm counsel/compliance determines that SEC Rule 10b-5, FINRA Rules 5280/2241/2242, or firm ethical wall policies apply to the use case, a Channel Agent deployed in a Teams channel that includes members from barrier-separated segments (e.g., Investment Banking and Research) could surface barrier-restricted information without IB enforcement. Document the limitation, approved deployment criteria, and escalation process in supervisory procedures and information barrier policies.

Required compensating controls:

  1. Restrict Channel Agent deployment to homogeneous segments. Do not deploy Channel Agent in any Teams channel where members from IB-separated segments are present. Before deploying a Channel Agent, audit the channel's membership to confirm all members belong to a single IB segment or are in non-restricted segments.

  2. Do not rely on sensitivity-label DLP to block Channel Agent. Microsoft Learn documents that Channel Agent in Teams cannot be prevented from summarizing labeled files that are identified by a Microsoft Purview DLP policy. Sensitivity labels remain useful for classification, label inheritance, and EXTRACT-rights behavior for the requesting user, but they are not a compensating control for IB enforcement in Channel Agent.

  3. Monitor Channel Agent activity where tenant telemetry supports it. Verify in your tenant whether DSPM, Purview audit, Teams app inventory, and agent registry views expose Channel Agent deployments and interactions. Anomalous cross-segment content surfacing via Channel Agent should generate compliance review under the firm's incident process.

  4. Document in supervisory procedures. The Channel Agent IB limitation and the firm's compensating controls must be documented in supervisory procedures, information barrier policies, and (for Regulated level) in the regulatory examination package.


Governance Levels

Level Requirement Rationale
Baseline Define organizational segments based on department attribute; create block policies between Investment Banking and Research where approved by Legal/Compliance; enable information barriers for Teams, SharePoint, and OneDrive; functionally test approved Copilot scenarios; disable Channel Agent in Teams channels where IB-separated users are members Minimum ethical-wall implementation for firms whose approved policy requires segment separation, including explicit handling of the Channel Agent IB limitation
Recommended Add Trading segment separation where approved; implement temporary deal-specific barriers; validate supported workloads; quarterly barrier validation testing; compliance review of barrier configurations; integrate barrier events with audit logging; deploy Channel Agent only in homogeneous-segment channels with documented segment membership audits; document why sensitivity-label DLP is not an IB substitute for Channel Agent Comprehensive barrier strategy suitable for multi-service financial firms with investment banking, research, and trading operations, with Channel Agent compensating controls in place
Regulated All approved segments defined and enforced; automated barrier provisioning for new deals; monitoring of barrier policy events and failed access attempts; annual barrier effectiveness audit by compliance; supervisory access documented and reviewed quarterly; barrier configurations included in regulatory examination packages; Channel Agent IB limitation documented in supervisory procedures; tenant telemetry monitoring configured for all Channel Agent deployments where available; Channel Agent prohibited in any channel with mixed IB-segment membership Full ethical-wall implementation for large, diversified financial institutions subject to frequent examinations. The Channel Agent limitation and compensating controls should appear in the examination package where counsel/compliance determine the cited rules or firm policies apply.

Setup & Configuration

Step 1: Define User Segments

Portal: Microsoft Purview > Information barriers > Segments

  1. Create segments based on Entra ID user attributes (typically Department or custom attributes)
  2. Ensure all Copilot-licensed users are assigned to at least one segment. In non-Legacy IB mode (SingleSegment or MultiSegment), users may be assigned to up to 10 segments — this multi-segment support enables more complex organizational scenarios such as Compliance users spanning multiple business units or M&A team members needing temporary additional segment assignments. In Legacy mode, each user is restricted to exactly one segment (maximum 250 total segments). Organizations should verify their IB mode by running Get-PolicyConfig and checking the InformationBarrierMode property.
  3. Verify segment membership accuracy with business stakeholders
# Connect to Security & Compliance PowerShell
Connect-IPPSSession

# Create segment definitions
New-OrganizationSegment -Name "InvestmentBanking" `
  -UserGroupFilter "Department -eq 'Investment Banking'"

New-OrganizationSegment -Name "EquityResearch" `
  -UserGroupFilter "Department -eq 'Equity Research'"

New-OrganizationSegment -Name "Trading" `
  -UserGroupFilter "Department -eq 'Proprietary Trading'"

Step 2: Create Information Barrier Policies

# Block Investment Banking from Research
New-InformationBarrierPolicy -Name "IB-Research-Block" `
  -AssignedSegment "InvestmentBanking" `
  -SegmentsBlocked "EquityResearch","DebtResearch" `
  -State Active
# IMPORTANT: Create the reciprocal policy (Research blocked from InvestmentBanking) to ensure bidirectional enforcement

# Block Trading from Research
New-InformationBarrierPolicy -Name "Trading-Research-Block" `
  -AssignedSegment "Trading" `
  -SegmentsBlocked "EquityResearch","DebtResearch" `
  -State Active
# IMPORTANT: Create the reciprocal policy (Research blocked from Trading) to ensure bidirectional enforcement

# Block Investment Banking from Trading
New-InformationBarrierPolicy -Name "IB-Trading-Block" `
  -AssignedSegment "InvestmentBanking" `
  -SegmentsBlocked "Trading" `
  -State Active
# IMPORTANT: Create the reciprocal policy (Trading blocked from InvestmentBanking) to ensure bidirectional enforcement

Step 3: Apply Barrier Policies

# Start policy application (this processes all policies)
Start-InformationBarrierPoliciesApplication

# Check application status
Get-InformationBarrierPoliciesApplicationStatus

Step 4: Enable Information Barriers for SharePoint and OneDrive

Portal: SharePoint admin center > Settings > Information barriers

  1. Enable information barriers for SharePoint
  2. Enable information barriers for OneDrive
  3. Apply IB mode to sites: "Owner Moderated" or "Implicit" based on firm requirements

Step 5: Verify Copilot Barrier Enforcement

  1. Sign in as an Investment Banking user
  2. Open Copilot Chat and query for content that should be restricted (e.g., research reports)
  3. Verify that Copilot does not return results from barrier-separated segments
  4. Repeat for other segment combinations

Step 6: Configure Deal-Specific Temporary Barriers

# Create temporary deal team segment
New-OrganizationSegment -Name "ProjectAlpha-DealTeam" `
  -UserGroupFilter "CustomAttribute1 -eq 'ProjectAlpha'"

# Create barrier blocking non-deal personnel
New-InformationBarrierPolicy -Name "ProjectAlpha-Barrier" `
  -AssignedSegment "ProjectAlpha-DealTeam" `
  -SegmentsBlocked "ClientAdvisory","RetailBanking" `
  -State Active

Financial Sector Considerations

  • Broker-Dealer Operations: Where broker-dealer compliance determines that investment banking / research separation applies, Copilot test plans should verify that approved AI surfaces do not expose segment-exclusive content across the firm's wall.
  • Multi-Service Financial Institutions: Firms operating across banking, insurance, and securities face the most complex barrier requirements. Each line of business may require separation from multiple other segments, creating a matrix of barrier policies.
  • Deal-Specific Barriers: M&A transactions require temporary barriers that restrict deal information to authorized deal team members. These barriers must be provisioned rapidly (within hours of deal engagement) and decommissioned cleanly after transaction close. Copilot must respect these temporary barriers immediately upon activation.
  • Supervisory Access: Compliance and legal functions typically need supervisory access across all segments for monitoring purposes. Information barriers support this through allow policies that permit one-way or bidirectional access for supervisory segments. Document the business justification for all supervisory access exceptions.
  • Wall-Crossing Procedures: When employees are temporarily "brought over the wall" for a transaction, their information barrier segment assignment must be updated and Copilot access adjusted accordingly. Establish a documented wall-crossing procedure that includes Copilot access considerations.
  • Private-Side vs. Public-Side: Financial firms distinguish between private-side (access to MNPI) and public-side (no MNPI access) roles. Information barriers should align precisely with the firm's private-side/public-side designation. Any misalignment creates regulatory risk.
  • Examination History: SEC and FINRA have brought enforcement actions against firms with inadequate information barriers. AI tools that access data across organizational boundaries represent a heightened enforcement risk. Maintain detailed evidence of barrier effectiveness testing.
  • Work IQ and cross-app grounding: M365 roadmap items show Work IQ features for PowerPoint and Work IQ APIs reaching GA in 2026. For FSI organizations with ethical-wall requirements, any Copilot feature that can reason across files, meetings, emails, or agents should be included in tenant functional tests to confirm whether segment boundaries are respected for the approved workflow.

Verification Criteria

  1. Segment Assignment: Verify that all Copilot-licensed users are assigned to at least one appropriate organizational segment; confirm IB mode (Get-PolicyConfig) and that multi-segment assignments, if used, are intentional and documented
  2. Policy Application Status: Confirm all information barrier policies show "Active" and "Applied" status
  3. Copilot Chat Barrier Enforcement: As an Investment Banking user, query Copilot Chat for research content — confirm no cross-segment results are returned
  4. File Grounding Restriction: Attempt to reference a Research segment file in Copilot while signed in as an Investment Banking user — confirm Copilot cannot access the file
  5. Teams Copilot Barrier Enforcement: Verify that Teams Copilot meeting summaries do not include content from barrier-separated participants
  6. Channel Agent IB Gap Documentation: Confirm that Channel Agent deployments are documented with IB segment membership audits for each channel; confirm no Channel Agents are deployed in channels with mixed IB-segment membership; confirm the Channel Agent IB limitation is documented in supervisory procedures
  7. Channel Agent Compensating Controls: Verify Channel Agent is disabled or restricted to homogeneous-segment channels; confirm the firm does not rely on sensitivity-label DLP as an IB substitute; confirm tenant telemetry monitoring is configured where available
  8. SharePoint IB Mode: Confirm SharePoint sites have appropriate IB modes applied and that Copilot in SharePoint respects barrier boundaries
  9. Temporary Barrier Activation: Create a test temporary barrier and verify Copilot enforcement within 1 hour of policy application
  10. Supervisory Access: Verify that Compliance segment users can access content across barriers as designed, and that access is logged
  11. Barrier Event Audit Logs: Confirm that information barrier policy match events appear in the Unified Audit Log
  12. Periodic Validation: Confirm quarterly barrier validation testing is scheduled, documented, and reviewed by compliance

Additional Resources