---
title: "Outlook 550 5.7.x tenant rejections: causes and fixes"
description: "Fix Outlook 550 5.7.705, 5.7.708 and 5.7.233 tenant rejections, and see how Smartlead pauses or blocks warmup on your Outlook mailboxes."
url: https://helpcenter.smartlead.ai/en/articles/411-outlook-550-57x-tenant-rejections-causes-and-fixes
collection: "Email Deliverability"
updated: 2026-11-17
language: en
---

# Outlook 550 5.7.x tenant rejections: causes and fixes

Fix Outlook 550 5.7.705, 5.7.708 and 5.7.233 tenant rejections, and see how Smartlead pauses or blocks warmup on your Outlook mailboxes.

When you send from a Microsoft 365 mailbox, Microsoft can reject mail with a `550 5.7.x` code. Some of these codes mean Microsoft has limited or restricted your whole tenant, not just one email.

This article covers the tenant codes Smartlead reacts to. For any other code, read the full bounce message to see the receiving provider's reason.

## Common causes and fixes

### 550 5.7.708: traffic not accepted from this IP

Microsoft blocks outgoing mail because the sending IP has a low reputation. This is common on new and trial Microsoft 365 tenants.

1.  Your Microsoft 365 admin opens a support request with Microsoft and asks for an exception for the tenant.
    
2.  Once Microsoft lifts the block, reconnect the mailbox in Smartlead. Open it and click **Reactivate Account** under **Attention Required**.
    
3.  Unblock warmup, as described below.
    

### 550 5.7.705: access denied, tenant restricted

**This is a reputation block, not a volume limit.** Microsoft has restricted your tenant. Sending less will not clear it.

1.  Your Microsoft 365 admin clears the restriction. They can check restricted entities in Microsoft Defender, or open a support request with Microsoft.
    
2.  Reconnect any disconnected mailboxes with **Reactivate Account**.
    
3.  Unblock warmup, as described below.
    

### 550 5.7.233 or 5.7.232: tenant sending limit reached

These codes mean your tenant hit Microsoft's recipient limits for the day. Warmup emails count toward these limits.

1.  Wait for Microsoft's limit to reset. Smartlead pauses warmup for you, so you don't need to do anything in Smartlead.
    
2.  If it keeps happening, use fewer warmup mailboxes on the same tenant.
    

## How Smartlead reacts on warmup

Smartlead reacts per sending domain, and only for Outlook mailboxes. Gmail and SMTP mailboxes on the same domain are not affected.

-   **5.7.233 or 5.7.232:** warmup pauses on every Outlook mailbox on that domain for 24 hours, then resumes.
    
-   **5.7.705 or 5.7.708:** warmup is blocked on every Outlook mailbox on that domain until you unblock it.
    

To unblock warmup after your admin has fixed the tenant:

1.  Open the mailbox and go to **Warm Up**.
    
2.  Click **Generate Intell-Unblock Code**.
    

You can also click **Fix now** on the banner, then **Validate mailboxes**.

Still stuck? Contact support from the chat in your Smartlead dashboard. Include the mailbox address, the campaign ID and the full error text.

## Related articles

-   [Outlook Tenant error (550 5.7.708 Access denied)](https://helpcenter.smartlead.ai/en/articles/81.md)
    
-   [What Are Sender Bounces, Why Do They Happen, and How Can You Reduce Them?](https://helpcenter.smartlead.ai/en/articles/458.md)
    
-   [Understanding Email Account Disconnection Reasons in Smartlead](https://helpcenter.smartlead.ai/en/articles/65.md)
