All Docs
FeaturesNurtureHubUpdated March 21, 2026

Microsoft 365 Email Delivery — Release Highlights v1.0.66

Microsoft 365 Email Delivery — Release Highlights v1.0.66

Released in v1.0.66. NurtureHub can now send nurture emails through an agent's own Microsoft Outlook or Microsoft 365 account, using the Microsoft Graph API.

Overview

For agencies running on Microsoft 365 or Outlook, nurture emails can now be sent directly from the agent's own mailbox — from their own domain, through their own mail infrastructure. Emails land in recipients' inboxes with the agent's real sending address and appear in the agent's Outlook Sent Items folder exactly as if they had written each email themselves.

This removes reliance on third-party sending domains and preserves the email thread continuity that agents already manage in Outlook.

How It Works

1. Connect Your Microsoft Account

Agents connect their Microsoft account from the Integrations section of NurtureHub settings. Clicking Connect Microsoft 365 initiates the standard Microsoft OAuth 2.0 consent flow.

The following permission scopes are requested:

ScopePurpose
Mail.SendSend emails on behalf of the agent
offline_accessObtain refresh tokens for background sending

Both personal Microsoft accounts (Outlook.com, Hotmail) and organisational Microsoft 365 tenants (custom domains via Azure AD / Entra ID) are supported.

2. Token Storage and Refresh

After consent, NurtureHub stores access and refresh tokens in encrypted form. Tokens are never stored in plaintext. Before each send, the platform checks token validity and silently refreshes if needed — agents are not interrupted or asked to re-authorise during normal use.

3. Email Delivery via Microsoft Graph API

When a nurture sequence email is dispatched, NurtureHub calls the Microsoft Graph API mail endpoint:

POST https://graph.microsoft.com/v1.0/me/sendMail

The email is composed with the personalised content generated for the contact's nurture sequence and sent from the agent's own mailbox address. A copy is automatically saved to the agent's Outlook Sent Items folder by the Graph API.

4. Delivery Tracking

Delivery confirmation is recorded and surfaced in the NurtureHub engagement dashboard. Open and click events are tracked alongside delivery status, feeding into the platform's real-time intent scoring and hot lead alerts.

Supported Account Types

Account TypeSupported
Personal Microsoft account (Outlook.com, Hotmail.com, Live.com)✅
Microsoft 365 Business (organisational tenant, custom domain)✅
Microsoft 365 Enterprise / Azure AD tenants✅
On-premises Exchange (no Graph API access)❌

Note for M365 tenant administrators: Depending on your organisation's Azure AD settings, an administrator may need to grant tenant-wide admin consent for the Mail.Send scope before individual users can connect. This is a standard Microsoft requirement for multi-tenant OAuth applications.

Benefits for Agents

  • Send from your own domain — Recipients see the agent's real email address, not a third-party sending domain.
  • Outlook Sent Items continuity — Every nurture email appears in Sent Items, keeping the agent's inbox history complete.
  • No extra configuration — Once connected, email delivery is fully automatic. No SMTP credentials, no DNS records to manage.
  • Secure by default — OAuth 2.0 with encrypted token storage; NurtureHub never sees the agent's Outlook password.

Connecting Your Account

  1. Go to Settings → Integrations.
  2. Under Email Delivery, select Microsoft 365 / Outlook.
  3. Click Connect Microsoft 365 and complete the Microsoft consent screen.
  4. Once authorised, the status will show Connected with the sending address confirmed.
  5. All future nurture sequence emails for this account will be sent via Microsoft Graph API.

To disconnect, click Remove Connection from the same screen. This immediately revokes NurtureHub's access and stops Graph API sending.

Related