Microsoft 365 sending restrictions

Microsoft 365 error 550 5.1.8: what to do when sending is blocked

“550 5.1.8 Access denied, bad outbound sender” points to a sending restriction that your Microsoft 365 administrator needs to investigate. Keep the full non-delivery report and pause the affected automated sending. Establish and address the cause before asking for the account to be unblocked.

What does Microsoft 365 error 550 5.1.8 mean?
Microsoft associates this error with a user restricted from sending email. The account can still receive messages. The restriction can follow suspected compromise or sending activity that triggers service or outbound-policy controls. It is not proof that a recipient put you on a personal blocked-sender list, and the error alone does not identify the cause.

Microsoft describes the restriction and the administrator’s recovery route in its Restricted entities guidance (opens in a new tab). If unauthorised access or sending is suspected, involve your IT or security provider promptly. A deliverability review does not replace their incident response.

1. Make sure this is the problem you have

Illustrative distinction between sending restrictions and other delivery outcomes
EvidenceWhat it suggestsNext step
An NDR includes 550 5.1.8 and bad outbound senderInvestigate the affected sending user and Microsoft 365 restriction.Give the full report to your sending administrator and check Restricted entities.
The message was sent and found in a customer’s junk folderA placement or recipient-filtering question, not this error by itself.Use the Microsoft 365 spam guide and received evidence.
An NDR reports 550 5.7.711 and a bad inbound connectorA connector restriction, rather than the user restriction covered here.Use Microsoft’s blocked-connector procedure (opens in a new tab).
An NDR reports 550 5.7.233 and a tenant external-recipient limitA tenant-wide recipient control, not simply one blocked user.Check the relevant tenant report and sending-limit guidance (opens in a new tab).
Only one application reports a send failureIts connection, sending route or mailbox may be affected.Compare the application record with the underlying provider’s error.
There is no bounce and the prospect has not repliedDelivery and placement remain unconfirmed.Do not infer an account restriction from silence.

2. Give your administrator a useful evidence pack

Record the failed attempt

  • The complete NDR, including its diagnostic text and the system reporting the failure
  • Affected sending account, intended recipient, timestamp and time zone
  • The application used, such as Outlook, a connected CRM, a sequencer or a relay, and whether other routes fail

Describe the change in behaviour

  • When sending last worked and when the first failure appeared
  • Recent changes to sending volumes, connected tools, account access or automation
  • Whether the administrator can see a matching restricted user, alert or unusual activity

Keep the original report available to the authorised administrator. A cropped screenshot containing only the error number can hide the affected system or additional diagnostic detail. Use an agreed private channel for message evidence and account information, rather than uploading it through a public enquiry form.

3. Investigate and recover through the authorised administrator

  1. Pause the affected activity

    Pause the campaign, sequence or application job producing failed attempts. Do not continue the same sending through replacement accounts while the original restriction remains unexplained.

  2. Match the account to the restriction

    In the Microsoft Defender portal, the administrator checks Restricted entities for the correct user and reviews the associated alerts. They confirm the tenant, account and restriction type before choosing a recovery procedure.

  3. Investigate account activity and sending behaviour

    Review relevant sign-in activity, sending evidence and connected applications. Distinguish an unexpected access or sending event from authorised activity that exceeded a control. Keep the evidence supporting that conclusion.

  4. Address the cause before removing the block

    If compromise is suspected, the security owner follows Microsoft’s account-recovery guidance, including the appropriate account, session, authentication and persistence checks. If authorised sending caused the issue, correct its pattern or configuration with the relevant owner.

  5. Use the supported unblock procedure

    After the required remediation, an administrator with the necessary permissions uses Microsoft’s current Restricted entities procedure. Removing a restriction is a security-sensitive change, so keep the approver, reason and completed checks in the incident or change record.

  6. Verify a limited, controlled return to sending

    Allow for propagation, then test with agreed recipients and check for a fresh NDR or restriction. Confirm the relevant application route separately before resuming an automation.

Use Microsoft’s compromised-account response guidance (opens in a new tab) when the evidence warrants it. A password change alone may not address every session, permission or forwarding change involved. The investigation should be owned by people authorised to secure the environment.

What if the user is not listed in Restricted entities?

Check that the administrator is looking at the correct tenant and sending identity, then obtain a fresh failure with its full diagnostic text. An old NDR is not proof that the current account remains restricted. Confirm whether the failing application uses that mailbox or another sending route.

Restricted connectors and restricted users have different procedures. Microsoft publishes separate blocked-connector guidance (opens in a new tab). Similarly, a tenant-wide sending limit is not resolved merely by unblocking one user.

If the current evidence still points to a restriction but the administrator cannot reconcile it with the account state, preserve the evidence and use the appropriate Microsoft support route. Do not repeatedly change DNS, relax tenant-wide protection or create new senders as trial fixes.

4. Verify sending and inbox placement as separate outcomes

An unblock action is not an immediate end-to-end delivery test. Microsoft says removing a user restriction normally completes within one hour, with transient issues potentially extending the wait to 24 hours. This is Microsoft’s published guidance, not a promised Neotiqa recovery time. Record the removal time and investigate persistent or renewed restrictions rather than repeatedly unblocking the account.

Start with a small agreed test from the affected route and retain its time and outcome. Confirm that the account can submit a message, that the mail system processed it and, where the recipient can confirm, where it arrived. These are separate observations.

If sending resumes but messages reach junk, the immediate restriction may be resolved while a different delivery problem remains. Read why delivered does not always mean inbox. Returning to the same volume, audience and application behaviour without resolving the cause can recreate the original problem.

Illustrative example: Outlook works again but a CRM still fails

A fictional sales team has completed an administrator-led account recovery. A manual Outlook test now succeeds, but the connected CRM reports failures. The next check depends on fresh evidence, not the earlier error alone.

Illustrative branches after account recovery, not client results
Fresh observationWhat it establishesUseful next check
The CRM displays an old failed activityThat an earlier attempt failed, not that a new attempt used the recovered account.Match a new controlled test to its timestamp and sending event.
A new attempt fails at account connectionThe application has a connection problem before delivery.Have its owner check the authorised connection and required permissions.
A new attempt returns 550 5.1.8 againA current sending restriction still needs to be explained.Ask the administrator to review propagation, restriction state and fresh alerts.
The CRM test is accepted but lands in junkSending and placement now need separate analysis.Compare the received headers, message and route with a suitable successful sample.

5. Make the sending workflow fit the provider’s controls

Review the affected mailbox’s combined activity across Outlook, CRM connections and automations. Each application may show only its own share of the workload. Name an owner who can pause sending, investigate alerts and keep the operating instructions current.

Microsoft’s outbound spam protection guidance (opens in a new tab) distinguishes service and policy controls. Standard Microsoft 365 mailboxes are not unrestricted bulk-sending infrastructure. A provider limit is not a recommended campaign target or a promise that every lower-volume pattern is acceptable.

Review how the intended traffic is authorised, targeted and operated. Where a different supported sending service or architecture is needed, scope it properly instead of shifting the same problem between mailboxes. Our outbound infrastructure checklist covers provider fit, ownership and stop conditions.

For application-specific evidence, use the Salesforce sending-route guide or HubSpot delivery guide. Keep mail administration, CRM ownership and campaign operation connected.

Where can Neotiqa help with recurring sending problems?

Your administrator or security provider owns active account recovery. Neotiqa can help with a separately scoped deliverability assessment when the recurring problem spans mailbox controls, connected sales tools and sending practices. The assessment is read-only, with evidence, priorities and a technical handover. Implementation is agreed separately.

We work alongside IT services providers and MSPs, and assess sales-email workflows for B2B SaaS teams and treasury and payments software vendors. A shared customer environment needs clear ownership of the mailbox, application and approved change.

Bring the symptom, affected platforms and a summary of what the administrator has already checked. We can help define the next investigation without asking you to send passwords or confidential message samples through the website.

Questions about error 550 5.1.8 and restricted sending

Can I still receive email if Microsoft blocks me from sending?

Microsoft’s restricted-user guidance says a user restricted in this way can still receive email. That does not establish that every other account function is healthy, so check the actual incident with your administrator.

Does bad outbound sender mean the account was hacked?

Not by itself. The administrator should investigate suspected compromise and the relevant sending or policy controls. The error identifies a sending problem, not a complete explanation of its cause.

Can I unblock my own Microsoft 365 account?

The supported procedure requires the appropriate administrator permissions. An ordinary mailbox user should provide the NDR to their IT provider. The cause needs investigation and remediation before the restriction is removed.

Will changing SPF or DKIM remove a restricted-user block?

It is not a substitute for the restricted-user recovery procedure. Correct authentication where evidence justifies it, but establish the account restriction and its cause with the administrator first.

Should we move the campaign to another mailbox?

Do not use another account to continue the same unexplained activity. Resolve the underlying security, sending-pattern or provider-fit problem, then agree and verify a supported way to resume.

Does Neotiqa provide emergency Microsoft 365 incident response?

This guide is not an emergency response service. Involve your authorised IT or security provider for suspected compromise. Neotiqa’s deliverability investigations and any subsequent implementation are separately scoped and agreed.

Understand why sending restrictions keep returning.

Once your administrator has addressed any active security issue, we can discuss the mailbox, application and sending-workflow evidence behind a recurring problem.