Using New Outlook on Windows for personal email, calendar, and contact management
Escalate this through Outlook.com’s in-app support because the failure occurs in the cloud-backed People experience while newly created contacts remain deletable, so further Classic Outlook, CSV, or MFCMAPI repair is unlikely to affect the problematic records.
Submit an Outlook.com support case
- Sign in to Outlook.com with the affected Microsoft account.
- Select Help on the menu bar.
- Enter Couldn't delete imported contacts.
- If self-help does not resolve it, scroll to Still need help? and select Yes to contact Outlook.com support.^1^
- Include these details:
- Existing/imported contacts return “Couldn't delete contact.”
- Newly created test contacts delete normally.
- The affected or duplicate cards appear in Outlook.com and New Outlook, but not in Classic Outlook or CSV exports.
- The issue followed an export/re-import operation.
- Export/import and MFCMAPI deletion have already been attempted.
- Approximate date the issue started and two or three example contact names.
- Screenshots of the duplicate cards and deletion error.
Ask support to examine the account’s Outlook.com contact store and duplicate-contact aggregation state, rather than troubleshooting the local Outlook profile.
Do not perform another import while the case is being investigated; it can create additional contact records and obscure which entries are affected.
Why the views disagree
New Outlook and Outlook.com continuously process duplicate contacts. Exact duplicates and records that are proper subsets of another contact can be hidden rather than physically removed. Editing or deleting one underlying record can therefore cause another hidden record to appear.^2^
Microsoft documents that deleting a contact from New Outlook or Outlook.com should remove that contact and its hidden duplicates across Outlook clients.^2^ The documented People → select contact → Delete → Delete operation is supported for personal contacts.^3^ Because that operation fails only for the older/imported records, this is not expected duplicate-display behavior.
Classic Outlook and CSV exports not showing the same entries also means they cannot currently provide a reliable cleanup set. This is why repeating the Classic Outlook import workflow or additional MFCMAPI deletion is not appropriate here.
One conditional source-sync check
If the Microsoft account is also signed into Teams mobile, check:
Teams mobile → profile icon/Home → Settings → People → Sync my device contacts
If that switch is enabled, turn it off and allow several hours for synced device contacts to be removed before updating the support case. Microsoft previously documented Teams mobile contact synchronization as a cause of Outlook.com duplicates.^4^
That documented incident was fixed in 2023, so it should not be assumed to explain a newly started October issue. If Teams contact sync is absent or already disabled, proceed directly with support rather than using the old cleanup utility.
References