## TL;DR

Dynamics 365 duplicate detection caught the account create. Review the duplicate, and either use the existing account or adjust the duplicate rule.

## Error

```text
Dynamics 365: duplicate record detected
```

## Steps

1. Review the flagged duplicate Expected: you see the existing account.
2. Use the existing account instead of creating Expected: no duplicate.
3. Or adjust the duplicate detection rule if it is too aggressive Expected: legitimate creates pass.
4. Re-run the create Expected: it succeeds.

## When to use

- Dynamics duplicate record detected
- The account already exists

## When not to use

- It is not a duplicate (then tune the rule)
- You need it anyway (then the rule may allow override with privilege)

## Tool compatibility

- Dynamics duplicate detection
- Account creates

## Variant phrasings

### dynamics duplicate record detected

Review the match. Use the existing account or tune the rule.

### duplicate account dynamics 365

Same: duplicate detection fired.

## Why it happens

Duplicate rules are fuzzy by design. Agents bulk-create and trip them constantly.

## Edge cases

- Rules run async too; duplicates can appear after the create
- Cross-entity rules catch account/contact pairs

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_hMrd41y2zgXJOnk-tka7kA