D365 Task Status Was Reverting on Its Own — No Workflow, No Plugin, No Error
It Started With a Simple User Complaint
A user reported something strange — a Task status in Dynamics 365 kept changing back on its own after being updated.
No error on save. No warning. Nothing suspicious.
Just a status that refused to stay updated.
We Checked Everything
The usual suspects first:
Workflows — none triggered
Plug-ins — nothing registered on that entity
Business rules — checked and cleared
JavaScript — no relevant code found
Field security — not restricted
Power Automate flows — nothing relevant
Everything inside CRM looked completely clean.
The Clue That Changed Everything
The audit history showed the user's own name on the update. But the user swore they had not touched it since the initial save.
Even stranger — the timing was completely random. Sometimes it reverted in minutes. Sometimes hours.
That inconsistency was the real clue.
Root Cause: Outlook Server-Side Sync
The mailbox had Task sync enabled.
But the custom Task status we created was not recognised by Outlook. So during every periodic sync cycle, Outlook pushed its own Out-Of-The-Box status back into Dynamics 365 — silently overriding the CRM data with zero warning and zero error.
The trigger was sitting completely outside CRM the whole time. That is why nothing inside CRM gave us any clues.
The Fix
Disable Task sync on the affected mailbox.
One setting. Done.
Simple fix. Incredibly long investigation.
What I Took Away From This
When a D365 issue has no consistent timing, no error message, and no visible trigger inside CRM — look outside CRM first.
Server-Side Sync runs silently in the background and can override your data without leaving any obvious trace.
11 years in the D365 ecosystem… and it still finds new ways to surprise me.
Have You Seen This Before?
Has anyone else run into Server-Side Sync silently overriding CRM data? How did you eventually catch it?
Drop a comment below — I would love to hear your story.
I share real D365 field stories every week on this blog and on LinkedIn.