01 — Overview
What this engagement is
This service is the tenant-level counterpart to IT Partner's HubSpot + Microsoft Outlook integration: instead of a handful of individually connected users, it plans and delivers HubSpot email integration across an Exchange Online estate. The supported core is first-party. HubSpot's connected-inbox capability logs sent email from Microsoft 365 mailboxes to the right HubSpot contacts, companies, and deals automatically, and the HubSpot Sales add-in for Outlook — published by HubSpot on Microsoft AppSource — is deployed centrally from the Microsoft 365 admin center so every in-scope user gets logging, tracking, and templates without per-user installs. IT Partner handles what makes this work cleanly at the tenant level: which mailboxes connect and which never do, shared mailbox and alias handling, never-log lists and excluded domains agreed with compliance, add-in deployment policies, and validation across the client mix of Outlook on the web, Windows, and Mac. On top of that foundation, scoped custom automation uses the Microsoft Graph API and Power Automate with the HubSpot REST APIs — for example, a flagged email creating a HubSpot follow-up task with context, meeting activity feeding HubSpot records, or approval and reminder notifications by email or Microsoft Teams. Where a HubSpot connector exists in the tenant's connector catalog it is validated during discovery; the dependable route is the HubSpot APIs through HTTP actions or a custom connector, which requires Power Automate premium licensing. Discovery also draws an honest line between automation that belongs in HubSpot's own workflow engine and automation that belongs in the Microsoft stack.
02 — Outcomes
Success criteria
01The agreed Microsoft 365 mailboxes are connected to HubSpot, and sent email logs automatically to the correct contacts, companies, and deals under the approved rules.
02The HubSpot Sales add-in for Outlook is deployed centrally to the agreed user groups and verified across the client's supported Outlook clients.
03Tenant-level logging rules — never-log lists, excluded domains, shared mailbox and alias handling — are configured and approved by the client's compliance stakeholder.
04Where scoped, custom workflows run as designed: flagged email creates a HubSpot follow-up task with email context, and reminders or approvals notify the agreed recipients by email or Microsoft Teams.
05Where scoped, calendar or meeting activity feeds the agreed HubSpot records through Microsoft Graph API or Power Automate automation.
06The boundary between HubSpot-native workflow automation and Microsoft-side flows is documented and approved.
07Agreed scenarios pass user acceptance testing with representative mailboxes and CRM records.
08Administrators receive handover documentation for mailbox connections, add-in deployment, logging rules, and custom flows.
03 — Deliverables
What you receive
✓Connected-inbox rollout for the in-scope Exchange Online mailboxes, with automatic logging of sent email to HubSpot.
✓Centralized deployment of the HubSpot Sales add-in for Outlook through the Microsoft 365 admin center for the agreed user groups.
✓Tenant-level logging and privacy configuration: never-log lists, excluded domains, association defaults, and the agreed handling of shared mailboxes and aliases.
✓Scoped custom automation built on Microsoft Graph API and Power Automate with the HubSpot REST APIs — flagged-email follow-up tasks, reminder and approval notifications, or calendar-driven activity logging.
✓A documented split between automations owned by HubSpot's native workflow engine and those owned by Microsoft-side flows.
✓Security configuration for custom components: OAuth 2.0 authentication, least-privilege Microsoft Graph permissions, and TLS-encrypted API connectivity.
✓Functional testing across representative mailboxes, Outlook clients, and HubSpot records, plus UAT support.
✓Administrator handover documentation covering mailbox connectivity, add-in deployment policies, logging rules, and any custom flows.
04 — Plan
How the work unfolds
Discovery and scope confirmation
Confirm the mailbox population, user groups, logging and privacy requirements, shared mailbox handling, HubSpot objects and association rules, and any custom automation requirements. Acceptance gate: scope and logging rules approved.
Readiness validation
Validate Microsoft 365 licensing, Exchange Online configuration, tenant add-in deployment policy, HubSpot subscription features for the scoped functionality, and Power Automate premium licensing where custom flows are in scope.
Connected inboxes and add-in rollout
Connect the agreed mailboxes to HubSpot, deploy the HubSpot Sales add-in centrally, and verify logging and tracking with pilot users across the client's Outlook client mix.
Logging rules and governance
Configure never-log lists, excluded domains, and association defaults with the client's compliance stakeholder, and document shared mailbox and alias behavior.
Custom workflow build
Build the scoped Graph API and Power Automate automations — flagged-email tasks, reminders, approvals, calendar-driven logging — and record which automations remain HubSpot-native.
Testing, UAT, and handover
Validate the agreed scenarios, support client UAT, remediate in-scope defects, and deliver administrator handover documentation.
05 — Before we start
Prerequisites
→Active Microsoft 365 tenant with Exchange Online mailboxes for the users in scope.
→Active HubSpot portal; connected-inbox logging and the Sales add-in are broadly available, while some template, sequence, and workflow features vary by HubSpot tier and are confirmed during scoping.
→Microsoft 365 administrator able to approve centralized add-in deployment, Microsoft Graph API consent, and any Exchange Online configuration in scope.
→HubSpot administrator able to approve inbox connections, app access, and logging settings.
→Power Automate licensing — premium where HTTP actions or a custom connector call the HubSpot APIs — for custom workflows in scope.
→Approved logging and privacy rules, including never-log addresses and domains and the treatment of shared mailboxes and aliases.
→Pilot users, representative test records, and sample email and calendar scenarios for validation.
→Named business, compliance, and technical contacts for design decisions, testing, and acceptance.
06 — Working together
Who does what
IT Partner
- Lead discovery and document the mailbox population, logging rules, association behavior, and custom automation scope.
- Connect the agreed Exchange Online mailboxes to HubSpot and validate automatic logging behavior.
- Deploy the HubSpot Sales add-in for Outlook centrally and verify it across the client's supported Outlook clients.
- Configure never-log lists, excluded domains, and association defaults with the client's compliance stakeholder.
- Build the scoped Microsoft Graph API and Power Automate automations against the HubSpot REST APIs with OAuth 2.0 and least-privilege permissions.
- Recommend honestly which automations belong in HubSpot's native workflow engine rather than external flows.
- Support testing, UAT, and remediation of implementation defects during the agreed validation period.
- Provide administrator handover documentation for the delivered configuration.
Your team
- Provide timely access to Microsoft 365, Exchange Online, and HubSpot administrators for approvals and configuration.
- Confirm Microsoft 365, HubSpot, and Power Automate licensing for the agreed scope.
- Approve the logging and privacy rules, including never-log lists, excluded domains, and shared mailbox treatment.
- Define the business rules for custom workflows: triggers, task fields, reminder logic, approvers, and notification recipients.
- Provide pilot users, test mailboxes, and representative HubSpot records for validation.
- Complete user acceptance testing and provide production sign-off.
- Communicate the rollout to end users, including what is logged and how to exclude a message.
- Own HubSpot data quality, mailbox lifecycle, licensing, and logging-rule maintenance after handover.
07 — Scope
What's not included
✕Microsoft 365, Exchange Online, HubSpot, or Power Automate license costs; premium connector licensing for custom flows is purchased by the client.
✕Historical backfill of email or calendar items predating the integration, unless separately scoped as a custom import.
✕Large-scale HubSpot cleanup, deduplication, or CRM redesign beyond what the integration requires.
✕Exchange Online migration, mailbox migration, hybrid Exchange work, or tenant-wide remediation unless separately scoped.
✕Marketing strategy, campaign content, template copywriting, or deliverability consulting.
✕Custom Outlook add-in development beyond deploying the HubSpot Sales add-in and the scoped Power Automate or Graph API workflows.
✕Integration with additional CRMs, marketing platforms, ticketing, ERP, or data warehouse systems unless added to scope.
✕Compliance program design — retention, eDiscovery, DLP, records management — beyond validating the integration's logging rules.
✕End-user training programs or organization-wide change management beyond standard handover, unless added to the statement of work.
✕Guarantees that every message associates with the correct HubSpot record; matching depends on data quality and the agreed rules.
✕24/7 support, continuous monitoring, ongoing maintenance, and optimization are not included by default; they are available as optional extra-cost add-ons delivered through IT Partner's NOC, third-party support partnerships, and a Microsoft Premier Support agreement.
08 — Fine print
Limitations & technical notes
!Automatic logging applies from the moment a mailbox is connected; earlier email is not backfilled by default.
!Shared mailboxes, aliases, and delegate scenarios behave differently from personal mailboxes and are designed case by case during discovery.
!Add-in support follows the current HubSpot and Microsoft compatibility matrices for Outlook on the web, Windows, and Mac.
!Some HubSpot features vary by subscription tier; the scoped functionality is validated against the client's actual HubSpot edition.
!Custom flows are subject to Microsoft Graph API and HubSpot API rate limits, and premium Power Automate licensing applies where HTTP actions or custom connectors are used.
!Message properties restricted by encryption, sensitivity labels, or tenant security policies may be unavailable to logging or automation.
!The client owns the privacy decisions the logging rules implement; IT Partner configures what compliance approves.
!The service is billed hourly at the published rate; a standard engagement is planned at five days, with the final timeline depending on mailbox count, logging rules, and custom workflow scope.
09 — Questions
Frequently asked questions
What is the HubSpot + Microsoft Exchange Online Integration service?
IT Partner connects HubSpot to Exchange Online across the tenant: connected inboxes that log sent email to HubSpot automatically, centralized deployment of the first-party HubSpot Sales add-in for Outlook, tenant-level logging and privacy rules, and scoped Microsoft Graph API and Power Automate automation for what the first-party tools do not cover.
How is this different from the HubSpot + Microsoft Outlook integration?
Same first-party foundation, different altitude. The Outlook service focuses on the user-facing add-in experience; this service delivers the Exchange Online estate work — mailbox population planning, shared mailbox and alias handling, centralized add-in deployment policy, and compliance-approved logging rules — so the integration is consistent across the whole tenant rather than per user.
Is there a supported first-party path for HubSpot and Microsoft 365 email?
Yes. HubSpot's connected-inbox capability logs sent email from Microsoft 365 mailboxes automatically, and HubSpot publishes the HubSpot Sales add-in for Outlook through Microsoft AppSource, deployable centrally from the Microsoft 365 admin center. This service builds on those supported capabilities; custom Graph and Power Automate work extends them.
How are shared mailboxes and aliases handled?
Deliberately, because they behave differently from personal mailboxes. During discovery IT Partner maps which shared mailboxes and aliases should log to HubSpot at all, how their email should associate with records, and which must never be connected — then configures and validates exactly that. The design is documented so behavior is predictable.
Can we control what gets logged into HubSpot?
Yes. Never-log lists and excluded domains keep specified senders and recipients out of the CRM, users can exclude individual messages, and the mailbox population itself is an explicit decision. The rules are agreed with your compliance stakeholder before any mailbox is connected.
Can a flagged email create a follow-up task in HubSpot?
Yes, as scoped custom automation: a Power Automate flow watches for the agreed trigger and creates a HubSpot task with email context through the HubSpot APIs. Flows calling the HubSpot APIs through HTTP actions or a custom connector require Power Automate premium licensing.
Can calendar events feed HubSpot activities?
Yes, where scoped — Microsoft Graph API and Power Automate can turn agreed meeting activity into HubSpot activity records or tasks. For the dedicated calendar scenarios, including HubSpot's first-party calendar sync and Meetings scheduling pages, see IT Partner's HubSpot + Microsoft Outlook Calendar integration service.
Should automation live in HubSpot workflows or in Power Automate?
It depends on the trigger and the data, and discovery answers it per automation. HubSpot's own workflow engine natively handles much marketing and follow-up automation; Power Automate earns its place when the trigger or the target lives in Microsoft 365 — a flagged email, a Teams notification, a calendar event. The split is documented so both sides stay maintainable.
What licensing do we need?
A Microsoft 365 tenant with Exchange Online, and a HubSpot portal — connected-inbox logging and the Sales add-in are broadly available, with some features varying by HubSpot tier and confirmed during scoping. Custom flows calling the HubSpot APIs require Power Automate premium licensing.
Can historical email be imported into HubSpot?
Not by default: automatic logging starts when a mailbox is connected. Historical backfill is separately scoped custom work through the HubSpot APIs, sized against volume, matching quality, and API limits before any commitment.
How long does the integration take, and how is it priced?
The service is billed hourly at the published rate, with total effort scoped per project. A standard engagement is planned at five days; the final timeline depends on mailbox count, logging-rule complexity, and the number of custom workflows.
What happens after the integration is completed?
Connected inboxes keep HubSpot current automatically, the add-in serves every in-scope user, and custom flows run under documented ownership. Administrators hold the handover documentation; 24/7 support, continuous monitoring, and ongoing maintenance are optional extra-cost add-ons through IT Partner's NOC, third-party support partnerships, and a Microsoft Premier Support agreement.