OpenAI Failover Cross-Regional Routing

What it is

This provision states that if OpenAI's services experience a failover event, Customer Data will be temporarily redirected to a Microsoft Azure endpoint, with the document noting that regional priority is subject to availability rather than guaranteed.

Why it matters (compliance & governance perspective)

This provision establishes a conditional cross-regional data routing mechanism that activates automatically during failover events without requiring a separate customer election. For customers with contractual or regulatory data residency obligations, the 'subject to availability' qualification on regional priority introduces uncertainty about whether data residency commitments are maintained during failover periods.

Consumer impact (what this means for users)

Under this clause, Customer Data processed through OpenAI-integrated features may be temporarily routed to Microsoft Azure infrastructure during failover events. The agreement states that regional priority is given to the customer's provisioned region subject to availability, meaning residency cannot be guaranteed during such events.

Institutional analysis (Compliance & governance intelligence)

(1) REGULATORY LANDSCAPE: This provision implicates GDPR Chapter V international data transfer requirements and equivalent frameworks in jurisdictions including the UK, Switzerland, South Korea, and Brazil, where transfers to third countries require an appropriate legal mechanism. If a failover routes data to a Microsoft Azure region outside the customer's contracted jurisdiction, the adequacy of the transfer mechanism for that routing path requires evaluation. The relevant enforcement authorities are EU national data protection authorities and the UK ICO. (2) GOVERNANCE EXPOSURE: Medium. The provision introduces a conditionally triggered cross-regional transfer that may not be covered by the customer's primary data transfer impact assessment if that assessment assumes fixed processing locations. The 'subject to availability' qualification on regional priority means the actual routing destination during a failover event may not be deterministic at the time of contract execution. (3) JURISDICTION FLAGS: Heightened exposure exists for customers in EU and EEA jurisdictions, the UK, Switzerland, South Korea, and Brazil, all of which impose restrictions on transfers outside their respective adequacy or equivalence frameworks. Customers in these jurisdictions should evaluate whether their DPAs and transfer mechanisms explicitly cover conditional Azure failover routing. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement and legal teams should assess whether existing Data Processing Agreements with Salesforce explicitly authorize this failover routing mechanism and whether the Microsoft Azure sub-processor relationship is covered under the applicable DPA's sub-processor authorization provisions. The conditional nature of the transfer may complicate standard transfer impact assessment documentation. (5) COMPLIANCE CONSIDERATIONS: Compliance teams should document this provision in their records of processing activities as a conditional cross-regional transfer pathway, ensure that transfer impact assessments account for failover routing scenarios, and confirm that the Microsoft Azure endpoints implicated are covered by the organization's applicable transfer mechanisms.

Applicable agencies

Provision details

Other risks in this policy

• Global CDN Data Processing Designation medium
• Sub-processor Notification Subscription Mechanism medium
• Feature-Triggered Sub-processor Activation and Cross-Regional Data Flows medium
• Customer Data Regional Selection and Region-Affecting Interdependencies low
• Identifying Information Storage Outside Provisioned Region medium
• Middle East Data Routing to European Union medium