Hybrid MX: keep Google Workspace, add AzAd mailboxes

Hybrid MX Google AzAd is the pattern for organizations that cannot (or should not) move MX off Google Workspace yet — but still need selected mailboxes on AzAd Mail. The same buying intent applies to Microsoft 365 as primary MX. Canonical product page: hybrid Google / Microsoft mail.

Why hybrid exists

• Some addresses should not consume a Google license
• Gradual migration beats a risky weekend cutover
• Most users must keep Gmail while a few need AzAd webmail/IMAP pricing

AzAd does not use per-mailbox Google Routing APIs (not publicly available). Instead: one Google route for unrecognized/inactive recipients → AzAd host on port 25.

Buying checklist

1. Start AzAd (/start/) and verify the domain.
2. Enable Hybrid mail (external primary MX) in AzAd Admin.
3. In Google Admin, add host server.azademail.com port 25 with TLS — not 587.
4. Configure Routing for unrecognized recipients (avoid Non-Gmail mailbox at domain root).
5. Ask AzAd ops to sync hybrid sender access so Google → AzAd local delivery does not hit 550 Sender address rejected.
6. Optionally connect Google Directory so new AzAd mailboxes do not collide with existing Google users.

DNS: keep Google MX; merge SPF; keep AzAd DKIM/verification. Client IMAP for AzAd users remains server.azademail.com — hybrid does not change that hostname (IMAP setup).

Pricing

Hybrid is a routing mode, not a separate SKU. You still pay AzAd storage for AzAd mailboxes — 15 GB ≈ US$2.86/mo display USD (800 PKR ÷ 280). See pricing.

When not to use hybrid

If everyone is ready to leave Google mail for the domain, a full MX cutover is simpler to operate long term. Hybrid is a bridge (or a permanent split) — choose deliberately.

Failure modes to rehearse

1. Wrong Google port (587): Google gets 554 Access denied because SASL is required. Use port 25 with TLS and hostname validation.
2. Non-Gmail mailbox at domain root: can break Gmail for existing users. Use unrecognized/inactive routing instead.
3. No sender sync: Google users mailing AzAd-only addresses hit 550 Sender address rejected. Ask platform ops to run hybrid sender sync after enablement.
4. Directory collision: creating an AzAd mailbox that already exists in Google. Connect Google Directory when possible so AzAd blocks duplicates.
5. SPF left on Google-only: outbound AzAd mail fails alignment. Merge includes.

Who owns which ticket

• Customer admin: AzAd hybrid toggle, Google Admin host + routing, DNS SPF merge.
• AzAd platform ops: Mailcow hybrid sender access sync.
• End users: IMAP/webmail for AzAd addresses only — Google users keep Gmail.

Exit criteria for hybrid

Hybrid can be permanent or temporary. Exit to full AzAd MX when Google mail seats are gone and every address lives on AzAd. Exit back to Google-only if the pilot fails — disable hybrid, remove routing, keep Google MX authoritative.

Timeline for a typical hybrid pilot

Week 1: AzAd trial, domain verify, enable hybrid flag, create two AzAd-only test addresses.
Week 2: Google Admin host on port 25, unrecognized routing, confirm “Unrecognized route configured” in AzAd.
Week 3: Request hybrid sender sync; test Google user → AzAd-only address; test external → AzAd.
Week 4: Add production mailboxes; document who stays on Gmail vs AzAd webmail/IMAP.

Do not skip week 3 — internal 550 failures show up only after real Google senders mail AzAd addresses.

Microsoft 365 primary MX

The same buying pattern applies when Microsoft keeps MX: configure tenant mail flow so unrecognized or selected recipients reach AzAd on port 25. AzAd Admin hybrid toggle, merged SPF, and IMAP at server.azademail.com for AzAd users still apply. Provider-specific connector steps vary — involve whoever administers Exchange Online transport rules.

Deliverability checklist (hybrid)

• Google/Microsoft MX unchanged unless you plan full cutover later
• Single merged SPF TXT (not duplicate records)
• AzAd DKIM published and verified
• Outbound from AzAd mailboxes passes alignment tests
• Inbound tests: external Gmail, Google workspace user, Microsoft user if applicable

When hybrid becomes technical debt

If AzAd mailbox count approaches Google seat count, hybrid complexity may exceed savings. Re-evaluate full MX cutover quarterly. Permanent hybrid makes sense for steady “unlicensed address” demand — not as an accidental default because migration never finished.

Pricing reminder

Hybrid is not a separate SKU. Each AzAd mailbox still uses a storage tier — 15 GB ≈ US$2.86/mo display USD (800 PKR ÷ 280). Google or Microsoft suite seats continue on their own contracts. Compare total cost, not AzAd line item alone.

Internal FAQ for helpdesk

Prepare answers for: “Why do I still use Gmail?” (active Google user), “Why does my AzAd address use a different webmail?” (AzAd-hosted), and “Why did Google mail to test@ fail?” (routing or sender sync). Hybrid confusion is people confusion — document roles.

Next step

Read the full hybrid guide, compare pricing, then provision during trial at /start/.