Forum Widgets
Latest Discussions
Extended channel not working for Edge 142
We have been running the extended channel for a long time, and as far as I can tell, everything on our end looks to be configured correctly. But when checking for updates, Edge is saying that we're up-to-date with 140.0.3485.130. Clearly we should be getting updated to 142.0.3595.53. Is anyone else using extended channel experiencing the same issue?Is Edge Copilot susceptible to Prompt Injection Attack?
I am getting lots of negative vibe when reading about OpenAI's Altas browser. But what about Edge browser? Let's say if you have Copilot in Edge turned on with Page Content allowed. You asked the Copilot to summerise the page you are browsing and the page has hidden text to initiate a prompt injection attack. Is it safe to say that as long as Copilot does not have control over your browsing or desktop, the damage is limited. The worst thing it could happen is the change of AI behaviour, meaning the response returned from your question may not be what you asked for. There is zero DLP risk, right?Stolen session token from Edge
We can steal the session token from Edge using tools like Burp Suite or Fiddler to intercept proxy traffic on the mobile phone, even when the Edge is MAM protected by Intune. This makes the Edge browser unsafe to use for Enterprise Applications on personal mobile. Recently I discovered that the https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-token-protection in Conditional Access Policy. However it is only available for Windows. I am wondering if anyone knows when it would become available for mobile on Entra roadmap. Also, if you know any Edge configuration, I could use to stop Token Theft, please let me know! Thank you everyone.
Camera and Mic Site Permissions
edge settings/privacy/sitePermissions/allPermissions/camera edge settings/privacy/sitePermissions/allPermissions/microphone I was looking to add some sites / urls to automatically permit access to both camera and mic to stop the age old i said no and now cant use service x type service calls from coming in. i added these 2 policies to the admin template Sites that can access audio capture devices without requesting permission Sites that can access video capture devices without requesting permission both succeed in delivery to the device but don't appear in the edge site permission list as expected have i got the wrong policy? is it broke?
Chrome extension managed storage policy
Hi there, I've developed a chrome extension and now we want to deploy it using Intune. Force install of extension works great but I can't pass managed data to the extension. Here is the scheme: { "type": "object", "properties": { "apiKey": { "title": "API Key", "description": "An API key to communicate with server.", "type": "string" } } } This is the policy that I created in Intune: OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~3rdparty~extensions~eagefwefpbjpewefliifpgfgoewfknnmk~policy Data type: String Value: {"apiKey":"mykey123"} But it doesn't appear in chrome://policy and when I get policies in my code with: const result = await chrome.storage.managed.get(null); The result is empty! What is the problem here? And how to fix it?Edge Dev > Enterprise State Roaming / Sync Broke
I noted in Edge DEV my profile stopped syncing even though its set by policy to be on the journey took me to edge://settings/profiles/sync where turn on sync is presented - so i turn it on a confirm and cancel button appear as well as the expected other areas (but showing as off by policy???) hitting confirm just makes confirm and cancel disappear with no changes these are not new? what gives or is changing? is sync just broke in dev for now? Edge Beta and Stable are not impacted.
Starting Edge as a process immediately fires exited event
Hi! Recently I have encountered a rather annoying bug on Windows 11 IoT LTSC where I launch an edge as a process from my .net 9.0 C# code. I need to track Edge and if it exits for some reason I have to relaunch it. I'm tracking whether it has exited by subscribing to the Process.Exited event, but on the beforementioned operating system this event immediately fires even though the Edge itself visibly does not close and stays functional without any problem. This results in infinite edge processes getting launched, since every new instance also exits. Interestingly this issue does not occur when tested with other browsers nor it occurs on Windows 11 Pro, everything works completely fine in these two scenarios. I'm guessing IoT version has some kind of different power plan to reduce battery drainage and CPU usage if possible. My other assumption is that the msedge.exe available with default windows is just a parent process on the IoT version, and it just starts the actual processes needed to present the content of my web app. It'd be great if you could check this and come back to me. Thank you! Kind regards, Gallusz.Manifest V2/V3 timeline update?
Google/Chromium announced at the end of March that MV2 would be completely removed from Chrome in v139, meaning that v138 will be the last version that can run MV2 extensions even using the policy override. Since v139 is expected sometime in July, that time is coming up fast! In Microsoft's timeline, it is stated: Manifest V2 extensions will continue to be supported through Enterprise policies at least until the date in the Chromium Manifest V2 support timeline. Since Google will be removing it as of v139, can we expect the same for Edge? Just trying to plan out notification to some groups who use custom extensions (ie: from vendors or internally created) that they will see the older extensions be removed/disabled. Thank you!
Edge Update Service Error
Hello, Our organization recently set a target version in Intune to update Edge 132.0.2957.115 to 134.0.3124.51, and we noticed that around 80% of our clients failed to install this update. In the Microsoft Edge Update Service log, it appears that our devices were failing the hardware compatibility check: None of these devices are more than 5 years old, so I assume there is a bug with this check in the service. We were able to work around this issue by deploying the MSI, which installed without any error. Hope this helps someone! Andrew
