Forum Widgets
Latest Discussions
Edge for Android top bar after update to 121.0.2277.105 version
On a work fully managed Android device, after the Edge for Android app was updated to 121.0.2277.105 version when I open the Edge app on top of the screen I get a bar named "Edge" that will take from the screen and is very annoying. I noticed that this is happening only if I am not prompted to enter the device PIN when I open the app, if I am prompted to type the PIN then the content is rendered properly. A workaround that I find was to change the device theme but this will be only a temporary fix as next time if I will open the app and I am not asked to type the PIN the top bar will reoccur. The application protection policy is enforced via Intune, and for inactivity we have 10 minutes set up for recheck the access. Anyone come across with this issue? Thanks. MarioMario_1313Jun 19, 2025Copper Contributor2.9KViews3likes18CommentsManifest 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!lexcynJun 05, 2025Steel Contributor179Views2likes0CommentsInsecurePrivateNetworkRequestsAllowed
In Dev version 138.0.3338.1 I noticed the following policies are showing as "error/not found" and was wondering if these policies are scheduled to be depreciated: InsecurePrivateNetworkRequestsAllowed InsecurePrivateNetworkRequestsAllowedForUrls These policies are still functional on stable 137.0.3296.58. Thanks!SolvedlexcynJun 03, 2025Steel Contributor72Views0likes4CommentsEdge Sync w/ MS 365 Basic and Business Standard
Hi, I noticed that some of my customers with MS 365 Basic and Business Standard plans can sync their MS Edge information, while others can't. Based in this article, sync only works with plans that include Azure AD Premium P1 and P2, Microsoft 365 Business Premium, and EDU. https://docs.microsoft.com/en-us/deployedge/microsoft-edge-enterprise-sync Could it be that MS is starting to expand to smaller plans? Is there an article with details about this? Thanks...Daniel VelezMay 22, 2025Copper Contributor34KViews5likes92CommentsMicrosoft edge chromium deployment
Hi, As Microsoft will discontinue IE, therefore we are deploying Microsoft Edge in our organization. I have downloaded the MIS pack and ADMX files. I can push the package in my company but it is hard to find relevant GPOs. I am missing GPO to control Edge, like Zone settings, Set Local Intranet sites, Set Trusted Sites, Set Content off, remove Office 365 App Launcher button, set language, enable time and weather. I want to remove IE and replace by Edge. Can you please guide me how to achieve this? Thank you. Kind regards, DineshDineshVermaMay 14, 2025Copper Contributor2.7KViews1like5CommentsMachine learning powered autofill suggestions
Hello, It looks like a new Machine Learning autofill feature was rolled out with Edge 132 and enabled by default. There is a bug with this setting where even if you have the parent "Save and fill basic info" setting disabled, the Machine Learning suggestions still appear even though the setting is grayed out. This leads to a confusing user experience, because folks that work in enterprise forms with PII try to disable their autofill, only for the feature to remain active. The workaround to disable this feature is to re-enable Autofill, turn of ML suggestions, then disable Autofill again. It looks like there is an enterprise policy to control this setting rolled out on January 17 with Edge 132.0.2957.115. However, I do not see this setting in Intune's Settings Catalog. We are trying to manage in the cloud and avoid creating any more group policies. Is anyone aware of an ETA for this to be added to Settings Catalog? I'd prefer not to set up a Remediation or ADMX CP only for the setting to become available shortly thereafter. Thanks! AndrewAndrewSAIFMay 12, 2025Iron Contributor497Views1like9CommentsMicrosoft Editor does not work
As the title states, if you have the Microsoft Editor enabled in Edge (this appears to be any version from Stable to even Canary), no spell or grammar check will work at all. If you enable the standard editor, you will get at least spell check back. This screenshot is with the MS Editor enabled - it seems to know what is spelled incorrectly but gives you zero suggestions. And here is the standard spell check working as it should. Testing in Edge stable 136.0.3240.50 + Dev 137.0.3282.1SolvedlexcynMay 09, 2025Steel Contributor1.6KViews6likes15CommentsWaffle Error?
Here is a screen shot of the default screen waffle in Edge. If you click on or hover over the waffle you get this message. This only seems to occur in our local AD bound/based system images. On InTune deployments this isn't the case. What in our local deployment could cause this problem in the browser?DanielCayeaApr 29, 2025Copper Contributor2.6KViews0likes11CommentsOrgBrandingCustomName no longer working in Dev/Canary
The latest Dev/Canary builds have moved the profile icon from the top left back to the address bar near the extension/plugin list. We have the OrgBrandingCustomName cloud policy enabled which no longer works due to this change. Is this expected behavior? Current stable channel behavior: New Dev/Canary behavior:SolvedlexcynApr 24, 2025Steel Contributor104Views1like2CommentsEdge 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! AndrewAndrewSAIFApr 11, 2025Iron Contributor153Views1like2Comments
Resources
Tags
- edge43 Topics
- IE mode13 Topics
- Group Policy11 Topics
- gpo10 Topics
- enterprise9 Topics
- policy9 Topics
- Edge Chromium8 Topics
- BUG7 Topics
- Internet Explorer5 Topics
- dev5 Topics