skip to content »

Outlook not updating other users folder

outlook not updating other users folder-20

SIU updates your sent messages with signatures after processing by the program.In this article you will learn more about this feature.

The service is totally independent of your mail flow and the functioning of your Office 365 tenant, which means it has no influence on your email processing and delivery time. Moreover, Sent Items Update does not require any service accounts to operate as the entire authentication and authorization process uses OAuth 2.0.The Sent Items Update works as a separate service and is installed along with the Code Two Email Azure Service.SIU needs to be registered in your tenant's Azure Active Directory in order to update Sent Items in the mailboxes of your users.If a user has any OWA/Outlook rules enabled that instantly move messages from the Sent Items folder to another location (including the subfolders of the Sent Items folder), the SIU service will not be able to find and process them.If possible, execute such rules manually or with a delay, to allow some time for the SIU service to update your sent emails.As each attendee receives an email message with calendar appointment information, their email and calendaring client reads the message and updates their individual copy of the meeting on their personal calendar.

Some best practices are listed below: Microsoft Outlook, OWA (Outlook Web App) and the Outlook mobile app are the recommended clients.

What matters is the fact that even though you only see one signature in the Sent Items folder, your recipients get the right signature (internal or external), based on their affiliation.

If you enabled message copying in your Exchange Online, the Sent Items Update works with messages sent by users with delegate (Send As or Send on Behalf) rights to other mailboxes.

Important If you use Microsoft Outlook, emails in your Sent Items folder might not always be refreshed and displayed correctly.

This is usually caused by Outlook's default behavior in the Cached Exchange mode, and is not related to the SIU service.

See this article to learn how to solve this problem.