Skip to main content

Connecting a Microsoft Email

Jaclyn Curtis avatar
Written by Jaclyn Curtis
Updated over a week ago

Important Note About Microsoft Email Support in Alsona

At this time, Alsona only supports personal Microsoft email accounts.

We do not currently support Microsoft Enterprise or Business email accounts, as these require Microsoft application verification, which is still in progress. We are actively working toward this verification and will update our documentation once Enterprise Microsoft accounts are supported.

If you are using a Microsoft Business or Enterprise account, the recommended workaround is to use a subdomain connected to Gmail, which is also considered best practice for outbound and automated email.


Why Using a Subdomain Is Best Practice (Even If Microsoft Were Supported)

Regardless of email provider, experienced outbound teams almost always use a subdomain instead of their main domain.

Using a subdomain allows you to:

  • Protect the reputation of your primary domain

  • Isolate outbound activity from internal and customer communication

  • Control deliverability, warm-up, and sending limits independently

  • Reduce risk if an inbox or domain encounters issues

For these reasons, setting up a subdomain is recommended even outside of Microsoft limitations.


Recommended Setup for Microsoft Users

If your primary email is on Microsoft 365 (Outlook), the recommended configuration is:

  • Main domain (example: alsona.com)

    • Remains on Microsoft 365

    • Used for internal and customer communication

  • Subdomain (example: mail.alsona.com)

    • Connected to Google Workspace (Gmail)

    • Used for outbound email and automation

    • Connected directly to Alsona

This setup keeps systems fully separate and avoids any Microsoft Enterprise restrictions.


How This Works

Email routing is controlled at the DNS level.


You can route your main domain to Microsoft and your subdomain to Google at the same time without conflict.

Alsona then connects to the Gmail inbox on the subdomain.


Step-by-Step: Setting Up a Microsoft Subdomain on Gmail

1. Choose a Subdomain

Common options include:

  • mail.yourdomain.com

  • m.yourdomain.com

  • e.yourdomain.com

  • email.yourdomain.com

The subdomain is created in DNS, not inside Microsoft 365.


2. Add the Subdomain to Google Workspace

In Google Admin:

  1. Go to Domains

  2. Add a Secondary domain

  3. Enter your subdomain (for example, mail.alsona.com)

Google will provide a TXT record to verify ownership.


3. Point Subdomain MX Records to Google

In your DNS provider, add Google’s MX records only for the subdomain.

Do not modify the MX records for your main domain.

This ensures:

  • @alsona.com stays on Microsoft

  • @mail.alsona.com routes through Gmail


4. Configure SPF for the Subdomain

Add an SPF record that authorizes Google to send email:

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

This record should apply only to the subdomain.


5. Enable DKIM (Required)

In Google Admin:

  1. Generate a DKIM key for the subdomain

  2. Add the provided TXT record to DNS

  3. Enable DKIM signing

DKIM is required for proper email authentication and deliverability.


6. Add a DMARC Record (Recommended)

Start with a monitoring policy:

v=DMARC1; p=none; rua=mailto:dmarc@your-subdomain.yourdomain.com

This can be tightened later once sending is established.


Connecting the Gmail Inbox to Alsona

Once your Gmail inbox is live on the subdomain:

  1. Log in to Alsona

  2. Go to Email Accounts / Inbox Settings

  3. Select Gmail

  4. Authenticate the inbox

  5. Assign it to your campaign or sender seat

Your Microsoft email remains unchanged and does not need to be connected.


Important Things to Avoid

  • Do not change the MX records for your main domain

  • Do not mix Microsoft and Google email services on the same subdomain

  • Do not skip inbox warm-up (we suggest Instantly for 3-6 weeks)

  • Do not send outbound email from your root domain


If you need help with DNS records, warm-up, or inbox setup, contact Alsona support.

Did this answer your question?