Sending, receiving, and organizing email in Outlook on the web for business
Reset the sending address in Outlook on the web first; if that does not restore sending, check whether Microsoft 365 has placed the mailbox on the Restricted entities list.
Reset the Outlook on the web sending address
This directly matches a receive-working/send-failing condition with no displayed error:
- In Outlook on the web, select Settings.
- Go to Mail > Sync email.
- Under From, verify that the sending address is the affected mailbox’s correct address.
- Go to Mail > Compose and reply.
- Reset the default From address to that mailbox.
- Sign out and back in, or open Outlook on the web in another browser, and send a new test message. ^1^
If sending is still blocked, check Restricted entities
A mailbox restricted by Exchange Online can continue receiving messages but cannot send. Before removing that restriction, investigate why it was applied.
- Run the Blocked Sender History diagnostic. It shows listing/delisting history and the sender’s MFA status.
- Open the Microsoft Defender portal and go to: Email & collaboration > Review > Restricted entities.
- Search for the affected mailbox.
- If it appears:
- Review recent sign-ins, Sent Items, mailbox forwarding, and Inbox rules for unauthorized activity.
- If compromise is suspected, secure the account first: reset its password, revoke active sessions, remove unknown authentication methods or applications, remove suspicious forwarding/rules, and enable MFA. Microsoft specifically requires regaining control of a potentially compromised account before unblocking it. ^2^
- Select the mailbox, choose Unblock, review the recommendations, select Next > Submit, and confirm with Yes.
Restrictions are normally removed within one hour, although transient issues can extend this to 24 hours. Removing a mailbox requires membership in Organization Management or Security Administrator; being a Microsoft 365 administrator does not necessarily include those roles. ^3^
Alternatively, after securing the account, an appropriately authorized Exchange Online PowerShell session can check and remove the restriction. Replace <user-UPN> with the mailbox’s actual user principal name before running these commands:
Get-BlockedSenderAddress
Get-BlockedSenderAddress `
-SenderAddress <user-UPN> |
Format-List
Remove-BlockedSenderAddress `
-SenderAddress <user-UPN>
If the mailbox is not restricted
Run a message trace to determine whether Exchange Online accepted or rejected a test message:
- Send a new test message from the affected mailbox.
- Open the Exchange admin center.
- Go to Mail flow > Message trace.
- Select a date range covering the test and add the affected mailbox as the sender.
- Select Search, open the matching result, and review Status, Details, and How to fix it.
- Message-trace data can take from 10 minutes to one hour to appear. Wait one hour before concluding that there is no trace entry. ^4^
Interpret the result as follows:
- Failed/Rejected: open the details and apply the listed policy, connector, or recipient-domain correction.
- Pending/Deferred: review the stated delay reason.
- Delivered: Exchange Online transferred the message successfully; investigate the receiving system.
- No result after one hour: the message likely was not submitted to Exchange Online. Recheck the Outlook on the web From configuration above, then run the Microsoft 365 Email delivery troubleshooter described in the same admin guidance.
- Multiple users affected: in the Microsoft 365 admin center, open Health > Service health and check Exchange Online for an active incident. ^4^
References