How do I connect Microsoft 365 to HubSpot?

Most firms that adopt HubSpot already run their email, calendars and chat on Microsoft 365. The goal is obvious: every client email logged against the right contact, meetings booked straight into Outlook calendars, and nobody copying details from one system to the other. The question is how much of that HubSpot does natively, and where the gaps are.

The direct answer: connect Microsoft 365 to HubSpot through four separate native pieces, each set up on its own: the connected inbox (per user), the Outlook add-in (per user), the calendar connection for the meetings tool (per user), and the Microsoft Teams app (per account). Together they cover most of what a 10 to 50 person firm needs. The biggest gap is shared mailboxes: an Office 365 shared mailbox such as info@ or accounts@ cannot be connected as a normal inbox, and that shapes how you set things up.

The four pieces and what each does

Feature details below are as documented in HubSpot's knowledge base in October 2026. Menu names change often, so follow the linked articles rather than screenshots from older guides.

1. Connect each person's inbox

Each user connects their own Microsoft 365 mailbox to HubSpot. HubSpot's article on connecting your inbox sets out the conditions:

• the user needs the Personal email access permission, and View-Only seat users cannot connect,
• Exchange Online users connect through HubSpot's Outlook integration, which signs in with Microsoft rather than a stored password, because Microsoft has retired basic authentication,
• Microsoft 365 shared mailboxes are not supported for individual connections, and
• tracked correspondence is visible to other users in the HubSpot account.

That last point matters for firms with confidential matters. Decide before rollout which conversations should never be logged, and use the "never log" settings below.

2. Install the Outlook add-in

The HubSpot Sales Office 365 add-in puts log and track controls inside Outlook and shows the contact's CRM record beside the email. HubSpot lists support for classic Outlook for Windows and Mac, new Outlook for Windows and Mac, and Outlook on the web.

Two details catch people out:

• The task pane must be open when you send a logged or tracked email. If it is closed, the email is not logged. Train the team on this in the first week.
• "Never log" lists let you block specific addresses or domains from being logged. Super Admins can set account-wide defaults that override personal preferences. Use this for internal domains, personal contacts and any client whose correspondence must stay out of the CRM.

Most firms deploy the add-in centrally through the Microsoft 365 admin center, so nobody has to install it by hand. Check with your IT provider before rollout.

3. Connect calendars for the meetings tool

HubSpot's calendar connection lets clients book through a meetings link without landing on top of existing Outlook appointments, and puts meetings created in HubSpot on the user's calendar. As documented in October 2026:

• each user can connect one Google, Office 365 or Exchange calendar,
• the user needs Personal email access turned on, and
• if a user's inbox is connected as a shared inbox in the conversations tool, their calendar cannot be connected to the meetings tool.

Without a connected calendar, the meetings page runs in offline mode: requests arrive but are not added to the calendar automatically.

4. Add the Microsoft Teams app

The HubSpot and Microsoft Teams integration sends HubSpot notifications into Teams, lets people act on tasks and tickets there, and adds Teams meeting links to HubSpot meetings. An admin-level install needs a HubSpot Super Admin (or App Marketplace access) and a Teams Global Admin, and it unlocks more features than a user-level install. One HubSpot account can connect one Teams instance.

Keep Teams notifications selective. A channel that receives every deal update quickly becomes a channel nobody reads.

The shared mailbox problem

Many firms run client contact through shared mailboxes: info@, enquiries@, accounts@. In Microsoft 365, a shared mailbox has no password of its own, and HubSpot does not support connecting one as an individual inbox. HubSpot's own ideas forum thread asking for this has been open for years.

Your options:

1. Connect the address as a team email channel in the conversations inbox or help desk. HubSpot's article on connecting channels lists team email on all plans, with every incoming email visible to all users who have inbox access, and no history from before the connection. Check how your IT provider must configure the address first, since a true shared mailbox may not connect.
2. Turn the shared address into a licensed mailbox, which some firms do. It costs a Microsoft license, and the account must be secured properly with MFA and a password manager, not left as a loophole.
3. Forward or alias, approaches suggested in HubSpot's community. They are workarounds, not documented features, so test them with real mail before relying on them.

Pick one route per address and write it down. Mixing them is how the same enquiry ends up logged twice or not at all.

Contacts sync: usually skip it

HubSpot also offers an Outlook contacts sync. It is installed per user, syncs only that user's personal contacts folder, and does not sync shared contacts or the Active Directory address book. For most firms, the CRM should be the single place where client contacts live, and a two-way sync with twenty personal address books is a reliable source of duplicates. Our guide to syncing apps without duplicates explains why. If you do turn it on, start with one-way sync into HubSpot and a filter.

When native is not enough

The native pieces cover email, calendar and chat. They do not cover:

• filing emails or attachments to SharePoint or OneDrive folders by client,
• creating HubSpot records from Microsoft Forms or SharePoint lists, or
• approvals that span HubSpot and Teams.

For those, you need an automation layer: Power Automate if most of the work stays in Microsoft, or Zapier or Make if it reaches into other apps. Our comparison of Power Automate vs Zapier for Microsoft 365 firms covers the licensing trade-offs.

A sensible rollout order

1. Agree what must never be logged, and set account-wide "never log" rules.
2. Connect each user's inbox and deploy the Outlook add-in.
3. Connect calendars for anyone who uses meetings links.
4. Decide the route for each shared mailbox.
5. Add Teams last, with a short list of notifications people actually want.

How Flow Mesh helps

Our stack audit reviews how your Microsoft 365 and HubSpot setup handles email, calendars and shared mailboxes today, gives each tool a verdict (keep, configure, consolidate or replace) and sets out the fixes in a written scope. Any build is quoted in writing after the audit and done inside your own accounts.

Key takeaways

• Microsoft 365 connects to HubSpot through four separate pieces: inbox, Outlook add-in, calendar and Teams.
• Office 365 shared mailboxes cannot connect as individual inboxes; choose a team email channel, a licensed mailbox or a tested workaround for each one.
• The Outlook add-in only logs emails when its task pane is open, so train for it.
• Set "never log" rules before rollout, because tracked email is visible across the account.
• Skip personal contacts sync in most firms; let HubSpot own client contacts.