Identify network traffic originating from App Guard containers at the proxy level
Microsoft Edge Version 91.0.834.0 (Official build) canary (64-bit) The newly added flag for this feature: edge://flags/#edge-wdag-traffic-identification If enabled, Application Guard traffic will be tagged with a X-MS-ApplicationGuard-Initiated header – Windows By the way, if any user or developer is reading this, can you help me understand how exactly we should monitor WDAG connections? There are some difficulties I've been trying to solve in the past few hours.[FIXED] Edge insider Canary Not working anymore. opens all websites in WDAG Application Guard Window
UPDATE: Fixed in Edge insider Version 79.0.294.0 (Official build) canary (64-bit) I just updated my Edge insider Canary to Version 79.0.292.0 (Official build) canary (64-bit) and After that, when I type in something in the omnibox or click on any bookmark, the browser launches the Windows Defender Application Guard window and attempts to open that websites in there. I said attempt because It tries and fails with this error: I'm on Windows 10 fast ring build 18990. tried restarting computer and disabling all extensions but still no luck. whatever this last update had triggered this problem. so right now Edge insider canary is literally dead and I'm posting this with Edge classic. Elliot Kirk anyone else experiencing this?Application Guard window uses the wrong theme - Edge insider
Both the normal and Windows Defender application guard window are set to use system theme (set to dark) but WDAG mode still uses the white theme. this issue wasn't there previously and both modes used to load the correct theme. Version 80.0.320.0 (Official build) canary (64-bit) Windows 10 build 19013.1102
