# HubSpot Outlook Integration: Fix Missing Logs, Tracking and Duplicate Activities

To make HubSpot and Outlook work together, confirm the mailbox provider, connect the correct work email, use the compatible add-in and inspect the account's logging rules. Then trace one controlled message from Outlook to the intended CRM record. Delivery, logging, record associations and open tracking are separate outcomes; fixing one does not prove the others are correct.

Canonical URL: https://www.martechdevs.com/blog/hubspot-outlook-integration

By [Jafrin Akter Alo](https://www.martechdevs.com/authors/jafrin-akter-alo)

Data Engineer and Co-founder at [Martechdevs](https://www.martechdevs.com) and [Growth and Analytics Partners](https://www.growthandanalytics.com)

[LinkedIn](https://linkedin.com/in/jafrinalo)

Last updated: 2026-10-25

Next step: [Salesforce to HubSpot migration: plan, field mapping and cutover checklist](https://www.martechdevs.com/blog/salesforce-to-hubspot-migration)

An email can reach the customer while never appearing on the deal. It can appear on the deal without any open event. It can also appear on several related records without having been sent several times. Start with the observed failure instead of reinstalling everything labelled Outlook.

This guide covers individual work email and the HubSpot Sales Office 365 add-in. Shared team email, marketing campaigns, calendar sync and Outlook Contacts are different connections. The [HubSpot implementation checklist](https://www.martechdevs.com/blog/hubspot-implementation-checklist) covers the wider rollout; this guide narrows acceptance to one working email path.

## Which Outlook integration do you need?

Identify where the mailbox is hosted as well as the Outlook client being used. Outlook can display mail from different providers, but that does not make every account eligible for the same HubSpot add-in.

HubSpot's Office 365 add-in requires a Microsoft 365-hosted mailbox and supports classic/new Outlook on the listed Windows, Mac and web clients. Its legacy Outlook desktop add-in is in maintenance mode and limited to classic Outlook for Windows. HubSpot warns against using both add-ins on the same device. [Installation and compatibility](https://knowledge.hubspot.com/connected-email/how-to-install-hubspot-sales).

Microsoft confirms that new Outlook for Windows supports web add-ins rather than COM/VSTO add-ins. General Outlook add-in support also varies by mailbox and client. Check the HubSpot-specific requirements before treating Microsoft's broad platform support as proof that this integration will work. [Microsoft add-in model](https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/outlook-add-ins-overview).

| Connection or component | Its job | Evidence to check |
| --- | --- | --- |
| Individual work email | Connect the user's mailbox to CRM email features | Correct provider, primary mailbox and connected state |
| Office 365 add-in | Bring HubSpot tools into Outlook | Compatible host/client and correct HubSpot account |
| Account logging rules | Decide which messages are captured | Known-contact versus reply-only policy and exclusions |
| Tracking settings | Enable permitted open/click measurement | Message controls, recipient eligibility and relevant seat |

In HubSpot, the individual email connection is under Settings → General → Email. Personal email access is required; View-Only users cannot connect it. Microsoft 365 shared mailboxes are not supported as individual work email, and the same address cannot be both an individual and team email connection. [Individual email requirements](https://knowledge.hubspot.com/connected-email/connect-your-inbox-to-hubspot).

If several employees need one shared address, design that as a team-email workflow rather than sharing a person's connection. Record which team owns replies, CRM visibility and escalation. Our [CRM and lifecycle implementation service](https://www.martechdevs.com/crm-lifecycle) can help map that operating requirement before choosing the connection type.

## Which email logging rule is active?

Read the account policy before deciding what the Outlook pane should have done. HubSpot offers reply-only logging and logging of all email to/from known contacts; the latter is its documented default. With that rule, mail sent outside the CRM can log through a connected individual inbox. A separate beta can create contacts from incoming email. Never Log exclusions still apply. [Contact email logging rules](https://knowledge.hubspot.com/connected-email/manage-contact-email-logging-rules).

The Office 365 add-in's selected tracking and logging preferences require its task pane to be open when sending. That is an add-in requirement, not proof that background account logging is disabled when the pane is closed. Pin the read and compose panes separately; closing a pane unpins it. [Add-in preferences and pinning](https://knowledge.hubspot.com/connected-email/customize-your-hubspot-sales-office-365-add-in).

This distinction matters for both troubleshooting and privacy. A salesperson clearing a compose checkbox should not be assumed to have changed the account-wide capture policy. Inspect the governing rule and verify the result with a controlled message before promising that a category of correspondence stays outside the CRM.

Define the expected behaviour explicitly:

- Which messages from known contacts should log automatically?
- Should new correspondents become CRM contacts, and through which route?
- Which addresses and domains must remain excluded?
- Which companies, deals or tickets should receive the activity association?
- Which users are allowed to view the logged content?

An email policy is part of the data model. The [CRM property ownership guide](https://www.martechdevs.com/blog/crm-property-ownership) helps assign responsibility for the related records and automation, rather than leaving every user to choose incompatible defaults.

## How do you verify one complete message path?

Use a test recipient and a harmless, unique subject, then inspect delivery and CRM evidence separately. Avoid real confidential correspondence while diagnosing an uncertain logging rule.

1. **Record the context.** Capture the mailbox provider, primary address, alias if used, Outlook client/build, HubSpot account and active logging policy.
2. **Choose an existing test contact.** Confirm the expected company/deal association and that the address is not excluded by policy.
3. **Compose one new message.** Open the HubSpot pane, verify the account, and deliberately choose Log and permitted tracking settings.
4. **Send once.** Record the sent-message evidence and actual recipient delivery separately from HubSpot's activity feed.
5. **Inspect the CRM activity.** Check sender, recipient, subject, content and associated records. Preserve the activity link or ID for comparison.
6. **Reply from the test mailbox.** Observe the result under the selected logging rule, then test a changed subject or new thread separately.
7. **Change one condition.** Repeat with the pane closed, an alias or an excluded recipient only when that case is part of the approved test plan.

For add-in logging, the Log control populates HubSpot's BCC address and allows record associations to be selected. Eligible sender addresses include the user, connected addresses and configured aliases. New contacts created through this route are non-marketing when the account uses marketing contacts. [Office 365 logging behaviour](https://knowledge.hubspot.com/connected-email/track-and-log-emails-with-the-hubspot-sales-office-365-add-in).

Keep a concise evidence record:

```text
case: known contact, individual Microsoft365 mailbox
client: actual Outlook edition and build
hubspot_account: verified account identifier
logging_rule: actual configured rule
compose_pane: open or closed
log_and_track: actual selections
sender_and_alias: controlled test addresses
expected_records: contact and approved deal
sent_message_reference: retained test evidence
crm_activity_reference: observed activity or missing
reply_result: observed outcome
```

This is a diagnostic record, not an importable HubSpot configuration. Its value is that another operator can reproduce the same case and distinguish a changed setting from a different email.

## Why is an Outlook email missing from HubSpot?

Locate the first missing outcome: actual sending, the mailbox connection, the capture rule or the target association. An Outlook Sent item alone does not prove that the integration logged the message to the correct portal.

| Observation | First check | What the result tells you |
| --- | --- | --- |
| Message never reached the test recipient | Outlook delivery and mail-system evidence | Investigate mail delivery before CRM logging |
| Add-in is absent or greyed out | Host/client, deployment, reading pane and admin permissions | Installation or client availability issue |
| Repeated connection prompt | Primary mailbox versus alias | A mailbox identity mismatch may be causing the loop |
| Message appears in another HubSpot account | Add-in account selection | Correct the portal association |
| Message exists on contact but not deal | Selected/default record associations | Logging worked; association needs correction |
| Message is excluded | Never Log and account policy | Expected exclusion may be working correctly |

HubSpot's troubleshooting guide identifies primary-address/alias confusion as a connection-loop cause. It also distinguishes reading-pane and encrypted-message cases when an add-in is greyed out, and points login loops to cookie/session configuration. Involve the Microsoft 365 and HubSpot administrators with the exact symptom. [Office 365 troubleshooting](https://knowledge.hubspot.com/connected-email/troubleshooting-the-hubspot-sales-office-365-add-in).

Use an approved test environment to isolate conflicts. Keep organisational security and single-sign-on requirements in place while IT identifies the compatibility issue. Replacing a controlled login policy with a weaker one is not a necessary definition of a working CRM integration.

For multiple HubSpot accounts, check the account selected in Add-in settings. Switching changes the CRM and tools the inbox uses. Default associations and contact-creation preferences also affect where the message appears. [Account and association settings](https://knowledge.hubspot.com/connected-email/customize-your-hubspot-sales-office-365-add-in).

## Why are replies or new incoming messages missing?

Check whether the account uses reply-only logging or broader known-contact capture. A new incoming thread can be absent under reply-only rules even when a reply to an already logged thread works.

For reply-only mode, HubSpot requires the original email to have been logged through an eligible route, a connected individual inbox when the reply arrives, an active user, no Never Log exclusion and the same subject. Changing the mailbox provider without reconnecting can break reply detection and sequence unenrolment. [Reply-only conditions](https://knowledge.hubspot.com/connected-email/log-email-replies-in-the-crm).

Do not apply those reply-only limitations to an account configured to log all known-contact email. Read the current setting and test each case under that setting. If the business needs new enquiries captured, decide whether the appropriate route is the available contact-creation feature, a team inbox or a controlled manual process.

After a mailbox migration, test existing threads and new messages. Confirm the provider type, current connection and sender identity before resuming automated follow-up. A sequence that cannot detect a reply can continue contacting someone who already answered.

## Why is open or click tracking missing?

A missing tracking event is not proof that the customer did not receive or read the email. First check whether tracking was enabled and permitted for that message, then consider how the recipient's client handled it.

The Office 365 add-in needs the connected inbox, tracking selection and open task pane for its tracked send. Plain-text messages cannot carry the required HTML tracking. With data privacy settings enabled, recipient processing eligibility also controls tracking. Link-click tracking requires the relevant assigned Sales Hub seat. [Tracked-send requirements](https://knowledge.hubspot.com/connected-email/track-and-log-emails-with-the-hubspot-sales-office-365-add-in), [HTML and pane checks](https://knowledge.hubspot.com/connected-email/troubleshooting-the-hubspot-sales-office-365-add-in).

HubSpot uses an image for open tracking. Image blocking can prevent the event, while a later click or reply can cause an inferred open. It excludes suspected non-human activity, but an open remains an engagement signal rather than a reliable proof of a particular person's attention. Forwarding and copied tracking pixels can also complicate interpretation. [Tracking mechanics and limits](https://knowledge.hubspot.com/connected-email/understand-hubspot-sales-email-open-and-click-tracking). The [eight HubSpot email-tracking checks](https://www.martechdevs.com/blog/hubspot-email-tracking) explain inferred opens, anonymous notifications, link formats and mismatched report populations.

Do not assign a fabricated legal basis merely to enable a greyed-out checkbox. Apply the organisation's approved tracking policy, and accept that some messages should be logged without tracking. For follow-up decisions, a customer's explicit reply or completed business action is more useful than treating every pixel load as purchase intent.

## How do you recover a past email or investigate duplicates?

Recover missing history through a supported logging route, and verify whether an apparent duplicate is actually the same activity associated with several records. Preserve evidence before deleting anything.

The Office 365 add-in can retroactively log sent or received messages from its This email activity panel. This requires the connected individual email and relevant access; View-Only users cannot use it. Non-inline attachments are not included in that retroactive path, and the legacy desktop add-in does not support the feature. [Retroactive logging](https://knowledge.hubspot.com/connected-email/log-your-sent-emails-to-the-crm).

Manual BCC and forwarding are alternatives with their own rules. BCC-only logging does not add open/click tracking. It can create contacts for CC recipients and has default association behaviour, so inspect the resulting records. The manual route's total email size limit is 40 MB, including body, headers and attachments. [BCC and forwarding behaviour](https://knowledge.hubspot.com/connected-email/log-email-in-your-crm-with-the-bcc-or-forwarding-address).

Before calling an activity duplicated, compare:

- The CRM activity ID or link on each record.
- The original sender, recipients and message reference where available.
- The direction and subject, distinguishing an original from its reply.
- The logging route: add-in, account capture, BCC, forwarding or another integration.
- Whether a user manually logged a message already captured elsewhere.

If the same activity appears on a contact and its deal, that can be the intended association. If separate activity records represent the same underlying message, identify the competing capture routes and reproduce the case with test mail. Do not remove legitimate conversation history solely because two rows have the same subject.

Attachments deserve a separate check. Their handling and size limits vary by logging route, and mail-security processing can affect reply attachments. The existence of a logged body is not proof that every file was retained. [Reply attachment considerations](https://knowledge.hubspot.com/connected-email/log-email-replies-in-the-crm).

![Missing email activity first branches on whether the message was sent, then whether a CRM activity exists, then whether its record association is correct. The branches separate mail delivery, logging configuration, association repair and tracking/reply investigation.](https://www.martechdevs.com/assets/blog/hubspot-outlook-integration.svg)

Diagram connections:

- Expected Outlook email activity missing to Message actually sent?. 
- Message actually sent? to Resolve the mail sending problem: No. 
- Message actually sent? to CRM activity exists?: Yes. 
- CRM activity exists? to Check connection policy and logging route: No. 
- CRM activity exists? to Associated with intended record?: Yes. 
- Associated with intended record? to Correct record associations: No. 
- Associated with intended record? to Investigate tracking or reply evidence separately: Yes

## What should a team rollout prove?

Roll out the approved mailbox and logging policy to a small group first, then confirm that users can operate it without capturing excluded correspondence. Test every Outlook client the team actually uses.

| Controlled case | Required observation | Evidence to retain |
| --- | --- | --- |
| Known contact under the chosen logging policy | Expected CRM activity and associations | Sent message and linked CRM activity |
| New correspondent | Approved contact-creation or exclusion behaviour | New-record decision and active logging setting |
| Never Log address/domain | No prohibited logging or contact creation | Matching exclusion and verified absence from the CRM |
| Pane open versus closed | Background logging and add-in tracking distinguished | Pane state, account policy and separate results |
| Primary address versus approved alias | Correct mailbox connection and sender attribution | Connected primary mailbox and actual From address |
| Reply with unchanged versus changed subject | Behaviour consistent with active logging mode | Thread headers and logged reply result |
| Manual recovery of one past message | Correct activity without assumed missing attachments | Recovered activity and its attachment list |
| Same message inspected on several records | One association set or a documented duplication issue | Activity identifiers and record associations |

Record the expected result before running the case. A passing test should show what the system did and which policy required it; it should not merely record that the add-in button appeared.

## Checklist

- [ ] Mailbox provider, client and add-in compatibility are confirmed.
- [ ] Individual and shared/team email responsibilities are distinct.
- [ ] Primary address, aliases and HubSpot account selection are correct.
- [ ] Account-wide logging rules and Never Log exclusions are approved.
- [ ] Add-in preferences and pane behaviour are understood.
- [ ] Tracking follows the approved recipient and permission policy.
- [ ] Known/new contact creation and record associations pass controlled tests.
- [ ] Replies still behave correctly after mailbox or provider changes.
- [ ] Manual recovery and attachment limitations are documented.
- [ ] A named owner can investigate one missing or duplicate activity.

If the issue persists, collect the controlled contact/activity reference, client details, active settings and relevant email headers for the support owner. HubSpot provides debug-log collection in Add-in settings → Help & troubleshooting. Review that evidence before sharing it through the approved support route. [Debug-log procedure](https://knowledge.hubspot.com/connected-email/troubleshooting-the-hubspot-sales-office-365-add-in).

For a broader CRM handoff problem, [get the $99 martech audit](https://www.martechdevs.com/pricing) with a redacted example. The useful result is a clear capture policy, one reliable email path and an owner who can explain the next failure.

## Frequently asked questions

### Does connecting Outlook import every historical email into HubSpot?

Do not assume it does. Define the historical messages the business needs, check the supported logging or migration route and verify a controlled sample. Retroactive logging is a separate action from connecting a mailbox. Preserve access to any approved legacy history until its coverage is reconciled, especially where an open deal or service commitment depends on an earlier conversation.

### Can a user with several mailboxes install the add-in once and forget it?

Check each mailbox where the user needs HubSpot tools. HubSpot's installation guide requires individual installation in each relevant email account, unless deployment is handled through the organisation's supported process. [Mailbox installation](https://knowledge.hubspot.com/connected-email/how-to-install-hubspot-sales). Test the actual sender address and account selection in each path rather than assuming a working primary inbox proves that every alias or secondary mailbox is configured.

### Should a missing open notification trigger an automatic reminder?

Not on its own. A missing event can reflect disabled tracking, image blocking or another measurement limit rather than lack of interest. Combine the approved follow-up schedule with explicit replies, meetings and customer actions. Test stop conditions so an answered or resolved conversation does not continue receiving reminders simply because its open-tracking record is incomplete.

### Can email-body redaction remove sensitive content from all CRM history?

HubSpot's redaction beta applies to emails logged after it is enabled; earlier bodies remain unchanged. It retains sender, recipients, subject and attachments, and redacted body content cannot be restored. [Redaction behaviour](https://knowledge.hubspot.com/connected-email/manage-contact-email-logging-rules). Review the full data path and existing history separately. Redacting only the body is not a complete sensitive-data or access-control strategy.

### What should change when a salesperson leaves?

Review mailbox access, CRM ownership, active sequences and the conversations another employee must continue. Preserve records under the organisation's retention and access policy, then remove or transfer connections through the approved process. Test that replies reach an accountable person and that automated follow-up does not continue from an abandoned identity. Removing a user's login alone does not complete the operational handover.

## Sources

1. [HubSpot: Install Sales email add-ins](https://knowledge.hubspot.com/connected-email/how-to-install-hubspot-sales).

2. [Microsoft: Outlook add-in compatibility](https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/outlook-add-ins-overview).

3. [HubSpot: Connect individual work email](https://knowledge.hubspot.com/connected-email/connect-your-inbox-to-hubspot).

4. [HubSpot: Contact email logging rules](https://knowledge.hubspot.com/connected-email/manage-contact-email-logging-rules).

5. [HubSpot: Office 365 add-in settings](https://knowledge.hubspot.com/connected-email/customize-your-hubspot-sales-office-365-add-in).

6. [HubSpot: Track and log with Office 365](https://knowledge.hubspot.com/connected-email/track-and-log-emails-with-the-hubspot-sales-office-365-add-in).

7. [HubSpot: Office 365 troubleshooting](https://knowledge.hubspot.com/connected-email/troubleshooting-the-hubspot-sales-office-365-add-in).

8. [HubSpot: Reply-only logging](https://knowledge.hubspot.com/connected-email/log-email-replies-in-the-crm).

9. [HubSpot: Open and click tracking](https://knowledge.hubspot.com/connected-email/understand-hubspot-sales-email-open-and-click-tracking).

10. [HubSpot: Retroactive sent/received logging](https://knowledge.hubspot.com/connected-email/log-your-sent-emails-to-the-crm).

11. [HubSpot: BCC and forwarding](https://knowledge.hubspot.com/connected-email/log-email-in-your-crm-with-the-bcc-or-forwarding-address).