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.
A "451 4.7.500-699 (ASxxx)" bounce is Microsoft 365 anti-spam filtering applying what Microsoft calls IP throttling to mail from a sending server. Microsoft says you get it because the source email server (the connecting IP address) changed its previous sending pattern by sending a much higher volume of messages than in the past. Microsoft calls the behaviour IP throttling.
Microsoft's dividing line is whether your organisation uses the built-in security features for all cloud mailboxes. If it does, an email admin can fix this with a connector. If it does not, for example because you use a third-party service, Microsoft says the error resolves itself as you establish a sending history over a period of a few days.
What the error means
Microsoft describes this code as part of anti-spam filtering in Microsoft 365 or Office 365. You get the error when the source IP address that is sending you mail changes significantly from its previously established patterns. It is part of a technique called graylisting: when new senders appear, they are treated more suspiciously than senders with an established history of sending mail. Microsoft likens it to a probation period.
The number after 4.7. is a range, 500 to 699, and the code ends in ASxxx. Microsoft gives no meaning for individual numbers, so do not try to decode them. Microsoft's own wording is that the error "can help reduce the amount of spam that you receive".
Who sees it depends on the direction. If the NDR is returned for a message you sent, Microsoft's advice depends on your set-up. If your organisation uses the built-in security features for all cloud mailboxes, or the Built-in security add-on for on-premises mailboxes, an email admin can use the connector steps. If you use a third-party service and not the built-in features, the error resolves itself over a period of a few days as you establish a sending history with Microsoft 365.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Your own mail server relays outbound mail through Microsoft 365 without a connector | 451 4.7.5xx on outbound relay after a cut-over or a volume jump | Mail flow, Connectors lists no connector from your email server |
| Inbound mail reaches Microsoft 365 through a third-party filter, appliance or device with no connector | The 451 hits mail from that filter's IP addresses | No connector applies security restrictions for that service |
| A new tenant sending more than test messages from its initial onmicrosoft.com domain | Microsoft says email from onmicrosoft.com domains "is limited and filtered to prevent spam"; Microsoft does not say this produces the 451 code | Domain used is contoso.onmicrosoft.com, and no custom domain is added |
| Genuine volume jump from a sender with no history, outside the built-in security features | An error that Microsoft says resolves itself over a period of a few days | Message counts before and after the change |
Prove the cause before changing anything
Read the bounce first. Keep the whole text, the time, and the ASxxx value. Then check the current connectors in the Exchange admin center under Mail flow, then Connectors. Microsoft's connector page says to check for any connectors already listed for your organisation before setting up a new one, because a hybrid wizard run may already have created them. If a suitable connector already exists, do not create a second one.
Check which domain the mail is sent from. Microsoft says it does not recommend sending more than test messages from your initial onmicrosoft.com domain, because email from onmicrosoft.com domains is limited and filtered to prevent spam, and that in production you need to add a custom domain and then send your regular volume.
Then compare the volume. Count the messages the sending server relayed on a normal day and on the day the bounces started. Your mail server's own log or a message trace from the Exchange admin center will give the counts. Message trace data can take from 10 minutes up to an hour to appear.
Example (illustrative): after a weekend cut-over, mail01.contoso.com.au starts relaying all of Contoso's outbound mail through Microsoft 365. The server used to send around 200 messages a day directly. On Monday it relays 2,600 messages, which is 2,600 / 200 = 13 times the old volume, from an address Microsoft has no history for. Part of the mail bounces with 451 4.7.500-699. No connector exists from mail01 to Microsoft 365.
Fix
Mail you send and relay through Microsoft 365. Microsoft's page says that to remove throttling for these messages you configure a connector. For outbound relay from your own server, you need a connector from your email server to Microsoft 365 or Office 365.
Disruptive step: a new connector changes how Microsoft 365 treats everything sent from that server or those IP addresses, including mail that today works. Check the listed connectors first and write them down. Use the certificate option if you can; Microsoft marks it as recommended, and an IP address entry must list only addresses that belong exclusively to your organisation. Back-out: delete the connector you created. Mail from that server then returns to its earlier treatment.
Microsoft's connectors page describes the steps. In the Exchange admin center go to Mail flow, then Connectors, and select Add a connector. Under Connection from, choose Your organization's email server. Name the connector. Choose how the server authenticates: by the subject name on the certificate it uses, which the page marks as recommended, or by the IP address of the sending server, where the addresses must belong exclusively to your organisation. Check the settings on the summary screen and select Create connector.
Before you build it, Microsoft's prerequisites for the on-premises side apply. The server must be able to send and receive Internet email. It should have Transport Layer Security enabled with a valid certificate authority-signed certificate. Port 25 must be open on your firewall so Microsoft 365 can connect to your email servers, and your firewall must accept connections from the published Microsoft 365 IP address ranges. Make a note of an email address for each domain in your organisation, because you need it later to test that the connector is working properly.
These steps build only the Microsoft 365 side. Microsoft's connectors page has a second part: your own email server must also be set up to relay mail to the internet via Microsoft 365. For Exchange Server the page has you create a Send connector with smart host routing, whose smart host has the form yourdomain-com.mail.protection.outlook.com. Follow that part of Microsoft's page for the server side.
Mail that reaches you through a third-party service. For inbound mail first routed through a third-party service, appliance or device, Microsoft's page says only that you need to set up a connector to apply security restrictions. It gives no direction for that connector and no steps, so take the details from your service's documentation and Microsoft's connectors page.
Disruptive step: applying a connector to a partner service changes filtering for all mail from that service, and Microsoft's connectors page warns that steps meant for your own servers can cause unintended consequences, including email delivery failure, if applied to partner email services. Microsoft's connectors page links a guide to secure mail flow with a partner organisation for those services; read that guide before you build anything, and record the existing connectors first. Back-out: delete the new connector.
New tenants. Microsoft says not to send more than test messages from your initial onmicrosoft.com domain, and that in typical production you add a custom domain and then send your regular volume.
Disruptive step: adding a custom domain changes DNS and, if you accept the records Microsoft offers, mail routing. Microsoft's add-domain page says that after you finish setting up a custom domain, the domain's MX record is updated to point to Microsoft 365 and all email for the domain starts coming to Microsoft 365, and that incorrect DNS records can cause email and service outages. Save-first: the accepted domains list (Get-AcceptedDomain | Format-List | Out-File -FilePath .\accepted-domains-before.txt) and a copy of the domain's current DNS records from your registrar. Add users and mailboxes before any MX change, and do not accept an MX change you do not want. Back-out: Microsoft says that before you remove a domain, make sure the domain is not the default domain, that no users, shared mailboxes, resource mailboxes or contacts use it, and that no Microsoft 365 groups, distribution lists or teams use it. Check your own tenant for each of these; if any user or group uses the domain, move it to another domain first (Microsoft's Step 1 and Step 2), then remove the domain (Microsoft's Step 3). Then restore any DNS records you changed from your saved copy.
After you set up a connector, Microsoft says you can monitor whether IP throttling has stopped.
Confirm the fix
Send a test message from the relaying server and run a message trace to confirm it is delivered. Then watch normal volume across a full business day. If the 451 code keeps appearing for new messages after a day or two, check that the connector matches the server's actual certificate name or IP address, and that the connector is the one that applies to this server rather than an older one that was already in the list. Record what you find before you edit anything.
What to watch afterwards
- Queue length on the relaying server in the first days after any cut-over.
- Any new third-party service placed in front of Microsoft 365, since it needs its own connector.
- Sending volume from a new domain, which should grow rather than jump.
- Bounce codes that change from 451 to 550 5.7.x, which signal a different problem.
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
- Troubleshooting550 5.1.10 RESOLVER.ADR.RecipientNotFound: a Microsoft 365 user can't email a hybrid user whose address existsMicrosoft 365 user gets 550 5.1.10 RESOLVER.ADR.RecipientNotFound sending to a hybrid user? Check the on-premises object and ExchangeGuid, then fix.Read article
- HostingBusiness freeze windows and change blackouts before a migration cutoverHow long to freeze configuration and data changes before cutover, who may approve an exception, and what the freeze is meant to protect — distinct from replication lag and DNS mechanics.Read article
Risks and limits
These steps have not been run or lab-tested in a tenant. They are portal steps and no commands are given. Microsoft's NDR page gives no duration for the throttling and no number for the volume that triggers it, so any threshold here is unknown. It also says nothing about which AS number means what. For organisations that do not use the built-in security features, Microsoft says the error resolves itself over a period of a few days, and it does not say how to speed that up. The connector page is dated 2025-07-28 and its screens can differ in your tenant.
Sources
- Fix NDR error code "451 4.7.500-699 (ASxxx)" in Exchange Online — Microsoft Learn, page dated 2026-08-11, accessed 20 November 2026
- Set up connectors to route mail between Microsoft 365 or Office 365 and your own email servers — Microsoft Learn, page dated 2025-07-28, accessed 20 November 2026
- Add a custom domain to Microsoft 365 — Microsoft Learn, page dated 2026-05-08, accessed 20 November 2026
- Remove a domain from Microsoft 365 — Microsoft Learn, page dated 2026-04-23, accessed 20 November 2026
- Get-AcceptedDomain — Microsoft Learn, date not shown, accessed 20 November 2026
- Find and fix email delivery issues as a Microsoft 365 for business admin — Microsoft Learn, page dated 2025-06-25, accessed 20 November 2026
This article was originally published on .