You can leave Microsoft 365 email without throwing away Office. Many organizations need Word, Excel, and PowerPoint — but do not need Exchange Online, Teams, and SharePoint for every seat. AzAd Mail is positioned as a Microsoft 365 email alternative, not as a Teams replacement.
Split the purchase
| Keep on Microsoft (if needed) | Move to AzAd Mail |
|---|---|
| Desktop Office apps | Custom-domain mailboxes |
| (Optional) Teams/SharePoint only for groups that use them | Webmail + admin |
| IMAP Outlook profiles | |
| Optional AzAd CRM |
Microsoft licensing varies by region and SKU — confirm with your reseller which licenses still make sense after mail leaves Exchange. The marketing point is simple: do not pay suite seats solely for email if AzAd covers the mailbox job.
How Outlook still works
Point Outlook at AzAd with IMAP/SMTP (server.azademail.com). You lose some Exchange-only features. Day-to-day send/receive and folders work. Setup guide: IMAP & SMTP. Longer walkthrough: Outlook IMAP AzAd Mail.
Migration outline
- Trial AzAd at /start/; provision matching addresses.
- Migrate mailbox history over IMAP while Microsoft still receives MX.
- Either cut MX to AzAd, or use hybrid mail if Microsoft must remain primary MX for some users.
- Rebuild Outlook profiles for AzAd IMAP.
- Reduce or cancel Exchange-oriented licenses only after a stable week.
Approximate AzAd display price: 15 GB ≈ US$2.86/mo per mailbox (800 PKR ÷ 280). CRM remains optional at US$10/mo per org.
Objections
“Shared calendars will break.” True for Exchange-grade calendaring. Use another calendar stack if that is critical — do not expect AzAd to claim Exchange parity.
“Finance wants one vendor.” One vendor is convenient; it is not always cheaper. Split stacks are normal for SMBs.
Calendar and contacts reality check
Contacts migrate reasonably via CSV into AzAd Contacts. Calendars are the sticky point: Exchange shared calendars and room lists will not appear magically on AzAd IMAP. Plan an alternate calendar (Microsoft for some groups, Google free, or another tool) before you cut Exchange if meetings are mission-critical.
License conversation with finance
Bring three numbers:
- Current Microsoft seats × price (mail-capable SKUs).
- Planned AzAd mailboxes × storage tier (pricing — 15 GB ≈ US$2.86/mo display USD).
- Residual Microsoft spend for Office apps you still need.
If (2)+(3) is lower than (1) with acceptable feature loss, the split stack wins. If not, stay on Microsoft for mail too — AzAd should not win on ideology.
Pilot design
Move a non-executive team first. Keep Microsoft MX or use hybrid until the pilot’s Outlook profiles and deliverability look boring. Boring is the goal.
Teams and SharePoint stay separate
AzAd does not replace Teams chat, SharePoint sites, or OneDrive. If those tools are daily drivers for most staff, keep the Microsoft licenses that cover them — just stop paying Exchange-oriented SKUs solely for mailboxes AzAd can host. Procurement may prefer one vendor; finance should still compare total seat tax vs split stack cost.
Timeline suggestion
Week 1–2: AzAd trial, mirror addresses, SPF/DKIM, one Outlook IMAP pilot.
Week 3: IMAP history migration while Exchange still receives MX (or hybrid for subset).
Week 4: cutover or hybrid routing; verify external send/receive.
Week 5+: reduce Exchange licenses only after calendar/contacts expectations are documented.
Deliverability after Exchange
Correct MX, SPF, and DKIM are necessary; sending reputation still depends on list quality and volume. Test to Gmail, Outlook.com, and a corporate inbox before company-wide announcement. Hybrid setups merge Microsoft and AzAd SPF until one side stops sending.
Reducing Microsoft licenses safely
Cancel Exchange-oriented SKUs only after: inbound MX or hybrid routing is stable, Outlook IMAP profiles work, calendar expectations are documented, and finance signed off on residual Office app licenses. Keeping one Exchange seat “just in case” for a month is cheaper than emergency rollback.
Word/Excel licensing note
This article assumes you may keep Microsoft desktop apps via non-Exchange SKUs or existing agreements. Confirm with your reseller — regions and bundles differ. AzAd does not sell Office licenses.
Hybrid alternative
If executives must stay on Exchange MX temporarily, host selected mailboxes on AzAd via hybrid mail instead of delaying the whole project.
Contacts vs calendars (again)
CSV import into AzAd Contacts works for address books. Shared Exchange calendars do not. Document the calendar plan in writing before mail cutover so sales does not assume room booking still works.
Outlook profile naming
Label AzAd IMAP accounts clearly in Outlook so users do not reply from the wrong From address during the overlap week.
Teams chat is unchanged
Leaving Exchange mail does not remove Teams for groups that still license it. Mail threads move to AzAd; Teams channels stay on Microsoft if you keep those SKUs — do not expect Teams to read AzAd inbox.
Next step
Compare tiers on pricing and start the mail trial at /start/ before you cancel Microsoft seats.