My IT Support Cannot Provide a ProxyMode Exception

Hi, Darian Glover! Thanks for your interest; I'm the original developer of Fiddler and the current owner of the networking area within Edge, so this question is right up my alley.

>Is this a limitation with how policies are managed for Chromium

I'm not sure I understand this question: Your IT admin has configured your system to enforce a "No Proxy" setting, and the browser respects that demand. If they wanted to do so, they could either remove that setting for everyone, or for just you (by targeting you with a different policy configuration). I assume that you're not an Administrator on your PC (since you could just go delete the policy out of the registry each time it is set by the policy agent)

It is a bit odd to have IT Admins force proxy settings to DIRECT (typically, if settings are configured at all, they'll either hardcode a particular proxy or hardcode "system"). It might be interesting to understand why they've done this. Unfortunately for your scenario, policy overrides the myriad other ways to specify a proxy (e.g. command line, extensions, etc).

If you only need to see the traffic, there's a great alternative approach:

1. Capture the traffic using the browser's logging feature:

https://textslashplain.com/2020/01/17/capture-network-logs-from-edge-and-chrome/

2. Import that traffic capture into Fiddler's Viewer using the NetLog importer:

https://textslashplain.com/2020/04/08/analyzing-network-traffic-logs-netlog-json/

If you need to modify traffic, things get a little more complicated; e.g. you could run Fiddler as a reverse-proxy, or you could possibly just use client urls of e.g. http://127.0.0.1:8888 and use the AutoResponder or Hosts extension to forward the requests to the correct backend server.