How to set up a proxy in Microsoft Edge

Routing Microsoft Edge through a proxy is straightforward, but there's one thing to understand up front that saves a lot of confusion: Edge doesn't have its own independent proxy settings the way some browsers do. Because it's built on Chromium and ships with Windows, it uses the system proxy settings by default — so configuring "Edge's proxy" usually means configuring Windows. Here's how to do it cleanly, plus the command-line flags for when you need per-launch control.

Step 1 — Open the proxy settings

The fastest route is through Edge itself, which links straight to the Windows settings:

1. Open Edge Settings.
2. Type proxy in the settings search bar.
3. Open the proxy configuration entry — it takes you to Windows' proxy settings (the same panel as Windows Settings → Network & Internet → Proxy).

Step 2 — Enter the proxy

In the manual proxy section:

1. Turn on Use a proxy server.
2. Enter the IP address and port of your proxy.
3. Add any addresses that should bypass the proxy, if needed.
4. Save.

That's the whole manual setup. Because this is a system-level setting, it applies to Edge and to any other application that follows Windows' proxy configuration — not just one browser. Keep that in mind: you're configuring the system, and Edge inherits it.

Per-launch control with command-line flags

For finer or temporary control — testing, or running an instance with different settings — Edge accepts Chromium's proxy flags at launch (run msedge.exe with the flag). The useful ones:

• --proxy-server=<scheme>=<host:port> — route traffic through the specified proxy, e.g. --proxy-server="https=127.0.0.1:8080" or a plain host:port. Use --proxy-server="direct://" to force a direct connection.
• --no-proxy-server — disable the proxy entirely, overriding other proxy flags.
• --proxy-auto-detect — auto-detect the configuration (ignored if --proxy-server is set).
• --proxy-bypass-list="<host>;<host>;…" — list hosts that should skip the proxy; used together with --proxy-server.

These affect the launched instance and are handy when you don't want to change the system-wide setting just to test something.

Step 3 — Verify it works

Once set, open any site. If your proxy requires authentication, you'll get a prompt for a username and password — these are the credentials issued with the proxy (with a dedicated proxy, that's the login tied to your address). Enter them and the page loads through the proxy. To confirm the address the world now sees, check your IP on any "what is my IP" service and make sure it shows the proxy's location, not your own.

A few practical notes

• Because Edge follows Windows settings, the manual configuration applies to every app using the system proxy, not Edge alone. Use the command-line flags when you want an isolated change.
• If you also run a VPN, mind the order: traffic typically hits the proxy first, then the VPN. Test the combination — chaining them incorrectly can leak or break the connection.
• SOCKS proxies with authentication can be unreliable through the Windows system settings; if a SOCKS5 login won't hold, that's a known rough edge.
• Skip free public proxies — they're slow, often already blocked, and can leak your data. A clean, dedicated address is the difference between "it sort of works" and "it just works."

For a stable setup that holds up day to day, a dedicated static IPv4 or ISP proxy gives Edge a predictable, clean origin — HTTP and SOCKS5 on one port, with credentials that stay yours. Configure it once in Windows, verify the IP, and you're set.