A customer says an email sent from an Exchange Online alias never arrived, and a search for the mailbox’s primary address returns nothing.

Fastest check: search Message Trace using the alias that appeared as the actual sending address. A search for only the primary SMTP address may miss messages sent through an alias. If the search is empty, verify the recipient, time range, and trace details before concluding that the message was never sent.

This guide is for Microsoft 365 administrators checking alias-sending records, and for freelancers or small-business owners who send customer or project mail from an alias. It also helps anyone maintaining several business addresses distinguish the mailbox’s primary address from the address used for a particular message.

Last updated November 17, 2026. The feature and trace guidance were checked against the Microsoft Exchange announcement about sending from email aliases and Microsoft’s Message Trace documentation.

Step 1: Search Exchange Online alias-sending mail by the actual alias

Microsoft’s Exchange team announced general availability of sending from email aliases on October 7, 2026. The announcement also states the key tracing detail: Message Trace results searched by the primary SMTP address don’t include messages sent through an alias. To find those messages, use the alias as the sending address in the query. Read the announcement and its trace guidance.

That distinction matters because an address can identify a mailbox without being the address used for a particular message. For an Exchange Online alias-sending check, keep these values separate:

  • Primary SMTP address: the mailbox’s main email address.
  • Alias: another address associated with that mailbox.
  • From address: the address displayed as the sender in the message.
  • Trace sender: the sender value used to find a message in Message Trace.
  • Recipient: the address to which that particular message was addressed.

A visible From address is useful evidence, but it isn’t a substitute for checking the trace query and its events. Start with the address the message was sent from, then confirm the recipient and time window. If the original search used the primary address only, repeat it using the alias before treating the empty result as a delivery failure.

Step 2: Check a customer message using both addresses

When a customer reports that a message is missing, query with the alias used to send it and the customer’s recipient address. Keep a copy of the exact addresses and the approximate sending time before searching; this prevents a plausible-looking but mismatched query from being mistaken for proof.

In the new Exchange admin center, Message Trace provides filters and message details for investigating mail flow. Microsoft’s guide to running a message trace in the modern Exchange admin center describes the query process and the information available in results. Use the sender and recipient fields to narrow the investigation, then open the matching message’s details and events.

Read the result as a record of processing, not as a read receipt. A trace can help establish whether Exchange processed a message, encountered a delivery problem, or recorded a delivery event. A delivery event does not show that the customer opened or read the message. It also doesn’t establish what happened after delivery in the recipient’s own mailbox, such as a later move, deletion, or filtering action.

If the alias query is empty, don’t immediately widen the search to every message in the mailbox. First check whether the address was entered correctly, whether the customer’s address is the recipient you used, and whether the selected dates include the send time. Then run a separate query with the primary address only if there is a specific reason to test that identity. Keep the two results distinct in the investigation notes.

Why does Message Trace miss an alias message when the primary mailbox is searched?

The search can miss the message because the query address and the sending alias don’t match. The mailbox may own both the primary address and the alias, but that relationship doesn’t mean a primary-address search will return mail sent using the alias. For Exchange Online Message Trace, the sender value should match the address actually used for alias sending.

This is a query-scope problem, not proof that the message failed. If a primary-address search returns no match, repeat the search with the alias before escalating the case. Keep the original query recorded too: the difference between those results can explain why the first investigation appeared to show no message.

Microsoft documents that Message Trace data is available for the last 90 days, and that an individual search can cover a maximum 10-day date range. Those are separate limits: a message can be within the overall retention window and still be outside the date span selected for a particular query. Check the current Message Trace FAQ and the message trace instructions before investigating older mail or splitting a long investigation into smaller searches.

Step 3: Check incoming mail using the sender and target alias

For a message that was sent to an alias but didn’t arrive in the expected mailbox, start with the other direction of the mail flow. Search using the original sender and the target alias as the recipient, then confirm that the query includes the time the sender says the message was sent.

Don’t put the mailbox’s primary address into the recipient field simply because the alias and primary address belong to the same mailbox. The trace query should represent the address involved in the message being investigated. If the message passed through mail-flow rules that changed a recipient address, the original destination and the changed destination may need separate searches. Record which address each query uses; otherwise, the results can be difficult to compare.

For a customer or project workflow, ask the sender for the address they used and the approximate send time. A forwarded copy or screenshot may show a display name while hiding the actual address needed to narrow the trace. If the sender can provide the original message details, use those to check the recipient and sender values rather than relying on a name shown in a mail client.

Should an alias message be searched by sender or recipient?

Use the field that matches the direction of the message. For an outgoing message sent from an alias, use the alias as the sender and the customer or project address as the recipient. For an incoming message addressed to an alias, use the outside sender and the alias as the recipient. If the investigation involves an address rewritten by a mail-flow rule, search and record the original and rewritten recipient separately where needed.

This keeps a trace search tied to the actual message path. A search that swaps sender and recipient, or substitutes the primary address without a reason, can produce an empty result that looks more conclusive than it is.

Step 4: Review rules and trace events before assigning a cause

Aliases and primary addresses may lead to the same mailbox, but rules can match on particular message properties or addresses. Don’t assume a rule treated an alias exactly like the primary address. Check the trace events for the message and compare them with the conditions and actions in the tenant’s mail-flow configuration.

Microsoft’s mail-flow rules documentation explains how rules are configured. The precise outcome still depends on the tenant’s current configuration and the conditions that applied to the message. The documentation is a reference for rule behavior, not evidence that a particular rule matched a particular message.

When an event suggests a rule or another processing step affected the message, note the event and its time, then review the matching rule conditions with an administrator. Also check whether journaling, filtering, or other mail-handling processes are relevant in that tenant. Don’t label a rule as the cause based only on its existence; confirm that the trace evidence and configuration align.

A useful escalation note says what is known and what remains unverified. For example: “The alias query returns a message record for the recipient; the trace records a delivery event; customer mailbox placement and reading status are not confirmed.” That is more actionable than “sent successfully,” which can imply more than the trace establishes.

Does a missing trace result prove the message was never sent?

No. An empty result means the current query did not return a matching record. It may reflect a sender or recipient mismatch, an incorrect time range, an address rewrite, or a message outside the available trace window. It does not, by itself, prove that the sender never submitted the message.

Repeat the search with the alias actually used, verify the recipient, and adjust the date range if the message falls outside the current query interval. If the message is older than the documented retention window, an empty result may reflect data availability rather than sending behavior. In either case, record the limits of the search and avoid turning one missing result into a conclusion about ongoing deliverability.

Step 5: Save a repeatable investigation record

Administrators and project owners benefit from recording the query inputs alongside the result. That makes a later check easier to reproduce and gives another person enough context to continue the investigation without guessing which address was searched.

Use this checklist before closing a case:

  • [ ] Record the alias used as the sending address, if the message was outgoing.
  • [ ] Record the primary SMTP address separately; don’t substitute it for the alias in the sender query.
  • [ ] Record the outside sender or recipient address, according to message direction.
  • [ ] Record the query’s date and time range, including any timezone assumption used by the team.
  • [ ] Save the relevant trace result and event details, not only a summary such as “delivered.”
  • [ ] Note whether a mail-flow rule, address rewrite, or other processing step was checked.
  • [ ] State what the trace confirms and what it cannot confirm, such as whether the recipient read the message.
  • [ ] If the search returned no record, note which sender, recipient, and date range were tested before escalating.

This record is especially useful when an alias supports several customers or projects. A message can be investigated again without confusing a mailbox’s identity with the address used on a specific send. It also helps teams avoid drawing long-term conclusions from a single trace result, which is limited by its query scope, available data, and tenant configuration.

Compare the trace question with the address-management question

Message Trace answers a mail-flow question: what record does Exchange Online show for a message matching these search inputs? It doesn’t decide whether an address is a good long-term public contact point, whether replies should continue to reach a particular team, or how a business should manage its addresses over time.

For the separate choice between a one-off inbox and an address intended for ongoing use, see this guide to disposable and secondary email addresses. For temporary inbox planning, the mailbox lifetime planner can help frame that decision. Neither type of guide replaces Exchange Online trace data or confirms delivery from a Microsoft 365 tenant.

The comparison below keeps the responsibilities separate:

Need Use this address or tool What it can help establish What it cannot establish
Find an outgoing message sent through an alias The actual sending alias in the sender field Whether a matching trace record and events appear Whether the recipient read the message
Investigate incoming mail sent to an alias The original sender and target alias in the recipient field Whether the incoming message appears in the searched path Whether a rule or mailbox action was the cause without further review
Decide whether a business contact address should remain usable A maintained long-term mailbox or alias arrangement Whether the address supports the intended continuing workflow Exchange Online trace status for an individual message
Protect a primary address during a one-off signup A temporary email service, when the account is nonessential A way to avoid giving the primary address to that signup Long-term account recovery or a trace of Exchange Online mail

A useful way to score an investigation is to rate each item as confirmed, not confirmed, or not checked. Confirm the alias and recipient against the message details; confirm the date range against the trace limits; and confirm any suspected rule against both the events and the tenant configuration. A “not checked” item is a next action, not evidence of failure.

Investigation check Confirmed when… If not confirmed…
Sender identity The query uses the actual alias for an outgoing message Repeat the query with the alias
Recipient identity The recipient field matches the address involved in that message Verify the original recipient and any rewritten destination
Time coverage The selected range includes the send time and fits the current trace limits Use an appropriate range and split the search if required
Event interpretation The recorded event is described without claiming the customer read the mail Review the event details and qualify the conclusion
Rule handling Relevant rule conditions and trace events have been compared Check the tenant’s rules before assigning a cause

Choose a lasting address separately from trace troubleshooting

For client or project mail, decide whether the address must remain usable for replies, account recovery, and future correspondence. If those requirements apply, use an address-management setup that the business can maintain over time and document who owns it. A temporary address may suit a one-off registration, but it should not be assumed to provide a permanent customer contact path or ongoing account recovery.

Keep those choices separate from Exchange Online alias sending. A long-term alias or forwarding arrangement can help manage where business messages go; Message Trace is for investigating matching mail-flow records in Exchange Online. A temporary inbox is not a substitute for trace queries, and a trace record is not a long-term address-management plan.

For a one-off signup or a single verification message that doesn’t need future replies or recovery, QuickTMP can provide an immediately usable temporary inbox without registration, keeping the primary address out of that signup’s contact field and away from its follow-up mail. For customer messages, project correspondence, or any account that needs reliable future access, keep the business address under a maintained mailbox arrangement—and add the actual sending alias to the investigation record whenever a trace needs to be repeated.

Create first, then extend with the task

Open a temporary inbox and watch the remaining time and confirmation after each extension.

Create a disposable email