Sending, receiving, and organizing email in Outlook on the web for business
A Microsoft 365 administrator must secure the affected mailbox and then unblock it under Microsoft Defender → Email & collaboration → Review → Restricted entities.
This message normally corresponds to 550 5.1.8 Access denied, bad outbound sender, which Exchange Online returns when an account has exceeded outbound sending limits and is restricted from sending. It is not a Gmail safe-sender or Outlook Web browser issue.^1^
If you are the Microsoft 365 administrator
- Secure the account before unblocking it
- Review Sent Items and Deleted Items for messages the user did not send.
- Check for unknown Inbox rules or forwarding addresses.
- Reset the password, revoke active sessions, and remove unfamiliar authentication methods or application access.
- Enable multifactor authentication if it is not already enabled.
- Review the restriction
- Open the Microsoft Defender portal.
- Go to Email & collaboration → Review → Restricted entities.
- Find the affected mailbox. Its Entity value should be Mailbox.
- Select it and choose Unblock.
- Complete the Unblock user wizard
- Review the recommendations.
- Confirm the account has been secured.
- Select Next → Submit → Yes.
Administrators can alternatively verify and remove the restriction through Exchange Online PowerShell:
# List restricted senders
Get-BlockedSenderAddress
# Inspect the affected mailbox
Get-BlockedSenderAddress -SenderAddress [Email] |
Format-List
# Run only after the account has been secured
Remove-BlockedSenderAddress -SenderAddress [Email]
If you are not the administrator
- Change the mailbox password immediately if you notice unfamiliar sent messages, rules, forwarding, or sign-ins.
- Send the complete delivery-failure report to your organization’s IT or Microsoft 365 administrator.
- Ask them to check your mailbox on the Restricted entities page and unblock it after completing the security review.
Do not repeatedly resend the message or ask the Gmail recipient to add you as a safe sender; this rejection occurs on the Microsoft 365 sending side before normal recipient spam handling.
If the mailbox is not listed under Restricted entities, the administrator should inspect the complete Diagnostic information for administrators section of the bounce message. A different SMTP code requires a different remediation; the procedure above specifically applies to the unrecognized-sender/550 5.1.8 failure.
References