Freshdesk and Outlook: what syncs, what doesn't, and how to set it up
Freshdesk connects a Microsoft 365 mailbox as a support email and turns incoming mail into tickets. An older app pushes ticket alerts into Outlook. Calendar and contacts do not sync.
- Connector
- Native mailbox connection built by Freshdesk (Admin > Channels > Email), plus a Freshdesk-built Office 365 app from the Apps page; no separate fee in the docs
- Sync direction
- Outlook → Freshdesk for email; Freshdesk → Outlook for replies and agent alerts; agents can update tickets from Outlook
- Setup time
- Under 30 minutes for the mailbox (our estimate; the docs give no time), longer if a Microsoft 365 admin must enable IMAP and SMTP
- Availability
- Freshdesk Growth, Pro and Enterprise (Blossom and above on previous plans); the docs conflict on Free; any Microsoft 365 mailbox with IMAP and authenticated SMTP enabled
- Our rating
- 3 out of 5. Microsoft 365 mail becomes tickets and replies go out through Outlook; calendar and contacts don't sync, and tokens can need reauthorizing every 90 days.
| What | Direction | Detail |
|---|---|---|
| Incoming support email | Outlook → Freshdesk | Freshdesk converts each email received on the connected Microsoft 365 mailbox into a ticket. You choose Incoming only, Outgoing only, or both when you add the address. |
| First fetch on setup | Outlook → Freshdesk | Freshdesk fetches the last day of Inbox email, read and unread, and creates tickets from it. Older mail does not come in. |
| Agent replies | Freshdesk → Outlook | With Outgoing only or both, Freshdesk sends replies through the Microsoft server. With Incoming only on a company-domain address, it sends through the Freshworks mail server instead. |
| Delete after fetching | Freshdesk → Outlook | Optional setting that deletes each email from the mailbox once Freshdesk fetches it. Freshdesk recommends leaving it off. |
| Ticket alerts to agents (Push to Outlook) | Freshdesk → Outlook | A Dispatch'r or Observer rule forwards the ticket as an actionable message to the assigned agent's Outlook inbox. The agent's email in Freshdesk must match their Outlook address. |
| Notes from Outlook | Outlook → Freshdesk | Agents add a private note from the actionable message. They add a public note by replying to the ticket email. |
| Priority and agent changes | Outlook → Freshdesk | Agents change ticket priority or assigned agent from the Outlook message, without opening Freshdesk. |
| Group and product routing | Derived | Each connected address can assign its tickets to a group and link them to a product. Freshdesk applies this by the address that received the email. |
Setting it up
- Check that your Microsoft 365 mailbox has IMAP and authenticated SMTP enabled. Ask your Microsoft 365 admin if SMTP authentication is off.
- Log in to Freshdesk as an administrator and go to Admin > Channels > Email > New Support Email.
- Choose Incoming only, Outgoing only, or Incoming and outgoing. Pick the last one if replies should leave through Outlook.
- Select Microsoft Office 365, sign in, and authorize read, write and delete access. Use an incognito window if your browser is signed in to a personal account.
- Open the address on the email list, then set the group, the product link and the delete-after-fetching option under General Settings.
- Optional: go to Admin > Support Operations > Apps, install Office 365, add each agent's Outlook address in Freshdesk, and create a Dispatch'r or Observer rule with the Push to Outlook action.
Where the integration stops
- No calendar sync. The docs describe none, and a Freshworks community reply says there is no native Outlook calendar integration and gives no date. Use Zapier, Power Automate or the Freshdesk API.
- Tokens expire. Microsoft's default refresh token lifetime is 90 days, so you may need to reauthenticate. A password change also breaks the link, and one unauthorized mailbox shows the reauthorize banner to every user.
- Your Microsoft 365 tenant can block the connection. IMAP and authenticated SMTP must be on, and Freshdesk's troubleshooting page says most tenants disable SMTP authentication by default. It also cites a 10,000 emails per day Office 365 sending limit.
- Shared mailboxes need care. Enter the shared mailbox's primary address. A Freshworks community reply advises against shared inboxes and suggests forwarding to an individual mailbox.
- The Outlook app is old and narrow. Its help page was last modified on 18 June 2021, covers individual Office 365 accounts only, and does not work for groups.
- Contact sync is undocumented. A Microsoft Outlook Contacts app is listed in the Freshworks marketplace, but the listing gives no direction, fields or plan.
Freshdesk connects a Microsoft 365 or Outlook.com mailbox as a support email. It suits teams that already run support from an Outlook address and want that mail in tickets. Freshdesk reads the mailbox, creates tickets, and can send replies through the same account.
The fact that surprises teams: this is a mailbox connection, not a record sync. Contacts, calendar events and ticket fields do not move between Freshdesk and Outlook. The only extra layer is an Office 365 app that pushes ticket alerts into agents' Outlook inboxes.
The mailbox connection is the integration
You add the mailbox under Admin > Channels > Email and pick a direction. Incoming only fetches mail. Outgoing only sends replies through Microsoft. The third option does both.
The choice changes where replies come from. If you pick Incoming only for a company-domain address such as help@acme.com, Freshdesk sends replies through its own Freshworks mail server. Pick both if customers should see replies leave from Microsoft.
On setup, Freshdesk fetches only the last day of Inbox email, read and unread. Older conversations stay in Outlook. If a mailbox cannot send, Freshdesk falls back to the next connected mailbox for agent replies, so check which address answered after an outage.
Your Microsoft 365 settings decide whether it connects
Freshdesk needs IMAP and authenticated SMTP on the mailbox. Its troubleshooting page says most Microsoft 365 tenants disable SMTP authentication by default. That setting lives in the Microsoft 365 admin center, so the admin who connects Freshdesk may not be the person who can fix it.
Authentication uses OAuth. Microsoft's default refresh token lifetime is 90 days, so you may have to reauthenticate. The tenant owner can change that policy. Freshdesk shows a reauthorization banner when the link breaks.
Plan access is the other check. The setup page marks Free with a cross but also says Free accounts can add one custom-server email. Confirm with Freshdesk before you rely on it, and see Freshdesk pricing for current plans. The Gmail version of this setup works the same way; see Freshdesk and Gmail.
The Outlook app sends alerts, not data
The Office 365 app forwards tickets to the assigned agent's Outlook inbox as actionable messages. Agents add a private note, change priority or change the assigned agent from the message. You trigger it with a Dispatch'r or Observer rule that uses the Push to Outlook action.
Its help page was last modified on 18 June 2021 and describes the feature as a preview for Outlook on the web. It works for individual Office 365 accounts, not groups. I could not open the app's marketplace listing, so test it in a sandbox before you promise it to agents.
Calendar and contacts need another route
Freshdesk's docs describe no calendar sync. A Freshworks community reply says no native Outlook calendar integration exists. The reply offers the API or a systems integrator as the alternatives.
The Freshworks marketplace lists a Microsoft Outlook Contacts app, published by Freshworks and free. The listing says it synchronizes contacts between Outlook and Freshdesk. It does not say which way or which fields. Zapier lists Outlook triggers for new calendar events and contacts, and a Freshdesk Create Ticket action; see Freshdesk and Zapier for that route.