Hiver and Outlook: what syncs, what doesn't, and how to set it up
Hiver Omni syncs an Outlook shared mailbox, distribution list or Microsoft 365 group into a Hiver Shared Inbox. One Source User account carries the sync, and it stops if that account loses access.
- Connector
- Native connection built by Hiver inside Hiver Omni, paid, authorized with a Microsoft sign-in and Entra consent
- Sync direction
- Two-way for email: incoming mail syncs to Hiver, replies send from the Outlook address; folders import once
- Setup time
- Admin steps in Microsoft and Hiver, plus up to 30 minutes for Microsoft to apply permission changes
- Availability
- Hiver Omni Growth, Pro and Elite (no free plan listed, 7-day trial); the Hiver docs name no minimum Microsoft 365 plan
- Our rating
- 4 out of 5. Two-way shared mailbox and distribution list email sync from the entry plan; sync stops if the connecting account loses access.
| What | Direction | Detail |
|---|---|---|
| Incoming email | Outlook → Hiver | Hiver uses the Source User's Microsoft account to sync incoming mail from the shared mailbox, distribution list or Microsoft 365 group into the Shared Inbox. |
| Outgoing email | Hiver → Outlook | Agents reply from Hiver. Hiver sends through the Source User's account, using the shared address as the sender. |
| Initial import | Outlook → Hiver | On connection, Hiver imports up to 10,000 emails from the previous two weeks. They land in the Closed view, unassigned, with the Imported tag. |
| Folders | Outlook → Hiver | Existing folders in the shared mailbox become Tags in Hiver once, at connection. Folders created later do not import automatically. |
| Aliases | Two-way | Hiver fetches mail sent to the primary address and each alias. Agents can send from an alias, and customers see it in the From field. |
| Distribution lists and Microsoft 365 groups | Two-way | Same Shared Inbox model as a shared mailbox. The inbox takes the name of the list or group, and the connecting account needs member and delegate access. |
Setting it up
- As a Microsoft admin, grant Hiver access in Microsoft Entra. Sign in to Hiver and tick Consent on behalf of your organization, or enable an admin consent request workflow.
- Choose the Source User account. For a shared mailbox, add it as a member with Read and manage, Send as and Send on behalf of in the Microsoft 365 Admin Center.
- For a distribution list or Microsoft 365 group, add the account as a member. Then add it as a delegate with Send as and Send on behalf in the Exchange admin center.
- Wait up to 30 minutes for Microsoft to process the membership and delegate changes.
- In Hiver, name the Shared Inbox, pick the team, select Microsoft as the provider, then choose Outlook Shared Mailbox or Distribution List or Microsoft 365 Group.
- Enter the mailbox or list address and select Authorize. Sign in with the Source User's personal Microsoft account. If the mailbox forwards mail, tick Keep a copy of forwarded messages.
- Invite your team. To use aliases, add them under Admin Panel → Shared Inbox and wait 24 hours.
Where the integration stops
- One account carries the sync. The Source User's Microsoft account syncs and sends for the whole inbox. If that person leaves or loses access, syncing and sending stop until an admin reauthorizes or switches the Source User.
- The import is two weeks deep. Hiver describes an import of up to 10,000 emails from the previous two weeks. Plan for older history to stay in Outlook.
- Folders import once. Folders you create in Outlook after connecting do not appear as Tags. Create the matching Tags in Hiver by hand.
- Aliases take 24 hours. Microsoft can take that long to activate them. The alias must already exist in Microsoft Admin with the Send from alias permission enabled.
- Failed drafts and scheduled emails don't resend. After an access outage, agents must send them again.
- The docs are silent on state changes. The pages I read don't say whether read status, deletions or Outlook category changes sync back to Outlook. Test with a pilot mailbox before you rely on either.
Hiver Omni connects an Outlook shared mailbox, distribution list or Microsoft 365 group to a Hiver Shared Inbox. It suits support and operations teams on Microsoft 365 who want assignment, tags and ticketing on mail that already arrives in Outlook. Hiver builds the connector, and it comes with Hiver Omni plans rather than as a separate app.
The fact that surprises teams: one personal Microsoft account carries the whole inbox. Hiver calls it the Source User. If that person leaves, syncing and sending stop.
Hiver Omni is also not an add-on inside Outlook. It is a standalone platform, so agents work in Hiver. If your team uses Gmail, Hiver and Gmail works differently.
One account carries the whole inbox
The Source User signs in with a personal Microsoft account when you connect the inbox. Hiver uses that account to sync incoming mail and send outgoing mail. The account needs member access plus send permissions on the mailbox or list.
When access breaks, Hiver emails every admin and shows a banner on the inbox. New mail still lands in Outlook, and Hiver catches up after reauthorization. Drafts that failed and scheduled emails do not send themselves.
For shared mailboxes and distribution lists, an admin can switch the Source User from the Admin Panel. Pick a service-style account that stays with the role, not with a person.
Setup starts in Microsoft, not in Hiver
Two Microsoft admin tasks come first. The admin approves Hiver in Microsoft Entra, either by ticking the organization consent box at sign-in or by setting up an approval workflow. Then the admin sets mailbox permissions.
Shared mailboxes need Read and manage, Send as and Send on behalf of. Distribution lists and Microsoft 365 groups need member access and delegate access, set in the Exchange admin center. Microsoft takes about 30 minutes to process membership and delegate changes.
Sign-in errors usually trace back to Entra settings: user consent turned off, user assignment required, or a Conditional Access policy. The Hiver help center lists a fix for each.
Mail syncs; the rest the docs don't cover
The documented sync covers email, aliases and a one-time folder import. The pages I read list no contact sync, no calendar sync and no Outlook add-in. If you need records in a CRM, that is separate work, and Hiver and Zapier is one route.
Plan cost matters here. Hiver lists Growth, the entry Omni plan, at $25 to $35 per user per month depending on billing period, and it includes Shared Inbox and ticketing. See Hiver pricing for the full comparison, or the Hiver vendor page and Outlook integrations for related tools.