Microsoft 365 + Bluehost

Set up Microsoft 365 email on Bluehost

The records Microsoft 365 needs, written with the field names Bluehost uses (Host Record, Points to, TXT Value), in the order to add them.

  • 6 steps
  • 7 DNS records

Before you start

  1. Have your Microsoft 365 account ready. Some values are unique to your account and come from the Microsoft 365 admin center .
  2. Open DNS at Bluehost: Log in to the Bluehost Portal and click Domains in the left-hand menu. Select your domain, then open the DNS tab.
  3. Keep both tabs open and add the records below one at a time.

Microsoft 365 on Bluehost: what to know

How long changes take

Bluehost says saved changes are processed in a few minutes but can take up to 8 hours to fully propagate, depending on caching and TTL.

Source: How to Edit MX Records (Bluehost Help)

Records to add

Copy each value with the button next to it. Rows marked “Copy from Microsoft 365 admin center” are unique to your account.

Domain verification Proves you own the domain Type TXT Host Record @ Value Copy from Microsoft 365 admin center Looks like: MS=ms followed by digits Priority n/a TTL 3600 (1 h)
MX records Where incoming email goes Type MX Host Record @ Value Copy from Microsoft 365 admin center Looks like: <your MX token>.mail.protection.outlook.com, or for domains set up on Microsoft's newer DNSSEC infrastructure <your MX token>.<subdomain>.mx.microsoft Priority 0 TTL 3600 (1 h)
SPF record Which servers may send as you Type TXT Host Record @ Value v=spf1 include:spf.protection.outlook.com -all Priority n/a TTL 3600 (1 h)
DKIM A signature on every message · recommended Type CNAME Host Record selector1._domainkey Value Copy from Microsoft 365 admin center Looks like: selector1-yourdomain-com._domainkey.<your onmicrosoft prefix>.<letter>-v1.dkim.mail.microsoft (older domains: selector1-yourdomain-com._domainkey.<prefix>.onmicrosoft.com) Priority n/a TTL 3600 (1 h)
DKIM A signature on every message · recommended Type CNAME Host Record selector2._domainkey Value Copy from Microsoft 365 admin center Looks like: selector2-yourdomain-com._domainkey.<your onmicrosoft prefix>.<letter>-v1.dkim.mail.microsoft (older domains: selector2-yourdomain-com._domainkey.<prefix>.onmicrosoft.com) Priority n/a TTL 3600 (1 h)
DMARC record What to do with fakes · recommended Type TXT Host Record _dmarc Value v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com Priority n/a TTL Default
Autodiscover Automatic app setup · recommended Type CNAME Host Record autodiscover Value autodiscover.outlook.com Priority n/a TTL 3600 (1 h)

Step by step in Bluehost

Verify your domain

Your email provider needs proof that you control this domain before it accepts email for it.

Type
TXT
Host Name
@
TXT Value
Copy it from Microsoft 365 admin center (see below)

Where to find your value

In the Microsoft 365 admin center go to Settings > Domains and add your domain (or select it and choose Start setup). On Verify you own your domain, choose Add a TXT record to the domain's DNS records and copy the TXT value.

It looks like: MS=ms followed by digits

  • Verification usually takes up to 10 minutes after adding the record, sometimes up to 48 hours.

1 more note from Microsoft 365 on this record

In Bluehost

  1. On the DNS tab, click + Add Record and select Single Record.
  2. Set Record Type to TXT and Refers to to Other Host.
  3. Enter the Host Name and paste the TXT Value.
  4. Click Add.

Point your MX records

MX records tell other mail servers where to deliver your email. How MX works

Type
MX
Host Record
@
Priority
0
Points to
Copy it from Microsoft 365 admin center (see below)

Where to find your value

In the Microsoft 365 admin center go to Settings > Domains, select your domain, then DNS records > Manage DNS. On the Add DNS records page, expand MX Records and copy the value.

It looks like: <your MX token>.mail.protection.outlook.com, or for domains set up on Microsoft's newer DNSSEC infrastructure <your MX token>.<subdomain>.mx.microsoft

  • Remove MX records that point to your previous email provider, or give them a lower priority (a higher number) than the Microsoft 365 record.
  • Add users and mailboxes in Microsoft 365 before switching the MX record so incoming mail keeps flowing.

2 more notes from Microsoft 365 on this record

In Bluehost

  1. Under the DNS tab, go to Manage Advanced DNS Records and click Add Record.
  2. Set Type to MX. Type @ in Host Record, enter the mail server in Points to, and set the Priority. Leave TTL at its default.
  3. Save the record.

Add the SPF record

SPF lists the services allowed to send email as you. How SPF works

Type
TXT
Host Name
@
TXT Value
v=spf1 include:spf.protection.outlook.com -all
  • If an SPF record already exists, don't create a second one. Add include:spf.protection.outlook.com to the existing record so there is a single SPF record.

2 more notes from Microsoft 365 on this record

In Bluehost

  1. On the DNS tab, click + Add Record and select Single Record.
  2. Set Record Type to TXT and Refers to to Other Host.
  3. Enter the Host Name and paste the TXT Value.
  4. Click Add.

Set up DKIM (recommended)

DKIM signs your mail so receivers can trust it. How DKIM works

Type
CNAME
Host Record
selector1._domainkey
Points to
Copy it from Microsoft 365 admin center (see below)

Where to find your value

In the Microsoft Defender portal open Email authentication settings (security.microsoft.com/authentication), select the DKIM tab and your domain, then copy the two CNAME values. They are also shown in the admin center under Add DNS records > Advanced options > DomainKeys Identified Mail (DKIM).

It looks like: selector1-yourdomain-com._domainkey.<your onmicrosoft prefix>.<letter>-v1.dkim.mail.microsoft (older domains: selector1-yourdomain-com._domainkey.<prefix>.onmicrosoft.com)

  • After both CNAME records resolve, turn on Sign messages for this domain with DKIM signatures in the Defender portal.
Type
CNAME
Host Record
selector2._domainkey
Points to
Copy it from Microsoft 365 admin center (see below)

Where to find your value

Same place as selector1: Defender portal > Email authentication settings > DKIM tab > your domain.

It looks like: selector2-yourdomain-com._domainkey.<your onmicrosoft prefix>.<letter>-v1.dkim.mail.microsoft (older domains: selector2-yourdomain-com._domainkey.<prefix>.onmicrosoft.com)

  • Add both selector records. Microsoft rotates between them.

1 more note from Microsoft 365 on this record

In Bluehost

  1. Under the DNS tab, click Add Record.
  2. Set Type to CNAME, enter the name, and put the target hostname in Points to.
  3. Save the record.
  4. Repeat for each CNAME record above.

Add the DMARC record (recommended)

DMARC tells receivers what to do with mail that fakes your domain. How DMARC works

Type
TXT
Host Name
_dmarc
TXT Value
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com
  • Replace the report address with a shared mailbox or group, not a personal inbox.

3 more notes from Microsoft 365 on this record

In Bluehost

  1. On the DNS tab, click + Add Record and select Single Record.
  2. Set Record Type to TXT and Refers to to Other Host.
  3. Enter the Host Name and paste the TXT Value.
  4. Click Add.

Add the Autodiscover record (recommended)

Autodiscover lets Outlook and other mail apps find your account settings without manual setup.

Type
CNAME
Host Record
autodiscover
Points to
autodiscover.outlook.com
  • Optional but highly recommended: lets Outlook and other apps set up mailboxes automatically.

In Bluehost

  1. Under the DNS tab, click Add Record.
  2. Set Type to CNAME, enter the name, and put the target hostname in Points to.
  3. Save the record.

Check your setup

Once the records are saved, run a live check. We look up your domain in public DNS and tell you what is right, missing or wrong, with the fix in Bluehost’s words.

We only read public DNS records. Nothing is stored.

Common mistakes with Microsoft 365 on Bluehost

Switching MX before adding mailboxes

Add users and mailboxes in Microsoft 365 before changing the MX record, or incoming mail has nowhere to go.

Adding a second SPF record

Microsoft says not to create a new SPF record if one exists. Add include:spf.protection.outlook.com to the existing record so there is a single SPF record.

Bluehost: Replace Bluehost's default MX record

By default Bluehost's MX record points to your own domain, which delivers mail to Bluehost's local server. Change it to your provider's mail server.

Bluehost: Set email routing to Remote

If Bluehost doesn’t host your email, change the domain’s email routing setting to Remote. Otherwise Bluehost keeps treating mail for the domain as local.

2 more Microsoft 365 mistakes to avoid

Microsoft 365 on Bluehost: questions

Will my old Bluehost emails disappear when I switch to Microsoft 365?

No. Bluehost says new mail is delivered to the new provider, and messages already in Bluehost mailboxes stay there unless you move or remove them.

Where do I add Microsoft 365 DNS records in Bluehost?

Log in to the Bluehost Portal and click Domains in the left-hand menu. Select your domain, then open the DNS tab. Add each record there, one at a time.

What goes in the Host Record field at Bluehost?

Enter @ for records on your bare domain, such as MX and SPF. For the others, enter autodiscover.

Do I need to delete my existing MX records at Bluehost?

Remove MX records that point to your previous email provider, or give them a lower priority (a higher number) than the Microsoft 365 record. By default Bluehost's MX record points to your own domain, which delivers mail to Bluehost's local server. Change it to your provider's mail server. If Bluehost doesn’t host your email, change the domain’s email routing setting to Remote. Otherwise Bluehost keeps treating mail for the domain as local.

How long until Microsoft 365 email works on Bluehost?

DNS changes typically take about 15 minutes to take effect, occasionally longer. Bluehost says saved changes are processed in a few minutes but can take up to 8 hours to fully propagate, depending on caching and TTL.

Sources

Every value and step on this page comes from these official pages. Dashboards change, so if something doesn’t match what you see, tell us.