CSE - Legacy Configuration Notice message due to PoP Limit.

This KB article explains why the Legacy Configuration Notice appears and how to remove additional PoPs in a Global Edge environment when a SonicWall firewall is used as a connector.

Note that the recent CSE release (April 17, 2026) introduced a new maximum limit of 4 Global Edge PoPs.

For additional details, refer to the official Release Notes:

https://www.sonicwall.com/support/technical-documentation/docs/cse/release-notes

What is PoP (Points of Presence)?

Cloud Secure Edge (CSE) uses PoP’s to streamline users’ connections to resources while helping admins maintain control over data residency. In the CSE ecosystem, a PoP is essentially a CSE-managed Access Tier: while Access Tiers are self-hosted in Private Edge deployments, PoPs are fully hosted and maintained by CSE in a Global Edge deployment.

NOTE: The PoP selection feature is only available for Global Edge deployments in orgs created after the March 2026 release. PoP editing is available for all orgs.

For additional details, refer to below link:

https://cse-docs.sonicwall.com/docs/banyan-components/edge-network/managing-pops/

If you see the Legacy Configuration Notice in your CSE console, it indicates that your CSE tenant is using more PoPs than the newly enforced limit.

To clear the notice, you must take one of the following actions:

Option A – Reduce to 4 PoPs

Remove the additional PoPs directly from the CSE console. (Please continue with the steps outlined in this KB article.)

Option B – Request a Higher PoP Limit

If more than 4 PoPs are required because you have end users distributed across multiple geographic locations, you may request an increase by using one of the following options:

• Need More → Submit Request in the CSE console

The requests will be reviewed on a case-by-case basis based on user quantities, location of private resources and user locations.

How to Remove Additional PoPs?

IMPORTANT: Connected users may experience a brief service disruption. Clients will need to reconnect.

You can edit or remove PoPs directly from your CSE console:

1. Go to CSE Console | Networks | Access Tiers & PoPs | Manage Access  
2. Select Edit Global Edge Points of Presence.
3. Choose the 4 PoPs you WANT TO KEEP (typically the closest to your primary geo‑locations).
4. A warning about possible user disconnection will appear → select Yes, Disconnect. 

      5.Wait a few minutes for the CSE console and firewall to synchronize.

      6. CSE console and the Sonicwall firewall must reflect same tunnels. If the firewall does not reflect the updated PoP list, you can manually synchronize it from firewall: Firewall UI | Network | Cloud Secure Edge | Access Settings | Synchronize CSE

Additional Frequent Questions:

How long will customers have to edit or remove the additional PoPs?

There is no hard deadline right now. When we decide on one, we will notify customers in console, via release notes and other means at least 6 weeks ahead of time.

What is the best‑practice recommendation for removing additional PoPs?

SPA PoPs should be closest to the private resource locations for optimal routing.  

SIA PoPs are separate and are distributed globally, this selection does not affect those.