Using Outlook for iOS in business environments for email and scheduling
For outgoing email bounces in Microsoft 365, use this order to isolate the cause:
- Check whether the problem is only in Outlook or the local mail app.
- Sign in to Outlook on the web and test sending from there.
- If mail works in Outlook on the web but not in the installed app, the issue is likely the local Outlook profile or app rather than Exchange Online.
- Run Microsoft Support and Recovery Assistant on the affected computer.
- This is recommended as a first troubleshooting step for Outlook or Microsoft 365 issues affecting a single user.
- It can detect and help fix Outlook profile, account, and related client issues.
- It is not available for new Outlook for Windows.
- If admin access is available, check Microsoft 365 service health.
- In Microsoft 365 admin center: Admin > Service health > View the service health.
- If Exchange Online is degraded, outbound delivery can be delayed and no separate service request is needed while the incident is active.
- Run the email delivery troubleshooter.
- In Microsoft 365 admin center, launch Diag: Troubleshoot Email Delivery.
- Enter the sender and recipient addresses and run the tests.
- This requires a Microsoft 365 administrator account.
- It is not available for Microsoft 365 Government, Microsoft 365 operated by 21Vianet, or Microsoft 365 Germany.
- Run a message trace for a failed message.
- In Exchange admin center: mail flow > message trace.
- For Microsoft 365 Small Business admin: Admin > Service settings > Email, calendar, and contacts > Email troubleshooting > Troubleshoot message delivery.
- Message trace is the main tool to confirm what happened to a specific outbound message and whether it was delivered, delayed, or failed.
- If the bounce message is 550 5.7.23, check SPF configuration.
- Verify the SPF DNS record for the domain.
- Provision all owned domains.
- Add any on-premises sending IPs to the SPF record if mail is sent for those domains through Microsoft 365 or Office 365.
- Check whether the outbound message was identified as spam and routed through the High Risk Delivery Pool. If it was incorrectly detected as spam, contact support.
What information is needed to determine the cause:
- The full non-delivery report or bounce message.
- The exact error code, especially anything like 550 5.7.23.
- The sender and recipient addresses used in the failed test.
- Whether the message fails from Outlook on the web, desktop Outlook, or both.
- The approximate time the failed message was sent, so it can be checked in message trace.
A practical first path is:
- Test in Outlook on the web.
- Run Support and Recovery Assistant if the issue appears user-specific.
- If admin access is available, check Service health.
- Run Diag: Troubleshoot Email Delivery.
- Run message trace on one failed message.
- If the NDR shows 550 5.7.23, review SPF and outbound spam handling.