There needs to be a policy to enable Edge Secure Network
As soon a single policy is set for Microsoft Edge, either through group policy or registry, the Edge Secure Network becomes unavailable. There needs to be a policy to enable it again. Using a registry key or local policy to control Edge doesn't mean it's controlled by an organization or personal Microsoft accounts are not used.Official Download links for Microsoft Edge Stable Enterprise
I'm not 100% sure it's final but anyone who wishes/wants can test it. Microsoft Edge Stable Enterprise X64.msi http://go.microsoft.com/fwlink/?LinkID=2093437 X86.msi http://go.microsoft.com/fwlink/?LinkID=2093505 MicrosoftEdgePolicyTemplates.cab http://go.microsoft.com/fwlink/?LinkID=2099616 MicrosoftEdgeIntunePolicyTemplate.cab http://go.microsoft.com/fwlink/?LinkID=2099617 macOS.pkg http://go.microsoft.com/fwlink/?LinkID=2093438 Blocker Toolkit to disable automatic delivery of Microsoft Edge https://docs.microsoft.com/en-us/deployedge/microsoft-edge-blocker-toolkit
Edge extension policy
In our extension we want to use one of our micro-frontend application so we will load it inside an iframe in the some part of the our extension, does the extension policy allow this? This application can send events via “post message”, and also we have authentication through auth0. Does this mean that if we will load our micro-frontend application we are violating the policy?
Edge does not use the configured policys
Hi together, We currently have this very strange problem: We've downloaded the Edge Enterprise MSI (97.0.1072.69) including the Windows 64-bit Policys from here: https://www.microsoft.com/en-us/edge/business/download and successfully deployed them to all our Clients. The new ADMX Templates were also copied to the SYSVOL Store of the Main DC, which is a WS 2012 R2 one. We've created a new GPO and "gpreport -H report.html" reports that it was successfully applied to one of our Test-Clients (W10 Pro 21H1): However, the "edge://policy/" Link shows that no single Policy was applied: Can someone explain to me why it doesn't apply the Edge-GPO?
Having issues getting Chromium Edge to accept policy changes
I'm running onto some issues trying to change a few settings on a new Chromium Edge install using policy edits through the registry. These computers are not domain managed, so the only method available for me to do this is by using a powershell script to edit the registry files to get these settings changed. I'm trying to set the browser to restore 2 pages each time it starts up, everything I have found indicates that the settings should be set in the HKCU:\Software\Policies\Microsoft\Edge I have the registry files set so they write the settings that I believe should be correct, but after setting them and opening edge the policies don't seem to apply. The script I'm using for the registry edits is attached below. #Disable Edge "First Run" #Create registry key "HideFirstRunExperience" new-item –Path "HKCU:\SOFTWARE\Policies\Microsoft\" –Name "Edge" New-ItemProperty -Path "HKCU:\SOFTWARE\Policies\Microsoft\Edge" -Name "HideFirstRunExperience" -Value ”1” -PropertyType "DWORD" #Set multiple pages to open on startup #Set restore on startup New-ItemProperty -Path "HKCU:\SOFTWARE\Policies\Microsoft\Edge" -Name "RestoreOnStartup" -Value ”0x00000004” -PropertyType "DWORD" -Force #Create "Recommended" and "Mandatory" new-item –Path "HKCU:\SOFTWARE\Policies\Microsoft\Edge" –Name "Recommended" new-item –Path "HKCU:\SOFTWARE\Policies\Microsoft\Edge" –Name "Mandatory" new-item –Path "HKCU:\SOFTWARE\Policies\Microsoft\Edge\Mandatory" –Name "RestoreOnStartupURLs" #G2A FastSupport New-ItemProperty -Path "HKCU:\SOFTWARE\Policies\Microsoft\Edge\Mandatory\RestoreOnStartupURLs" -Name "1" -Value ”www.fastsupport.com” -PropertyType "String" #Password Self Serve New-ItemProperty -Path "HKCU:\SOFTWARE\Policies\Microsoft\Edge\Mandatory\RestoreOnStartupURLs" -Name "2" -Value ”https://https://passwordreset.microsoftonline.com/” -PropertyType "String" I'm extremely new to this sort of thing, and especially using powershell, so It very well may be something I'm overlooking, but If anybody can provide assistance I'd appreciate it.
Found a bug in Edge 87 policy
So whenever I enable this policy This option in Edge which is related to secure DNS lookups, becomes unavailable and disabled I see no relation between the 2 options. in Edge policy I only have this which should only apply to this and not other settings. so In my perspective this is a bug/unwanted behavior. I'll report it using feedback button on Edge too. Edge Dev 87-88 Windows 10 20H2 if for any reason this is actually an expected behavior, please let me know with some explanation, thank you.
