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 purchases demographic data and contact information from data brokers to supplement internally collected data. This purchased data is described as subject to the same practices outlined in the privacy statement plus any additional restrictions imposed by the source.
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 discloses a data enrichment practice that may implicate state data broker registration laws, GDPR transparency requirements regarding data sourced from third parties, and CCPA notice obligations regarding the categories of sources from which personal information is collected.
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 discloses that Microsoft supplements its first-party collected data with demographic and contact information purchased from data brokers. Under these terms, consumers may have their data processed by Microsoft even if they have not directly interacted with Microsoft products, as the data may have originated from a third-party data broker.
Cross-platform context
See how other platforms handle Data Broker Sourcing of Personal Data 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.
"We also receive data from Microsoft affiliates, subsidiaries, and third parties. We protect data obtained from third parties according to the practices described in this statement, plus any additional restrictions imposed by the source of the data. These third-party sources vary over time and include: Data brokers from which we purchase demographic data and contact information to supplement the data we collect.Excerpt from Microsoft Azure's Microsoft Privacy
1. REGULATORY LANDSCAPE: The purchase of personal data from data brokers implicates CCPA's notice-at-collection requirements, which require disclosure of the categories of sources from which personal information is collected. GDPR Article 14 requires that when personal data is obtained from a source other than the data subject, the controller must provide the data subject with specific information including the categories of data, the sources, and the purposes of processing. Several U.S. states including Vermont and California have enacted data broker registration laws. The FTC Act's prohibition on unfair or deceptive practices applies to the adequacy of these disclosures. 2. GOVERNANCE EXPOSURE: Medium. The disclosure is present but described at a category level without naming specific data brokers or specifying the categories of demographic data purchased. This level of disclosure may be insufficient under GDPR Article 14's granular transparency requirements. The statement that third-party sources vary over time further limits the specificity of the disclosure. 3. JURISDICTION FLAGS: California residents have CCPA rights regarding the categories of sources from which personal information is collected, and the adequacy of this disclosure warrants assessment. EU and EEA users are subject to GDPR Article 14 requirements, which may require more granular disclosure than this statement provides. Vermont's data broker registration law may require Microsoft to register as a data broker or to register data brokers from whom it purchases data. 4. CONTRACT AND VENDOR IMPLICATIONS: Enterprise procurement teams should assess whether data broker sourcing affects the integrity of data used in enterprise analytics or AI products. Data Processing Agreements with Microsoft should address the provenance of personal data used in enterprise services to confirm that data broker-sourced data is not commingled with enterprise customer data without authorization. 5. COMPLIANCE CONSIDERATIONS: Legal teams should evaluate whether the current level of disclosure regarding data broker sourcing satisfies GDPR Article 14 transparency requirements, including the obligation to identify categories of sources. Organizations should assess whether any regulatory notification obligations arise from the use of broker-sourced data in products or services subject to sector-specific privacy laws.
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 discloses a data enrichment practice that may implicate state data broker registration laws, GDPR transparency requirements regarding data sourced from third parties, and CCPA notice obligations regarding the categories of sources from which personal information is collected.
The agreement discloses that Microsoft supplements its first-party collected data with demographic and contact information purchased from data brokers. Under these terms, consumers may have their data processed by Microsoft even if they have not directly interacted with Microsoft products, as the data may have originated from a third-party data broker.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Microsoft Azure.