Dynamics 365 includes native GDPR compliance modules. This page covers the specific configuration work required to meet GDPR obligations when Dynamics 365 is your core ERP or CRM platform — what the platform handles natively, what requires external tooling, and where the audit gaps typically appear.
Platform profile
| Attribute | Detail |
|---|---|
| Vendor | Microsoft Corporation |
| Category | ERP |
| Deployment | Cloud (SaaS) |
| Typical company size | SMB to Enterprise (10–5000 employees) |
| Implementation range | 4–18 months |
| Budget range | $80,000–$1,500,000 |
| Native compliance modules | SOX, HIPAA, GDPR, ASC 606 |
| Integration approach | Azure Integration Services; Power Automate; 300+ pre-built connectors |
Source: https://dynamics.microsoft.com/en-us/erp/
GDPR surface area in Dynamics 365
Dynamics 365 processes personal data across several functional areas. Each creates GDPR obligations that must be mapped before an implementation or audit:
ERP modules: Employee records (HR/HCM module) contain special category data — health, trade union membership, ethnicity where collected. Customer and supplier contact data sits in the procurement and sales modules. Financial records may include personal data where the counterparty is an individual.
The ROPA entry for Dynamics 365 must document: the categories of personal data processed, the purpose and lawful basis for each, the retention period, and the third-party processors who receive data from Dynamics 365 (integration partners, hosting infrastructure, support vendors).
What Dynamics 365 handles natively
Consent tracking: Dynamics 365 includes consent management fields that can be configured to record lawful basis per contact record. These are not a standalone CMP — they record the consent state but do not capture the notice version or timestamp in audit-grade format without additional configuration.
Data residency: Dynamics 365 is deployed on Cloud (SaaS). Cloud deployments offer EU data residency options — verify that your tenant is configured for EU data residency before go-live. This is a configuration choice made at provisioning; changing it post-implementation requires data migration.
Access controls: Role-based access control in Dynamics 365 limits who can read personal data. GDPR's principle of integrity and confidentiality (Article 5(1)(f)) requires that access to personal data is restricted to those with a legitimate need. Audit the role matrix against actual job functions — default role configurations are rarely correct for a GDPR-compliant data architecture.
Integration requirements for full GDPR compliance
Because Dynamics 365 includes GDPR compliance modules, the integration work focuses on extending native controls to connected systems.
| Requirement | Mechanism |
|---|---|
| Consent management | Native fields + CMP integration for web/email consent |
| DSAR workflow | Native DSAR module or connected privacy platform |
| ROPA population | Dynamics 365 data map exported to privacy platform |
| Erasure enforcement | API-triggered deletion across Dynamics 365 and connected systems |
| Breach notification | Incident log in GRC or privacy platform; Dynamics 365 as a source system |
| Audit evidence | Export from Dynamics 365 + privacy platform combined |
Integration approach for Dynamics 365: Azure Integration Services; Power Automate; 300+ pre-built connectors
Implementation considerations
Strengths relevant to GDPR: Deep Microsoft 365 integration; Power Platform for low-code customisation; strong partner ecosystem
Limitations relevant to GDPR: Module fragmentation (F&O vs Business Central vs Sales are separate SKUs); licensing can be complex
The hard part: For Dynamics 365, the most common GDPR implementation gap is erasure propagation. When a data subject requests erasure, Dynamics 365 can mark the record, but connected systems — email platforms, analytics tools, data warehouses — must also erase. Without an orchestrated erasure workflow that calls each connected system's API, the erasure is incomplete.
Audit preparation checklist for Dynamics 365
- ROPA entry for Dynamics 365 documented and current
- Lawful basis recorded per data category in Dynamics 365
- Access roles audited against data minimisation principle
- Data residency confirmed and documented (Cloud (SaaS))
- Processor agreement with Microsoft Corporation executed (Article 28)
- Erasure workflow tested across Dynamics 365 and all connected systems
- DSAR workflow covers all personal data held in Dynamics 365
- Breach detection and notification workflow includes Dynamics 365 as a source system
- Retention schedules configured and automated where possible
- Sub-processor list from Microsoft Corporation reviewed and documented