Skip to content

Control 2.7: Data Residency and Cross-Border Data Flow — Portal Walkthrough

Step-by-step portal procedures for verifying and configuring data residency controls for M365 Copilot processing.

Prerequisites

  • Entra Global Admin role
  • Microsoft 365 Admin Center access
  • Understanding of organizational data residency requirements
  • Legal and compliance input on cross-border data flow obligations

Steps

Step 1: Verify Tenant Data Location

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

Review the tenant's data residency configuration. Microsoft 365 stores data at rest in the geography associated with the tenant's provisioning country. Verify the data location for each workload (Exchange, SharePoint, Teams).

Step 2: Review Copilot Data Processing Location

Portal: Microsoft 365 Admin Center Path: Admin Center > Copilot > Settings > Data access

Review the tenant-level Copilot data access posture and cross-check Microsoft's published data processing commitments for your tenant geography. Verify the documented processing model meets your regulatory data residency requirements.

Document the data processing locations for each Copilot workload.

Step 3: Evaluate Microsoft EU Data Boundary or Advanced Data Residency

Portal: Microsoft 365 Admin Center Path: Admin Center > Settings > Org Settings > Data Residency

If your organization requires strict data residency, evaluate: - EU Data Boundary: For organizations subject to EU data regulations - Advanced Data Residency (ADR): For organizations requiring in-country data processing - Multi-Geo: For organizations with data residency requirements across multiple regions

Document which residency options are active and their scope.

Step 4: Assess Cross-Border Data Flow Risks

Document cross-border data flow scenarios specific to Copilot: - User in one region accessing content stored in another region - Copilot processing requests that reference multi-region content - Third-party plugins that may route data through external services - Microsoft support access and data handling during support incidents

Review each enabled AI provider in Microsoft 365 Admin Center > Copilot > Settings > View all:

  • Anthropic standard models: record that Anthropic operates as a Microsoft subprocessor, but the models are outside the EU Data Boundary and applicable in-country processing commitments.
  • Anthropic models with Data Retention: treat this as a separate independent-processor path governed by Anthropic terms; document retention, approved users/groups, and explicit risk acceptance.
  • SpaceXAI as an independent processor: treat this as an independent-provider path outside Microsoft-managed environments and Microsoft contractual residency commitments; document the xAI terms review and approved Copilot Studio environments (and Copilot Cowork use, where enabled).
  • SpaceXAI as a subprocessor (preview): record whether the separate subprocessor setting is enabled; Microsoft Product Terms and DPA apply except as disclosed, but these models are excluded from in-country processing commitments when applicable.

Step 5: Document Data Residency Compliance Position

Create a data residency compliance document that includes: - Tenant data location for each workload - Copilot processing location confirmation - Any cross-border data flow exceptions and justifications - Legal basis for any cross-border transfers (SCCs, BCRs, adequacy decisions) - Review cadence for data residency compliance

FSI Recommendations

Tier Recommendation
Baseline Verify and document tenant data location; confirm Copilot processing geography
Recommended Evaluate Advanced Data Residency for in-geography processing; document cross-border flows
Regulated Advanced Data Residency or EU Data Boundary enabled; formal cross-border transfer documentation; legal review of processing locations

Next Steps