Native dedupe for Dynamics 365 CE

Yes. You can enable Deduplicate on both standard and custom entities. For each entity you decide which scenarios apply, which prevention features are active, and how merges should behave. That way, dedupe rules match your actual data model, not just core CRM tables.

No. Real‑time checks are optimized via the search index so users see fast suggestions while they work. For heavy clean‑up, DC Jobs run on Plauti Cloud or DC Local, processing large volumes outside Dynamics 365 and only sending back results, so everyday usage stays responsive.

Yes. You can configure per entity if Deduplicate should only warn users, block them from saving, or route records into a job for later review. For batch clean‑ups you can choose to merge, deactivate, or delete duplicates, with optional auto‑merge for straightforward matches.

Records created via API or imports are screened using the same scenarios you configure for manual entry. Potential duplicates are detected and handled according to your prevention settings, so new data from marketing, other CRMs, or custom apps doesn’t silently create duplicate records.

Yes. Deduplicate keeps an audit log that records merges, deactivations, and deletions, including who performed the action and when. This makes it easier to investigate issues, answer user questions, and meet compliance or auditing requirements.