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.
The statement discloses that Microsoft collects biometric data, including fingerprint and facial recognition data, through Windows Hello for identity verification. Collection and use of biometric data is described as consent-dependent and product-specific.
This analysis describes what Microsoft Azure'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 authorization to collect and process biometric identifiers, a category of sensitive personal data subject to heightened regulatory requirements including Illinois BIPA, GDPR Article 9, and various U.S. state biometric privacy laws.
Interpretive note: The statement does not specify the retention period or destruction schedule for biometric data collected through Windows Hello, creating uncertainty about compliance with jurisdiction-specific biometric privacy laws that require such disclosures.
Microsoft now discloses that it may contact you by phone for marketing using automated dialers and AI-generated voices if you have consented to marketing communications, which represents a new disclosure of contact method and technology type. The company has also reorganized its data retention policy to state it retains data for broader business purposes including improving products and protecting systems, while removing previous specific examples and retention criteria, making it less clear exactly how long specific types of your data will be kept. You should review your consent settings for marketing communications and verify what contact methods you have authorized, particularly if you have concerns about automated or AI-generated calls.
View change record →Microsoft's privacy policy now provides a less detailed explanation of how long your data is retained. Previously, the policy included specific examples, such as how long deleted emails remain in your system before final deletion, and listed criteria for deciding retention periods. Now those details are consolidated into a more general statement pointing readers to separate product documentation. This means you'll need to consult multiple documents to understand retention timelines for specific services, which reduces transparency at the point of reading the main privacy policy.
View change record →Microsoft's updated retention policy provides greater specificity about how long your data persists and under what conditions it is deleted. The policy now explicitly states that deleted items from OneDrive and Outlook.com may remain in Microsoft's systems for up to 30 days before permanent removal, even after you empty the Deleted Items folder. Additionally, the updated terms clarify that retention periods depend on whether you have an expectation that Microsoft will keep the data until you actively remove it, and whether automated controls exist to let you access and delete data yourself. You can review Microsoft's privacy dashboard to exercise available deletion controls and understand which services retain your data under these criteria.
View change record →The agreement authorizes collection of biometric data including fingerprint and facial recognition data through Windows Hello for identity verification purposes. The statement indicates collection depends on user consent and the features used, though the specific consent mechanism and scope of biometric data retention are not fully detailed in the main privacy statement.
Cross-platform context
See how other platforms handle Biometric Data Collection (Windows Hello) and similar clauses.
Compare across platforms →Monitoring
Microsoft Azure has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"Biometric data. Unique data about you from specific technical processing related to your physical, physiological, or behavioral characteristics to verify or confirm your identity. For instance, you can use your fingerprint or facial recognition to sign in to your Windows device via Windows Hello (please see the Windows Hello section below for more information). Our collection and use of biometric data depends on the products and features you use and your consent.Excerpt from Microsoft Azure's Microsoft Privacy
1. REGULATORY LANDSCAPE: Biometric data collection implicates GDPR Article 9, which classifies biometric data as a special category requiring explicit consent or another qualifying condition for processing, enforced by EU Data Protection Authorities. In the United States, the Illinois Biometric Information Privacy Act (BIPA) imposes specific consent, retention, and destruction obligations for biometric identifiers and biometric information. Washington State's My Health MY Data Act and similar state laws may also apply. Texas and Washington biometric privacy statutes create additional obligations. 2. GOVERNANCE EXPOSURE: High. Biometric data represents a high-sensitivity data category under both EU and U.S. law. The statement's general reference to consent without specifying the mechanism, retention period, or destruction schedule for biometric data may create compliance gaps under BIPA and analogous state laws, which typically require written informed consent, a published retention and destruction schedule, and restrictions on disclosure. 3. JURISDICTION FLAGS: Illinois creates heightened exposure due to BIPA's private right of action and per-violation statutory damages. EU and EEA users are protected by GDPR Article 9 explicit consent requirements. Texas and Washington impose state-level biometric privacy obligations. Organizations deploying Windows Hello in Illinois or to Illinois residents should assess BIPA compliance posture. 4. CONTRACT AND VENDOR IMPLICATIONS: Enterprise customers deploying Windows Hello in workplace environments should assess whether employee biometric data processing under Windows Hello is governed by applicable enterprise agreements and whether those agreements include adequate BIPA-compliant consent, retention, and destruction provisions. Procurement teams should confirm that biometric data is not shared with third parties beyond what is disclosed. 5. COMPLIANCE CONSIDERATIONS: Legal teams should verify that Windows Hello deployment includes consent mechanisms that satisfy BIPA and applicable state law requirements, including written consent and published retention schedules. Data mapping should confirm that biometric data collected through Windows Hello is retained only for stated identity verification purposes and not used for AI training or advertising.
Full institutional analysis
Regulatory citations, enforcement risk, and due diligence action items.
Monitor: same-day alerts on the platforms you choose. Analyst: full institutional analysis.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision establishes Microsoft's authorization to collect and process biometric identifiers, a category of sensitive personal data subject to heightened regulatory requirements including Illinois BIPA, GDPR Article 9, and various U.S. state biometric privacy laws.
The agreement authorizes collection of biometric data including fingerprint and facial recognition data through Windows Hello for identity verification purposes. The statement indicates collection depends on user consent and the features used, though the specific consent mechanism and scope of biometric data retention are not fully detailed in the main privacy statement.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Microsoft Azure.