How to Setup Proxy Settings in Microsoft Edge in 2026
TL;DR
Microsoft Edge has no independent proxy stack on desktop; its network layer reads the OS proxy settings by default.
SOCKS5 in Edge supports no authentication at all, so a username-and-password SOCKS5 endpoint cannot work — use the HTTP endpoint instead.
Edge ignores credentials embedded in proxy settings, so user:pass@host silently fails; authentication comes through Edge's own prompt.
An HTTPS-scheme proxy cannot be set through Windows or macOS settings; it needs a command-line switch, PAC file, extension, or policy.
Enabling the ProxySettings policy makes Edge ignore every proxy-related command-line option, which is why --proxy-server does nothing on managed machines.
HTTP/1.1 proxies in Edge are capped at 32 simultaneous connections across all domains, so a "slow proxy" is sometimes a connection ceiling.
What Is an Edge Proxy Setting and Why Would You Need One?
An Edge proxy setting is the configuration that tells Microsoft Edge to send requests through an intermediary server, so sites see that server's IP instead of yours. The wrinkle specific to Edge is that most of the time you are not configuring Edge at all — you are configuring Windows or macOS, and Edge inherits it.
Four reasons drive this search: checking how a page or ad renders in another region, reaching an internal service behind a corporate gateway, testing traffic through a debugging proxy, and separating one browser's traffic from the rest of the machine. That last one is where the default disappoints, because a system proxy is not browser-scoped.
Take a Quick Look
Edge rejects credentials embedded in a proxy URL and supports no authentication on SOCKS5, so a gateway speaking plain HTTP with Basic auth is what actually works here — Nstdata's HTTP/HTTPS endpoints drop straight into the fields below.
Five things, and missing the last one causes most failed attempts.
Host and port — the gateway address your provider issues. If you are unsure where these live, finding your proxy server address varies by provider.
Username and password — kept separate, not pasted into the host field.
The scheme — Edge supports HTTP, HTTPS, SOCKSv4, SOCKSv5 and DIRECT, and the choice changes what works. Edge accepts Basic, Digest, Negotiate and NTLM authentication on HTTP proxies, and no authentication on SOCKSv4 or SOCKSv5, so a username-and-password plan needs the HTTP or HTTPS endpoint. Version differences are covered in this SOCKS proxy guide.
Administrator rights, but only for the policy method.
One thing you do not need: credentials formatted into the address. Microsoft's Edge proxy support documentation states Edge does not implement cleartext credentials in proxy settings and will not use any embedded there.
How Does Microsoft Edge Actually Handle Proxies?
Microsoft is direct about it: "The Microsoft Edge network stack uses the system network settings by default." Those settings cover the proxy configuration along with the certificate and private key stores.
That default explains three things readers find confusing. Opening Settings → System and performance hands you off to the OS dialog rather than an Edge-owned screen. Any change there applies to every application honouring the system proxy. And an HTTPS-scheme proxy is unavailable through that dialog entirely — Microsoft notes it cannot be specified through system proxy settings, and that a PAC script or an Edge-level setting is required instead.
Two hard limits shape which method you pick. HTTP/1.1 proxies in Edge are capped at 32 simultaneous connections across all domains, while an HTTPS proxy negotiating HTTP/2 gets a higher ceiling. And with SOCKSv5, Edge always resolves names proxy-side with no option to change it — Firefox exposes a preference for this, Edge has no equivalent.
How Do You Set a Proxy in Microsoft Edge?
Four routes work, differing in scope: two configure the whole machine, two configure Edge alone.
Method 1: The System Proxy via Edge Settings
The fastest path, and the one Edge's own UI points at. Machine-wide, not Edge-only.
Step 1: Open the proxy entry from Edge
Open Settings → System and performance and select the option to open your computer's proxy settings. Edge hands off to the OS.
Step 2: Enter the gateway
On Windows, go to Settings → Network & Internet → Proxy, and under Manual proxy setup turn on Use a proxy server. Enter host and port, add any hosts that should stay direct to the exception list, then save.
On macOS: System Settings → Network → Wi-Fi or Ethernet → Details → Proxies, tick the scheme, fill in host and port.
Step 3: Authenticate on first request
Load any site. Edge prompts for the username and password on the first request and caches them for the session.
Step 4: Note what this does not cover
This route cannot express an HTTPS-scheme proxy, and it applies to every app honouring the system proxy. For either, use Method 2.
Method 2: A Command-Line Switch for Edge-Only Routing
Use this when the proxy should apply to Edge and nothing else, or when you need a scheme the OS dialog cannot express.
Step 1: Close every Edge window
Switches apply at launch; a running Edge process will not pick them up.
Step 2: Launch Edge with the proxy switch
Start Edge with --proxy-server set to your gateway. Microsoft's command-line proxy documentation gives three forms: a single endpoint for all traffic (--proxy-server="proxy2:8080"), a per-scheme map (--proxy-server="http=proxy1:8080"), or an explicit URI including the scheme, which is how you reach an HTTPS proxy. Appending ,direct:// makes Edge fall back to a direct connection if the gateway is unreachable rather than failing with ERR_PROXY_CONNECTION_FAILED.
Step 3: Add exceptions if you need them
Pair it with --proxy-bypass-list for hosts that should stay direct; this switch only works alongside --proxy-server. Watch the matching rule — trailing-domain patterns carry no implied dot, so *microsoft.com also matches imicrosoft.com, and you want *.microsoft.com if you meant the subdomain.
Step 4: Know the sibling switches
--no-proxy-server forces a direct connection regardless of system settings, --proxy-pac-url points Edge at a PAC file, and --proxy-auto-detect runs WPAD discovery but is ignored whenever --proxy-server is also present.
Method 3: Using Nstdata Through Edge's HTTP Endpoint
Use this when the proxy needs to present a specific country or a stable residential identity rather than reach an internal gateway.
Step 1: Generate a channel and read the credentials
Create a channel in the Nstdata dashboard and copy the four values it issues: gateway host, port, username, password. Nstdata's proxy documentation lists a global gateway plus regional US, EU and Asia endpoints; pick the nearest, since every request pays that round trip.
Step 2: Choose the HTTP endpoint, not SOCKS5
Select HTTP or HTTPS. Not a preference — Edge supports no authentication on SOCKSv5, so a username-and-password SOCKS5 gateway cannot authenticate in Edge at all.
Step 3: Enter the gateway using Method 1 or Method 2
Put host and port into the Windows or macOS fields, or pass them to --proxy-server to confine routing to Edge. Nstdata encodes session control into the username string — channel, country and session duration are parameters within it — so paste the entire generated username.
Step 4: Let Edge prompt for the password
Load a site and enter the credentials when Edge asks. One real limitation: Nstdata ships no Edge extension, so per-tab switching needs a third-party extension or separate profiles.
Method 4: The ProxySettings Policy for Persistent Configuration
Use this on machines you administer, or when the configuration must survive restarts and resist user changes.
Step 1: Confirm the policy you need
ProxySettings is the current dictionary policy. Microsoft marks the older ProxyMode and ProxyServer policies deprecated, and ProxySettings overrides them. Supported on Windows and macOS from Edge 77, Android from 30, and not supported on iOS.
Step 2: Pick a ProxyMode value
The ProxySettings policy reference defines five: direct never proxies, system inherits the OS setting, auto_detect runs discovery, fixed_servers uses your ProxyServer and exception list, and pac_script uses ProxyPacUrl.
Step 3: Write the policy
On Windows, set ProxySettings as REG_SZ under SOFTWARE\Policies\Microsoft\Edge, or use Administrative Templates → Microsoft Edge → Proxy server. On macOS the preference key has the same name. The value is a JSON dictionary of the fields above.
Step 4: Understand the side effect
Once enabled, Edge ignores all proxy-related command-line options, which makes Method 2 inoperative on that machine. Documented behaviour, not a bug. The policy does apply per profile.
How Do You Confirm It Actually Worked?
Load an IP-reflection service in Edge and compare against the same check in another browser on the same machine.
Success: the reported IP is the gateway's, the country matches the region you selected, and the page loads without a repeated credential prompt. Failure has three distinct signatures — your own IP still showing means the proxy is not applying; a prompt that keeps reappearing means authentication is failing rather than routing; ERR_PROXY_CONNECTION_FAILED means Edge found the configuration and could not reach the gateway.
For the command-line and policy routes, edge://net-internals/#proxy shows the configuration Edge actually resolved, which beats inferring it from the OS dialog.
How Do You Turn It Off or Roll It Back?
Each method reverses differently, and reversing the wrong layer leaves the proxy in place.
Method 1: On Windows, switch Use a proxy server off under Settings → Network & Internet → Proxy. On macOS, untick the scheme under Details → Proxies. No restart needed.
Method 2: Close Edge and relaunch normally; nothing persists. To force direct while the system proxy remains configured, launch with --no-proxy-server.
Method 3: Reverse whichever of Method 1 or Method 2 you used. Removing the credentials alone does not stop the routing.
Method 4: Delete the ProxySettings registry value or set the Group Policy object back to Not Configured, then restart Edge. Setting ProxyMode to direct does the same while keeping the policy in place.
Why Isn't It Working?
Most Edge proxy failures come from platform limits rather than typos, so check these before rechecking host and port.
A policy is overriding your command line. Symptom: --proxy-server appears ignored. Cause: the ProxySettings policy is enabled, and Edge then ignores all proxy-related command-line options. Fix: check edge://policy, and configure through the policy instead.
SOCKS5 will not authenticate. Symptom: the gateway never accepts your credentials. Cause: Edge supports no authentication on SOCKSv5 or SOCKSv4. Fix: switch to the HTTP or HTTPS endpoint, or use IP allowlisting.
Credentials in the address are ignored. Symptom: you entered user:pass@host:port and Edge still prompts. Cause: Edge does not use credentials embedded in proxy settings. Fix: enter host and port only.
An HTTPS proxy will not save. Symptom: nowhere to enter one in the OS dialog. Cause: that scheme cannot be specified through system proxy settings. Fix: use --proxy-server with an explicit https:// URI, a PAC script, an extension, or policy.
Throughput collapses under load. Symptom: many tabs or parallel requests crawl. Cause: HTTP/1.1 proxies in Edge are limited to 32 simultaneous connections across all domains. Fix: use an HTTPS proxy that can negotiate HTTP/2.
Localhost refuses to route. Symptom: localhost requests go direct regardless. Cause: Edge applies implicit exception rules to localhost names and link-local addresses. Fix: add the <-loopback> rule, accepting the security implications.
Which Option Should You Choose?
Match the method to the scope you need rather than to how advanced it looks.
One machine, one proxy, occasional use → the system proxy through Edge Settings.
Edge only, other apps direct → a command-line switch. The only no-install way to keep routing browser-scoped, and the way to reach an HTTPS-scheme proxy.
Frequent switching between endpoints → a proxy extension from the Edge Add-ons store, which gives per-tab switching the native dialog cannot.
Fleet or long-lived configuration → the ProxySettings policy. Survives restarts, works per profile, disables the command-line route.
Needing a specific country or residential identity → a commercial gateway over HTTP/HTTPS. Nstdata's Residential Prime offers country, city and ASN filtering, Static ISP a fixed address billed per IP, Mobile carrier IPs. Per GB on traffic-based lines, per IP on Static ISP.
Just wanting encryption on public Wi-Fi → Edge Secure Network, not a proxy.
What Limits and Rules Should You Know First?
Edge's proxy support has gaps no configuration closes.
SOCKSv5 relays TCP only and cannot carry UDP. SOCKSv4 additionally cannot reach IPv6 targets, and Edge neither supports SOCKSv4a nor falls back to it. Exception rules specifying IP ranges apply only to URLs that are literal IP addresses, not hostnames resolving into that range — Microsoft calls their usefulness rather limited and points to a PAC script instead. ProxySettings is unsupported on iOS; Edge Secure Network is unavailable on managed devices.
Anything routed through a third-party proxy is visible to that operator to the extent the scheme allows: an HTTP proxy sees the target hostname in the clear even when tunnelling HTTPS through CONNECT, whereas an HTTPS proxy protects it because CONNECT itself travels over TLS. And a proxy changes network origin and nothing else — not your fingerprint, your signed-in account, or your behaviour.
So What's the Fastest Path From Here?
Decide on scope first, because that one choice picks the method. Whole machine and HTTP only: use the system proxy through Edge Settings and let Edge prompt for credentials. Edge alone, or an HTTPS-scheme endpoint: launch with --proxy-server. Administered machine or persistence required: write the ProxySettings policy. Whichever you pick, choose the HTTP endpoint over SOCKS5 whenever authentication is by username and password, verify the exit IP before trusting the setup, and check edge://policy first if a switch appears to be ignored.
Q: Does Microsoft Edge have its own proxy settings?
Not on desktop. Edge's network stack uses the system network settings by default, so the proxy entry in Edge Settings opens the Windows or macOS dialog rather than an Edge-owned screen. Edge-scoped configuration is possible only through a command-line switch, an extension, or the ProxySettings policy.
Q: Does Microsoft Edge support SOCKS5 proxies?
Yes for routing, no for authentication. Edge supports the SOCKSv5 scheme, but Microsoft documents that no authentication methods are supported for SOCKSv5 in Edge, so a gateway requiring a username and password will not work. Use the HTTP or HTTPS endpoint, or IP allowlisting if your provider supports it.
Q: Why does Edge ignore the username and password in my proxy address?
Because Edge does not implement cleartext credentials in proxy settings and will not use credentials embedded there. Enter only host and port, then supply the username and password when Edge prompts on the first request.
Q: Why is my --proxy-server switch being ignored?
Almost always because the ProxySettings policy is enabled on that machine, which makes Edge ignore all proxy-related command-line options. Check edge://policy for a ProxySettings entry; if one exists, change the proxy through the policy instead.
Q: Is Edge Secure Network the same as setting a proxy?
No. Edge Secure Network routes selected traffic through an encrypted Cloudflare tunnel, capped at 5 GB per month with a personal Microsoft account, with streaming sites excluded by default and no availability on managed devices. It gives you no control over exit location or scheme.
Q: How do I set a proxy in Edge on Android or iOS?
On Android, Edge follows the device's Wi-Fi proxy settings, and the ProxySettings policy is supported from Edge 30 on managed devices. On iOS that policy is not supported at all, leaving only the network-level configuration iOS itself provides.
Neo Maxwell
Sep. 9th 2026
Experience Nstdata - Start Your Free Trial Today
110M+ real IPs with 99.9% access success
Get immediate access to premium residential, datacenter, IPv6 and ISP proxy pools.
Blazing-fast average response ~0.5s for high-concurrency tasks
