As of October 27, 2026, the practical rule is simple: record OAuth authentication, SMTP submission, and controlled inbox receipt as separate results. OAuth success proves that an identity was accepted; it does not prove that a message was submitted or received. This workflow is for testing your own application in a Microsoft 365 environment you own or are authorized to use.

This guide is for independent developers validating registration, password-reset, or notification email from their own app. It also helps QA engineers deciding whether an SMTP test actually verifies delivery.

Microsoft 365 email sending test: define the evidence first

Before changing code or tenant settings, decide what the test is supposed to prove. In practice, teams often use “email sent” to describe several different events:

  • The application obtained an OAuth access token.
  • The SMTP connection authenticated with that token.
  • The SMTP server accepted a message for submission.
  • A controlled recipient mailbox received a readable message.

Those results are related, but they are not interchangeable. If the test only checks token acquisition, it says nothing about whether SMTP accepted the message. If the SMTP server accepts the message, that still does not show that the intended recipient’s inbox contains it.

We recommend writing a pass condition for each boundary before running the test. For example: “The app obtained an SMTP-capable token,” “the SMTP transaction received a successful server response,” and “the controlled recipient received the message with this run’s identifier.” Keep the log or observation that supports each result.

This is also where account type matters. An Exchange Online work or school mailbox belongs to a Microsoft 365 organization, where organization-level and mailbox-level settings can affect SMTP AUTH. A personal Outlook.com account is not an Exchange Online tenant. Don’t apply an Exchange Online tenant-setting conclusion to a personal account, or use a personal-account test to claim that an organization’s configuration is correct. Microsoft’s Exchange Online SMTP AUTH configuration guidance describes the Exchange Online scope.

Test boundary: Run this process only against your own application and a Microsoft 365 account or tenant you’re authorized to test. A test recipient should also be under your control or explicitly approved for the test.

Preparation and authorization: separate the app, tenant, and mailbox

First, identify the sending account and environment. Record whether the sender is an Exchange Online mailbox, which tenant it belongs to, and whether the application is using delegated or application permissions. Also record whether the intended path is SMTP AUTH or a different mail-sending API. An application that sends through Microsoft Graph, for example, is not thereby proving that SMTP AUTH works.

Next, inspect the app registration and its consent state. The right permissions depend on the authorization model and the protocol. Microsoft’s OAuth guidance for IMAP, POP, and SMTP documents the OAuth flow and SMTP-specific permission details. Use that guidance to verify the permission appropriate to your flow; don’t substitute a permission for a different API just because it also relates to sending mail.

Consent deserves its own check. A permission listed in an app configuration is not necessarily permission that has been granted and is usable in the test. Confirm which account or administrator granted consent, which tenant the consent applies to, and whether the token request uses the same app and authorization model you documented. Microsoft explains the distinction between permissions and consent in its identity platform permissions overview.

Then inspect SMTP AUTH settings at both relevant scopes:

  • Organization scope: Check whether the organization’s configuration permits authenticated client SMTP submission.
  • Mailbox scope: Check the sender mailbox’s SMTP AUTH setting. A mailbox-level restriction can affect the test even when the broader organization configuration appears permissive.
  • Account and policy context: Confirm that the sender is the mailbox you expect and that tenant policies do not contradict the assumptions in your test notes.

Microsoft’s SMTP AUTH settings documentation covers the organization and mailbox settings. The important distinction is that SMTP AUTH availability and Basic Auth availability are not the same statement. A permitted SMTP AUTH path does not mean that Basic Auth will remain available indefinitely.

If you’re testing application-generated personal data, use test values rather than real people’s details. Our guide to data practices for test environments covers ways to keep demonstration and QA data separate from production identities.

OAuth authentication: prove the token is meant for SMTP

During the authentication stage, verify that the test app obtains a token intended for the SMTP operation and authorization model you chose. A token that is valid for another resource or API is not evidence that SMTP AUTH will accept it.

Follow the Microsoft OAuth guidance for the selected flow and check the permission or scope listed for SMTP. If your application uses delegated access, confirm that the signed-in identity and consent match the mailbox and tenant being tested. If it uses application permissions, verify the application authorization and mailbox access configuration required by that model. Don’t mix the two flows in a test report: they have different consent and access implications.

For an SMTP AUTH connection using OAuth, the client must present the token using the authentication mechanism expected by the SMTP service. Compare the implementation with Microsoft’s OAuth authentication instructions for SMTP, rather than assuming that a successful general-purpose token request is enough.

Capture evidence that can be reviewed later:

  • The app registration and authorization model used for the run.
  • The requested permission or scope, without exposing credentials.
  • Whether token acquisition succeeded or failed.
  • The SMTP authentication result and a correlation identifier, if your application provides one.
  • The tenant and sender mailbox tested, stored in an appropriate, access-controlled test record.

Never paste a live access token, client secret, password, or authorization code into a ticket, shared test report, or example output. If a log contains a secret, redact it before sharing and follow your organization’s credential-handling process.

A successful OAuth exchange earns a narrow conclusion: identity authentication passed for this attempt. It does not show that the SMTP server accepted a message, that the recipient address was valid, or that a recipient mailbox received the message.

SMTP submission: distinguish application success from server acceptance

Once authentication is verified, trigger a test message from the application you are developing. Use the same code path that production will use where possible, but keep the destination and content controlled. Include a unique, non-sensitive test-run marker in the subject or body so the recipient-side message can be matched to the sender-side logs.

Record the sender, intended recipient, run marker, timestamp, and SMTP response. Also note whether your application reported a failure before connecting, during authentication, or after sending the message data. Those distinctions narrow the next investigation:

  • Token acquisition failed: Review the authorization request, consent, tenant, and permission configuration.
  • Token acquired but SMTP authentication failed: Compare the token and SMTP authentication mechanism with the documented OAuth flow; then verify the sender mailbox and tenant settings.
  • Authentication passed but submission failed: Inspect the SMTP response and the organization- and mailbox-level SMTP AUTH configuration. Check whether the application is addressing the intended sending mailbox.
  • SMTP server accepted the submission: Record that response as submission evidence. Do not mark recipient delivery as passed yet.

Microsoft’s client SMTP submission guidance for applications describes the supported configuration context for sending through Microsoft 365. Use its current guidance for connection settings; don’t copy settings from an unrelated account type or an old test script without checking the applicable documentation.

A useful internal report keeps the sender’s response close to the run identifier. Otherwise, teams can accidentally pair a successful SMTP response from one attempt with a recipient message from another. That creates a false pass, especially when automated tests retry or multiple runs share a mailbox.

A decision guide for test results

Observed result What it proves Next action
OAuth token request fails The identity or authorization step did not complete Check flow, consent, requested SMTP permission, tenant, and account
OAuth succeeds; SMTP authentication fails A token was issued, but the SMTP authentication attempt did not pass Check token suitability, authentication mechanism, sender, and SMTP AUTH settings
SMTP authenticates; submission is rejected The connection authenticated, but the message was not accepted for submission Review the SMTP response and tenant/mailbox configuration
SMTP accepts the message; no controlled receipt is found Submission passed; recipient receipt is unverified Check the controlled recipient and gather recipient-side evidence
Controlled recipient receives the matching message The message reached that recipient in this test Record the environment and run; do not generalize to production delivery

Controlled receipt: verify the message at the destination

Use a test address that you control and can inspect. The destination should be separate from unrelated personal or production correspondence so that the message is easy to identify and the test does not expose real user data. A controlled test recipient is one option; choose an address only if its access, retention, and privacy properties fit the test.

After the application submits the message, check the recipient mailbox for the unique run marker. Confirm that the recipient is correct, the message content belongs to the current run, and any registration or password-reset link is readable and points to the expected test environment. If the message is in junk or another folder, record that location rather than reporting “not received.” If nothing appears, note the time of the check and continue investigating; don’t convert the sender’s success response into a delivery claim.

For tests where receipt time matters, compare the sender-side event with recipient-side observations. A mail arrival delay check can help structure that observation. It does not establish a universal delivery time or predict how production recipients will be treated.

A single successful observation has a limited scope. It shows that this message, from this sender, through this environment, was received by this controlled destination. It does not prove that all recipient providers will accept the message, that every future run will pass, or that production messages will avoid filtering.

The same boundary applies to a missing message. It may indicate an issue after submission, a recipient-side filter, a mismatched address, or a message that has not yet been observed. Keep it as “receipt not verified” until you have destination-side evidence or another reliable delivery record.

Policy review and test record: keep Basic Auth separate from OAuth

Microsoft’s latest timeline matters if a test plan still relies on Basic Auth. In its update published on January 27, 2026, the Exchange team said SMTP AUTH Basic Auth behavior would remain unchanged through the end of December 2026. After that, existing tenants are to have Basic Auth disabled by default, though administrators can enable it as needed; new tenants are to have it unavailable by default. Microsoft also said it plans to announce a final removal date in the second half of 2027. See the Exchange team’s updated SMTP AUTH Basic Auth timeline.

That timeline is specifically about Basic Auth behavior for SMTP AUTH. It is not a statement that OAuth support for SMTP AUTH is being removed. Keep the protocol and authentication method distinct in your notes: SMTP AUTH is the submission mechanism; OAuth is an authentication approach; Basic Auth is a different authentication method. Don’t describe “SMTP AUTH is enabled” as proof that Basic Auth remains available or will continue to work.

At the end of a test run, save three separate conclusions:

  • OAuth authentication: passed, failed, or not tested, with the relevant redacted evidence.
  • SMTP submission: accepted, rejected, or not tested, with the response and run identifier.
  • Controlled receipt: received, not found, or not tested, with the recipient-side observation.

Add the tenant and mailbox context, the application authorization model, and the date of the policy check. Revisit the plan whenever Microsoft updates its timeline, changes tenant defaults, or revises the OAuth or SMTP AUTH documentation. As of October 27, 2026, the policy summary above is based on the January 27 Exchange team announcement and Microsoft’s current OAuth and SMTP AUTH configuration documentation.

FAQ

OAuth authentication passed, but the test message is missing

Check the application’s SMTP connection and submission response first. Then search the controlled recipient’s inbox and junk folder for the run marker, and verify that the recipient address matches the test configuration. Keep the result as “receipt not verified” until you observe the message or obtain recipient-side evidence. A successful OAuth result alone cannot settle whether submission or delivery occurred.

SMTP accepted the message, but how can receipt be confirmed?

Inspect a mailbox that you control and match the message to the current run using its recipient, content, and unique marker. Confirm that any link or notification can be read. Save this observation alongside the SMTP acceptance response. That pairing confirms receipt for the specific test and recipient, but it does not guarantee delivery to production users or to other mail services.

How does the Basic Auth change affect a Microsoft 365 test setup?

Microsoft’s January 27, 2026 announcement says behavior remains unchanged through the end of December 2026. After that, existing tenants are expected to have Basic Auth disabled by default, with administrators able to enable it when needed; new tenants are expected to have it unavailable by default. Microsoft plans to announce the final removal date in the second half of 2027. Check the official announcement again before relying on an older timeline.

Which log tells me whether authentication, submission, or receipt failed?

Use the stage where the evidence stops. Token acquisition or SMTP authentication errors belong to the authentication stage. A server rejection after successful authentication belongs to submission. A successful acceptance response without a matching message at the controlled recipient means receipt is unverified. Preserve the relevant redacted log and recipient observation for the same run so that retries or parallel tests do not create a misleading pass.

For a one-off registration, notification, or verification-message check, a separate test recipient can keep your primary inbox out of the run and make destination-side inspection easier. fwdtemp is one option for receiving a controlled test message; check its current service details before relying on it for any retention or access requirement. It can help verify a test of your own application, but it cannot promise delivery to every recipient or predict production mail handling.

Frequently asked questions

What should I check when OAuth succeeds but the test email never appears?

Treat the OAuth result as identity evidence, not delivery evidence. Check whether the application opened the intended SMTP connection, used a token with the SMTP permission for its authorization model, and received a successful submission response. Then inspect the controlled recipient’s inbox and junk folder, and compare the message headers and timestamp with the test run. These checks help isolate a submission issue from a later delivery or filtering issue.

How can I prove that an SMTP-accepted message reached my test address?

Use a recipient mailbox you control and verify the message itself, rather than relying on the sender’s success screen. Match the subject, body, recipient, and test-run identifier, then confirm that any verification link or notification content can be read. Save the recipient-side observation with the SMTP response. This proves receipt in that mailbox for that run; it does not establish delivery performance for production users or other providers.

What does the Basic Auth timeline mean for an existing Microsoft 365 test tenant?

Microsoft’s January 27, 2026 update says Exchange Online SMTP AUTH Basic Auth behavior remains unchanged through the end of December 2026. After that, existing tenants are to have it disabled by default, with administrators able to enable it as needed; new tenants are to have it unavailable by default. Microsoft plans to announce a final removal date in the second half of 2027. Recheck the official timeline before changing a test plan.

How do I tell OAuth failure from SMTP submission failure or a missing message?

Keep separate evidence for each boundary. An OAuth error points to token acquisition, consent, permission, or authentication handling. A successful OAuth exchange followed by an SMTP error points to connection, tenant, mailbox, or submission configuration. A successful SMTP acceptance with no message in the controlled recipient means receipt is still unverified; investigate recipient-side filtering and message trace or delivery evidence available to your organization.

Start with disposable email

Create a disposable email to receive codes and notifications online; switch to email forwarding when you need ongoing contact.

Open disposable inbox