Help ›

Microsoft 365 SMTP AUTH is being switched off: your options

Microsoft 365 is switching off password sign-in for sending email (SMTP AUTH with Basic authentication). If you have printers, business apps, or scripts that send through Microsoft 365 with a username and password, this guide compares the ways to keep them working, so you can choose the one that fits.

What is changing, and when

WhenWhat happens
Until December 2026Signing in to SMTP AUTH with a password keeps working as it does now.
End of December 2026Password sign-in is switched off by default for existing organizations. Administrators can still turn it back on if needed.
Organizations created after December 2026Password sign-in is unavailable by default. OAuth is the supported way to sign in.
Second half of 2027Microsoft announces the date that password sign-in is removed completely.

This affects anything that signs in to smtp.office365.com or smtp-mail.outlook.com with a username and password. It doesn’t affect apps that already sign in with OAuth (“modern authentication”). See Microsoft’s announcement for the details. Note that Microsoft has changed these dates before, so we keep this page up to date.

💡  Not sure whether you’re affected? Our “Will my email stop working?” checker takes a minute, and the legacy sign-in report analyzer finds the devices and apps in your organization that still sign in with a password.


Your options

OptionWhat you changeSends to anyone?Good to know
Turn password sign-in back onA setting in Microsoft 365YesOnly possible until Microsoft removes this option completely, and may not be available for new organizations. It keeps a password-only sign-in open, which is what Microsoft is retiring
Update the app or device to use OAuthThe app or device itselfYesThe best answer where it exists, but many printers, older apps, and scripts can’t support OAuth, or need an upgrade or replacement
Direct sendThe device’s server settings, and your DNS recordsNo – only to your own organizationNo sign-in at all. Needs port 25, which many networks block, and your organization may have chosen to reject this option due to security concerns
A connector (SMTP relay)A connector in Exchange Online, and your networkYesNeeds a fixed public IP address or a certificate, and port 25. Anything at that address can send as anyone in your organization
A separate email sending serviceThe device’s settings, and your DNSYesEmail no longer goes through your mailbox, so needs its own DNS records. Most services have their own limits and costs, and can’t receive mail
Auth-EmailThe device’s server name and passwordYesThe device keeps using a username and password; Auth-Email signs in to Microsoft 365 with OAuth on your behalf. Email is sent by your own mailbox. Also works for IMAP and POP

Turning password sign-in back on

From the end of December 2026, administrators of existing organizations can still re-enable password sign-in for SMTP AUTH. This buys time, but only until the removal date that Microsoft will announce in the second half of 2027 – and it isn’t expected to be available by default for new organizations. If you take this route, it is important to plan what replaces it later in 2027.

Updating the app or device to use OAuth

If the vendor has added OAuth (“modern authentication”) support, using this is the most direct fix. In practice this often means a firmware update, a paid upgrade, or registering an app in Microsoft Entra and maintaining its credentials. Many devices and older apps will never support OAuth.

Direct send

The device delivers straight to your organization’s mail server on port 25, without signing in. It can only send to addresses inside your organization, and messages are treated like any other incoming email – so they can be marked as spam unless your DNS records allow the sending address. Many internet providers block port 25, and Microsoft now lets organizations reject direct send altogether, as it can also be used for email spoofing.

A connector (SMTP relay)

A connector tells Exchange Online to accept email from a particular public IP address or certificate. It can send to anyone, but needs a fixed IP address (or a device that can present a certificate), port 25, and an administrator to set it up and keep it up to date. Because the address is what is trusted, anything sending from it can send as any address in your organization.

A separate email sending service

Services built for sending email accept a username and password or an API key. They work well for bulk and application email, but your messages no longer come from your mailbox: you add DNS records for the service, sent messages don’t appear in the mailbox’s Sent folder, there are separate limits and charges, and it can’t be used to read email.

Auth-Email

Auth-Email signs in to Microsoft 365 with OAuth for you. Your device or app keeps using SMTP with a username and a password that you choose, so the only thing that changes is the server name. Email is sent by your own mailbox, exactly as before, so there is nothing to change in DNS and no effect on deliverability – and the same account works for IMAP and POP, for apps that read email.

If your organization would rather keep SMTP AUTH turned off altogether, Auth-Email can send through Microsoft Graph instead, with nothing to enable for the organization or mailbox.


Which should I choose?

  • The app or device supports OAuth, and you can set it up: do this.
  • It only sends to people inside your organization, from a network with a fixed IP address and port 25: direct send or a connector can work.
  • It sends bulk or marketing email: use a service built specifically for bulk sending.
  • It needs to keep sending as your mailbox, to anyone, with as little change as possible, or it reads email too: this is what Auth-Email is for.

Try Auth-Email

The free trial needs no payment details, and is enough to link a mailbox, enter the settings in your device or app, and send yourself test messages. Most people are set up in a few minutes:

💡  Need help?

Not sure which option fits? Tell us what you’re trying to connect and we’ll give you a straight answer – including if that isn’t Auth-Email. Reach out anytime to support@auth-email.com.