Blog
SavedSearch
Visit Hostlelo

Microsoft 365 SMTP Basic Auth: Prepare for the December Default-Off Change

Microsoft 365 turns off SMTP AUTH Basic Auth by default at the end of December 2026. Find every app sending with a password and move it to OAuth or a relay.

The short answer

At the end of December 2026, Microsoft will disable SMTP AUTH Basic Authentication by default for existing Microsoft 365 tenants; administrators can still re-enable it temporarily, and the final removal date has not been announced. Find password-based senders with the SMTP AUTH clients report, then move each one to OAuth, an API-based WordPress mailer, or an appropriate relay.

Email sender migrating from password authentication to a secure OAuth token through a cloud mail gateway
Reading options

On this page

Before you start

You need Exchange Online admin access to review SMTP AUTH usage. OAuth app changes also require Microsoft Entra admin consent and developer review; relay connectors require a fixed, organization-owned public IP. Inventory senders, preserve current settings privately, and use a dedicated test mailbox before production rollout.

If your website, WordPress plugin, scanner or invoice app sends email by logging in to smtp.office365.com with a username and password, it is using SMTP AUTH with Basic Authentication. Microsoft says that at the end of December 2026 this will be disabled by default for existing Microsoft 365 tenants. Admins can still switch it back on for now, but the lasting fix is OAuth or another supported sending method.

Here is the part that catches people. Nothing breaks loudly. The contact form still says thank you, the plugin still looks configured, and the email simply never leaves. You find out weeks later when a customer asks why nobody replied.

By the end of this guide you will be able to list every app that still sends with a password, pick the right replacement for each one, and prove it works before Microsoft flips the default.

What SMTP AUTH is and why Microsoft is changing it

SMTP AUTH is how an app proves who it is before it hands an email to Microsoft 365 for sending. Microsoft describes it as the protocol for client email submissions, typically on TCP port 587, and says it supports OAuth as well as Basic Authentication.

Basic Authentication means the app sends a real username and password every time it connects. OAuth means the app shows a short-lived token instead, issued by Microsoft Entra ID (Microsoft's sign-in service) after you approve the app.

Think of a hotel. Basic Auth is like giving the cleaner a copy of your house key. OAuth is like the front desk handing them a key card that opens one room, for a limited time, and that the desk can cancel without changing your locks.

Microsoft's Exchange Team posted the updated timeline on 27 January 2026. At the time of writing (16 November 2026), it says:

  • Now to December 2026: SMTP AUTH Basic Authentication behaviour stays unchanged.
  • End of December 2026: it will be disabled by default for existing tenants, and administrators will still be able to enable it if needed.
  • New tenants created after December 2026: it will be unavailable by default, and OAuth will be the supported method.
  • Second half of 2027: Microsoft will announce the final removal date.

Microsoft gives "end of December" and no exact day, so plan as if your senders could stop at any point in the last week of the month.

Why this matters: the option to switch Basic Auth back on is a pause button. A final removal date is coming, so fixing each sender properly now means you only do this work once.

Before you start

Run through this list first. It takes ten minutes and saves hours later.

  • Admin access. Microsoft lists these role groups for mail flow reports: Compliance Administrator, Exchange Administrator, Organization Management, Security Administrator, Security Reader and View-Only Recipients.
  • A list of everything that sends email. Contact forms, WordPress, shop and booking plugins, invoice tools, printers and scanners, backup and monitoring alerts. Step 1 fills the gaps.
  • A backup of current SMTP settings. For each app, screenshot the server, port, username and encryption setting into a private note. Never paste passwords into shared documents.
  • A WordPress backup if a site is involved. Take a full backup of files and database from your hosting control panel or backup plugin before you change mail plugins.
  • Time. About an hour for the report and inventory, then 30 to 60 minutes per app. Custom code can take longer.
  • Risk. Most steps are read-only or touch one mailbox. The risky move is changing settings for the whole organisation, and this guide flags it.

Find your password senders and plan the move

Step 1: Find every app that sends with a password

Microsoft has a report built for exactly this. Open the new Exchange admin center at https://admin.exchange.microsoft.com and go to Exchange admin center > Reports > Mail flow > SMTP AUTH clients report.

The section called Messages sent using SMTP Auth shows Sender address, Domain, Authentication Protocol, the share of messages sent with TLS 1.0, 1.1 and 1.2, and Messages sent.

Watch the Authentication Protocol column. Microsoft says Basic Auth shows as TlsAuthLogin and Modern Auth shows as XOAUTH2.

The report covers the last 7 days by default, and you can widen it to 90 days. Widen it, because a monthly invoice run will not appear in a 7-day window. Then select Export to save a .csv file. That file is your checklist.

What you should see: sender addresses such as forms@example.com, each with a protocol. Every TlsAuthLogin row is a job for you.

Quick tip: look at the TLS columns too. Microsoft says client SMTP submission needs TLS 1.2 or TLS 1.3, so a sender still on TLS 1.0 or 1.1 probably needs a software or firmware update first.

Step 2: Match each sender address to a real app

The report shows which mailbox signed in, not which app did it. Search your notes, plugin settings, printer admin pages and config files for each TlsAuthLogin address.

Made-up example: a small bakery uses orders@example.com, and the report shows it with TlsAuthLogin. The owner finds three users of that login: a WordPress order form, an office scanner and an old invoice tool on a laptop. Each needs a different fix.

Step 3: Pick the right method for each app

Microsoft documents four ways for a device or app to send through Microsoft 365:

  • Client SMTP submission with OAuth. The app signs in as a mailbox with a token. Server smtp.office365.com, port 587 (recommended) or 25, TLS 1.2 or later. Microsoft recommends OAuth here.
  • SMTP relay through a connector. Your device sends to your domain's Microsoft 365 MX endpoint on port 25, trusted by a certificate or a fixed IP registered in an inbound connector.
  • Direct Send. Unauthenticated sending on port 25, where your device acts as an outside mail server delivering straight to Microsoft 365.
  • High Volume Email. Large volumes to internal recipients, through a special HVE account on port 587.

A rough rule: custom code goes to OAuth, WordPress goes to an API-based mail plugin, and printers or scanners without OAuth go to a relay connector if they send from a fixed public IP.

Heads up: Microsoft says a device or app that recommends or defaults to port 465 does not support the TLS versions it requires. Port 465 is not an option.

Client SMTP submission is also capped at 10,000 recipients per day and 30 messages per minute, so newsletters belong on a proper bulk sending service.

Step 4: Check which mailboxes can use SMTP AUTH at all

There is an organisation-wide switch and a per-mailbox switch, and Microsoft says the mailbox setting takes precedence.

This command loads the Exchange Online module and signs you in (use your own admin address).

Import-Module ExchangeOnlineManagement
Connect-ExchangeOnline -UserPrincipalName admin@example.com

This command shows the organisation setting. True means SMTP AUTH is off for the organisation, False means it is allowed.

Get-TransportConfig | Format-List SmtpClientAuthenticationDisabled

This command shows the setting for one mailbox.

Get-CASMailbox -Identity forms@example.com | Format-List SmtpClientAuthenticationDisabled

What you should see: an empty value means the mailbox follows the organisation setting. True turns SMTP AUTH off for that mailbox, and False turns it on whatever the organisation says.

You can check one mailbox without PowerShell too. In the Microsoft 365 admin center go to Users > Active users, select the user, then Mail, then Manage email apps, and look at the Authenticated SMTP checkbox.

Why this matters: a good end state is SMTP AUTH off for the organisation and on only for the few mailboxes that need it. Then a leaked staff password cannot be used to send spam through SMTP.

Variant A: OAuth for custom apps and scripts

This path suits an in-house app, a PHP or Node script, or software that explicitly supports Microsoft OAuth for SMTP. The commands below are an implementation outline, not a copy-paste migration: a tenant administrator and developer must review app permissions, secret or certificate handling, mailbox scope and monitoring before production use.

Step A1: Register the app in Microsoft Entra

Register an application in Microsoft Entra. Open its API Permissions blade, select Add permission, choose APIs my organization uses and search for Office 365 Exchange Online.

Select Application permissions, choose SMTP.SendAsApp, select Add permissions, and grant admin consent.

Heads up: Microsoft says the token request scope must be https://outlook.office365.com/.default. If the app signs in as a person instead, the scope is https://outlook.office.com/SMTP.Send.

Step A2: Register the service principal in Exchange

A service principal is Exchange's record of your app. These commands install the module if needed, load it and connect to your tenant.

Install-Module -Name ExchangeOnlineManagement
Import-Module ExchangeOnlineManagement
Connect-ExchangeOnline -Organization <tenantId>

This command registers the service principal with the Application (client) ID and the Object ID.

New-ServicePrincipal -AppId <APPLICATION_ID> -ObjectId <OBJECT_ID>

Heads up: Microsoft says the Object ID must come from the Overview page of the Enterprise Application, not from App Registrations. The wrong one causes an authentication failure.

Step A3: Give the app access to one mailbox

This command lists service principals so you can copy the ID of the new one.

Get-ServicePrincipal | fl

This command grants that service principal access to the one dedicated mailbox it will send from.

Add-MailboxPermission -Identity "forms@example.com" -User <SERVICE_PRINCIPAL_ID> -AccessRights FullAccess

If the app sends as a different address than the mailbox, Microsoft says to also grant Send As with Add-RecipientPermission.

Step A4: Point the app at the token

Your developer sets the server to smtp.office365.com, port 587 with TLS 1.2 or later, and authentication to XOAUTH2. Microsoft documents the login string built from the mailbox and token, where ^A is the Control+A character.

base64("user=" + userName + "^Aauth=Bearer " + accessToken + "^A^A")

Many mail libraries can build this once they have the token, so check the library's documentation first.

Variant B: SMTP relay connector for printers and scanners

Many printers and scanners cannot do OAuth. For these, Microsoft documents an SMTP relay through an inbound connector.

Check one thing first. Microsoft says dynamic IP addresses are not supported, and the IP must belong exclusively to your organisation. If your connection's IP changes, talk to your internet provider before going further.

Step B1: Create the connector

Open https://admin.cloud.microsoft/exchange#/ and go to Mail flow > Connectors, then select Add a connector.

Set Connection from to Your organization's email server. Connection to is fixed as Office 365.

Name it clearly, such as "Office scanner relay". Check that Turn it on is selected and Retain internal Exchange email headers is not.

On Authenticating sent email, choose the certificate option (Microsoft marks it recommended) or the IP option with your fixed IP, for example 203.0.113.25. On Review connector, select Create connector.

Step B2: Point the device at your MX endpoint

Set the device's SMTP server to your MX endpoint, which follows the pattern example-com.mail.protection.outlook.com for example.com, on port 25.

Step B3: Update SPF

Microsoft says that for an IP-based connector you should add the IP to your domain's SPF record, or mail may land in Junk. This hypothetical record lists a documentation-only IP next to Microsoft 365. Do not copy it unchanged: first inventory every legitimate sender and edit the domain's existing SPF record.

example.com.  TXT  "v=spf1 ip4:203.0.113.25 include:spf.protection.outlook.com -all"

Edit your existing record instead of adding a second one. Microsoft says only one SPF record is allowed per domain, and two make SPF return permerror. Our guide to SPF, DKIM and DMARC setup for small business email covers the basics, and the one on the SPF 10 DNS lookup limit helps if your record is crowded.

Quick tip: a website on shared hosting usually shares its server IP with other customers. That fails Microsoft's requirement that an IP used for connector authentication belongs exclusively to your organisation, so use the WordPress path for websites instead.

Variant C: WordPress sites

Most WordPress sites send through a mail plugin holding a Microsoft 365 username and password. That is exactly the setup that stops.

Step C1: Find out how your plugin sends

Open your mail plugin's settings. If you see smtp.office365.com with a username and password, the site uses Basic Auth. Screenshot the settings before changing anything.

Step C2: Switch to an API-based Microsoft mailer

WP Mail SMTP is one common example. Its documentation (last updated 29 June 2026) says its Outlook mailer is "only available with the Pro license or higher" and uses Microsoft's API rather than an SMTP password. You register an app in Microsoft Entra, paste the plugin's redirect URI, create a client secret, then allow the plugin to send with your Microsoft account.

Heads up: the plugin's guide sets the client secret to expire after 730 days (24 months), and warns you cannot see the secret value again after leaving the page. Put a calendar reminder a few weeks before expiry.

Another heads up: a separate WP Mail SMTP blog post, updated 25 May 2026, still says Microsoft will start rejecting requests in March 2026 and stop fully by 30 April 2026. That is out of date. Microsoft's post of 27 January 2026 moved the default change to the end of December 2026, so trust Microsoft's own timeline over third-party summaries.

Other plugins have their own Microsoft options. Look for OAuth, Microsoft API or Microsoft Graph in their docs, and avoid any setup that asks for a Microsoft 365 password.

If website mail does not need a staff mailbox at all, it can go through your host's mail server instead. If emails to your own domain then go missing, read WordPress email to the same domain fails, check cPanel.

How to check it worked

Do these checks for every app you moved, including the last one.

  • Send a real test. Submit the form, scan a page or trigger a test invoice. It should reach an outside inbox within a few minutes.
  • Use the plugin's test tool. A successful "send test email" in WordPress means Microsoft accepted the message.
  • Rerun the SMTP AUTH clients report after a day or two. A mailbox moved to OAuth should show XOAUTH2. One moved to a relay or an API-based plugin should drop off the report.
  • Recheck the mailbox setting with the Get-CASMailbox command from Step 4.
  • Read the headers. In the received test email, SPF and DKIM should pass. Our guide to reading DMARC aggregate reports shows how to confirm the sender is aligned.

When the report shows no TlsAuthLogin rows across a full billing cycle, you are done.

Troubleshooting

The SMTP AUTH clients report is empty

Symptom: no rows at all. Likely cause: nothing used SMTP AUTH in the default 7 days. Fix: Microsoft suggests changing the date range, so set it to 90 days before deciding you have no senders.

OAuth app gets a token but authentication still fails

Symptom: the token request works, yet the SMTP login is refused. Likely cause: the service principal used the Object ID from App Registrations, or the token scope is wrong. Fix: confirm the Object ID given to New-ServicePrincipal came from the Enterprise Application, and use the scope https://outlook.office365.com/.default.

Messages bounce with a Send As error

Symptom: the email returns with this text from Microsoft's documentation: 5.7.60 SMTP; Client doesn't have permissions to send as this sender. Likely cause: the app signs in as one mailbox but uses another From address. Fix: give the sign-in account Send As permission, or match the From address to the sign-in mailbox.

The device only offers port 465

Symptom: an older scanner has port 465 and no port 587 option. Likely cause: Microsoft says such devices lack the required TLS versions. Fix: update the firmware. If it still cannot do port 587 with TLS 1.2, use a relay connector on port 25 or replace the device.

SMTP AUTH is ticked on the mailbox and logins still fail

Symptom: Authenticated SMTP is enabled, yet logins fail. Likely cause: Microsoft says SMTP AUTH is already disabled when Entra security defaults are on, and an authentication policy blocking Basic Auth for SMTP overrides the mailbox setting. Fix: do not switch off security defaults for an old app, because they protect every account. Move the app to an API-based mailer, OAuth or a relay, and ask your admin to review authentication policies.

Relay mail lands in Junk

Symptom: scanner emails arrive in Junk. Likely cause: SPF does not list the device IP. Fix: add it to your single SPF record as in Step B3, then test again.

Pro tips and security notes

  • Use a dedicated sending mailbox such as forms@example.com that nobody reads on their phone, so a leak stays small.
  • Turn SMTP AUTH off for everyone else once senders are moved, allowing it per mailbox only where needed. Test on one mailbox first and keep your screenshots for rollback.
  • Do not lean on the re-enable switch. It is a short safety net while you finish, since a final removal date is due in the second half of 2027.
  • Track secret expiry dates next to each app in your inventory.

When to ask for help: ask a developer when the sender is custom code, because OAuth means code changes and safe secret storage. Ask your host when you are unsure which mail server your website really uses. Ask your Microsoft 365 admin or partner when security defaults or authentication policies are involved, because those touch every user.

The one message worth forwarding

Copy this, fill in the blanks and send it to whoever looks after your website or apps.

"Hi, Microsoft says that at the end of December 2026 it will disable SMTP AUTH Basic Authentication by default for existing Microsoft 365 tenants (Exchange Team post, 27 January 2026). Our SMTP AUTH clients report shows [sender address] still signing in with a password (TlsAuthLogin). Could you move [app or site name] to a supported method before mid-December: OAuth (XOAUTH2) on smtp.office365.com port 587, an API-based Microsoft mailer for WordPress, or a relay connector if it is a device with a fixed IP? Please send a test email afterwards and tell me any client secret expiry date. Thanks."

The takeaway: run the SMTP AUTH clients report this week, because every TlsAuthLogin row is a sender that could go quiet at the end of December.

Reader questions

Will my website emails stop on a specific day in December 2026?

Microsoft only says the end of December 2026 and has not named a day. Treat the last week of December as the risk window and finish your changes before then.

Does this change affect tenants created in 2027?

Yes. Microsoft says tenants created after December 2026 will not have SMTP AUTH Basic Authentication available by default, and OAuth will be the supported method.

Does the change apply to every Microsoft cloud environment?

Microsoft's announcement says the updated timeline covers customers with tenants in all cloud environments.

Is OAuth sending still SMTP AUTH?

Yes. Microsoft says SMTP AUTH supports OAuth as well as Basic Authentication, and the SMTP AUTH clients report shows OAuth logins as XOAUTH2.

Can an app send without SMTP at all?

Yes. Microsoft's Basic authentication deprecation page lists the Microsoft Graph API as another option for sending authenticated mail.

Is the WP Mail SMTP Outlook mailer free?

No. WP Mail SMTP's own documentation says the Outlook mailer is only available with the Pro licence or higher.

Sources & further reading

  1. Microsoft Exchange Team: Updated Exchange Online SMTP AUTH Basic Authentication deprecation timeline
  2. Microsoft Learn: Enable or disable SMTP AUTH in Exchange Online
  3. Microsoft Learn: SMTP AUTH clients report
  4. Microsoft Learn: Mail flow reports in the new Exchange admin center
  5. Microsoft Learn: Set up a multifunction device or application to send email using Microsoft 365
  6. Microsoft Learn: Authenticate an IMAP, POP or SMTP connection using OAuth
  7. Microsoft Learn: Deprecation of Basic authentication in Exchange Online
  8. Microsoft Learn: Connect to Exchange Online PowerShell
  9. Microsoft Learn: Set up SPF for Microsoft 365
  10. WP Mail SMTP: How to set up the Outlook mailer

What changed

Corrected the headline to reflect Microsoft’s default-off milestone rather than final removal. Rechecked the 27 January 2026 timeline and OAuth service-principal steps, labelled custom-app commands as an implementation outline, and marked the SPF record as hypothetical. Added original accessible media.

Originally published . About our editorial updates.

Your next project deserves a better foundation.

Explore hosting built for your next chapter.

Explore hosting

Find your next answer.

Search published guides and articles.

Ctrl / ⌘ K to open · Esc to close