Yes, you can add HubSpot to Outlook Classic on Windows. HubSpot offers two separate products that plug into Outlook Classic, and picking the right one shapes everything from feature access to long-term support. The legacy HubSpot Sales Outlook desktop add-in installs as a COM add-in through a downloaded setup.exe, while the newer HubSpot Sales Office 365 add-in installs from Microsoft AppSource and runs inside the Outlook web-style framework.
HubSpot has announced it will no longer actively develop the desktop add-in because of Microsoft’s pivot to the “New Outlook” runtime, so the Office 365 add-in is now the recommended path even for Outlook Classic users per the HubSpot Knowledge Base install guide. That choice has real consequences for sales reps, IT admins, and compliance teams. According to HubSpot’s 2025 State of Sales report, reps who log email activity automatically close 28% more deals than reps who log manually, which is why getting this integration right matters.
Here is what you will learn in this guide:
- 🧩 How Outlook Classic differs from New Outlook and why HubSpot treats them differently
- 🛠️ Step-by-step install paths for individual users, AppSource, and tenant-wide admin deployment
- ⚖️ U.S. legal and compliance rules that control email tracking, logging, and disclosure
- 🧪 Named real-world scenarios showing success, failure, and recovery
- 🧯 The seven most common mistakes that break the integration and how to fix each one
What “Outlook Classic” Actually Means in 2026
Microsoft rebranded the traditional Win32 desktop Outlook as “Outlook Classic” in 2024 to separate it from the new React-based “New Outlook for Windows.” The classic build still ships with Microsoft 365 Apps for Enterprise, perpetual Office 2021, and Office 2024, and it continues to support COM add-ins, VSTO, and MAPI. That matters because HubSpot’s older Outlook desktop add-in is a COM add-in and simply cannot run inside New Outlook.
You can confirm which version you have by opening Outlook, clicking File → Office Account → About Outlook, and checking the build number. If the toggle in the top-right says “New Outlook” you are not in Classic. The Microsoft Learn switching guide shows how to toggle back to Classic if the add-in fails to load.
Outlook Classic supports both the legacy HubSpot Sales Outlook desktop add-in and the HubSpot Sales Office 365 add-in, making it the only Outlook flavor that can run either product. New Outlook, Outlook on the Web, and Outlook for Mac support only the Office 365 add-in per HubSpot’s Office 365 add-in setup page.
Why Microsoft’s Split Matters for HubSpot
Microsoft’s New Outlook runtime does not load COM add-ins, and HubSpot confirmed in a 2024 product notice that it “will no longer actively develop or improve the HubSpot Sales Outlook desktop add-in.” The consequence is that teams relying on desktop-only features risk a dead-end stack when IT eventually forces a New Outlook migration. A common misconception is that the desktop add-in will be removed immediately, but HubSpot has committed to keeping it available and supported in Outlook Classic, just without new features as noted in the HubSpot setup doc.
Supported Outlook Builds
Outlook Classic builds that support the HubSpot Sales Outlook desktop add-in include Outlook 2016, 2019, 2021, 2024, and Microsoft 365 Apps Click-to-Run editions. Volume-licensed MSI builds and Outlook 2013 are no longer fully supported and can produce silent ribbon failures. The ConsultEvo Outlook add-in guide warns that MSI editions may miss WebView2 components required for the login panel.
Two HubSpot Add-Ins, One Outlook Classic
HubSpot maintains two distinct add-ins that both attach to Outlook Classic, and picking between them controls which features you get, how tracking works, and whether IT can deploy centrally. This is the single most confusing decision for new customers, and the wrong pick forces a painful rip-and-replace later.
The HubSpot Sales Outlook desktop add-in installs via a Windows .exe and works offline for basic logging, but it lacks the newer meetings, sequences, and documents experiences. The HubSpot Sales Office 365 add-in installs from Microsoft AppSource and mirrors HubSpot’s web-app sales tools in real time.
Feature Differences at a Glance
| Feature or Capability | Desktop Add-In | Office 365 Add-In |
|---|---|---|
| Runs in Outlook Classic | Yes | Yes |
| Runs in New Outlook / OWA / Mac | No | Yes |
| Requires connected inbox | No | Yes |
| Central deployment via M365 admin | No | Yes per HubSpot deployment docs |
| Sequences from inbox | Limited | Full |
| Meetings scheduler | No | Yes |
| Actively developed | No | Yes |
| Works offline | Yes | No |
When Each Add-In Wins
The desktop add-in wins for field reps on unreliable networks who need offline draft logging, or for IT shops that still block AppSource installs. The Office 365 add-in wins for everyone else because it survives the New Outlook migration, supports central deployment, and receives new features every sprint. HubSpot’s comparison table lists exact feature gating by tier.
System Requirements Before You Install
Skipping the requirements check is the single biggest cause of failed installs, and each mismatch creates a specific failure mode. The desktop add-in needs a 1 GHz or faster x86/x64 processor with SSE2, 4 GB of RAM, 3 GB of free disk space, and a 1024×768 display per the HubSpot desktop add-in requirements table. The operating system must be Windows 8 or newer, with Windows 11 recommended for security patches.
The add-in also needs Microsoft Edge WebView2 runtime because HubSpot’s login panel renders inside a Chromium surface. If WebView2 is missing the ribbon appears but the sign-in popup hangs on a white screen, a known issue documented in the HubSpot troubleshooting guide. The fix is to install WebView2 from Microsoft before launching Outlook.
HubSpot Account and Tier Requirements
Every Outlook Classic user needs a free HubSpot account at minimum to use the add-in, and premium features gate by seat tier. Sales Hub Free users get five templates, five documents, five snippets, and 200 email tracking notifications per month. Starter raises those limits and adds meetings links. Professional unlocks sequences and 1,000 sends per seat per day per HubSpot’s pricing page. Enterprise adds advanced permissions, hierarchical teams, and single sign-on through HubSpot’s SSO guide.
Connected Inbox Rules
The Office 365 add-in requires a connected inbox where HubSpot authenticates against Microsoft Graph to send and log mail. The desktop add-in does not require a connected inbox because logging happens locally through MAPI. Shared mailboxes, resource mailboxes, and mailboxes with delegated permissions cannot be connected, so pooled inboxes must fall back to the BCC dropbox address shown in HubSpot’s BCC logging guide.
How to Install the HubSpot Sales Outlook Desktop Add-In
The desktop add-in install takes under five minutes on a clean machine, but skipping any step produces silent failures. Close Outlook completely before you start; otherwise the installer’s registry writes collide with the running Outlook process and the ribbon never appears.
First, download the installer directly from HubSpot’s Sales add-in download page. Second, run setup.exe as the signed-in user, not elevated as a different admin account, because the add-in registers in HKCU and will not show up for the logged-in user if installed under another profile. Third, restart Outlook. Fourth, sign in with your HubSpot credentials when the side panel opens.
Step-by-Step for Individual Users
- Quit Outlook and confirm no OUTLOOK.EXE process remains in Task Manager.
- Download setup.exe from the HubSpot install page.
- Double-click setup.exe and accept the VSTO runtime prompt.
- Launch Outlook and look for the Sales Tools button on the Home ribbon.
- Click Log in with HubSpot and authenticate via the WebView2 popup.
- Pin the task pane open and test with a throwaway email to yourself.
Tenant-Wide Deployment (Admin Path)
The desktop add-in cannot be centrally deployed through the Microsoft 365 admin center because COM add-ins are per-user. IT teams must push it through Group Policy software installation, Microsoft Intune Win32 app packaging, or SCCM. Create a Win32 .intunewin package pointing at setup.exe with a silent install switch (/quiet), then scope to user groups following Microsoft’s Intune Win32 docs. The consequence of skipping scope targeting is that every tenant user gets the add-in whether they have a HubSpot seat or not, which triggers login error loops in their Outlook.
Troubleshooting a Missing Ribbon
If Sales Tools does not appear, open File → Options → Add-ins, set Manage to COM Add-ins, and click Go. Re-enable HubSpot Sales if it is unchecked. If it sits under Disabled Items, select it and click Enable. Outlook disables slow-loading add-ins automatically to protect startup time, a behavior explained in the Microsoft add-in resiliency doc.
How to Install the HubSpot Sales Office 365 Add-In
The Office 365 add-in installs in two ways: individually from AppSource or centrally by a Microsoft 365 admin. Either path ends with the Sales Tools button appearing in the Outlook Classic ribbon, but the permission model and audit trail differ substantially.
Individual install takes under two minutes. Central deployment takes longer but is the only scalable path for teams of more than ten users because it survives device resets, new hires, and Outlook reinstalls.
Individual AppSource Install
Open a browser, go to the HubSpot Sales listing on AppSource, and click Get it now. Sign in with the same Microsoft 365 credentials as your Outlook mailbox. Accept the permissions prompt, which grants HubSpot read/write access to your mailbox through Microsoft Graph. Restart Outlook Classic and the Sales Tools button appears on the ribbon.
Central Deployment via Microsoft 365 Admin
Admins sign into the Microsoft 365 admin center, go to Settings → Integrated apps → Get apps, search for HubSpot Sales, and click Get it now. Assign the app to specific users, groups, or the entire tenant. The consequence of tenant-wide assignment is that every mailbox, including shared and resource mailboxes, receives the manifest, and shared mailboxes will show an “inbox not connected” error until a user connects them manually. HubSpot’s central deployment guide recommends scoping to a security group named hubspot-seat-holders.
Connecting the Inbox to HubSpot
Installation is only half the job because the add-in needs the inbox to be a “connected inbox” in HubSpot. Inside HubSpot navigate to Settings → General → Email → Connect personal email, choose Office 365, and complete the OAuth flow. Without this step, emails sent from Outlook will not log automatically and tracked-email notifications will not appear per HubSpot’s connected inbox setup doc.
Three Real-World Installation Scenarios
Installation rarely happens in a vacuum, and the following scenarios show how small environmental differences change the outcome.
Scenario Table 1: Sales Rep on Laptop
| Rep Action | Outcome |
|---|---|
| Maria, an SDR at a SaaS firm, installs the desktop add-in on a company laptop with Outlook 2021 Click-to-Run | Sales Tools ribbon appears, logging works in under 3 minutes |
| Maria migrates to New Outlook preview without uninstalling first | Desktop add-in silently stops loading, HubSpot auto-installs the Office 365 add-in, Maria loses two weeks of tracking notifications until she reconnects her inbox |
Scenario Table 2: IT Admin Tenant Rollout
| Admin Action | Outcome |
|---|---|
| David, an IT admin, centrally deploys the Office 365 add-in to the whole tenant | 340 users get the ribbon, but 40 shared mailboxes throw “inbox not connected” errors and generate 80 support tickets |
| David re-scopes the deployment to a security group of 175 seat holders only | Error tickets drop to zero, license utilization rises to 96% |
Scenario Table 3: Agency Owner with Mac and Windows
| Owner Action | Outcome |
|---|---|
| Priya, an agency owner, runs Outlook Classic on Windows and Outlook for Mac | Office 365 add-in works on both platforms, desktop add-in refuses to install on Mac |
| Priya tries to install the desktop add-in via Wine on macOS | Installer completes but Outlook for Mac never shows the ribbon because COM add-ins are Windows-only |
Named Examples of Common Workflows
Concrete workflows help teams see the integration’s value beyond a feature list.
Example 1: Maria the SDR. Maria’s goal is to hit 40 tracked outbound emails a day. She uses the Office 365 add-in’s Sequences panel to enroll 40 leads each morning, templates pre-fill the bodies, and HubSpot auto-logs every send to the contact record per HubSpot’s sequences guide.
Example 2: David the IT Admin. David’s goal is zero-touch onboarding for new hires. He scripts Intune to assign new hires to the hubspot-seat-holders Azure AD group on day one, which triggers automatic Office 365 add-in deployment and a HubSpot seat provision via SCIM per HubSpot’s SCIM docs.
Example 3: Priya the Agency Owner. Priya’s goal is to bill clients for exact email response times. She uses the meetings link from the Office 365 add-in to book client calls, and HubSpot timestamps every reply on the deal record, giving her an audit-ready billing trail.
U.S. Legal and Compliance Rules You Must Know
Email tracking is regulated under federal and state law, and ignoring these rules exposes your company to civil penalties and class-action risk. HubSpot’s tracking pixel is a powerful tool, but it is not a “free” feature from a legal standpoint.
CAN-SPAM Act
The federal CAN-SPAM Act requires commercial senders to identify the message as an ad, include a physical postal address, and offer a clear opt-out. The consequence of violating CAN-SPAM is up to $53,088 per email per the FTC’s 2024 civil penalty adjustment. A common misconception is that one-to-one sales emails are exempt, but the primary-purpose test in 16 CFR § 316.3 can pull sales emails into scope if the content is promotional.
State Wiretap Laws and Pixel Tracking
Two-party-consent states like California, Pennsylvania, and Massachusetts have produced class-action litigation against tracking pixels. In Popa v. Harriet Carter Gifts, the Third Circuit held that third-party tracking could violate Pennsylvania’s Wiretapping and Electronic Surveillance Control Act. The consequence for sales teams is that opening an email in Pennsylvania while a pixel phones home to HubSpot servers may constitute unconsented interception. The practical fix is to disable tracking for recipients in two-party-consent states or add express consent language to your email footer.
HIPAA and Regulated Industries
Healthcare organizations sending ePHI through Outlook Classic with HubSpot tracking must have a Business Associate Agreement with HubSpot. HubSpot offers a BAA only for Enterprise customers that opt in per the HubSpot HIPAA documentation. Sending ePHI without a BAA is a HIPAA violation carrying fines up to $2.1 million per year per violation category under the HHS penalty tiers.
Mistakes to Avoid
- Installing setup.exe while Outlook is still running. The installer cannot register the COM component, so the ribbon never appears and users assume the install failed.
- Enabling both add-ins at the same time. Running the desktop add-in and Office 365 add-in together causes duplicate logging and double-counted open events in reports.
- Connecting a shared mailbox as a personal inbox. HubSpot blocks this, but some users keep retrying and lock their account out of the Graph API for 24 hours.
- Installing on Outlook 2013 or an MSI build. The install appears to succeed but the add-in never receives updates and silently breaks after a few months.
- Skipping WebView2 installation. The ribbon shows up, but the login panel renders a white screen, leaving users unable to authenticate.
- Granting tenant-wide deployment without scoping. Every mailbox receives the manifest, shared mailboxes error out, and help desk volume spikes.
- Ignoring two-party-consent state laws. Tracking pixels fire without disclosure, exposing the company to state wiretap class actions.
- Failing to reconnect the inbox after a password change. HubSpot’s OAuth token expires, emails stop logging, and reps don’t notice until a deal review meeting.
- Using the desktop add-in as a long-term strategy. HubSpot stopped active development, so teams lose access to new features like AI-generated replies.
Do’s and Don’ts
Do
- Do install WebView2 before the desktop add-in because the login panel depends on it.
- Do use the Office 365 add-in for any team larger than ten seats because central deployment scales.
- Do scope tenant deployments to a security group to avoid error storms on shared mailboxes.
- Do add a tracking disclosure line in your email signature to reduce state wiretap exposure.
- Do pin the Sales Tools pane open on first launch so reps actually use it.
Don’t
- Don’t install setup.exe while Outlook is open because the COM registration will silently fail.
- Don’t run the desktop and Office 365 add-ins concurrently because events double-log.
- Don’t migrate to New Outlook before confirming all reps moved to the Office 365 add-in.
- Don’t send ePHI through any HubSpot-connected inbox without a signed BAA.
- Don’t assume one-to-one sales email is exempt from CAN-SPAM’s primary-purpose test.
Pros and Cons
Pros
- Auto-logs every send and reply to the right contact, saving reps roughly 45 minutes per day.
- Templates, snippets, and sequences cut repetitive typing and improve reply rates.
- Meetings scheduler removes back-and-forth and books calendar events automatically.
- Tracking notifications show opens and clicks so reps follow up at the right moment.
- Tight CRM-to-inbox sync eliminates forgotten contacts and duplicate records.
Cons
- Requires either a connected inbox or a COM add-in, each with its own failure modes.
- Tracking pixels create state-law and GDPR risk that must be managed legally.
- Desktop add-in is frozen in feature development and will eventually fall behind.
- Shared and resource mailboxes cannot connect, limiting team-inbox workflows.
- Admin deployment requires Microsoft 365 admin rights that some SMBs do not have in-house.
FAQs
Does HubSpot work with Outlook Classic on Windows?
Yes. Outlook Classic on Windows supports both the HubSpot Sales desktop add-in and the HubSpot Sales Office 365 add-in, making it the only Outlook build that runs either product.
Is the HubSpot desktop add-in still supported?
Yes. HubSpot continues to support the desktop add-in in Outlook Classic but will not add new features, so teams should plan a migration to the Office 365 add-in.
Can I install HubSpot on New Outlook for Windows?
No. New Outlook does not load COM add-ins, so only the HubSpot Sales Office 365 add-in works there, and the desktop add-in auto-migrates during the switch.
Do I need a paid HubSpot seat to use the Outlook add-in?
No. A free HubSpot account unlocks the add-in with capped template, snippet, document, and tracking limits; paid tiers raise those caps and add sequences and meetings.
Does the Office 365 add-in require a connected inbox?
Yes. The Office 365 add-in authenticates via Microsoft Graph and requires the mailbox to be connected to HubSpot for sending, logging, and tracking to function.
Can an IT admin centrally deploy the HubSpot add-in?
Yes. Admins can centrally deploy the Office 365 add-in through the Microsoft 365 admin center, while the desktop add-in requires Intune, Group Policy, or SCCM.
Is email open tracking legal in the United States?
Yes. Tracking is generally legal under federal law, but two-party-consent states like Pennsylvania have produced class-action rulings that may require disclosure or consent.
Can I use HubSpot with a shared mailbox in Outlook Classic?
No. Shared and resource mailboxes cannot be connected inboxes; teams should use the BCC dropbox address to log emails sent from shared mailboxes instead.
Does HubSpot sign a BAA for HIPAA-covered users?
Yes. HubSpot signs a BAA for Enterprise customers who opt into the HIPAA add-on, but not for Free, Starter, or Professional tiers.
Will installing both HubSpot add-ins break Outlook?
Yes. Running both simultaneously causes duplicate email logging, double-counted opens, and conflicting notifications, so admins should uninstall one before enabling the other.
Does the desktop add-in work offline?
Yes. The desktop add-in queues logs and tracking locally when offline and syncs to HubSpot when the connection returns, unlike the Office 365 add-in which needs internet.
Can I use HubSpot in Outlook for Mac?
Yes. Outlook for Mac supports only the HubSpot Sales Office 365 add-in; the Windows-only desktop add-in will not install or run on macOS.