We use this behavior for team inbox conversations since many teammates may read a conversation before the assignee, and we wait to sync read status until the teammate handling the conversation reads it. Read status will only sync for individual (private) Office 365 channels, and for team conversations when marked as read by the assignee. Folders that couldn't be translated into tags will fall into the normal workflow in which a Front tag is created when a message belonging to the Office 365 folder comes into Front.

Tags that are created but not added to your sidebar are accessible through the tag menu.Front will add tags to your sidebar regardless of whether there is content in the tag.If you already have other tags added, then Front will add as many more as possible up to 500. Front will add up to 500 tags to your sidebar, retaining the original nesting structure.When you connect an Office 365 channel, Front will try to fetch as many folders as we can from Office 365.*See the FAQ Why isn't the read status syncing? for exceptions.įAQ How do Office 365 folders sync to Front exactly? Not imported initially, but will sync post-connection Optionally import 50K most recent messages upon adding inboxĬonversations archived by default and found in the Archived tab of team inbox.Ĭonversation read/unread and open/archived status mirrored in Front. Note that SMTP forwarding channels will not have history import and syncing.

Continue reading to understand the details of how history import and syncing work between Front and Office 365.įor the same information on Gmail channels, see here. The cases where status syncing will stop are explained here, which is to be expected since Front and Office 365 have different features, and thus why you are using Front. When you connect an Office 365 individual inbox or team inbox to Front, you will have the option to import your history and Front will maintain a two-way sync of statuses with Office 365 whenever possible.

How to sync office 365 with email