Many teams lose inbound support mail after moving mail hosting from Gmail to Outlook/Microsoft 365. This guide describes the common causes and the Zoho Desk settings to check so forwarded messages reach your Desk account again.
What is it
This feature overview covers how Zoho Desk receives forwarded email after you migrate mail from Gmail to Outlook (Microsoft 365). It explains the forwarding targets Zoho Desk expects, the DNS and authentication checks that can block forwarded mail (SPF, DKIM, DMARC), and the Zoho Desk settings you should verify so customer emails create tickets as before. It also lists the Microsoft-side changes that commonly break forwarding rules after a migration. The steps below assume you already have a support address (for example support@yourdomain or an organization-specific Zoho Desk inbound address).
When to use it
- After migrating your organization email from Gmail to Microsoft 365 and inbound messages stopped appearing in Zoho Desk[1].
- When Outlook/Exchange forwarding rules send errors like "554 5.1.8 Email Outgoing Blocked" or mails bounce before reaching Zoho Desk[1].
- When you forward a catchall or noreply@ address and only some messages appear in Desk, or sender domains fail SPF/DKIM checks[1].
- When you previously used Gmail automatic forwarding and now need an Exchange transport rule or connector to replicate that behavior[1].
- When you want to confirm that Zoho Desk receives mail from a new Microsoft-hosted address without losing ticket history[1].
How to access it
Open Zoho Desk and go to Setup > Channels > Email. Verify the support email addresses listed under "Mail Accounts" and check the inbound forwarding target shown for each account—Zoho Desk provides an organization-specific forwarding address (example: yourorg@inbound.zoho.com) that Outlook must forward to [1]. On the Microsoft side, use the Exchange admin center (Exchange Online) to create a mail flow (transport) rule or a connector that forwards mail to the Zoho inbound address and preserves original sender headers; test by sending a message to the external support address and confirming it appears in Desk [1].
Related features
- SMTP & Outbound settings — configure sending from Zoho Desk and check bounce/reply behavior.
- Mail Filters and Rules — refine which forwarded messages create tickets and which are ignored.
- Domain Authentication (SPF/DKIM/DMARC) — verify DNS records that affect forwarding and sender validation.
- Logs & Audit Trail — review inbound logs and Exchange message trace when diagnosing delivery failures.
Notes and quick troubleshooting checklist
- Confirm the forwarding target: forward to the exact Zoho inbound address shown in Setup > Channels > Email rather than a generic support@ alias; wrong targets cause silent drops[1].
- Check SPF and forwarding: Microsoft forwarding may break SPF because the message appears to originate from Microsoft servers; enable Sender Rewriting Scheme (SRS) or use an Exchange connector that preserves sender information to avoid SPF failures[1].
- DKIM/DMARC: if your domain enforces DMARC reject/quarantine, forwarded messages may get blocked. Either adjust DMARC policy during migration or ensure SRS/remapping is in place so DMARC passes[1].
- Exchange transport rules vs. mailbox forwarding: prefer organization-level mail flow rules or connectors for high-volume forwarding; mailbox-level forwarding can strip headers and trigger spam checks[1].
- Test with raw headers: when a message fails, pull the message trace from Exchange and check Zoho Desk inbound logs to see where the message was dropped or rejected[1].
- Allowlist Zoho IPs if your tenant restricts outbound connections; conversely, check if Microsoft flagged outbound forwarding as blocked (554 style errors) and ask your M365 admin to review mail flow policies[1].
If forwarding still fails after these checks, capture an Exchange message trace and a sample bounce/SMTP rejection and open a support ticket with Zoho Desk including those traces so support can pinpoint where the handoff fails[1].