I have a client who is having issues with Office 365. They are accessing a local Outlook 365 client and any changes they make on their client are not being sync'd back up to Office 365. The changes they make are generally filing email away to sub folders or deleting them.
If they check on their phone, the inbox looks different and any change that was made is not shown. An admin assistance also has access to their mailbox (not cached) and they also do not see any changes.
I've been searching for some time on a possible solution to this but can only find reference to "local client not updating from cloud", which doesn't help as this is "cloud not updating from local client".
I've tried checking whether cached version is used (it is not), recreating the profile, whether Outlook is updating (account is selected in Send/Receive Group) and the end user can send/receive email fine, there is no delay there. The only issue appears to be changes they make aren't showing in Office 365. Anyone else come across this issue?
That's a new one on me, but the old support rule of divide and conquer should serve here as well as it usually does.
Things I would try;
* Rule in/out server-side issues = Have the user makes some changes on their phone and see if those are married up to their Office365 mailbox.
* Rule in/out Outlook/Office = Configure the users mailbox using the in-built Mail app in Windows 10. Check and see if the issue is reproducible. If, like me, you hate the in-built mail app, try Thunderbird instead.
* Rule in/out the mailbox = If the user is has access to a shared mailbox, make changes to that, and see if those are married up to Office365.
*Rule in/out the workstation itself = Recreate the users Outlook profile within another user profile on the same and/or a different workstation to see if it's reproducible.
Gut instinct is it's an upload issue, but those would typically manifest far more dramatically than what you're seeing. Also try Ctrl+Rightclick'ing the Outlook icon in the notification area. The "Connection Status" is usually typically fairly useless but it may shed some light in this situation.
Lastly, check there are no updates pending for Office itself.