Microsoft 365 includes security features whose effect depends on licensing, configuration and operating processes. A feature alone does not make a tenant secure.
Identity and access
Enable phishing-resistant authentication for privileged accounts where your environment supports it. Roll out Conditional Access step by step: document exclusions, test policies in report-only mode and keep emergency access. SMS-based MFA is better than no additional check, but it does not offer the same protection as phishing-resistant methods.
Continuous Access Evaluation (CAE) can enforce supported events and policies promptly; it does not apply equally to every application and every access. Plan tests for clients, resources and networks.
Protecting data
Start with an inventory of sensitive content. Purview DLP can detect or block activities depending on the workload and policy; test with sample data and review exceptions. Sensitivity labels can be applied manually or, with the appropriate features and licences, automatically. Automatic classification needs quality control.
Insider risk and privacy
Insider Risk Management requires prerequisites, roles and a configured policy. Pseudonyms are enabled by default for certain roles, but administrators can change the privacy setting; exports can contain names. Define purpose, access, retention and the investigation process transparently.
Swiss data location
Microsoft documents data locations by service and data type. Copilot is subject to its own conditions and exceptions. Determine for your tenant which workloads and interactions are covered and where further processing takes place. A data centre in Switzerland replaces neither a data-flow review nor the assessment of your obligations under the Swiss FADP.
Next steps
Prioritise accounts with high privileges, fix oversharing and review recovery and logging. For each control, record an owner, licence, test and fallback plan.
Sources: Microsoft: privacy settings in Insider Risk Management · Microsoft: where Microsoft 365 data is stored

