Security Policy Errors

How to Fix IP Addresses Not Saving in Exchange Online Connection Filter

Maira Mehtab Oct 22, 2026 868 views

Question details

Users need to resolve an issue where IP addresses fail to save to the Connection Filter Allow List in the Exchange admin center.

Fixing IP Addresses Not Saving in Exchange Online Connection Filter Allow List

Product: Exchange Online
Device & OS: not provided
Scenario: Attempting to whitelist an IP address in the Microsoft 365 Defender or Exchange admin interface.
Observed behavior: IP addresses entered in the web interface disappear immediately after saving, meaning the security policy does not update correctly.

Before you start

Ensure you have the Exchange Administrator role assigned to your account and that you have the latest Exchange Online PowerShell module installed on your computer.

Solution 1Recommended

Update the Connection Filter Policy via Exchange Online PowerShell

Bypassing the web interface and using PowerShell directly ensures the policy changes are forcefully applied to your Exchange tenant.

When the Microsoft 365 Defender or Exchange admin interface fails to commit changes due to synchronization issues, PowerShell offers a direct and reliable way to manage connection filters.

Ensure you use modern authentication with the current Exchange Online module. Legacy Basic Authentication commands are deprecated and may fail.

Open PowerShell

Launch Windows PowerShell on your machine as an Administrator.

Connect to Exchange Online

Run the command 'Connect-ExchangeOnline -UserPrincipalName YOUR_UPN' to authenticate with your administrator credentials using modern authentication.

Update the IP Allow List

Use the supported cmdlet for your tenant to add the IP address. For example, use 'Set-HostedConnectionFilterPolicy' to modify your specific policy's allowed IP addresses.

Verify the Changes

Confirm that your IP address was successfully saved by running the 'Get-HostedConnectionFilterPolicy' command and checking the allow list output.

Update the Connection Filter Policy via Exchange Online PowerShell

Security Warning: Never share your credentials or confidential tenant information when running scripts or seeking support online. Always avoid using Basic Authentication parameters like '-Authentication Basic'.

Free Microsoft Office alternative

Document Your IT Configurations with WPS Office

While resolving Exchange Online security policy errors, it is essential to keep track of your PowerShell scripts, tenant configurations, and troubleshooting steps. WPS Office provides a free, lightweight, and highly compatible alternative to Microsoft Office, allowing you to seamlessly manage your IT documentation.

1. Download the Installer: Visit the official WPS Office website and click the free download button.
2. Install the Software: Run the setup file and follow the straightforward on-screen instructions.
3. Create Documentation: Open WPS Writer to quickly draft and save your IT administrative guides and PowerShell reference documents.

High compatibility with Microsoft Word, Excel, and PowerPoint formats for seamless document sharing.Lightweight architecture ensures fast startup even on older administrative workstations.Familiar user interface requires no retraining for IT professionals.Completely free access to core editing tools to safely log your server configurations and PowerShell scripts.

microsoft office alternative - wps office

Frequently Asked Questions

Why do IP addresses disappear from the Exchange admin center after saving?

This usually happens due to web interface synchronization delays, browser caching issues, or the user account lacking the necessary Exchange Administrator permissions to commit the policy changes.

Which administrator role is required to modify the connection filter policy?

You must be assigned the Exchange Administrator or Global Administrator role in Microsoft 365 to successfully view and modify connection filter policies.

How can I verify if my IP address was successfully added to the allow list?

You can verify your current configuration by connecting to Exchange Online PowerShell and running the 'Get-HostedConnectionFilterPolicy' cmdlet. This will display the active IP allow list for your tenant.

Should I use Basic Authentication to connect to Exchange Online PowerShell?

No. Microsoft has deprecated Basic Authentication for Exchange Online to improve security. Always use modern authentication methods with the latest Exchange Online PowerShell V2 (EXO V2) or V3 module.

Microsoft Office Security Issues