Skip to main content

Outlook on your domain as the sender

Testimonial Requests From Microsoft 365 SMTP

Your company mail runs on Microsoft 365 and you want requests to arrive from an address customers already reply to. Microsoft calls the route an outside app uses "client SMTP submission", or SMTP AUTH. It is off for many newer tenants, it clashes with security defaults, and Microsoft is changing how password sign in works for it. Read the timeline first, then work through the checklist with whoever runs your Microsoft 365 admin center.

  • SMTP AUTH enabled on one chosen mailbox
  • The Basic auth change dated from Microsoft’s post
  • A fallback if your tenant blocks password sign in

Microsoft 365 checklist

Can your tenant send through SMTP AUTH?

Work through it with a Microsoft 365 admin. Cited items come from Microsoft Learn and the Exchange team blog as read on 2026-11-17.

1. Tenant settings
2. The sending mailbox
3. Connection and test

Your ticks stay in this browser tab and are not sent anywhere.

The problem, solved

Getting requests out of Outlook without weakening security

  • Problem 1

    Customers know our Outlook addresses

    Contracts, invoices and support all come from your Microsoft 365 domain. A request from elsewhere breaks that pattern.

  • Problem 2

    IT will not switch off security defaults

    Turning off a tenant wide protection to let one app send mail is a bad trade, and many admins will refuse.

  • Problem 3

    Thirty messages a minute feels tight

    Microsoft throttles this sending method, so a large batch can be slowed or refused partway through.

  • Problem 4

    Only recent customers should hear from us

    A staff mailbox that suddenly emails hundreds of old contacts collects bounces and complaints on an address your team uses every day.

  • Problem 5

    Setup is stuck waiting on IT

    Tenant changes can take weeks, and the customer who just praised you on a call is ready today.

What Microsoft has published about Basic auth for SMTP AUTH

From the Exchange Team Blog post of January 2026, as read on 2026-11-17. OAuth for SMTP AUTH is not being retired. Check for later updates.
WhenWhat Microsoft says happens
Until December 2026Behaviour is unchanged for existing tenants
End of December 2026Disabled by default for existing tenants; admins can enable it again
Tenants created after December 2026Unavailable by default; OAuth is the supported method
Second half of 2027Microsoft will announce the final removal date

In StoryProof

Connect a Microsoft 365 mailbox

Step 1 of 4

Check the tenant first

Confirm security defaults and authentication policies allow SMTP AUTH with a password. If they do not, stop here and use the fallback rather than loosening security.

Before you start

Limits worth knowing

  • Steps follow Microsoft’s docs as of 2026-11-17

    Every Microsoft step and date here comes from Microsoft Learn and the Exchange Team Blog on that date. Our team has not followed them on a live tenant.

  • No OAuth sign in is claimed

    This page does not say StoryProof can sign in to Microsoft 365 with OAuth. Ask StoryProof support before your tenant loses Basic auth.

  • The fallback is another provider

    If your tenant blocks password sign in, connect SendGrid, Mailgun, Mailchimp or another SMTP account that sends for your domain.

  • Microsoft’s limits apply

    Microsoft lists 10,000 recipients a day and 30 messages a minute for client SMTP submission, plus general mailbox limits.

FAQ

Questions people ask

Short answers to what usually comes up next.

Why does sign in fail even with the right password?

Usually SMTP AUTH is off for the mailbox, security defaults are on, or a policy blocks Basic authentication. Microsoft returns an error saying Basic authentication is not supported once it is blocked.

Can I use port 465?

Microsoft says a device or app that defaults to port 465 does not support the TLS versions needed for client SMTP submission. Use 587.

Is SMTP relay through a connector an option?

Microsoft says SMTP relay cannot be used to send from a third-party hosted service, and it needs a static IP or certificate. For an outside app, client submission is the route.

Will requests appear in the mailbox’s Sent Items?

Microsoft lists saving to Sent Items as a feature of client SMTP submission, so your team can see what was sent from that mailbox.

Still have a question? Ask the StoryProof team or book a demo.

Ask from your company address

Connect your own SMTP account and choose which recent customers hear from you.

Sources

  1. How to set up a multifunction device or application to send email using Microsoft 365 or Office 365, Microsoft Learn. Checked 2026-11-17.
  2. Enable or disable SMTP AUTH in Exchange Online, Microsoft Learn. Checked 2026-11-17.
  3. Exchange Online to retire Basic auth for Client Submission (SMTP AUTH), Microsoft Exchange Team Blog. Checked 2026-11-17.
  4. Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline, Microsoft Exchange Team Blog. Checked 2026-11-17.

Last updated 2026-11-17.