Skip to content

Control 2.7: Data Residency and Cross-Border Data Flow Governance

Control ID: 2.7 Pillar: Security & Protection Regulatory Reference: GLBA §501(b), GDPR (if applicable), State Privacy Laws Last Verified: 2026-09-22 Governance Levels: Baseline / Recommended / Regulated


Objective

Establish governance over data residency and cross-border data flows associated with Microsoft 365 Copilot processing. Financial institutions must understand where Copilot processes and stores data (prompts, responses, grounding data, telemetry), whether this data crosses jurisdictional boundaries, and how to configure residency controls for multinational operations. This control supports compliance with GLBA safeguard requirements, state-level data privacy laws, and international data transfer obligations for firms with global operations.


Why This Matters for FSI

  • GLBA §501(b) requires financial institutions to protect customer information throughout its lifecycle — understanding where Copilot processes customer data is essential for demonstrating safeguard adequacy
  • State privacy laws (California CCPA/CPRA, Virginia VCDPA, Colorado CPA, Connecticut CTDPA, and others) impose data handling obligations that may include data residency considerations for AI processing
  • GDPR (Articles 44-49) restricts transfers of personal data to countries outside the EEA without adequate safeguards — US-headquartered firms with EU operations must address Copilot data flows under GDPR
  • NYDFS Part 500 (Section 500.15) requires encryption of NPI in transit and at rest — data residency determines which jurisdictional encryption requirements apply
  • OCC/Fed Interagency Guidance expects banks to manage risks associated with third-party data processing, including understanding data processing locations
  • SEC/FINRA expectations for books and records may require that certain records remain accessible within US jurisdiction

Control Description

Microsoft 365 Copilot data processing follows the data residency commitments of the underlying Microsoft 365 services, with specific considerations for AI processing components.

Copilot Data Processing Locations

Data Type Processing Location Storage Location Residency Control
User prompts Tenant's provisioned geography Compliance copies stored in user's Exchange Online mailbox (hidden folder); subject to Purview retention policies Follows M365 tenant geo
Copilot responses Tenant's provisioned geography Stored as user content in M365 services Follows M365 tenant geo
Grounding data Tenant's provisioned geography Remains in source M365 service Follows M365 data residency
Semantic Index Tenant's provisioned geography Co-located with M365 tenant Follows M365 tenant geo
Azure OpenAI processing Microsoft-managed infrastructure Processing only — no persistent storage Regional processing commitments
Anthropic models (subprocessor since Jan 7, 2026; excludes Anthropic models with Data Retention) Anthropic-operated infrastructure under Microsoft Product Terms / DPA Processing only — no persistent storage Out of scope for the EU Data Boundary and in-country LLM processing commitments; on by default for most commercial-cloud customers (excluding EU/EFTA and UK)
SpaceXAI models (independent processor) SpaceXAI-hosted infrastructure outside Microsoft-managed environments Per xAI's Terms of Service and Data Processing Addendum Microsoft Product Terms, DPA, data residency commitments, and Customer Copyright Commitment do not apply; opt-in only; used with Copilot Studio and Copilot Cowork
SpaceXAI models (Microsoft subprocessor, preview) SpaceXAI-operated models under Microsoft Product Terms / DPA, except as disclosed in Learn's exclusions Per the Microsoft Product Terms and DPA Excluded from in-country processing commitments when applicable; Frontier-program customers only, not available in EU/EFTA or UK, or in other environments Learn lists as excluded; disabled by default; supported in Copilot in Word, Excel, and PowerPoint at initial availability
Web search queries Bing search service infrastructure (if enabled) User and tenant identifiers removed; Microsoft acts as data controller and the DPA does not apply EU Data Boundary does not apply to generated web search queries. See Control 2.6
Audit logs Tenant's provisioned geography Unified Audit Log location Follows M365 tenant geo
Telemetry Microsoft-managed Aggregated, anonymized Microsoft privacy commitments

Microsoft 365 Data Residency Options

Residency Option Description Copilot Coverage FSI Relevance
Default geo Data stored in the region where tenant is provisioned Yes for Microsoft-hosted Copilot processing — Copilot follows tenant geo. Third-party model providers (Anthropic, xAI) are not bound by tenant geo: Anthropic models are out of scope for the EU Data Boundary and in-country LLM processing commitments, and xAI processing occurs outside Microsoft-managed environments entirely when SpaceXAI is used as an independent processor. Most US FSI firms are provisioned in US datacenters; firms must separately assess provider-specific exclusions before enabling Anthropic or xAI
Advanced Data Residency (ADR) Add-on providing data residency commitments for additional workloads Yes for in-scope Microsoft-hosted Copilot processing; ADR commitments do not extend to Anthropic-hosted or xAI-hosted model traffic Recommended for firms requiring contractual residency assurances for Microsoft-managed workloads
Multi-Geo Data stored in multiple regions based on user assignment Yes for Microsoft-hosted Copilot processing — Copilot processes in user's assigned geo; Multi-Geo does not redirect Anthropic or xAI provider traffic Required for multinational FSI firms with regional regulatory requirements
EU Data Boundary EU customer data processed and stored within the EU Yes for Microsoft-hosted Copilot processing; Anthropic models are explicitly out of scope for the EU Data Boundary and remain disabled by default for EU/EFTA and UK tenants; xAI is also outside EUDB coverage when used as an independent processor, and SpaceXAI as a subprocessor (preview) is not available to EU/EFTA or UK customers Relevant for US firms with EU banking or investment operations; confirm Anthropic/xAI remain disabled in EU/EFTA/UK tenants where required

Cross-Border Data Flow Scenarios

Scenario Data Flow Regulatory Concern Mitigation
US firm, all US operations, Microsoft-hosted models only US datacenter processing Low — data stays in US for Microsoft-managed Copilot processing Default configuration adequate; verify Anthropic/xAI provider toggles match policy
US firm with EU subsidiary EU user data may process in US Copilot infra High — GDPR Article 44+ Enable Multi-Geo; assign EU users to EU geo; confirm Anthropic remains disabled by default for EU/EFTA tenants and that xAI is not enabled where EU residency is required
US firm with APAC operations APAC user data may process outside region Medium — local data laws Multi-Geo for APAC users
US firm with Canadian operations Canadian data may process in US Medium — PIPEDA considerations Multi-Geo for Canadian users
Tenant has Anthropic models enabled (subprocessor since Jan 7, 2026) Prompts and grounding data processed by Anthropic-operated infrastructure under the Microsoft DPA Medium-to-high — Anthropic processing is out of scope for the EU Data Boundary and in-country LLM processing commitments Document Anthropic in vendor risk register (Control 1.10); disable Anthropic in EU/EFTA/UK tenants if data residency requires
Tenant has Anthropic models with Data Retention enabled Prompts and responses are retained by Anthropic under separate Anthropic terms; Anthropic acts as an independent processor for this model category High — Microsoft Product Terms, DPA, and Microsoft residency commitments do not apply to this path Require explicit risk acceptance and user/group scoping; record retention implications; treat the model category as a separate vendor data-flow path under Control 1.10
Tenant has SpaceXAI models enabled (independent processor, Copilot Studio and Copilot Cowork) Prompts and responses processed outside Microsoft-managed environments under xAI's separate terms High — Microsoft Product Terms, DPA, data residency commitments, and Customer Copyright Commitment do not apply Treat SpaceXAI as an additional vendor under Control 1.10; review xAI Enterprise Terms of Service and Data Processing Addendum; restrict to approved Copilot Studio scenarios and Copilot Cowork users; document data flow in DPIA
Tenant has SpaceXAI enabled as a Microsoft subprocessor (preview, Frontier program) Prompts and responses processed by SpaceXAI-operated models under the Microsoft Product Terms and DPA, except as disclosed in Learn's exclusions Medium-to-high — excluded from in-country processing commitments when applicable; certifications are maintained by SpaceXAI; not FedRAMP High authorized Record the separate subprocessor setting and assigned users or groups; document SpaceXAI in the vendor risk register (Control 1.10); confirm in-country processing requirements are not relied on for this path

Data Residency Architecture

Multinational FSI Firm
         │
    ┌────┴────────────────────────┐
    │                             │
  US Operations              EU Operations
    │                             │
  US Tenant Geo               EU Multi-Geo
    │                             │
  ┌─┴──────────┐            ┌────┴─────────┐
  │ M365 Data  │            │ M365 Data    │
  │ US DC      │            │ EU DC        │
  │            │            │              │
  │ Copilot    │            │ Copilot      │
  │ Processing │            │ Processing   │
  │ US Region  │            │ EU Region    │
  └────────────┘            └──────────────┘

Copilot Surface Coverage

M365 Application Follows Tenant Geo Multi-Geo Support ADR Coverage Notes
Microsoft Copilot Chat Yes Yes Yes Cross-workload processing in user's geo
Word Yes Yes Yes Document processing in user's geo
Excel Yes Yes Yes Data analysis in user's geo
PowerPoint Yes Yes Yes Presentation generation in user's geo
Outlook Yes Yes Yes Email processing in user's geo
Teams Yes Yes Yes Meeting/chat processing in user's geo
OneNote Yes Yes Yes Note processing in user's geo
Loop Yes Yes Yes Loop content in user's geo
Copilot Pages Yes Yes Yes Pages stored in user's geo
SharePoint (Agents) Yes Yes Yes Agent processing follows site geo
Microsoft Scout (Frontier preview) — M365-sourced content Partial Partial Partial Scout activity on M365 content the user is already permitted to access follows the same tenant-geo and ADR posture as other Copilot surfaces. Automation instructions and tool output are stored on the local endpoint and are outside the Microsoft 365 DPA, and inference processed through GitHub Copilot and third-party model providers is outside M365 residency — these paths are not covered by tenant residency or ADR. See Control 4.16.

Governance Levels

Level Requirement Rationale
Baseline Document the M365 tenant's provisioned geography; confirm Copilot processing follows tenant geo; verify no unintended cross-border data flows; review Microsoft's data residency commitments for Copilot annually Establishes awareness of data processing locations — minimum requirement for any FSI Copilot deployment
Recommended Implement Advanced Data Residency (ADR) add-on for contractual residency assurances; configure Multi-Geo for multinational operations; map Copilot data flows for privacy impact assessments; include Copilot data residency in vendor risk assessment; quarterly review of residency configuration Provides contractual assurance and multi-region support — appropriate for firms with operations in multiple jurisdictions
Regulated All Recommended requirements plus: formal data flow mapping for each jurisdiction; legal review of cross-border transfer mechanisms (SCCs, adequacy decisions); data residency included in regulatory examination packages; real-time monitoring of data processing locations via Microsoft service health; annual third-party audit of data residency compliance Maximum residency governance for firms with the most complex jurisdictional requirements and highest regulatory expectations

Setup & Configuration

Step 1: Verify Tenant Geography

Portal: Microsoft 365 Admin Center > Settings > Org settings > Organization profile > Data location

  1. Confirm the tenant's primary data location
  2. Note which M365 services are covered by the default residency commitment
  3. Document the provisioned geography for governance records

Step 2: Enable Advanced Data Residency (if applicable)

  1. Evaluate whether ADR add-on is needed based on regulatory requirements
  2. Purchase ADR add-on through Microsoft licensing
  3. ADR provides contractual data residency commitments for:
  4. Exchange Online
  5. SharePoint Online / OneDrive
  6. Microsoft Teams
  7. Microsoft 365 Copilot interactions

Step 3: Configure Multi-Geo (if applicable)

Portal: Microsoft 365 Admin Center > Settings > Org settings > Multi-Geo

  1. Enable Multi-Geo capabilities (requires Multi-Geo add-on licensing)
  2. Assign satellite geographies for applicable regions
  3. Assign users to their correct preferred data location (PDL)
# Connect to Microsoft Graph
Connect-MgGraph -Scopes "User.ReadWrite.All"

# Set preferred data location for EU users
Update-MgUser -UserId "eu-user@firm.com" -PreferredDataLocation "EUR"

# Verify user's preferred data location
Get-MgUser -UserId "eu-user@firm.com" | Select-Object DisplayName, PreferredDataLocation

Step 4: Map Copilot Data Flows

Create a data flow mapping document that includes:

  1. Source data locations (where M365 content resides)
  2. Processing locations (where Copilot AI processing occurs)
  3. Output locations (where Copilot responses and Pages are stored)
  4. Ancillary data flows (audit logs, telemetry, web search if enabled)

Step 5: Privacy Impact Assessment

For firms subject to GDPR or comprehensive state privacy laws:

  1. Include Copilot data processing in the firm's Data Protection Impact Assessment (DPIA)
  2. Document the legal basis for processing (legitimate interest, contractual necessity)
  3. Evaluate cross-border transfer mechanisms if applicable
  4. Update Records of Processing Activities (ROPA) to include Copilot

Step 6: Document Residency Configuration

Maintain a residency configuration document that includes:

Element Detail
Tenant primary geography [e.g., United States]
ADR status [Enabled/Not Enabled]
Multi-Geo regions [List of satellite geos]
Copilot processing geography [Confirmed location]
Web search status [Enabled/Disabled — see Control 2.6]
Last review date [Date]
Reviewer [Name/Role]

Financial Sector Considerations

  • US-Only Operations: Most US-only FSI firms have M365 tenants provisioned in US datacenters. For these firms, data residency risk from Copilot is low, but documenting the residency posture is still a governance requirement. Examiners may ask where AI processing occurs.
  • Multinational Banking Groups: Large banking groups with operations in the EU, UK, and Asia face the most complex residency requirements. Multi-Geo is essential, and each regional subsidiary may need independent review of Copilot data flows against local regulations.
  • EU Operations and GDPR: US financial firms with EU banking, asset management, or brokerage operations must address GDPR requirements for Copilot. This includes legal basis for processing, DPIA completion, and cross-border transfer mechanisms (Standard Contractual Clauses or EU-US Data Privacy Framework).
  • State Privacy Laws: California (CCPA/CPRA), Virginia, Colorado, Connecticut, and other states with comprehensive privacy laws may impose requirements relevant to how Copilot processes resident information. Monitor evolving state-level AI-specific legislation.
  • Examination Readiness: SEC and FINRA may ask where firm records are processed and stored. If Copilot-generated content (emails drafted by Copilot, meeting summaries, document drafts) constitutes firm records, data residency documentation should cover these items.
  • Third-Party Risk Management: Include Copilot's data processing geography in the firm's vendor risk assessment for Microsoft. OCC and FFIEC guidance expects financial institutions to understand where third-party service providers process their data.
  • Future Regulatory Development: US federal financial regulators are developing AI-specific guidance that may include data residency requirements. Establishing residency governance now positions the firm for future compliance requirements.

Third-Party Model Provider Evidence Checklist

When Anthropic, Anthropic models with Data Retention, or SpaceXAI models are enabled (or any future third-party model provider), the following evidence should be collected and retained for examination readiness. (Provider posture in this control was verified against connect-to-ai-subprocessor and connect-to-ai-models on 2026-09-22; the SpaceXAI subprocessor (preview) path was added from spacexai-subprocessor; these claims are time-sensitive — re-verify before relying.)

Evidence Item Source Retention
Provider enablement decision record Document who authorized enablement, business justification, and risk acceptance Per institution retention policy (7 years recommended for regulated entities)
User/group scoping Screenshot or export of which users or security groups are scoped for third-party model access via M365 Admin Center > Copilot settings Quarterly refresh
Data processing terms review Documented review of the provider's Data Processing Addendum, privacy statement, and subprocessor list against institutional requirements At enablement and annually
Data residency assessment Mapping of where the provider processes inference requests relative to the institution's approved residency boundaries At enablement and on provider change
EU Data Boundary impact Confirmation that Anthropic/xAI remain disabled in EU/EFTA/UK tenants where the EU Data Boundary is required Quarterly verification
Power Platform external model rules For SpaceXAI (independent processor) and other providers exposed through Copilot Studio: review of Power Platform admin center settings governing external model usage, connector policies, and DLP rules At enablement and quarterly
Vendor risk register entry Third-party model providers documented in the institution's vendor risk inventory per OCC Bulletin 2023-17 lifecycle requirements Continuous
Incident response coverage Confirmation that the institution's incident response plan covers scenarios involving third-party model provider data breaches or service disruptions Annual review

Verification Criteria

  1. Tenant Geography Documented: Verify that the tenant's primary data location is documented and accessible to compliance
  2. Copilot Processing Location: Confirm that Copilot processing occurs within the tenant's provisioned geography (verify via Microsoft documentation or support confirmation)
  3. ADR Status: Verify ADR subscription status if contractual residency assurances are required
  4. Multi-Geo Configuration: For multinational firms, verify that users in each jurisdiction are assigned the correct preferred data location
  5. Data Flow Mapping: Confirm a Copilot data flow map exists that documents source, processing, output, and ancillary data locations
  6. Privacy Impact Assessment: Verify that Copilot is included in the firm's DPIA or privacy impact assessment (required for firms subject to GDPR or state privacy laws)
  7. Cross-Border Transfer Mechanisms: If data crosses borders, verify that appropriate transfer mechanisms (SCCs, DPF certification) are in place
  8. Vendor Risk Assessment: Confirm that Copilot data residency is documented in the firm's vendor risk assessment for Microsoft
  9. Review Cadence: Verify that data residency review is scheduled at the appropriate frequency (annually for Baseline, quarterly for Recommended, real-time for Regulated)
  10. Regulatory Examination Package: Confirm that data residency documentation is included in the firm's regulatory examination readiness materials

Additional Resources