Outlook address verification for consumer and business email
Outlook is used for both consumer email and business mail experiences. An address may use outlook.com, another Microsoft consumer domain, or an organization’s custom domain. Verify the actual domain instead of assuming that every Outlook user has the same address rules.
Open the relevant free tool →Consumer addresses and business domains differ
Separate the app from the provider
Someone reading mail in the Outlook application may use a mailbox hosted elsewhere. The application name is not evidence about the receiving server. Inspect the domain’s MX results when provider identification matters. Even those hostnames describe routing infrastructure rather than proving that a particular individual has a mailbox.
Start with structural mistakes
Check for missing characters, accidental spaces and a mistyped domain. Preserve the original input so a correction can be reviewed. Avoid rewriting aliases or removing punctuation based on rules remembered from Gmail. An address that looks similar is not necessarily the same recipient, especially across custom domains.
Treat plus addressing as configurable context
Exchange Online supports plus addressing, with tenant-level configuration affecting availability. That makes it a poor idea to reject every plus-tag address or assume that all Microsoft-related destinations behave identically. If you manage the receiving organization, inspect its documented configuration. If you do not, accept legitimate syntax within your product’s assistance policy and use confirmation when access matters.
Expect inconclusive mailbox checks
Receiving infrastructure can decline probing or return a response that does not confirm an individual account. Keep mailbox unknown separate from domain failure. For an existing customer, take recent successful messages and account activity in your own system. For a new registration, use an ownership-confirmation flow rather than interpreting a domain-level pass as account access.
Diagnose business-domain failures
If multiple addresses at one organization fail together, look at domain routing and the actual bounce text before removing them. A migration, tenant configuration or sender-policy problem may affect many valid accounts. Save the date, domain, provider and detailed reason. A narrow infrastructure investigation is more useful than repeatedly testing the same recipients and treating every unsuccessful probe as independent evidence.