'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Exchange Hybrid Connector Mail Flow Stopped After IP Change
Question details
Mail flow stops and messages remain queued when an on-premises Exchange server attempts to send mail to Microsoft 365 through a hybrid connector following a public IP address change.
- Product
- Microsoft Exchange
- Device & OS
- not provided
- Scenario
- Modifying or migrating the public IP address of an on-premises Exchange server connected to Microsoft 365.
- Observed behavior
- Messages are not successfully routed to Microsoft 365 and remain queued on the on-premises Exchange server.
Ensure you have Exchange Administrator permissions for both your on-premises environment and Microsoft 365, and verify that your new public IP address is active and successfully propagating globally.
Update Microsoft 365 Connector IP and Settings
The primary fix requires updating your Microsoft 365 inbound connector with the newly assigned public IP address so it recognizes the server as a trusted sender.
When an on-premises Exchange server changes its public IP, Microsoft 365 automatically rejects or queues incoming messages because the new IP address does not match the trusted sender configuration in the existing hybrid connector.
Log in to the Microsoft 365 admin center using your administrator credentials, and navigate to the Exchange admin center (EAC).
In the left-hand navigation pane, click on 'Mail flow' and then select 'Connectors'.
Select the connector responsible for routing mail from your on-premises organization to Microsoft 365. Click 'Edit', navigate to the identifying information section, and replace the old public IP address with the new one.
Review your TLS settings and accepted domains to ensure they are still correct. Save your changes and run the built-in connector validation tool to send a test email and confirm the connection.
Check Firewall Configurations and SMTP Block Lists
If updating the connector does not restore mail flow, external network barriers or IP reputation issues may be preventing communication.
Need a Lightweight Alternative for Office Productivity?
While resolving complex Exchange server and mail flow issues, ensure your team stays productive with WPS Office. It provides a robust, lightweight suite fully compatible with Microsoft Word, Excel, and PowerPoint formats.
- 1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
- 2. Install the Application: Run the installer and follow the on-screen instructions to set up the software.
- 3. Open Your Documents: Launch WPS Office and seamlessly open your existing Word, Excel, or PowerPoint files.
Frequently Asked Questions
How long does it take for mail flow to resume after updating the connector IP?
Once you update and save the new IP address in the Microsoft 365 Exchange admin center, mail flow typically resumes within a few minutes. However, in some cases, it may take up to an hour for the settings to fully propagate across the service.
Why are my Exchange messages still queuing after updating the Microsoft 365 connector?
If messages remain queued, the issue might be outside the connector. Common causes include outdated DNS/SPF records, a local firewall blocking outbound port 25 for the new IP, the on-premises server using an incorrect send connector route, or the new IP address being blacklisted by spam filters.
Can I test the Exchange hybrid connector after changing the IP address?
Yes. In the Microsoft 365 Exchange admin center, you can select the modified inbound connector and use the built-in validation tool. This tool sends a test email to verify that Microsoft 365 can successfully receive traffic from your new on-premises IP address.
