Content reviewed: 12 October 2026
Separate the SMTP protocol from Basic Authentication. Changes to password-based SMTP AUTH do not end SMTP or affect every connector and device in the same way.
The current retirement timeline
The updated Exchange team announcement keeps SMTP AUTH Basic Authentication behaviour unchanged through December 2026. At the end of December 2026, it is scheduled to be disabled by default for existing tenants, with administrators able to enable it again. For tenants created after December 2026, it will be unavailable by default and OAuth will be the supported method. Microsoft plans to announce the final removal date in the second half of 2027. That is not a statement that final removal will happen during 2027.
The older March and April 2026 retirement dates are superseded. Check the current announcement and notices for your own tenant before making a production change.
Complete the inventory before the default changes. Each sender needs a replacement method, a supplier responsible for configuration and a delivery test. The announcement does not establish that Basic Auth is currently enabled in your tenant.
Five sending methods
| Method | Use | Main requirement |
|---|---|---|
| SMTP AUTH with OAuth | Internal and external recipients | Licensed mailbox, supported OAuth client and enabled SMTP AUTH |
| SMTP relay | On-premises infrastructure; internal and external mail | Connector, certificate or static unshared IP, port 25 |
| Direct Send | Internal mail from a legacy system | MX endpoint, port 25, domain authentication and filtering |
| High Volume Email | Automated internal mail | HVE account, dedicated endpoint and active PAYG billing policy |
| Email service or API | Applications and external transactional mail | Provider requirements, domain, limits, cost and logs |
Microsoft compares the supported methods in its device and application setup guide. Choose according to where the sender runs, who receives the messages and how much operational support the business can provide.
OAuth needs more than a new password
For SMTP AUTH, use smtp.office365.com, preferably port 587, and STARTTLS with TLS 1.2 or 1.3. A server IP or port 465 is not a supported substitute. You need a licensed cloud mailbox and a client that actually supports OAuth for SMTP. An app password still uses password-based Basic Authentication.
SMTP AUTH settings exist at organisation and mailbox level. SmtpClientAuthenticationDisabled uses inverse logic: True disables it, False enables it and null on the mailbox inherits the organisation setting. Check Security Defaults and authentication policy separately. A checked Authenticated SMTP box does not prove sign-in works.
The mailbox setting is under Users → Active users → user → Mail → Manage email apps. Do not enable the service for every account. If the sender mailbox differs from the sign-in account, also verify Send As permission.
| Symptom | First check |
|---|---|
| No server connection | DNS name, port, firewall and supported TLS |
| Authentication rejected | Actual OAuth/Basic flow, mailbox SMTP AUTH and policies |
| 5.7.60 – sender permission missing | Sign-in account, From address and Send As |
| Internal delivery works; external rejected | Whether the route is internal-only Direct Send or HVE |
| HVE account exists but cannot send | Assigned valid billing policy and account status |
HVE is not a free external mailbox
High Volume Email uses a dedicated account without a mailbox and its own SMTP endpoint. Do not assign it a regular Microsoft 365 licence. The current recommended server is smtp.hve.mx.microsoft, port 587 with TLS. HVE serves recipients within the tenant; replies need an appropriate Reply-To address.
HVE supports OAuth and Basic Auth subject to identity policies, but it is not the same connection as smtp.office365.com. Do not automatically apply the standard SMTP AUTH retirement notice to this endpoint. Prefer OAuth rather than enabling Basic Auth merely because an alternative endpoint exists.
The HVE account needs a valid PAYG billing policy linked to an Azure subscription; it cannot send without one. No licence does not mean no cost. Check the 10 MB message limit for scans and the maximum of 50 recipients per message. The service is currently supported in Microsoft 365 Worldwide, not automatically in every cloud.
See the detailed guide to HVE and external recipient limits for volume, delivery and billing. Customer invoices need a method that supports external mail.
Inventory every sender
For every system, record its owner, SMTP endpoint or API, port, authentication method, sender address and recipient scope. Include its hosting location, supported firmware and access to logs.
Establish whether the sender serves employees only or customers too. A scan delivered to your own mailbox does not prove that invoices can reach external recipients.
Separate office devices from applications hosted by a third party. The Microsoft 365 SMTP relay described in the guide is not supported for third-party hosted applications, including Azure-hosted applications. A static cloud IP alone does not make that route supported.
What to ask the printer supplier
Ask about the exact printer model, firmware and supported OAuth flow. “Works with Microsoft 365” is insufficient. Obtain the registration procedure, token renewal process and instructions for diagnosing a failed connection.
Depending on the authentication flow, test token renewal and the effects of revoked consent, certificate replacement or a device restart. The supplier should explain how an authorised administrator restores access without depending on a departing technician’s personal account.
If the device cannot use modern authentication, choose a supported alternative. Disabling Security Defaults or tenant-wide protection for one scanner is not an automatic migration step. The replacement method must satisfy both network and identity requirements.
SMTP relay requirements
Relay requires an inbound connector and correct sender identification. Microsoft recommends a TLS certificate. For IP-based authentication, the public address must be static and not shared with another organisation, and port 25 must be reachable. A dynamic address or shared provider egress address does not satisfy those IP requirements.
Check branch offices and internet-provider changes. If authentication depends on the public IP, a new connection can interrupt sending even when the printer configuration stays unchanged.
Record the connector owner, IP changes, certificate expiry and related DNS configuration. The sender address must belong to an accepted domain. This relay scenario does not require a licensed mailbox, and the address need not receive mail; plan replies separately.
Direct Send is internal only
Direct Send delivers only to recipients in the cloud organisation. External recipients are not supported. Messages are treated as anonymous inbound email and pass through the relevant protections. An internal scan test does not validate external delivery.
Relay and Direct Send can use the same MX endpoint. Identify the route through the connector and connection authentication, not just the server entered on the printer. SPF and domain authentication must reflect the actual source of the messages.
Microsoft recommends Direct Send for advanced administrators and legacy devices that cannot use the earlier methods. Do not automatically choose it as the simplest password-free option. Someone must manage delivery, filtering and operational responsibilities.

Example: printer, ERP and website
In this hypothetical example, a company has an office printer, ERP on an on-premises server and a website hosted by an external provider. Their locations and recipient requirements differ, so their sending methods may differ too.
The printer sends to employees. ERP sends invoices to customers and needs delivery logs and retries. The website sends confirmations from its hosting environment. Giving all three one SMTP password ignores those differences.
Assign an owner and a separate acceptance test to each system. Finance checks invoice delivery, the office team checks scans and the website administrator checks confirmations. Success for one route does not establish that another route works.
Test delivery failures too
Test the intended recipient scope. For internal-only methods, confirm internal delivery and rejection of an external destination. For ERP, check internal and external recipients. Use a representative attachment and inspect the logs. In a controlled test, also check an unavailable network or invalid recipient.
Check retries and possible duplicate messages. For invoices, verify the business outcome rather than relying only on an “SMTP accepted” entry.
The handover must identify where failed messages are recorded and who responds. Otherwise, authentication may be modernised while delivery failures remain invisible.
Migration plan
- Inventory every sending system.
- Identify the current method and dependencies.
- Confirm supported alternatives with each supplier.
- Choose a method for the hosting location and recipient scope.
- Test delivery, attachments and failure handling.
- Migrate one system at a time.
- Remove obsolete access and update operational records.
Prepare a rollback procedure for the specific system, a responsible owner and clear activation conditions. Rollback must not silently restore a shared password or enable Basic Auth across the tenant. Recheck delivery and access records after recovery.
Frequently asked questions
Will all SMTP stop working in 2026?
No. The current timeline concerns Basic Authentication for standard SMTP AUTH. Announcing a final removal date in the second half of 2027 is not the removal date itself.
Will a new password or app password help?
It does not turn Basic Auth into OAuth. The client’s supported authentication mechanism must change.
Does every printer need a licensed mailbox?
No. SMTP AUTH submission requires a licensed cloud mailbox. Supported relay and Direct Send scenarios do not. HVE uses a dedicated account without a regular licence but needs a valid PAYG billing policy.
Can an Azure application use this corporate relay?
No. Microsoft does not support this SMTP relay for third-party hosted applications, including Azure. Assess OAuth submission or a suitable email service.
Can Direct Send or HVE send an invoice to a customer?
Not to a customer outside the cloud organisation. Both methods are for internal delivery. Choose a method supporting external recipients.
Does OAuth guarantee message acceptance?
No. Check the enabled protocol, identity policies, sender permissions, recipients, attachments and operational limits as well.
What to include in the handover
The completed migration has an inventory of senders, a verified method for each, recipient and attachment tests, operational logs and an assigned administrator. These records identify what must be checked again when a printer or hosting provider changes.








