A previously synced task can disappear from Exchange when it stops matching the user's filter, even while it still exists in Dynamics 365.
Key takeaways
- Confirm that the missing item is a task and still exists in Dynamics 365.
- Compare one rep's filter results with the tasks in that rep's Exchange mailbox.
- Check whether the missing task previously synchronized before testing the Delete action.
- Record the filter result and the record's existence separately.
Who these sync rules cover
This guide is for revenue leaders who run Dynamics 365 and see follow-up tasks disappear from reps' Exchange mailboxes after deals change. A missing task can hide the next step on a deal you are counting on, so it deserves a traceable explanation rather than a guess.
The main source is a Microsoft page on synchronization logic for appointments, contacts, and tasks, according to Microsoft. Its rules cover Dynamics 365 and Exchange, so they do not describe other systems. Read a different product's own documentation before applying these rules to it.
Your follow-up tasks are the records to trace first. Keep one line for each side in your notes, so a gap stands out during review. For a broader task review, use these sales follow-up checks.
Default two-way sync
Two-way sync by default
The rule names appointments, contacts, and tasks as synced both ways between Dynamics 365 and Exchange by default, according to Microsoft. Because several record types are named, a task is covered as a record type, not as an exception. Start your note with the record type of the missing item.
The phrase both ways describes the direction of the sync between Dynamics 365 and Exchange, according to Microsoft. Record which system showed each change, so the direction can be tested against one specific record rather than a memory of it. Write down what you saw in each system.
Confirm first that the task exists in Dynamics 365 for the rep who owns it. The later sections describe what happens after that starting point.
The default rule is about direction, not inclusion. Inclusion comes from the synchronization filter, according to Microsoft. When a task is missing, ask first whether its record type is named in the rule, then ask whether it meets the filter.
Your first look should be one Dynamics 365 task record for one rep, with the record name, the owner and the last change date written down. That single record becomes the test case for every check that follows, which keeps the review from drifting across many items. If the record type is confirmed but the task still does not appear, the next question is the filter for that same user. Separating those two questions keeps the review from circling.
Create action on first filter match
The filter is the gate that decides which records reach Exchange. Synchronization filters determine the records that sync from Dynamics 365 to Exchange using server-side synchronization, according to Microsoft. Name the user whose filter you are checking before any comparison begins.
The source reads, "When a Dynamics 365 record meets a user's synchronization filter criteria for the first time, the record is synchronized as a Create action to the target user's Exchange mailbox," according to Microsoft. Your review should ask whether the record ever met that user's filter for the first time. A record that never matched raises a different question.
For your review, the target user is the rep whose mailbox you are checking. Keep the rep's name beside the record name so the filter check and the mailbox check point at the same person.
Your notes should hold the filter result for one rep in a short list. List each task record that the filter currently returns, then compare that list with the tasks in the rep's mailbox. Any gap is a question to investigate, not a finding about deletion.
Note the date you first saw each record in the rep's mailbox, so new records can be separated from old ones during review. Repeat the same list at the next review, using the same user and the same filter. Comparing the two lists shows which records the filter returned at each point, so a change in the list becomes visible.
Check the filter before checking the mailbox for that record.
Update action on later changes
After a record has synced, later edits fall under a different action name, according to Microsoft. Split your review into the first sync and the later changes. Mark each observation in your notes with its stage.
The source reads, "Subsequent updates to the record in Dynamics 365 are synchronized to the corresponding Exchange item as an Update action," according to Microsoft. The quote names the corresponding Exchange item as the target, so a missing item is a different case from an update.
The word subsequent is the check to make. Your question is whether the record had already reached Exchange before the edit, since the source ties this action to subsequent updates, according to Microsoft. Write the edit date beside the first sync date in your notes.
Your comparison should set the Dynamics 365 record beside the Exchange item after a change. Note whether the item shows that change and the time you looked, so the observation can be repeated later. A change visible on one side but not the other is a prompt to re-check the filter, not a final answer.
Your notes should hold a short history of the last change you saw for each task. That history helps you decide whether to test the Create action or the Update action first. Entries kept in the same place each time are easier to compare than memory during a dispute.
If an update does not appear, record the filter result for that user on the same day. That pairing turns a single missing change into a dated comparison you can take to the rest of the team. An edit to a task that never reached Exchange belongs in the Create question instead. Sort each task into one of those two groups before you compare.
Delete action and logically deleted records
Delete action when the filter no longer matches
The Delete action applies when a record that was synced stops meeting the filter, and its wording is precise. The quote reads, "When a Dynamics 365 record that was previously synchronized to Exchange no longer meets the user's synchronization filter criteria, the Dynamics 365 record is synchronized as a Delete action to Exchange," according to Microsoft.
The sentence sets two conditions: the record was previously synchronized to Exchange, and it no longer meets the user's synchronization filter criteria, according to Microsoft. Your review should test the earlier condition first, then the filter. The earlier condition is easy to overlook when a task never appeared in Exchange at all.
A Delete action should not be read as removing the record from Dynamics 365, since the rule names Exchange as the place it is synchronized to, according to Microsoft. Your notes should state the Dynamics 365 record on one line and the Exchange item on a separate line.
Logically deleted records still existing in Dynamics 365
The source describes a logically deleted record as one that still exists in Dynamics 365 but is no longer returned by the user's synchronization filter, according to Microsoft. The same source says the Delete action can occur for records that are physically deleted and for records that are logically deleted, according to Microsoft.
Your check is whether the record still appears in Dynamics 365 and whether the filter still returns it. If the record exists but the filter does not return it, the mailbox gap fits the logical case. If the record is gone entirely, the physical case becomes the question.
Your notes should keep both answers on separate lines before you decide which case applies. Recording both answers stops one assumption from standing in for the remaining question.
As an editorial recommendation, examine the logical case first when the record still appears in Dynamics 365. Write down the filter result and the record status for the same user on the same day. A dated pair of observations is easier to act on than a general sense that the task is gone.
Reassigning a row to another user
The reassignment example in the source uses a contact row, not a task. The example reads, "Later, Paul re-assigns the contact row in Dynamics 365 to Laura," according to Microsoft. Write the old owner and the new owner side by side in your notes.
The rule that matters is the user's synchronization filter criteria, according to Microsoft. Your check should compare whether the new user's filter returns the record and whether the previous user's filter still returns it.
The example is about a contact row, so a task should not be assumed to follow the same path without checking. Reassigning a contact and reassigning a task are different records, so each needs its own note. Treat the example as a pattern to test rather than a result.
Close's help page advises deleting tasks, in the words "Delete Tasks that are no longer relevant to keep your workflow clear," according to Close. In HubSpot, the path to tasks is to click More, then navigate to CRM > Tasks, according to HubSpot.
Keep those pages apart from the Dynamics 365 check, and keep each vendor's page under its own heading in your notes.
Illustrative example: compare the filter results
At an earlier review, a task appeared in the rep's mailbox. Today, it is missing. Check the task record and the same user's filter: the record still exists, but the filter no longer returns it. Record the earlier mailbox observation, today's filter result and the record's existence separately. This fits the logical case described above; it does not establish why the filter result changed.
Related guides
For other follow-up checks, see how to log seller emails to the right deal and review due date checks for sales follow-ups.
Next step
Your next step today is to check the synchronization filter for one rep's mailbox and list which task records it currently returns.
Related guides: Activity linking: 8 rules for deals and visibility · AI call scorecard checks: 5 rules before the forecast · Check 8 data rules before the weekly sales call.
FAQ
Are tasks synced both ways by default?
Yes, tasks sync both ways between Dynamics 365 and Exchange by default, according to Microsoft. Your first check is whether the record type falls under the rule. Keep the direction question separate from the filter question.
What makes a record sync as a Delete action?
A record previously synchronized to Exchange triggers a Delete action when it no longer meets the user's synchronization filter criteria, according to Microsoft. Your next check is whether the filter still matches that record. The Dynamics 365 record is the item to compare with the filter result.
What is a logically deleted record?
A logically deleted record still exists in Dynamics 365 while the user's synchronization filter no longer returns it, according to Microsoft. Your first check is whether the record still exists in Dynamics 365. Compare that result with the filter for the same user.
What happens on the first filter match?
The first match leads to a Create action in the target user's Exchange mailbox, according to Microsoft. Your check is whether that first match happened for the user whose mailbox you are reviewing. Record the date of that first match in your notes.
What should I check first when a task is missing?
Your first check is the record type, because the rule names appointments, contacts, and tasks, according to Microsoft. Then review the direction, and finish with the filter result for the rep. Your notes should keep each check on its own line so the gap is easy to trace.
Does this article give a sync delay time?
No sync delay time appears in this guide, so the checks rely on records and filters rather than timing. Use the record and filter checks above to explain the missing task. Your notes should record the date and time of each look, so later comparisons are dated.
Does Close or HubSpot sync tasks with Exchange?
Use each product's own documentation to check its Exchange sync behavior. The Exchange sync rules in this guide come from the Microsoft page.