Overview
Outlook on Microsoft 365 brings mailbox email into the same system as your pipeline. For enterprises already on Entra ID, conditional access and admin consent flows are part of a successful rollout. Pair this with Outlook Calendar sync so meetings and mail stay aligned on each account.
What data is involved
- Email threads and metadata attached to CRM leads, contacts, and optionally opportunities.
- Microsoft identity (work or school account); shared mailboxes where supported.
- Complements but is distinct from Teams notifications—Teams is channel alerts; Outlook is mailbox content.
Step-by-step setup
Setup at a glance (3-5 bullets)
- Go to Settings → Integrations → Outlook / Microsoft 365 (Email).
- Sign in with Microsoft; complete admin consent in Entra ID if your IT policy requires it.
- Select the mailbox or shared mailbox and confirm sync folders (e.g. Sent, Inbox).
- Run a test send or receive and confirm the activity attaches to the correct lead or contact.
Sign in or sign up at HelloGrowthCRM. Open the login page, enter your credentials (or use Google), or choose Sign up if you need a new account. You must be signed in before you can open Settings and connect this integration.

Open login page(opens in a new tab)app.hellogrowthcrm.com/login
Open Settings. In the left sidebar, under Admin, click Settings (you will land on the Settings area; the URL is app.hellogrowthcrm.com/settings).

Open Settings(opens in a new tab)app.hellogrowthcrm.com/settings
Go to Integrations. On the Settings screen, use the middle settings menu. Under COMMUNICATION, click Integrations (star icon). Then find and configure this connector—the connector-specific steps below pick up from here.

Open Settings (Integrations)(opens in a new tab)app.hellogrowthcrm.com/settings
- Go to Settings → Integrations → Outlook / Microsoft 365 (Email).
- Sign in with Microsoft; complete admin consent in Entra ID if your IT policy requires it.
- Select the mailbox or shared mailbox and confirm sync folders (e.g. Sent, Inbox).
- Run a test send or receive and confirm the activity attaches to the correct lead or contact.
Best practices
- Work with IT on consent grants and retention policies before connecting production mailboxes.
- Use clear rules for when to create activities vs only link threads to existing records.
- Review litigation hold or archive requirements if regulated email must not leave Microsoft storage.
Best for & common use cases
Organizations on Microsoft 365 that want one place to see pipeline, tasks, and customer email.
- Enterprise sellers moving between Outlook and CRM without copy-paste.
- Compliance-friendly retention of customer email alongside deal updates.
Expected outcomes
- Faster lead handoff between tools and CRM owners
- Cleaner activity history for follow-up and reporting
- Lower manual copy-paste errors in the pipeline
FAQ
Governance
Treat API keys and webhooks as production secrets. Align field mapping with your privacy policy and regional regulations (GDPR, marketing consent, telemarketing rules). Your admin controls which roles can install or edit integrations.
Related integrations in this category
Rich CRM notifications in Slack channels (new leads, deal updates, task reminders).
CRM notifications with rich embeds via webhook to your server channels.
Adaptive Card notifications in Teams channels for CRM events and deep links to records.
Template messages with delivery tracking; send and receive WhatsApp conversations with leads (sent, delivered, read).
Creates and updates Intercom contacts from CRM records; adds internal notes for support context.
Gmail, Calendar, Sheets, and Drive integration: mailbox sync to leads and contacts plus Workspace productivity context alongside pipeline work.
Social messaging integration: route Meta inbox conversations into CRM threads with contact linkage.
Bot integration for messaging and notifications from CRM events to Telegram chats or channels.