Skip to content
Microsoft (Outlook.com and Microsoft 365) · temporary error

4.7.850–899: temporary restriction on the sending IP

Microsoft 365 detected suspicious activity on the sending IP and is restricting it temporarily while it evaluates the traffic.

Microsoft
Provider
Temporary (4xx)
Class
Sources checked
Author

At a glance

Code
4.7.850–899
Temporary or permanent
TemporaryThe sending server keeps the message and tries again later.
Who has to act
The sender. The fix is on the sending side: your domain, your server or your list.
What the server says
4.7.850 Access denied, please try again later

What it means

Microsoft documents codes from 4.7.850 to 4.7.899 for a temporary restriction placed on the connecting IP address after suspicious activity was seen from it. Like the 4.7.500 range, it is a deferral: the message stays in the sender's queue and is retried. Microsoft says that if the activity is valid the restriction is lifted shortly. Where the 4.7.500 to 4.7.699 range is described in terms of sending patterns, this range is described in terms of the IP itself, so check what else uses that address.

Common causes

  • The IP address sent traffic that Microsoft judged suspicious, such as a sudden burst or a spam-like pattern.
  • Another sender on the same shared IP produced the suspicious traffic.
  • A compromised account or server is sending from the IP.

How to fix it

  1. 01Let the server keep retrying at a normal pace; the deferral is temporary.
  2. 02Check the IP for unexpected traffic, such as a compromised mailbox or an open relay, and stop it.
  3. 03If deferrals continue for days, check the IP on public blacklists and review recent volume and content sent from it.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 451 4.7.500–699Temporary IP throttling.Microsoft 365 is deferring mail from the sending IP because its traffic changed sharply; the restriction lifts once the traffic looks legitimate.MicrosoftTemporary

Further reading

All 111 Microsoft codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer