Office 365 connection fails with account_has_no_email despite valid Exchange Online UserMailbox

Smart CRM & Sales Hub Account & Settings
1

Office 365 connection fails with account_has_no_email despite valid Exchange Online UserMailbox

Post

Hi all — I’m hoping someone has encountered this before or can point me toward a HubSpot-side resolution.

I’m trying to connect my Microsoft 365 work email to HubSpot as my individual email account. Every attempt fails with:

“Office 365 inbox and calendar not found”

The OAuth URL/error shows:

account_has_no_email

The mailbox is hosted in Microsoft 365 / Exchange Online, and I have already worked through the standard Microsoft-side troubleshooting.

What I have confirmed:

  • Exchange Admin Center shows the account as an active UserMailbox
  • The primary mailbox/email address is the same address I am using to authenticate with HubSpot
  • The Microsoft 365 user ID/sign-in address matches the mailbox address
  • Outlook on the web opens normally when signing in directly with that account
  • The mailbox is actively sending and receiving email
  • The user has Microsoft 365 Business Standard / Exchange Online
  • I retried the HubSpot connection in a clean private/incognito browser session with only this Microsoft account authenticated
  • The same account_has_no_email error still occurs

I also checked the HubSpot Sales Enterprise Application in Microsoft Entra.

All eight required Microsoft Graph delegated permissions are present with Admin Consent:

  • Calendars.ReadWrite
  • Calendars.Read
  • Mail.Send
  • Mail.ReadWrite
  • offline_access
  • openid
  • email
  • User.Read

I then checked Microsoft Entra Sign-in Logs immediately after attempting the connection. The HubSpot Sales sign-ins to Microsoft Graph show Success, including the connection attempts that ultimately produced the HubSpot error.

So at this point:

Exchange mailbox exists and is active → Microsoft authentication succeeds → Graph permissions are present and consented → HubSpot still reports that the authenticated Microsoft account has no mailbox.

I also went through HubSpot’s chat troubleshooting. After reviewing the above, HubBot said this appeared to require HubSpot-side escalation because there is no documented self-service reset for this specific Office 365 OAuth account_has_no_email state. Unfortunately, I wasn’t able to get a useful resolution through chat.

Has anyone seen this particular situation?

Specifically, I’m trying to determine:

  1. What Microsoft/Graph property is HubSpot using to decide that the authenticated account “has no email”?
  2. Can there be a stale or corrupted Microsoft 365 OAuth/integration state stored against a HubSpot user?
  3. Is there any way to fully reset the Microsoft connection on the HubSpot side, rather than simply revoking/re-authorizing Microsoft permissions?
  4. Is there another Exchange/Graph property I should inspect that is not part of HubSpot’s normal troubleshooting checklist?

I’d appreciate any suggestions from someone who has dealt with this exact account_has_no_email error after confirming that the Exchange Online mailbox and Graph authentication are valid.

Thanks!

2

You already cleared the usual Microsoft-side checklist. When Graph sign-in succeeds and HubSpot still returns account_has_no_email, it is usually a stale HubSpot-side OAuth binding or a mailbox attribute HubSpot’s connector expects that Entra UI does not highlight.

Worth one more pass before / while escalating:

  1. In HubSpot, fully disconnect Personal email + Calendar for that user (not only revoke in Entra). Wait a few minutes, then reconnect in a clean profile with only that M365 account signed in.

  2. Confirm the HubSpot user email exactly matches the Exchange primary SMTP (including alias vs primary). A login UPN that differs from primary SMTP still authenticates in Entra and fails HubSpot’s mailbox probe.

  3. In Exchange Online PowerShell (or admin center mailbox properties), confirm RecipientTypeDetails = UserMailbox and that the mailbox is not Shared / Room / Guest-only. Shared mailboxes often auth and then fail this exact probe.

  4. Check the user is not blocked from HubSpot Sales Outlook / email integration by a portal permission or seat that looks “connected” in Entra but is disabled in HubSpot users.

  5. Escalate with a tight packet: Portal ID, HubSpot user email, M365 UPN, primary SMTP, timestamp of a failed connect, Entra sign-in request id for that Graph success, and the OAuth error string account_has_no_email. Ask for a server-side Microsoft integration reset for that user. Self-serve re-consent usually does not clear a corrupted binding.

If primary SMTP and HubSpot login email differ by even an alias, fix that match first. Otherwise treat it as HubSpot-side reset, not more Graph permission toggles.

3

Update: Additional HubSpot-side checks completed.

I have now verified my HubSpot user configuration:

  • User is a Super Admin.
  • Assigned seat is Core Seat, not View-Only.
  • Personal email is not connected.
  • Calendar settings explicitly state “Your calendar is disconnected.”
  • There is no existing calendar connection available to disconnect or remove.

All previously documented Microsoft-side checks remain valid, including the active Exchange Online UserMailbox, successful Microsoft Graph sign-ins, and eight delegated permissions with admin consent.

The account_has_no_email error continues despite these checks.

Is there a HubSpot employee or Community expert who can advise how to escalate this for a server-side investigation? Specifically, I need someone to examine the OAuth mailbox-discovery failure and determine whether a stale integration binding needs to be cleared.

I would appreciate a diagnostic or escalation path rather than another round of the standard Microsoft mailbox troubleshooting.

4

Hi @JPartington,

Welcome to the community and thanks for walking us through what you’ve attempted so far.

One additional point that I’d make sure is: the address being connected is the mailbox’s actual primary address, not merely an alias. HubSpot documents limitations involving non-Microsoft primary aliases, and its Office 365 integration is intended for individual Microsoft 365-hosted mailboxes rather than shared mailboxes. We can see this noted here: Troubleshoot inbox and calendar connection errors

Hope this helps!

Sam, Community Manager

5

You’ve already done a pretty thorough round of troubleshooting here. If the Exchange mailbox is active, Outlook works normally, and the Entra sign-in logs show successful Graph authentication, I’d probably stop focusing on the Microsoft permissions side for now.

The part that stands out to me is the account_has_no_email response. In a setup like this, HubSpot is likely getting through the Microsoft authentication successfully, but something in the account/mailbox information returned during the OAuth flow isn’t matching what HubSpot expects when it checks for the mailbox.

A couple of things I’d check before pushing this back to HubSpot:

First, if you haven’t already, check the user through Microsoft Graph Explorer and look at the actual user/mailbox-related values being returned for that account. In particular, I’d compare the authenticated user’s id, userPrincipalName, mail, and proxyAddresses. Sometimes the sign-in address and the primary SMTP address look identical in the admin UI but there can still be an underlying alias/proxy-address difference.

I’d also check whether the account has any unusual Exchange configuration - for example, aliases, a recently changed primary SMTP address, a migrated mailbox, or a previous mailbox associated with the same Entra user. Those situations can sometimes make OAuth integrations behave differently even though Outlook itself works perfectly.

Since you’ve already revoked/re-authorized permissions and reproduced the issue from a clean browser session, I don’t think repeatedly consenting to the same Graph permissions is likely to change much.

At this point, I’d also try disconnecting/removing the Microsoft connection from the HubSpot user/account side, if that option is available in your portal, and then reconnecting it from scratch. If there’s no way to fully remove the existing connection/token state in HubSpot, that’s the point where I’d escalate it to HubSpot Support and specifically ask them to check the OAuth/integration record for the affected HubSpot user.

When opening the ticket, I’d include the exact error account_has_no_email, the affected HubSpot user, the Microsoft account UPN/email, and the fact that Microsoft Graph authentication succeeds in Entra sign-in logs. That should help them get past the basic permission checklist and look at what HubSpot is actually receiving from Microsoft.

I haven’t seen a documented HubSpot-side setting that lets an admin manually reset an account_has_no_email state, so if all of the above checks out, I’d treat this as an integration-state/data-mapping issue rather than an Exchange mailbox problem.

6

I faced a similar issue a while ago. In many cases, this happens when the Exchange Online mailbox has a license, but HubSpot is unable to properly identify the mail attribute.

You can try removing the Office 365 connection and reconnecting it. Also, check the mailbox permissions in the Microsoft 365 Admin Center. If the issue still persists, it may be worth submitting a ticket to HubSpot Support, as it could be related to a backend sync issue.