Get the weekly research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean. No account.
Microsoft certifies compliance with the EU-U.S., UK Extension, and Swiss-U.S. Data Privacy Frameworks, subjecting it to FTC enforcement and onward transfer liability for agent processing. Residual complaints not resolved through other mechanisms may proceed to binding arbitration under DPF Principles.
This analysis describes what Microsoft's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision establishes Microsoft's legal mechanism for cross-border personal data transfers from the EU, UK, and Switzerland to the United States. It also establishes that Microsoft retains liability for onward transfers to third-party agents, and that binding arbitration is the final dispute resolution mechanism for DPF-related complaints that cannot be resolved through other channels.
Interpretive note: The legal durability of the EU-U.S. DPF adequacy decision remains uncertain given the history of CJEU review of prior EU-U.S. transfer mechanisms, and reliance on this mechanism may require reassessment if the adequacy decision is challenged or invalidated.
The updated privacy statement removes the previous detailed list of third-party sources from which Microsoft obtains personal data, including data brokers, public social media posts, location service providers, co-branded partners, and developers. Under the revised language, Microsoft describes obtaining data from 'Microsoft affiliates, subsidiaries, and third parties' without specifying the categories or types of third parties as explicitly as before. The company states it has reorganized the document for greater clarity and accessibility, but the operational effect is that users receive less specific disclosure about where their data originates from outside Microsoft.
View change record →The updated policy establishes additional grounds on which Microsoft may retain personal data. While the prior version tied retention to specific user expectations and available deletion controls, the revised language authorizes retention for 'operating our business, meeting our contractual and legal obligations, improving and developing our products and services, protecting the safety and security of our systems and customers, and resolving disputes.' This expands the stated purposes beyond transaction fulfillment and legal compliance. The updated policy directs users to product-specific documentation for retention details rather than providing explicit deletion procedures and timelines in the privacy statement itself.
View change record →The updated policy now grounds data retention in five broad business purposes: operating the business, meeting contractual and legal obligations, improving and developing products and services, protecting system and customer safety, and resolving disputes. Previously, the policy articulated specific criteria for determining retention periods, including customer expectations for retention until manual deletion, availability of automated deletion controls, and data sensitivity. The revised language removes these granular criteria and instead requires users to consult individual product documentation to understand when their specific data will be deleted. This shifts the burden of finding retention timelines from the main policy statement to separate product-specific documents.
View change record →Under this provision, EU, UK, and Swiss individuals whose data is transferred to the U.S. under the DPF may escalate unresolved complaints to binding arbitration after first contacting Microsoft, then the relevant data protection authority or panel. Microsoft's DPF certification is publicly listed at the U.S. Department of Commerce's Data Privacy Framework website.
Cross-platform context
See how other platforms handle Data Privacy Framework Certification and Binding Arbitration and similar clauses.
Compare across platforms →Monitoring
Microsoft has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"Microsoft Corporation complies with the EU-U.S. Data Privacy Framework (EU-U.S. DPF), the UK Extension to the EU-U.S. DPF, and the Swiss-U.S. Data Privacy Framework (Swiss-U.S. DPF) as set forth by the U.S. Department of Commerce. As further explained in the DPF Principles, binding arbitration is available to address residual complaints not resolved by other means. Microsoft is subject to the investigatory and enforcement powers of the U.S. Federal Trade Commission (FTC). In the context of an onward transfer, Microsoft Corporation has responsibility for the processing of personal data it receives under the DPF and subsequently transfers to a third party acting as an agent on our behalf.Excerpt from Microsoft's Privacy Statement (Legacy)
(1) REGULATORY LANDSCAPE: This provision engages the EU-U.S. Data Privacy Framework, UK Extension, and Swiss-U.S. DPF as cross-border transfer mechanisms, each of which is certified by the U.S. Department of Commerce and subject to FTC enforcement. The GDPR (Chapter V) governs international data transfers and requires that transfers to non-adequate countries rely on approved mechanisms. The European Commission's adequacy decision for the EU-U.S. DPF is subject to ongoing review by the CJEU, and its legal durability is uncertain following the Schrems I and Schrems II decisions. The FTC has direct enforcement authority over DPF compliance obligations. (2) GOVERNANCE EXPOSURE: Medium. DPF certification provides a recognized lawful transfer mechanism, but the DPF's legal durability under EU law remains a risk factor given prior adequacy decisions being invalidated by the CJEU. Organizations relying on Microsoft's DPF certification as a transfer mechanism should maintain supplementary safeguards such as standard contractual clauses as a contingency. (3) JURISDICTION FLAGS: EU/EEA, UK, and Swiss individuals have the greatest exposure, as DPF invalidation would disrupt the legal basis for their data transfers. Organizations in regulated sectors (financial services, healthcare) may face heightened scrutiny of cross-border transfer mechanisms from sectoral regulators in addition to data protection authorities. (4) CONTRACT AND VENDOR IMPLICATIONS: Enterprise customers relying on Microsoft's DPF certification for EU-to-U.S. data transfers should confirm whether their specific Microsoft products and data flows are covered by the certified DPF scope, as listed in Microsoft's self-certification submission. Vendor assessment procedures should document the onward transfer liability chain, including Microsoft's stated responsibility for third-party agent processing. (5) COMPLIANCE CONSIDERATIONS: Legal teams should monitor CJEU proceedings and European Commission reviews of the EU-U.S. DPF adequacy decision, and maintain standard contractual clauses or other alternative transfer mechanisms as a contingency. DPF complaint resolution procedures, including escalation to relevant EU DPAs, UK ICO, and Swiss FDPIC, should be documented in data subject rights response procedures.
This provision establishes Microsoft's legal mechanism for cross-border personal data transfers from the EU, UK, and Switzerland to the United States. It also establishes that Microsoft retains liability for onward transfers to third-party agents, and that binding arbitration is the final dispute resolution mechanism for DPF-related complaints that cannot be resolved through other channels.
Under this provision, EU, UK, and Swiss individuals whose data is transferred to the U.S. under the DPF may escalate unresolved complaints to binding arbitration after first contacting Microsoft, then the relevant data protection authority or panel. Microsoft's DPF certification is publicly listed at the U.S. Department of Commerce's Data Privacy Framework website.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Microsoft.