M365 | COMPLIANCE
Reduced attack surface, greater control. This guide shows you how to configure your M365 tenant in a GDPR-compliant and secure manner: from global organizational settings to the depths of individual services. Without compromising productivity or protection.
Jump to the right sectionTable of contents

Organization Settings
Anyone administering Microsoft 365 will eventually end up in the same place: organizational settings. A change here immediately affects all users. Before rolling out individual tools, the foundation must be solid.

Services
The 'Services' tab controls what users are allowed to do in your tenant. Feature flags for Teams, Exchange Online, Planner, Forms, and other workloads are set globally here before specialized admin centers apply more granular adjustments. What is enabled here serves as the baseline for the entire tenant.

Security & Data Protection
Password policies, external sharing settings, and self-service capabilities: The foundation of tenant security doesn't lie in Defender, but here. Microsoft's defaults are designed for compatibility, not protection. Those who don't actively correct this are giving up control.

Organizational Profile
Data storage locations, visual designs, support information, and release preferences: The organization profile is more than just a business card. Whether new features are rolled out immediately across the tenant or first go through a pilot group—you decide here.

Data Protection in Services
The security framework is in place—but that’s just the beginning. Once the global settings are configured, we dive deep into the individual areas.

🔐 Microsoft Entra ID
Cross-tenant collaboration: Secure B2B scenarios. Use Cross-Tenant Access Settings to precisely control which external companies you share data with.
Directory synchronization: If you're running hybrid (Entra Connect), prioritize data minimization. Only sync the attributes and users that truly need to be in the cloud.
Data quality: Stale accounts are a security risk. Regular Access Reviews are mandatory.

💬 Microsoft Teams
The hub of collaboration—and often the largest data repository.
Team & Channel Management: Prevent sprawl. Clearly define who is allowed to create new teams (lifecycle management) so you don’t end up managing thousands of abandoned data graveyards.
Guest Access: Collaboration yes, but controlled. Ensure guests only have access to what they need and are required to use MFA.
Employee Training: Technology is only half the battle. Educate your users on handling chats, file sharing, and recordings.

📂 Microsoft SharePoint
This is where your documents reside. Managing permissions is key here.
External sharing: The biggest risk. Restrict "share with anyone" (anonymous links) and set expiration dates for external links.
Security measures: Use Data Loss Prevention (DLP) to block accidental sharing of credit card data or personal identification numbers.
Permission audit: Regularly review inherited permissions on libraries. "Less is more."

🤖 Microsoft Copilot
AI amplifies everything—including your security gaps. Copilot finds anything the user has access to (oversharing problem).
Control data access: Before enabling Copilot, clean up your permissions (Just Enough Access). Copilot respects existing rights—if they’re too broad, the AI sees too much.
Security measures: Use Sensitivity Labels. A document marked as "Highly Confidential" won’t be used by Copilot for responses.
Protection: Prevent copy-paste errors with DLP in Copilot responses.

🛡️ Microsoft Purview
The command center for your compliance. Here, you move beyond individual apps and deploy a protective layer across all your data.
Information Protection: Know your data. Use Sensitivity Labels to classify documents and—if necessary—automatically encrypt them, no matter where they reside.
Audit & eDiscovery: Who did what and when? Ensure audit logs are retained long enough to remain provable and responsive in the event of a data breach or legal dispute.

📧 Microsoft Exchange Online
The reports of its death are greatly exaggerated. Even in the age of Teams, email remains the number one entry point for ransomware and phishing attacks.
Protection against attacks: Harden your defenses. Configure anti-phishing and anti-malware policies strictly to protect users from malicious attachments and fake CEO emails.
Authentication (SPF/DKIM/DMARC): No dispatch without ID. Protect your domain reputation from abuse (spoofing) and ensure your legitimate emails don’t end up in customers’ spam folders.
Outdated protocols: Close the backdoors. Disable legacy authentication (IMAP/POP) globally to thwart brute-force password attacks.