When your employer or school provides you with Microsoft products (like Microsoft 365 or Teams), your employer is in charge of your data, not Microsoft directly. This means your privacy rights in that context must be exercised through your employer, not Microsoft.
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
Employees and students using Microsoft products through their organization may not be able to exercise data rights (like deletion or access) directly with Microsoft and must instead go through their employer or institution, which may have different privacy practices.
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 →New clarification distinguishing Microsoft's role as processor versus controller in enterprise contexts, establishing that client organizations retain data control authority.
View full change record →If you use Microsoft products provided by your employer or school, Microsoft states it acts only as a data processor, meaning your organization controls your data and you must direct any data access or deletion requests to your organization rather than to Microsoft.
How other platforms handle this
At Ledger, earning and maintaining our users' trust is a top priority. That's why we are deeply committed not only to protecting your privacy and securing your personal data, but also to being fully transparent about how we handle it.
If you are located in the European Economic Area, Switzerland, or the United Kingdom, you have the right to access, correct, or erase your personal data; the right to restrict or object to our processing of your personal data; the right to data portability; and, where our processing is based on your...
We may display advertisements on our Services and those advertisements may be targeted to your interests based on your personal information. We may share your personal information with advertising partners for interest-based advertising purposes. You may opt out of interest-based advertising by visi...
Monitoring
Microsoft Azure has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"When we provide enterprise online services to an organization that has licensed these services from Microsoft, we act as a data processor for the organization, which is the data controller. In these cases, the organization determines the personal data Microsoft collects on its behalf and how that data is used. The privacy practices of the organization govern your use of Microsoft's products and services.— Excerpt from Microsoft Azure's Microsoft Privacy
(1) REGULATORY LANDSCAPE: This provision directly engages GDPR Articles 4, 24, and 28, which define controller and processor responsibilities and require data processing agreements between them. Under GDPR, data subjects have rights against the controller; where Microsoft is processor, the employer organization bears primary responsibility for responding to data subject requests. The UK GDPR mirrors these requirements. (2) GOVERNANCE EXPOSURE: High. The controller-processor delineation has significant operational implications for enterprise HR, IT, and legal teams responsible for data subject access request fulfillment and for demonstrating GDPR accountability. Errors in this delineation or gaps in data processing agreements could result in regulatory exposure for both the enterprise customer and Microsoft. (3) JURISDICTION FLAGS: This distinction is most consequential in the EU/EEA and UK under GDPR, but also engages U.S. state privacy laws that recognize similar distinctions between controllers and processors (service providers under CCPA). (4) CONTRACT AND VENDOR IMPLICATIONS: Enterprise procurement and legal teams must ensure a valid data processing agreement is in place with Microsoft that satisfies GDPR Article 28 requirements, specifies the scope of processing, and addresses sub-processor arrangements. Absence or inadequacy of such an agreement represents a direct compliance gap. (5) COMPLIANCE CONSIDERATIONS: Organizations should audit whether their Microsoft DPAs are current, whether they cover all Microsoft services in use (including new AI and Copilot products), and whether internal data subject request workflows correctly route employee requests to the organization rather than Microsoft.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
Ad personalization controls removed. Contact scanning added. Advertiser data partnerships quietly dropped. A timeline of every change.
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.
Employees and students using Microsoft products through their organization may not be able to exercise data rights (like deletion or access) directly with Microsoft and must instead go through their employer or institution, which may have different privacy practices.
If you use Microsoft products provided by your employer or school, Microsoft states it acts only as a data processor, meaning your organization controls your data and you must direct any data access or deletion requests to your organization rather than to Microsoft.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Microsoft Azure.