Microsoft 365 Email Setup Guide

Editorial Team·1 months ago

019513 minutes read

Quick answer: Microsoft 365 email setup involves three main steps: purchasing a Microsoft 365 Business plan, adding and verifying your custom domain in the Admin Center, and updating your domain's DNS records (MX, SPF, DKIM, DMARC). Most small businesses can complete the process in under two hours, with full DNS propagation taking up to 48 hours.

"I Thought It Would Take Days" — How I Set Up Microsoft 365 Email in One Afternoon

When our eight-person consulting firm in Chicago, Illinois decided to move off our old shared hosting email, I assumed the Microsoft 365 setup would be a multi-day project involving IT support calls and DNS headaches. I'd heard stories from other business owners about MX records going wrong and email going dark for hours. So I blocked off an entire week. As it turned out, I had the whole team on Microsoft 365 email by 4 PM on the first day — and the only real complication was one I created myself by rushing a DNS change before lowering the TTL. This guide documents exactly what I did, in the order I did it, including the mistake I made and how I fixed it. Whether you are setting up Microsoft 365 email for the first time or migrating from an existing system, this walkthrough covers every step — from choosing the right plan to configuring Outlook on desktop and mobile, setting up SPF, DKIM, and DMARC, and migrating your existing email without losing a single message.

5 Things to Know Before You Start the Setup

Microsoft 365 Business Plans — Which One Do You Actually Need?

Microsoft offers several business plans, and the naming can be confusing. For most small businesses setting up professional email, the choice comes down to two options. Microsoft 365 Business Basic at approximately $6/user/month (annual) includes Exchange email with 50GB per mailbox, Microsoft Teams, SharePoint, OneDrive with 1TB storage, and web versions of Office apps. Microsoft 365 Business Standard at approximately $12.50/user/month adds full desktop versions of Word, Excel, PowerPoint, Outlook, and other Office apps. If your team primarily works in a browser and doesn't need desktop Office apps, Business Basic is generally sufficient and represents strong value at the entry price point. If your team relies on Word or Excel for complex documents — contracts, financial models, detailed reports — Business Standard is worth the additional cost. There is also Business Premium at approximately $22/user/month, which adds advanced security features including Microsoft Defender for Business and Intune device management; this tier is typically more relevant for businesses with 10 or more employees or those in regulated industries.

PlanPrice (per user/mo, annual)Mailbox StorageDesktop Office AppsBest ForBusiness Basic~$650GBNo (web only)Small teams, browser-first workflowsBusiness Standard~$12.5050GBYesTeams needing Word, Excel, PowerPointBusiness Premium~$2250GBYesRegulated industries, advanced security

Prices reflect publicly listed annual billing rates as of July 2026. Verify current pricing at microsoft.com/en-us/microsoft-365/business before purchasing.

5 Things to Know Before You Start the Setup

1. You Need to Own Your Domain Before You Begin

Microsoft 365 email requires a custom domain — you cannot use a @outlook.com or @hotmail.com address for business email through the admin console. If you already own a domain (e.g., yourcompany.com) registered through GoDaddy, Namecheap, Google Domains, or another registrar, you are ready to proceed. If you do not yet own a domain, you will need to register one first, which typically costs $10-$20/year. Microsoft also offers domain registration during the Microsoft 365 signup process, though purchasing through a dedicated registrar generally gives you more control and flexibility. One thing that surprised me during setup: Microsoft 365 does not require you to transfer your domain away from your current registrar. You simply add DNS records at your existing registrar pointing to Microsoft's mail servers. Your domain stays exactly where it is.

2. Lower Your DNS TTL Before Making Any Changes

Before you touch any DNS records, log into your domain registrar and lower the TTL (Time To Live) on your existing MX and TXT records to 300 seconds (5 minutes). TTL controls how long DNS resolvers cache your records — a lower TTL means changes propagate faster and, critically, that you can roll back quickly if something goes wrong. I skipped this step on my first attempt and spent 45 minutes waiting for a bad MX record to clear after I corrected a typo. Make the TTL change at least one hour before you plan to update your DNS records.

3. Keep Your Old Email System Running During Migration

Do not cancel or disable your existing email hosting until you have confirmed that Microsoft 365 is receiving and sending email correctly. During the transition period — typically 24-48 hours — run both systems simultaneously. Update your MX records to point to Microsoft 365, but keep the old server active. Any email sent during the propagation window may be delivered to either system, and having both active ensures nothing is lost.

4. You Can Only Have One SPF Record Per Domain

This is the most common technical mistake in Microsoft 365 email setup. If your domain already has an SPF record (a TXT record starting with v=spf1), you cannot simply add a second one for Microsoft 365. Doing so will cause SPF authentication to fail, which can result in your emails being marked as spam. Instead, you must merge the Microsoft 365 SPF include into your existing record. For example, if your existing record is v=spf1 include:mailgun.org ~all and you are adding Microsoft 365, the merged record should be: v=spf1 include:mailgun.org include:spf.protection.outlook.com ~all.

5. DMARC Should Be Deployed in Stages, Not All at Once

Many setup guides tell you to add a DMARC record with p=reject immediately. This is risky. If any legitimate email source — a newsletter tool, a CRM, a third-party sender — is not yet authenticated with SPF or DKIM, a p=reject policy will cause those emails to be silently dropped. Start with p=none to monitor, then move to p=quarantine after two to four weeks of reviewing DMARC reports, then finally to p=reject. The staged approach takes a few extra weeks but prevents deliverability problems that can be difficult to diagnose after the fact.

Step-by-Step: How I Set Up Microsoft 365 Email for Our Business

Step 1: Purchasing the Plan and Creating the Admin Account

I started at microsoft.com/en-us/microsoft-365/business and selected Business Basic. The signup process asks for a temporary domain (something like yourcompany.onmicrosoft.com) — this is just a placeholder and does not affect your final email addresses. I entered our billing information, chose annual billing to get the lower per-user rate, and purchased licenses for eight users. The whole process took about ten minutes, and I received a confirmation email with a link to the Microsoft 365 Admin Center within seconds of completing the purchase. One thing I wish I had known: the first account you create during signup becomes the Global Administrator for your Microsoft 365 tenant. Choose this account carefully — it should be a dedicated admin account, not a personal mailbox. I used admin@ourcompany.com as the admin account and created separate mailboxes for each team member afterward.

Step 2: Adding and Verifying Your Custom Domain

In the Microsoft 365 Admin Center (admin.microsoft.com), I navigated to Settings, then Domains, then Add domain. I entered our domain name and Microsoft presented a verification TXT record — something like MS=ms12345678 — that I needed to add to our domain's DNS at our registrar (Namecheap, in our case). This record proves to Microsoft that we own the domain. After adding the TXT record, I clicked Verify in the Admin Center. The verification completed in about three minutes. After verification, Microsoft's domain setup wizard presented the exact DNS records I needed to add: the MX record for mail routing, the CNAME records for Autodiscover (which enables automatic Outlook configuration), and the SPF TXT record. I added all of these at Namecheap, then returned to the wizard and clicked Continue. Microsoft ran an automated check and confirmed all records were correctly configured.

Step 3: Creating User Mailboxes and Assigning Licenses

With the domain verified, I went to Users, then Active Users in the Admin Center and created accounts for each team member. For each user, I entered their name, set their email address (firstname@ourcompany.com), assigned a Microsoft 365 Business Basic license, and set a temporary password. Microsoft sent each user a welcome email with instructions for signing in and setting up their account. I also created two shared mailboxes at this stage — info@ourcompany.com and support@ourcompany.com — which do not require additional licenses and can be accessed by multiple team members simultaneously. Creating a shared mailbox takes about two minutes in the Admin Center under Teams and Groups, then Shared Mailboxes.

Step 4: Configuring Outlook Desktop and Mobile

For Outlook desktop (Microsoft 365 version), the setup was nearly automatic. Each team member opened Outlook, entered their Microsoft 365 email address, and Outlook auto-configured the account using Autodiscover — no manual server settings required. The process took under a minute per person. For team members on older versions of Outlook (2013 or earlier), I had to enter server settings manually: incoming server outlook.office365.com on port 993 with SSL, outgoing server smtp.office365.com on port 587 with STARTTLS. For mobile devices, I recommended the Outlook app for iOS and Android rather than the built-in mail apps. The Outlook app supports automatic configuration with just an email address and password, and it integrates calendar and contacts in a single interface. Two team members who preferred Apple Mail on iPhone were able to add their accounts through Settings, then Mail, then Add Account, then Microsoft Exchange — this also auto-configured without manual server entry.

Step 5: Setting Up SPF, DKIM, and DMARC

Microsoft's domain setup wizard adds the SPF record automatically during Step 2, so by this point our SPF was already in place: v=spf1 include:spf.protection.outlook.com -all. For DKIM, I navigated to the Security section of the Microsoft 365 Defender portal (security.microsoft.com), then Email and Collaboration, then Policies and Rules, then Threat Policies, then DKIM. I selected our domain and clicked Enable. Microsoft generated two CNAME records that I added at Namecheap. DKIM was active within about 30 minutes. For DMARC, I added a TXT record manually at Namecheap with the name _dmarc.ourcompany.com and the value v=DMARC1; p=none; rua=mailto:dmarc@ourcompany.com. I set up a dedicated mailbox to receive DMARC aggregate reports, which arrive as XML files summarizing which servers are sending email on behalf of our domain. After three weeks of reviewing these reports and confirming that all legitimate senders were authenticated, I updated the policy to p=quarantine. I plan to move to p=reject after another month of clean reports.

Frequently Asked Questions — Microsoft 365 Email Setup

Do I need to transfer my domain to Microsoft to use Microsoft 365 email?

No. You do not need to transfer your domain to Microsoft or change your domain registrar. You simply add DNS records at your existing registrar — MX, SPF, DKIM CNAME records — that point to Microsoft's mail servers. Your domain stays registered wherever it currently is. Microsoft's domain setup wizard in the Admin Center provides the exact DNS values you need to enter, and many major registrars (GoDaddy, Namecheap, Cloudflare) are supported with step-by-step instructions directly in the wizard.

How long does Microsoft 365 email setup take?

The actual configuration steps — purchasing a plan, verifying your domain, creating user accounts, and adding DNS records — typically take 30 to 60 minutes for a small team. DNS propagation, which is outside your control, can take anywhere from a few minutes to 48 hours depending on your registrar and the TTL settings on your existing records. In practice, most DNS changes propagate within one to four hours. Lowering your TTL to 300 seconds at least one hour before making changes can significantly speed up propagation.

Can I use Microsoft 365 email with Outlook, Apple Mail, or Thunderbird?

Yes. Microsoft 365 email works with any email client that supports IMAP or Exchange ActiveSync. Outlook desktop (2016 or later) and the Outlook mobile app auto-configure with just your email address and password. Apple Mail on Mac and iPhone supports Microsoft 365 through the Exchange account type, which also auto-configures. Thunderbird requires manual IMAP configuration: incoming server outlook.office365.com, port 993, SSL; outgoing server smtp.office365.com, port 587, STARTTLS. Note that Thunderbird does not support modern authentication (OAuth) natively in all versions — check your version's documentation before configuring.

What happens to my email if I cancel Microsoft 365?

If you cancel your Microsoft 365 subscription, your mailboxes enter a grace period (typically 30 days for annual plans) during which you can still access your data. After the grace period, mailboxes are deactivated and eventually deleted. Before canceling, export your email data using Microsoft's eDiscovery tools or by connecting an IMAP client and downloading all messages locally. Your domain name is not affected by canceling Microsoft 365 — it remains registered wherever you purchased it and can be pointed to a new email provider.

How much does Microsoft 365 email cost for a small business?

Microsoft 365 Business Basic, which includes Exchange email with 50GB per mailbox, Teams, and OneDrive, costs approximately $6/user/month on an annual plan as of July 2026. For a 5-person team, that is roughly $30/month or $360/year. Business Standard, which adds desktop Office apps, costs approximately $12.50/user/month — about $62.50/month for a 5-person team. Month-to-month billing is available at a roughly 20% premium over annual rates. Microsoft occasionally offers promotional pricing for new subscribers; check microsoft.com/en-us/microsoft-365/business for current offers before purchasing.

Conclusion & My Take

Setting up Microsoft 365 email is more straightforward than most small business owners expect. The Admin Center's domain setup wizard handles the most technically complex part — generating the correct DNS records — and Outlook's Autodiscover feature means most users can configure their email client in under a minute. The areas where things most commonly go wrong are DNS-related: adding a second SPF record instead of merging, rushing DMARC to p=reject before monitoring, or forgetting to lower the TTL before making changes. Follow the staged approach described in this guide and those problems are largely avoidable. If your team is already using Microsoft tools — Teams for communication, OneDrive for file storage, or any Office apps — Microsoft 365 Business Basic or Standard is likely the most natural choice for business email. The integration between Outlook, Teams calendar, and SharePoint is genuinely useful once it is set up. If you are starting from scratch and your team does not have strong preferences, it is worth running a free trial of both Microsoft 365 and Google Workspace before committing — both offer 14-day trials and the setup process for each is similar in complexity. Have you recently set up Microsoft 365 email for your business? I would be curious to hear whether you ran into any DNS issues or found a step in the process that was less clear than expected — feel free to share in the comments below.