Halo Email Integration
Halo connects directly to your Microsoft 365 or Google Workspace mailbox and turns every incoming email into a ticket — instantly, automatically, with zero manual work. Native integration, included in every licence.
Email Providers
Whether your organisation runs Microsoft 365, Google Workspace, or something else — Halo has a native connection for it.
Connect any Microsoft 365 mailbox — including shared mailboxes like support@company.com. Choose between instant webhook delivery or a 3–5 minute polling scan.
Connect Gmail accounts to Halo via OAuth 2.0. Halo uses the Gmail API to process incoming mail and create tickets automatically. A dedicated Google licence is required per mailbox.
Not on Microsoft or Google? Halo also supports IMAP, POP3, and Exchange Web Services (EWS) for on-premises Exchange and other mail providers. Full flexibility for every environment.
Microsoft 365 Processing Methods
For Microsoft 365 mailboxes, Halo offers two email processing methods. Both work. One is significantly faster.
Azure sends a notification to Halo the instant an email arrives in the mailbox. Halo processes it immediately — tickets are created in seconds, not minutes. This is the recommended method for all new setups.
Halo polls the mailbox on a schedule — typically every 3 to 5 minutes. Straightforward to set up and reliable. Best suited for lower-volume environments or where webhooks are not possible.
What's Included
Halo's email integration handles the full lifecycle — not just creating the ticket, but threading replies, logging every message, and alerting your team when something goes wrong.
Connect a team inbox — support@, helpdesk@, info@ — not a personal account. Halo handles shared mailboxes natively, with the correct permission setup for both methods.
When a user replies to a ticket notification, Halo recognises the thread and updates the existing ticket — it doesn't create a duplicate. Conversation history stays in one place.
Every email that passes through the mailbox is logged — when it arrived, how it was processed, and whether it succeeded. Search the inbound log anytime from within Halo.
Configure which agents receive a notification if email processing fails. No silent errors — the right person knows the moment something goes wrong, before users start complaining.
Import Outlook contacts directly into Halo as users. Map Outlook fields to Halo user fields, and schedule regular syncs via the Halo Integrator. New users are matched to sites by email domain.
For webhook connections, Halo automatically renews the Azure subscription before it expires — no manual intervention, no maintenance windows, no risk of the mailbox going silent.
Who It's For
If most of your tickets come in via email — and you need that to work instantly, reliably, and with full visibility — Halo was built for this.
Setup Overview
Allied ESM handles the full email integration setup as part of every Halo implementation — so you're live from day one.
A single App Registration in your Microsoft tenant with the correct Mail.ReadWrite and Mail.Send permissions. Allied ESM does this for you.
Paste in your tenant credentials, choose your processing method (webhook is recommended), and create the subscription. Takes minutes.
From the moment the subscription is created, every email landing in your mailbox triggers a new ticket in Halo. Automated, logged, and threaded.
FAQ
Book a demo with Allied ESM and we'll walk you through how email lands in your mailbox and becomes a managed ticket in Halo — in under 30 seconds.