Microsoft 365 | Privacy Guide [UPDATED] | 11/16/26

Microsoft 365 | Privacy Guide

Microsoft 365 Data Protection Guide: Security, Compliance, and Governance

Many default settings in a new Microsoft 365 tenant are designed for collaboration, not data minimization. External sharing in SharePoint and OneDrive is set to the most permissive level, 'Anyone,' by default.

This guide shows you where to configure your tenant securely and in compliance with GDPR, from global organizational settings to individual services. Each section links to its own detailed guide.

Last updated on 16/11/2026. Microsoft frequently changes default values and deadlines, so we review this guide regularly. For critical changes, however, the official Microsoft documentation always takes precedence.

Organization settings

Basic settings in the Microsoft 365 Admin Center

Tenant-wide organization settings apply to all services. Any misconfiguration here will be inherited by every service, so these settings must be addressed before rolling out individual applications.

Microsoft 365 Admin Center | Organization settings

Services

Article 25 GDPR requires privacy by design. Therefore, do not adopt default settings without review. Exclude usernames from usage reports to prevent analyses from drawing conclusions about individuals, and disable 'Connected Experiences' that send content to Microsoft services if you do not need them.

Security and data privacy

Define which roles can access which data, and assign admin rights as restrictively as possible. Also check whether audit logging is enabled. Microsoft enables it by default, but it can be disabled. In Exchange Online PowerShell, you can check the status with Get-AdminAuditLogConfig | Format-List UnifiedAuditLogIngestionEnabled. The logs provide evidence during an audit of who accessed which data and when.

Organization profile

Keep master data and technical contact information up to date so that Microsoft can reach you in the event of a security incident. Under Article 33(2) GDPR, Microsoft, as a processor, must notify you of a data breach without undue delay, and this only works with an address that someone actually monitors.

Data privacy in services

Teams, SharePoint, Entra ID, and other services each have their own admin centers and default settings that are not covered by the organization-wide settings. The following sections list the settings you should review for each service before going live.

Microsoft Entra ID

Entra ID determines for every sign-in who can access which resource. An error here affects all other services.

  • Cross-tenant collaboration: Using Cross-Tenant Access Settings, you define which external organizations your users can collaborate with via B2B and whether you trust their MFA claims.
  • Directory synchronization: In hybrid operation with Entra Connect, you only synchronize the OUs, users, and attributes needed in the cloud. Each additional attribute represents another piece of personal data in the tenant, violating the data minimization principle under Article 5(1)(c) GDPR.
  • Data quality: Orphaned accounts remain sign-in capable until someone deletes them. Access Reviews automate regular checks but require Microsoft Entra ID P2 or Entra ID Governance. Without this license, you need a script or a fixed review date.

Microsoft Teams

Teams stores chats, files, meeting recordings, and transcripts, which often means it holds the largest volume of personal data in the tenant.

  • Creation and lifecycle: Every Team is a Microsoft 365 group. Therefore, you control who can create Teams via the group settings in Entra ID. An expiration policy for groups regularly asks owners whether a team is still needed, thus preventing orphaned teams filled with legacy data.
  • Guest access: Only grant guests access to the Teams they collaborate in, and enforce MFA for them via a conditional access policy.
  • Employee training: No setting can prevent someone from posting a customer list in the wrong chat or recording a meeting without notice. Training on chats, file sharing, and recordings reduces this risk.

Microsoft SharePoint

Files from Teams channels are technically stored in SharePoint, while files from chats are stored in OneDrive. The sharing settings here therefore determine which documents can leave the company.

  • External sharing: 'Anyone' links work without authentication and can be forwarded freely. Restrict or disable them, and set an expiration date for external links.
  • Data Loss Prevention: A DLP policy detects sensitive information types such as credit card numbers or ID numbers and blocks their sharing. Internal identifiers like employee numbers are only recognized if you create a custom information type for them.
  • Permissions: Regularly check where libraries or folders have broken inheritance. Individual permissions accumulate there, which no one can trace after a few years.

Microsoft 365 Copilot

Copilot finds everything via Microsoft Graph that the logged-in user has access to. An overly shared library that no one has searched for before will appear in the response at the first matching prompt (oversharing).

  • Data access: Clean up permissions before rollout (Just Enough Access). Copilot does not expand rights, but it makes overly broad permissions immediately usable.
  • Confidentiality labels: A label like 'Strictly Confidential' alone does not prevent Copilot from accessing a document. You only block Copilot via the label itself if it is encrypted and the user lacks the EXTRACT usage right. New content that Copilot creates from labeled files inherits the label with the highest priority.
  • DLP for Copilot: A DLP policy for the Microsoft 365 Copilot location excludes files with specific labels from processing, even without encryption. This is the approach when users are allowed to open a file, but Copilot should not analyze it.

Microsoft Purview

Purview operates across services. Labels, DLP policies, and monitoring apply to Exchange, SharePoint, OneDrive, and Teams simultaneously, rather than being configured per app.

  • Information Protection: Classify documents with sensitivity labels and automatically encrypt them if required. The encryption stays with the file, even if it leaves the tenant.
  • Audit and eDiscovery: Audit (Standard) retains logs for 180 days. Audit (Premium) stores entries from Entra ID, Exchange, OneDrive, and SharePoint for one year by default, with an add-on license extending this to ten years. Configure retention based on how long you need to provide information after a data breach (Article 33 GDPR) or in legal proceedings.

Microsoft Exchange Online

Even with Teams, email remains a central attack vector for phishing and ransomware.

  • Protection against attacks: Strictly configure anti-phishing and anti-malware policies, for example using the preset security policy 'Strict'. This prevents spoofed CEO fraud emails and malicious attachments from reaching the inbox in the first place.
  • Authentication with SPF, DKIM, and DMARC: Without these DNS records, anyone can send emails using your domain as the sender, and recipients are more likely to classify your legitimate emails as spam. Start DMARC with p=none, evaluate the reports, and then increase to quarantine or reject.
  • Outdated authentication: Microsoft disabled Basic Authentication for EAS, POP, IMAP, EWS, and PowerShell in Exchange Online back in 2022. Only SMTP AUTH remains open. At the end of December 2026, Microsoft will disable Basic Authentication for this by default in existing tenants; admins can temporarily re-enable it afterward. Microsoft plans to announce the final deactivation date in the second half of 2027. Since Basic Authentication bypasses MFA, any account sending via password over SMTP AUTH is a target for password spraying. Therefore, check the SMTP AUTH clients report in the Exchange Admin Center now, switch printers, scanners, and applications to OAuth or a relay connector, and then disable SMTP AUTH organization-wide (Set-TransportConfig -SmtpClientAuthenticationDisabled $true). Disable POP and IMAP for all mailboxes that don’t need them using Set-CASMailbox.

More information

Microsoft documentation

Changelog

23.09.2023Publication of the Data Protection Guide. Initial version focusing on secure baseline configuration of SharePoint Online (sharing permissions and access protection), Microsoft Teams (policies for external communication and guest access), and Entra ID (identity protection and security defaults).
10.04.2024Update: Existing content adjusted to changed Microsoft default settings, new hardening recommendations added, data protection notices editorially revised.
28.09.2024Update: Existing content checked against changed Microsoft settings.
19.03.2025Expansion: Microsoft 365 Copilot – New chapter on the introduction and securing of AI assistants. Focus areas include licensing, prerequisites for the Semantic Index, and privacy-compliant provisioning for end users.
01.09.2025Expansion: Microsoft Purview – Information Protection, configuration of sensitivity labels, and DLP for Copilot added.
14.09.2025Update: Terminology standardized, outdated screenshots replaced following UI changes in the Admin Center.
20/12/2025Update: All linked Microsoft sources verified for validity; PowerShell commands adjusted to new modules and deprecated functions.
21/12/2025Restructuring: Landing page layout and formatting revised.
25/12/2025Expansion: Microsoft 365 Copilot settings moved to a dedicated article and extended.
25/12/2025Enhancement: Exchange Online Hardening – SPF, DKIM, DMARC, phishing and spoofing protection (External Tagging, Anti-Spam), transport path hardening (SMTP AUTH deactivation, TLS 1.2 enforcement).
16/11/2026Fact-check: Corrected Copilot section (labels block Copilot only with encryption without EXTRACT rights or via DLP policy), adjusted Exchange section to SMTP AUTH deprecation timeline (27/01/2026), added retention periods for monitoring and license requirements for Access Reviews.

PhinIT article

Share:
No comments yet

Be the first to start the discussion with a helpful comment.

Leave a comment

Comments are reviewed briefly before they are published — factual, respectful and to the point is just right here.

Your email address will not be published.