If the AI steps do not help, please also try:
- Rule out account compromise
- Review your Microsoft account sign-in activity. If you see anything unfamiliar, select “This wasn’t me” and secure the account.
- Then follow Microsoft’s compromised-account guidance to secure the account (change password, review security options).
- Test a “clean” message to see if content/format is triggering the block
- From Outlook.com on the web, send a brand‑new email to a single recipient with: plain text, no signature, no links, no attachments. Switch to plain text format in Outlook.
- If the clean email works, rebuild your normal message gradually
- Add back only one element at a time (signature, then links, then attachments) to identify what triggers the rejection.
- Reduce reputation triggers Microsoft calls out for deliverability
- Avoid sending to many recipients at once, avoid heavy BCC use, and avoid sending repeatedly to recipients who don’t engage. Ask recipients to add your address to their Safe Senders list. See: Sender Support in Outlook.com - Microsoft Support
If you still get 550 5.7.520 even with the plain‑text, no‑link, no‑attachment, single‑recipient test, reply with the single diagnostic line from the bounce, with all email addresses removed, so the block type can be identified precisely.
Please tell me how it goes. If the problem persists, please don’t hesitate to reply to this thread and I will be happy to help. Have a lovely day!
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.