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?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.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.Why this policy is producing error? Configure new tab page URL
It's this Policy: https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#newtabpagelocation And based on the description, I've set it correctly on Edge 87 (the installed up-to-date policy files are also for Edge 87) But it isn't being applied and I see an error in Edge:policy why does it say the policy is blocked? what am I doing wrong?
