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 the operational scope of organizational control over accounts and data when users access Microsoft products through institutional credentials, clarifying that data governance and administrative authority rest with the organization rather than Microsoft in these configurations.
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 →The updated Privacy Statement removes previously stated language about additional rights available to European Economic Area users, narrowing the policy's explicit protections in that region. Simultaneously, the revised terms now explicitly authorize Microsoft to contact users via auto-dialer and prerecorded voice for marketing purposes, provided the user has consented to receive marketing communications to the phone number supplied. This establishes Microsoft's contractual permission to initiate automated marketing calls using artificial intelligence-generated voice technology where user consent to marketing contact has been given.
View change record →Users accessing Microsoft products through organizational accounts operate under administrative controls established by their organization, which retains authority over data access, account settings, usage monitoring, and setting modifications. The provision clarifies that Microsoft's privacy statement does not govern the organization's handling practices.
Cross-platform context
See how other platforms handle Products Provided by Employer/Organization — End User Notice 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.
"If you use a Microsoft product with an account provided by an organization you are affiliated with, such as your work or school account, that organization can: access and process your data, including the contents of your communications and files; control and administer your account and product settings; receive reports on your product usage; and control whether you can change certain settings. Microsoft is not responsible for the privacy or security practices of the organization, which may differ from this statement.— Excerpt from Microsoft's Microsoft Privacy Statement (Legacy)
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 the operational scope of organizational control over accounts and data when users access Microsoft products through institutional credentials, clarifying that data governance and administrative authority rest with the organization rather than Microsoft in these configurations.
Users accessing Microsoft products through organizational accounts operate under administrative controls established by their organization, which retains authority over data access, account settings, usage monitoring, and setting modifications. The provision clarifies that Microsoft's privacy statement does not govern the organization's handling practices.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Microsoft.