About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
One person cannot send email, and their bounce ends "Remote Server returned '550 5.1.8 Access denied, bad outbound sender." Microsoft 365 has restricted that user from sending, because the account exceeded the service's outbound limits or the limits in an outbound spam policy. The user can still receive mail. The account sits on the Restricted entities page in the Microsoft Defender portal, and only an admin can remove it.
Do not just unblock. Microsoft says a sender exceeding the limits is an indicator of a compromised account, and the documented order is to regain control of the account first.
What the error means
Microsoft describes a restricted entity as a user account or a connector that is blocked from sending email due to indications of compromise, which includes exceeding message receiving and sending limits. When a user is restricted, three things happen: they cannot send but can still receive, they are added to the Restricted entities page, and a message they try to send returns the NDR with this text:
"Your message couldn't be delivered because you weren't recognized as a valid sender. The most common reason for this is that your email address is suspected of sending spam and it's no longer allowed to send email. Contact your email admin for assistance. Remote Server returned '550 5.1.8 Access denied, bad outbound sender."
The limits are in Microsoft's sending-limits page. Per user: 10,000 recipients per day, as a 24-hour sliding window, and 30 messages per minute, which Microsoft calls hard limits enforced at service level that cannot be increased. One message may have 500 recipients by default, customisable from 1 to 1,000. In outbound spam policies an admin can also set an external recipients per hour limit, an internal one and a daily limit, each from 0 to 10,000, where 0 means the service default.
When a limit is reached, the policy action decides what follows: Restrict the user from sending mail until the following day, Restrict the user from sending mail, or alert only. "Restrict the user from sending mail" puts the user on the Restricted users list until an admin removes them.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Account compromised and used to send spam | 5.1.8 plus alert User restricted from sending email; unknown rules, forwarding or sent items | Sign-in logs, Inbox rules, sent items |
| Legitimate bulk send over the limits | The user ran a mailing; counts exceed 10,000 recipients a day or the policy limit | Message trace and the user's own account of what they sent |
| Outbound spam policy limits set low with the restrict action | Block after a modest send | Policy values for the user in the Anti-spam outbound policy |
| A different code for a tenant-wide limit | 550 5.7.233 for everyone sending externally | That is the tenant external recipient limit, not a single restricted user |
Prove the cause before changing anything
Read, do not unblock yet. List who is restricted. In Exchange Online PowerShell:
Get-BlockedSenderAddress
Then look at one user. Replace the address with the user's UPN for a hosted mailbox:
Get-BlockedSenderAddress -SenderAddress "a.nguyen@contoso.com.au" | Format-List
In the Defender portal the same list is the Restricted entities page (https://security.microsoft.com/restrictedentities). Microsoft also recommends running the Blocked Sender History self-help diagnostic before you unblock, which shows listing and delisting history and the sender's MFA status.
Check the signs of compromise that Microsoft lists: missing or deleted email, Inbox rules that forward to unknown addresses or move messages to unusual folders such as Notes, Junk Email or RSS Subscriptions, odd items in Sent Items, changes to the user's Global Address List entry, unexplained password changes or lockouts, newly added external forwarding, and strange signatures.
Two read-only commands from Microsoft's compromised-account page check for forwarding and hidden Inbox rules:
Get-Mailbox -Identity a.nguyen@contoso.com.au | Format-List Forwarding*Address,DeliverTo*
Get-InboxRule -Mailbox a.nguyen@contoso.com.au -IncludeHidden | Format-List Name,Enabled,RedirectTo,Forward*,Identity
A nonblank ForwardingSmtpAddress means mail is being forwarded to an external recipient. A nonblank RedirectTo or ForwardTo on a rule needs an explanation from the user.
Example (illustrative): Ana Nguyen at contoso.com.au sends a customer newsletter in two batches, 4,200 recipients in the morning and 6,000 in the afternoon. The total is 4,200 + 6,000 = 10,200 recipients in 24 hours, which is 200 over the 10,000 limit. The second batch trips the limit and she appears on the Restricted entities page. Her sign-in history, rules and sent items show nothing odd, so the cause is the volume, not compromise.
Fix
Step 1: if there is any sign of compromise, regain control first. Microsoft's page on responding to a compromised account says to disable the account during the investigation, or at least reset the password with a strong value that is not sent by email, revoke active sessions, check MFA devices, app consents and admin roles, and remove any forwarding the attacker added. First save the account state. In PowerShell, install the Microsoft Graph module if needed (Install-Module -Name Microsoft.Graph -Scope CurrentUser), then connect and find the user, using the commands on Microsoft's compromised-account page:
Connect-MgGraph -Scopes "User.ReadWrite.All"
$user = Get-MgUser -Search UserPrincipalName:'a.nguyen@contoso.com.au' -ConsistencyLevel Eventual
Get-MgUser -UserId $user.Id -Property Id,UserPrincipalName,AccountEnabled | Format-List Id,UserPrincipalName,AccountEnabled | Out-File -FilePath .\a.nguyen-account-before.txt
The -Property part is there because Microsoft's AccountEnabled property description says it "Requires $select to retrieve". Keep the file.
Disruptive step: disabling the account signs the user out and stops their access to mail until you enable it again. Save-first: the file a.nguyen-account-before.txt from the read above. Back-out for the account step: once the investigation is complete, reset the password and then enable the account again. Microsoft's page says to "reset the password and then enable the account as described in Step 1: Disable the affected user account", but it prints only the disable command, and the Update-MgUser reference shows no example that turns the setting back on. So the restore target is the value in the saved file a.nguyen-account-before.txt (AccountEnabled was True before you started): set the account's enabled setting back to that value through the admin tool your organisation uses for user accounts, and check the result with the same Get-MgUser -Property Id,UserPrincipalName,AccountEnabled read. The old password is not restored and is not meant to be: give the user the new password through a channel other than email, because the attacker could have access to the mailbox.
To disable the account, Microsoft's page gives:
Update-MgUser -UserId $user.Id -AccountEnabled $false
Save first for the session step: run Get-ExecutionPolicy and note the value.
Disruptive step: the session step changes the PowerShell script policy on that computer with Set-ExecutionPolicy RemoteSigned, and revoking sessions signs the user out everywhere until they sign in again. Revoking sessions cannot be undone, but the user signs in again with their credentials.
For the session step, the page first has you run Set-ExecutionPolicy RemoteSigned in an elevated PowerShell window. To undo the policy change, run Set-ExecutionPolicy followed by the value you noted.
After that the page has you install Microsoft.Graph.Authentication and Microsoft.Graph.Users.Actions if necessary, then connect with the revoke scope and run the revoke command:
Connect-MgGraph -Scopes User.RevokeSessions.All
Revoke-MgUserSignInSession -UserId a.nguyen@contoso.com.au
The command invalidates active sign-in sessions and refresh tokens.
Step 2: remove the restriction.
Save first: save the output of Get-BlockedSenderAddress -SenderAddress "a.nguyen@contoso.com.au" | Format-List | Out-File -FilePath .\a.nguyen-blocked-before.txt.
Risk: the portal steps below, and the PowerShell command after them, remove the restriction on that user. Microsoft says that under most circumstances all restrictions should be removed from the user within one hour. If the account is still compromised, spam resumes and the same restriction returns. Microsoft says that for the Restrict action, after an admin removes the user the person will not be restricted again for that day, so a second block may not appear until the next day.
In the Defender portal, go to Restricted entities, select the user (Entity is Mailbox), then Unblock. Read the Overview and its Recommendations, select Next, use the links to enable MFA and reset the password if not done, then Submit and confirm Yes.
The PowerShell form of the unblock:
Remove-BlockedSenderAddress -SenderAddress "a.nguyen@contoso.com.au"
To undo it: the saved file records the entry you removed. If you need to stop the user sending again, disable the account as described in step 1.
Step 3: for a legitimate mailing, change the method. Microsoft says Exchange Online is not designed for bulk mailing and points to services built for it, such as Azure Communication Services Email or non-Microsoft bulk providers, and to SMTP relay through a connector for application mail. If you must send in bulk through Microsoft 365, set up SPF, DKIM and DMARC, keep lists clean and do not exceed 30 messages per minute per mailbox.
Step 4: check alerting. The default alert policy User restricted from sending email notifies the TenantAdmins group (Global Administrator members), and needs audit logging on, which is on by default.
Confirm the fix
Microsoft says all restrictions should be removed from the user within one hour under most circumstances. It adds that transient technical issues might cause a longer wait, but the total wait should be no longer than 24 hours. Ask the user to send a test message, then check a message trace shows it delivered. Run Get-BlockedSenderAddress again and confirm the address is gone.
What to watch afterwards
- Whether the same user appears on the list again. A repeat points to compromise or an unsolved volume problem.
- The alerts Email sending limit exceeded and Suspicious email sending patterns detected.
- The Tenant Outbound External Recipients report, since the tenant has its own daily external limit.
- MFA coverage for all accounts. Microsoft calls enabling MFA a good defence against future compromise.
Read next
Related articles you may want next.
- TroubleshootingExchange Online 550 5.7.708 'Access denied, traffic not accepted from this IP': what it means and how to clear itExchange Online 550 5.7.708 blocks mail from a low-reputation IP, more likely on trial tenants. How to confirm it, and what 5.7.703, 705, 750 mean.Read article
- CloudEntra ID Conditional Access: tenant lockout, break-glass accounts and how to test policy safelyHow Conditional Access locks administrators out, how to build emergency accounts that work under mandatory MFA, and a safe order for testing policy.Read article
- TroubleshootingNot receiving the Microsoft 365 MFA verification code by text message or phone callMFA verification code by text or call not arriving: use another method, check the number format, rate limits, blocks and carrier settings safely.Read article
Risks and limits
These commands have not been run or lab-tested. The Remove-BlockedSenderAddress step has no documented command that puts the entry back. The Update-MgUser and Revoke-MgUserSignInSession steps change the live account, and each has its save-first file and back-out above (a revoked session cannot be restored). Microsoft's pages give the limits as they stand on their dates and they can change, so check the current page. The outbound spam policy page says the restrict action applies after limits are exceeded, but gives no timing for how fast the service restricts a sender. Restricted connectors are not covered here; they have their own removal steps. Neither is the case where the NDR comes from a different tenant.
Sources
- Remove blocked users from the Restricted entities page — Microsoft Learn, page dated 2026-10-30, accessed 20 November 2026
- Troubleshoot outbound sending limits and blocked users in Exchange Online — Microsoft Learn, page dated 2026-05-27, accessed 20 November 2026
- Configure outbound spam policies for cloud mailboxes — Microsoft Learn, page dated 2026-08-10, accessed 20 November 2026
- Respond to a compromised cloud email account — Microsoft Learn, page dated 2026-07-17, accessed 20 November 2026
- Get-MgUser — Microsoft Learn, date not shown, accessed 20 November 2026
- Update-MgUser — Microsoft Learn, date not shown, accessed 20 November 2026
- Out-File — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-BlockedSenderAddress — Microsoft Learn, date not shown, accessed 20 November 2026
This article was originally published on .