How to Set Up Email for a New Business: First Steps and Best Practices

On January 27, 2026, Microsoft updated its Exchange Online plan for SMTP AUTH: basic (password) authentication will be disabled by default for existing tenants at the end of December 2026, and new tenants created after December 2026 won’t have it available by default. What it means for you: set up your business email and any “send mail” tools (apps, scanners, forms) using modern sign-in methods now, so you don’t get stuck replacing a working setup later. ¹

Quick map (so you don’t get lost):

• Your domain = the name after @ (example: yourcompany.com ).
• Your email host = the service that stores mailboxes and sends/receives mail for that domain (example: Google Workspace, Microsoft 365, Zoho, Fastmail, etc.).
• Your DNS records = the settings that connect your domain to your email host (MX/SPF/DKIM/DMARC).
• Your email app (like Mailbird) = the desktop client you use to read and send mail from one or many mailboxes.

• Prerequisites: You own a domain (or you’re ready to buy one) and you can log in where that domain’s DNS is managed. You also need admin access to your chosen email host.
• Tools/ingredients: A laptop/desktop, a place to store passwords (a password manager is easiest), and a phone for multi-factor authentication (MFA).
• Time: A focused setup session, plus DNS waiting time. It can take up to 48 hours for SPF authentication to start working after changes. ³
• Cost range (USD): Domain registration is commonly about $9.70–$35/year for a standard .com , depending on registrar and promos. Business email hosting ranges widely, but mainstream suites often start around $6/user/month (Microsoft 365 Business Basic) or $8.40/user/month on Google’s Flexible Business Starter plan (with lower pricing on annual commitments). ^{6 4 5}
• Safety notes: DNS changes affect your whole domain. Before you edit anything, export/screenshot your current DNS page. Don’t paste passwords into email or chat. Turn on MFA for admin accounts before you invite the rest of the team.

New business email setup guide: step-by-step

1. Choose your domain and decide what addresses you need

   • Pick the domain you’ll use long-term (for example, yourcompany.com ). If you’re still naming your business, decide the domain first—your email addresses will be everywhere (invoices, logins, signatures).
   • Write down your “must-have” addresses now (examples: yourname@ , support@ , billing@ , sales@ ).
   • Choose a consistent “From name” format (example: “Avery Patel, YourCompany”).

   Check: You can log in to your domain registrar/DNS host and find the page where you add or edit DNS records.

2. Pick an email host (this is separate from your domain)

   • Decide whether you want email only or a full work suite (email + calendar + file storage + admin controls).
   • Confirm the host supports custom domains and modern sign-in (OAuth/SSO), especially if you’ll connect desktop apps and devices.
   • Create your admin account and keep its login info somewhere safe.

   Check: You can sign in to the email host’s admin console.

3. Add your domain inside the email host’s admin console

   • In your email host’s setup wizard, choose Add domain .
   • When asked who manages DNS, select your current DNS provider (or choose “manual” if it’s not listed).
   • Keep the setup screen open—you’ll copy records from it in the next steps.

   Check: You see your domain listed in the admin console with a “Verify” or “Pending” status.

4. Verify domain ownership (usually a TXT record)

   • Copy the verification TXT record Name/Host and Value from your email host.
   • In your DNS settings, add a new TXT record and paste the value exactly.
   • Go back to the email host and click Verify . If it fails, wait and try again.

   Check: The domain shows as verified/active in your email host.

5. Create your mailboxes and role addresses

   • Create a dedicated admin mailbox (example: admin@yourcompany.com ) and your day-to-day mailbox ( yourname@ ).
   • Create role addresses based on how you work:
     • If one person handles it: create an alias (support@ → yourname@).
     • If multiple people handle it: create a shared mailbox or group (support@ goes to everyone who needs it).
   • Set strong passwords and require MFA (you’ll lock this down more in Step 10).

   Check: You can sign in to webmail for your main mailbox and send a message to yourself internally (if the host allows internal mail before MX changes).

6. Route incoming mail to your new host (MX records)

   • In your email host’s setup wizard, find the MX records it wants you to add.
   • In DNS, remove old MX records that point to a previous email service (or follow your provider’s instructions to lower their priority).
   • Add the new MX records exactly as shown (same host/name, priority, and destination).
   • Tip: Create users/mailboxes before switching MX so mail doesn’t land in a “no mailbox exists” state during the changeover. ⁷

   Check: A test email sent to you@yourcompany.com arrives in the new inbox (if it doesn’t, see Troubleshooting).

7. Authorize outgoing mail with SPF (one TXT record)

   • In DNS, look for an existing SPF record: a TXT record whose value starts with v=spf1 .
   • If one exists, edit it (don’t create a second SPF record). Microsoft’s DNS guidance also warns against creating a new SPF record when one already exists—keep a single SPF TXT record and add what you need to it. ⁷
   • If you use only Google Workspace to send mail, Google’s example SPF record is: ³

   v=spf1 include:_spf.google.com ~all

   • If you also send mail from other services (website forms, CRM, invoicing), add their SPF includes too—otherwise their messages can fail SPF and land in spam. ³
   • Expect a delay: SPF authentication can take up to 48 hours to start working after DNS changes. ³

   Check: Send an email to a personal mailbox and confirm the message headers show spf=pass .

8. Turn on DKIM signing (so your mail is harder to spoof)

   • In your email host’s admin console, generate DKIM keys for your domain.
   • Add the DKIM DNS record(s) your provider gives you (often CNAME records, sometimes TXT ).
   • Back in the admin console, click Enable (or similar) to start DKIM signing.
   • If you ever send high-volume email to Outlook.com consumer addresses, Microsoft’s requirements include DKIM passing for those domains. ²

   Check: Send a test message and confirm headers show dkim=pass .

9. Publish a DMARC policy (start simple)

   • Add a TXT record at _dmarc.yourcompany.com .
   • Start with a monitoring policy while you confirm everything is aligned:

   v=DMARC1; p=none

   • If you send bulk email, both Gmail and Outlook.com have stricter expectations around SPF/DKIM/DMARC. Google notes bulk senders (more than 5,000 messages daily) must have SPF, DKIM, and DMARC. Microsoft’s Outlook.com requirements for high-volume senders also include DMARC with at least p=none and alignment with SPF or DKIM. ^{3 2}

   Check: Your email host’s admin panel shows DMARC detected (or your test headers show dmarc=pass after everything is aligned).

10. Lock down security (admin first, then everyone)

    • Enable MFA for admin accounts, then for all users.
    • Store backup codes/recovery methods somewhere safe (not inside your email inbox).
    • Limit who has admin roles. Use your admin mailbox for admin tasks—not day-to-day emailing.
    • Decide what happens when someone leaves (disable account, transfer access to a manager, set up forwarding if needed).

    Check: Admin login prompts for a second factor and recovery methods are set.

11. Connect your new business email to Mailbird (and add multiple inboxes)

    • Install Mailbird, then open Menu → Settings → Accounts → Add . ⁸
    • Add your first mailbox. Mailbird will try to auto-detect IMAP/SMTP settings; if detection fails, switch to manual and enter the settings from your email host. ¹⁰
    • If you run into IMAP-related errors, confirm IMAP is enabled for your email account before trying again. ¹¹
    • Add your other business addresses (for example, support@ and billing@ ) one at a time.
    • Enable a Unified Inbox so you can read and reply without constant account switching. In Mailbird, the Unified Inbox only appears once you’ve added more than one email account. ⁹
    • If you plan to connect more than one account, confirm your Mailbird plan supports multiple connected accounts (Mailbird Free supports one connected account). ¹²

    Check: You can see new mail in each inbox, the Unified Inbox is visible, and your replies send from the correct “From” address.

12. Do a final end-to-end test and document your setup

    • Send a message from each address (yourname@, support@, billing@) to an outside mailbox you can access, then reply back.
    • Confirm: inbound works, outbound works, replies go out from the correct address, and attachments deliver.
    • Create a short “Business email setup” note with:
      • Who owns the domain registrar login
      • Where the email host admin console is
      • Which DNS records you changed (MX, SPF, DKIM, DMARC)
      • Which addresses are aliases vs shared mailboxes

    Check: Two-way email works from your desktop (Mailbird) and from webmail, and you have your setup notes saved.