How to Connect Office 365 / Gmail to Freshdesk

Native mailbox vs forwarding: the decision first

Before you touch a setting, decide which of the two models you're building, because they behave differently once mail starts flowing.

Forwarding keeps your mailbox where it is and simply pushes a copy of every inbound message to your Freshdesk address. Your mail provider does the sending; Freshdesk only receives. It's the fastest thing to set up — one forwarding rule in Google Workspace or Exchange — and it works on every plan. The catch is that replies go out from Freshdesk's own infrastructure on your behalf, which means deliverability leans on you publishing the right SPF and DKIM records so that mail isn't spoofing your domain from a receiving server's point of view.

Native OAuth connection is the tighter integration. Here Freshdesk authenticates directly into your Office 365 or Gmail mailbox and both reads incoming mail and sends outgoing replies through that same account. Per the Freshworks documentation on using custom email servers, you connect a provider under Admin → Channels → Email → New support email and pick from Gmail, Microsoft Office 365, the Freshworks mail server, or a Custom server. The advantage is that outgoing replies genuinely originate from your real mailbox, so deliverability and threading behave the way your customers expect.

If you already run Office 365 or Google Workspace, the native OAuth route is usually worth the extra minutes — it's the setup this guide focuses on.

Step 1: Open the email channel and start a new support email

Everything starts in the same place regardless of provider.

1. Go to Admin → Channels → Email (labelled Support Email in some accounts).
2. Click New support email.
3. In the Connect your support email panel, choose your mail server: Gmail, Microsoft Office 365, Freshworks mail server, or Custom.
4. Choose whether Freshdesk should use this mailbox for Incoming only, Outgoing only, or Incoming and outgoing — most teams want both.

That single "incoming/outgoing/both" toggle matters more than it looks. If you want customers' mail to become tickets and agent replies to leave from your real mailbox, you need both. If you only want Freshdesk to send (and you're forwarding inbound some other way), pick outgoing only. This same channel screen is where all of Freshdesk's email configuration lives, so it's worth getting comfortable with it.

Step 2: Connect a Microsoft Office 365 mailbox over OAuth

With the Microsoft Office 365 card selected, Freshdesk reveals a Sign in button that kicks off the OAuth 2.0 handshake.

1. Click Sign in. You'll be redirected to Microsoft's own login page — you authenticate with Microsoft, not with a password you hand to Freshdesk.
2. Sign in with the account (or shared mailbox) you want to use as your support address.
3. Review the consent screen and authorize read/write/delete access to the mailbox. Freshdesk needs read to pull incoming mail into tickets, and write/send to post agent replies.
4. Microsoft returns a token to Freshdesk and you'll see a success confirmation. The mailbox is now live.

The reason OAuth is the default now is security: Freshdesk connects using a revocable token rather than storing your Microsoft password anywhere. If your IT team runs tight conditional-access policies, be ready to approve the Freshdesk app in Entra ID, and if the connection keeps dropping, your admins may need to allowlist Freshdesk's IP ranges on the mail server. Should an existing Office 365 mailbox ever fall out of authorization, Freshworks documents the fix under reauthorization of a custom mailbox — you re-run the same sign-in from Admin → Channels → Email → Re-authorize.

Step 3: Connect a Gmail / Google Workspace mailbox over OAuth

The Gmail flow mirrors Office 365 but goes through Google's consent screen.

1. On the New support email panel, select Gmail.
2. Click Sign in with Google and choose the Workspace account you want as your support inbox.
3. On Google's consent screen, authorize read/write/delete access so Freshdesk can fetch messages, compose, send, and delete on the mailbox's behalf.
4. Confirm, and Gmail is added as a connected support email.

This OAuth path isn't optional anymore, and that's the important thing to internalize. Per Freshworks' Gmail Basic Auth deprecation notice, Google stopped supporting third-party sign-ins that use only a username and password as of September 30, 2024. Any old Freshdesk-Gmail connection built on basic auth silently stops working after that date — no ticket creation, no agent replies, no notifications — until you re-authorize with Sign in with Google. If you're setting up fresh in 2026 you'll land on OAuth automatically; if you inherited an older account, check for a basic-auth warning on the email channel and re-authorize it.

Step 4: (Optional) Use a custom IMAP/SMTP server instead

If your mail isn't on Office 365 or Google Workspace — or your security team insists Freshdesk never hold an OAuth token — the Custom option lets you connect any IMAP/SMTP mailbox. You'll supply the incoming server and port, the outgoing server and port, and credentials. Freshworks' guidance is to enable IMAP and authenticated SMTP on the mailbox and use the standard secure ports: IMAP on 993 (SSL) and SMTP on 587 (or 465), with an auth method of Plain, Login, or CRAM-MD5. One honest gotcha: on the Free plan you can add only a single email through custom servers, so multi-mailbox teams on Free will hit that wall quickly. For most people, native OAuth is simpler and more resilient than hand-managing IMAP credentials — but the custom route exists for the edge cases.

Step 5: Verify domain deliverability (DKIM / DNS)

Connecting the mailbox is only half the job; you also want outbound replies to land in inboxes rather than spam. Freshdesk lets you verify your domain and publish DKIM records so that mail sent through the platform is cryptographically signed as legitimately yours. This is where the domain gating shows up honestly: DKIM and custom-domain verification are tied to you controlling the DNS for your sending domain, and you'll need to add the CNAME/TXT records Freshdesk generates to your DNS provider. If you skip this, a native OAuth mailbox will still send from your real address and generally be fine — but a forwarding setup that sends on your behalf is far more likely to get filtered without proper SPF and DKIM in place. Set it once, and both threading and deliverability get quietly better.

The honest limits — and where an AI layer picks up

Freshdesk's native email is genuinely solid. The OAuth mailbox connection is secure, the incoming/outgoing/both control is flexible, and turning mail into tickets is dependable. It's the right foundation and you should keep it. But it's worth being clear about what connecting a mailbox does not do.

Connecting Office 365 or Gmail to Freshdesk moves email into your help desk — it does not answer any of it. Freshdesk will faithfully create a ticket the moment a customer emails, thread the conversation, and send whatever an agent types back through your real mailbox. What it can't do is read the customer's actual question, pull the relevant answer from your docs or systems, and draft the reply. The mailbox is plumbing; the reasoning is still entirely on your agents.

That's the seam where an AI agent layer fits, and it's worth understanding the build-versus-buy tradeoff before reaching for one. The broader category of AI agents for customer service exists precisely to do the reading-and-writing work that a connected mailbox can't. Macha is one such layer: it runs on top of the Freshdesk you already use as a native connector — it does not replace your help desk, your mailbox connection, or your email channel. You link Macha to Freshdesk with your subdomain and API key, and it reads and writes the very same tickets your OAuth mailbox is creating: drafting or posting grounded first replies from your knowledge base, triaging incoming mail by intent, and looking up order or account status through a custom tool that turns a REST API into something the agent can call. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. And credits are consumed per AI action, not per resolution — see the pricing breakdown.)

The clean division of labour: let Freshdesk own the mailbox — receiving mail over OAuth, sending replies from your real domain, keeping the channel as the system of record — and layer an agent on top for the part the plumbing can't do, which is actually reading and answering the mail fast. If you're still standing up the account itself, our Freshdesk setup guide covers the surrounding pieces, and how to automate Freshdesk with AI picks up where this mailbox setup leaves off.

FAQ

Where do I connect an Office 365 or Gmail mailbox in Freshdesk? Go to Admin → Channels → Email (labelled Support Email in some accounts), click New support email, and select Microsoft Office 365 or Gmail as the mail server. Then sign in through the provider's own OAuth consent screen and authorize read/write/delete access to the mailbox.

Is OAuth required, or can I still use a password? For Gmail it's effectively required — Google stopped supporting username-and-password third-party sign-ins as of September 30, 2024, so any basic-auth connection stops working and must be re-authorized with Sign in with Google. Office 365 uses OAuth 2.0 as well, connecting via a revocable token rather than a stored password.

Should I forward email or connect the mailbox natively? Forwarding is faster and works on every plan, but replies go out through Freshdesk's infrastructure on your behalf, so deliverability leans heavily on your SPF and DKIM records. Native OAuth connects Freshdesk directly to your Office 365 or Gmail mailbox so outgoing replies originate from your real account — usually the better choice if you're already on those platforms.

Can I use a mailbox for only sending or only receiving? Yes. When you add a support email you choose Incoming only, Outgoing only, or Incoming and outgoing. Most teams pick both so inbound mail becomes tickets and agent replies leave from the same real mailbox.

Can I add AI to my Freshdesk email without replacing Freshdesk? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and runs on top of your existing help desk and its email channel — it doesn't replace your mailbox connection. It helps answer the mail by drafting or sending grounded first replies and triaging by intent, while Freshdesk stays the system of record for receiving and sending.

Ready to put an agent behind the mailbox you just connected? Start a free trial of Macha and connect it to your Freshdesk in minutes.