Public mode

No tenant, Graph, or device access. Every item links to its source. What this means

Some sources or documents need attention: 253/255 feeds/APIs · 0/410 docs · checked 16:05 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Edge Group Policy settings

910 settings · 155.0.4283.62 · 16 Oct 2026

37 folders · 438 settingsCSV
Back to the list

Microsoft Edge

Default sensors setting

Computer and userIntune-readyDefaultSensorsSetting

Supported on Microsoft Edge version 86, Windows 7 or later

What it does

Set whether websites can access and use sensors such as motion and light sensors. You can completely block or allow websites to get access to sensors. Setting the policy to 1 lets websites access and use sensors. Setting the policy to 2 denies access to sensors. Setting the policy to 3 is intended to prompt the user when a site requests access to sensors, but this option isn't yet supported; if you select it, websites can still access and use sensors. You can override this policy for specific URL patterns by using the 'SensorsAllowedForUrls' (Allow access to sensors on specific sites) and 'SensorsBlockedForUrls' (Block access to sensors on specific sites) policies. If you don't configure this policy, websites can access and use sensors, and users can change this setting. This setting is the global default for 'SensorsAllowedForUrls' and 'SensorsBlockedForUrls'. Policy options mapping: * AllowSensors (1) = Allow sites to access sensors * BlockSensors (2) = Do not allow any site to access sensors * AskSensors (3) = Ask whenever a site wants to access sensors (This policy is not yet supported) Use the preceding information when configuring this policy.

What it writes

Hive
HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER
Registry key
Software\Policies\Microsoft\Edge

Options

OptionTypeRegistry valueAllowed values
Default sensors setting Drop-down list DefaultSensorsSetting
  • Allow sites to access sensors1
  • Do not allow any site to access sensors2
  • Ask whenever a site wants to access sensors (This policy is not yet supported)3

Configure and deploy

Choose a state and the option values; the output below is generated from the template for exactly that.

State
Apply to
Options used when Enabled

Enabled · Computer · template defaults

Registry file (.reg)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge]
"DefaultSensorsSetting"=dword:00000001


PowerShell

$ErrorActionPreference = 'Stop'

function Set-RegistryValue {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name,
        [Parameter(Mandatory = $true)][string] $PropertyType,
        [Parameter(Mandatory = $true)][object] $Value
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        New-Item -Path $Path -Force | Out-Null
    }

    New-ItemProperty -LiteralPath $Path -Name $Name -PropertyType $PropertyType -Value $Value -Force | Out-Null
}

function Remove-RegistryValue {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name
    )

    if (Test-Path -LiteralPath $Path) {
        Remove-ItemProperty -LiteralPath $Path -Name $Name -Force -ErrorAction SilentlyContinue
    }
}

function Clear-RegistryKeyValues {
    param(
        [Parameter(Mandatory = $true)][string] $Path
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        return
    }

    foreach ($propertyName in (Get-Item -LiteralPath $Path).Property) {
        Remove-ItemProperty -LiteralPath $Path -Name $propertyName -Force -ErrorAction SilentlyContinue
    }
}

# Policy: Default sensors setting
# Name: DefaultSensorsSetting
# Scope: Machine
# State: Enabled
# Source: msedge.admx

Set-RegistryValue -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge' -Name 'DefaultSensorsSetting' -PropertyType 'DWord' -Value 1
  • The OMA-URI is an inferred ADMX-backed Policy CSP candidate derived from the source ADMX file name and policy name.
  • Some Microsoft policies use built-in Policy CSP pages whose area names don't match the ADMX file name, so verify the candidate against Microsoft Learn before deployment.
  • The generated payload is incomplete because one or more ADMX element values were not supplied: DefaultSensorsSetting

ADMX profile candidate (OMA-URI)

./Device/Vendor/MSFT/Policy/Config/ADMX_msedge/DefaultSensorsSetting
Intune remediation scripts

Detection

$ErrorActionPreference = 'Stop'
$reasons = [System.Collections.Generic.List[string]]::new()

function Test-RegistryValueExists {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        return $false
    }

    return $null -ne (Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction SilentlyContinue)
}

function Test-RegistryValueEquals {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name,
        [Parameter(Mandatory = $true)][string] $Kind,
        [Parameter(Mandatory = $true)][object] $Expected
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        return $false
    }

    $valueObject = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction SilentlyContinue
    if ($null -eq $valueObject) {
        return $false
    }

    $actual = $valueObject.$Name
    switch ($Kind) {
        'String' { return [string]$actual -ceq [string]$Expected }
        'ExpandString' { return [string]$actual -ceq [string]$Expected }
        'DWord' { return [uint32]$actual -eq [uint32]$Expected }
        'QWord' { return [uint64]$actual -eq [uint64]$Expected }
        'MultiString' {
            $actualArray = @($actual)
            $expectedArray = @($Expected)
            if ($actualArray.Count -ne $expectedArray.Count) { return $false }
            for ($index = 0; $index -lt $actualArray.Count; $index++) {
                if ([string]$actualArray[$index] -cne [string]$expectedArray[$index]) { return $false }
            }
            return $true
        }
        'Binary' {
            $actualArray = [byte[]]$actual
            $expectedArray = [byte[]]$Expected
            if ($actualArray.Length -ne $expectedArray.Length) { return $false }
            for ($index = 0; $index -lt $actualArray.Length; $index++) {
                if ($actualArray[$index] -ne $expectedArray[$index]) { return $false }
            }
            return $true
        }
        default { return [string]$actual -ceq [string]$Expected }
    }
}

# Policy: Default sensors setting
# Name: DefaultSensorsSetting
# Scope: Machine
# State: Enabled
# Source: msedge.admx

$isMatch = Test-RegistryValueEquals -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge' -Name 'DefaultSensorsSetting' -Kind 'DWord' -Expected 1
if (-not $isMatch) {
    $reasons.Add('Value mismatch: HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\DefaultSensorsSetting') | Out-Null
}

if ($reasons.Count -eq 0) {
    Write-Output 'Compliant'
    exit 0
}

$reasons | ForEach-Object { Write-Output $_ }
exit 1

Remediation

$ErrorActionPreference = 'Stop'

function Set-RegistryValue {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name,
        [Parameter(Mandatory = $true)][string] $PropertyType,
        [Parameter(Mandatory = $true)][object] $Value
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        New-Item -Path $Path -Force | Out-Null
    }

    New-ItemProperty -LiteralPath $Path -Name $Name -PropertyType $PropertyType -Value $Value -Force | Out-Null
}

function Remove-RegistryValue {
    param(
        [Parameter(Mandatory = $true)][string] $Path,
        [Parameter(Mandatory = $true)][string] $Name
    )

    if (Test-Path -LiteralPath $Path) {
        Remove-ItemProperty -LiteralPath $Path -Name $Name -Force -ErrorAction SilentlyContinue
    }
}

function Clear-RegistryKeyValues {
    param(
        [Parameter(Mandatory = $true)][string] $Path
    )

    if (-not (Test-Path -LiteralPath $Path)) {
        return
    }

    foreach ($propertyName in (Get-Item -LiteralPath $Path).Property) {
        Remove-ItemProperty -LiteralPath $Path -Name $propertyName -Force -ErrorAction SilentlyContinue
    }
}

# Policy: Default sensors setting
# Name: DefaultSensorsSetting
# Scope: Machine
# State: Enabled
# Source: msedge.admx

Set-RegistryValue -Path 'Registry::HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge' -Name 'DefaultSensorsSetting' -PropertyType 'DWord' -Value 1

History 37 retained releases

  1. 152.0.4191.5328 Aug 2026
    • Description … policy to 2 denies access to sensors. Setting the policy to 3 [removed: prompts][added: is intended to prompt] the user when a site requests access to [removed: sensors if the tri-state feature flag is enabled; otherwise, it defaults to allowing][added: sensors, but this option isn't yet supported; if you select it, websites can still] access [removed: to][added: and use] sensors. You can override this policy for specific URL patterns by using … * AskSensors (3) = Ask whenever a site wants to access sensors[added: (This policy is not yet supported)] Use the preceding information when configuring this policy.
      Whole description, marked

      Set whether websites can access and use sensors such as motion and light sensors. You can completely block or allow websites to get access to sensors. Setting the policy to 1 lets websites access and use sensors. Setting the policy to 2 denies access to sensors. Setting the policy to 3 [removed: prompts][added: is intended to prompt] the user when a site requests access to [removed: sensors if the tri-state feature flag is enabled; otherwise, it defaults to allowing][added: sensors, but this option isn't yet supported; if you select it, websites can still] access [removed: to][added: and use] sensors. You can override this policy for specific URL patterns by using the 'SensorsAllowedForUrls' (Allow access to sensors on specific sites) and 'SensorsBlockedForUrls' (Block access to sensors on specific sites) policies. If you don't configure this policy, websites can access and use sensors, and users can change this setting. This setting is the global default for 'SensorsAllowedForUrls' and 'SensorsBlockedForUrls'. Policy options mapping: * AllowSensors (1) = Allow sites to access sensors * BlockSensors (2) = Do not allow any site to access sensors * AskSensors (3) = Ask whenever a site wants to access sensors[added: (This policy is not yet supported)] Use the preceding information when configuring this policy.

    • A choice in “Default sensors setting” is renamed Ask whenever a site wants to access sensors [added: (This policy is not yet supported) ](3)
  2. 151.0.4129.5931 Jul 2026
    • Description … and use sensors. Setting the policy to 2 denies access to sensors.[added: Setting the policy to 3 prompts the user when a site requests access to sensors if the tri-state feature flag is enabled; otherwise, it defaults to allowing access to sensors.] You can override this policy for specific URL patterns by using the … to access sensors * BlockSensors (2) = Do not allow any site[added: to access sensors * AskSensors (3) = Ask whenever a site wants] to access sensors Use the preceding information when configuring this policy.
      Whole description, marked

      Set whether websites can access and use sensors such as motion and light sensors. You can completely block or allow websites to get access to sensors. Setting the policy to 1 lets websites access and use sensors. Setting the policy to 2 denies access to sensors.[added: Setting the policy to 3 prompts the user when a site requests access to sensors if the tri-state feature flag is enabled; otherwise, it defaults to allowing access to sensors.] You can override this policy for specific URL patterns by using the 'SensorsAllowedForUrls' (Allow access to sensors on specific sites) and 'SensorsBlockedForUrls' (Block access to sensors on specific sites) policies. If you don't configure this policy, websites can access and use sensors, and users can change this setting. This setting is the global default for 'SensorsAllowedForUrls' and 'SensorsBlockedForUrls'. Policy options mapping: * AllowSensors (1) = Allow sites to access sensors * BlockSensors (2) = Do not allow any site[added: to access sensors * AskSensors (3) = Ask whenever a site wants] to access sensors Use the preceding information when configuring this policy.

    • “Default sensors setting” gains the choice [added: Ask whenever a site wants to access sensors (3)]
  3. 150.0.4078.8016 Jul 2026
    • Already present in the first release ChangeIntel keeps.

34 later releases left it unchanged.

Template

Internal name
DefaultSensorsSetting
Namespace
Microsoft.Policies.Edge
Template file
msedge.admx
Release
Microsoft Edge 155.0.4283.62 · file set 0a733b0040dbbf02…
Definition, editor controls and support

Definition

<policy class="Both" displayName="$(string.DefaultSensorsSetting)" explainText="$(string.DefaultSensorsSetting_Explain)" key="Software\Policies\Microsoft\Edge" name="DefaultSensorsSetting" presentation="$(presentation.DefaultSensorsSetting)" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
      <parentCategory ref="Microsoft.Policies.Edge:microsoft_edge" />
      <supportedOn ref="Microsoft.Policies.Edge:SUPPORTED_WIN7_V86" />
      <elements>
        <enum id="DefaultSensorsSetting" valueName="DefaultSensorsSetting">
          <item displayName="$(string.DefaultSensorsSetting_AllowSensors)">
            <value>
              <decimal value="1" />
            </value>
          </item>
          <item displayName="$(string.DefaultSensorsSetting_BlockSensors)">
            <value>
              <decimal value="2" />
            </value>
          </item>
          <item displayName="$(string.DefaultSensorsSetting_AskSensors)">
            <value>
              <decimal value="3" />
            </value>
          </item>
        </enum>
      </elements>
    </policy>

Editor controls

<presentation id="DefaultSensorsSetting" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions"><dropdownList refId="DefaultSensorsSetting">Default sensors setting</dropdownList></presentation>

Supported platforms and category

Microsoft.Policies.Edge:category:microsoft_edge
<category displayName="$(string.microsoft_edge)" name="microsoft_edge" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions" />
Microsoft.Policies.Edge:definition:SUPPORTED_WIN7_V86
<definition displayName="$(string.SUPPORTED_WIN7_V86)" name="SUPPORTED_WIN7_V86" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions" />
Microsoft.Policies.Edge:category:microsoft_edge
<category displayName="$(string.microsoft_edge)" name="microsoft_edge" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions" />
<strings><string id="Microsoft.Policies.Edge:microsoft_edge">Microsoft Edge</string></strings>
Microsoft.Policies.Edge:definition:SUPPORTED_WIN7_V86
<definition displayName="$(string.SUPPORTED_WIN7_V86)" name="SUPPORTED_WIN7_V86" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions" />
<strings><string id="Microsoft.Policies.Edge:SUPPORTED_WIN7_V86">Microsoft Edge version 86, Windows 7 or later</string></strings>
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Oct 16:05 UTC · 253 of 255 readable · 252 fully read · documentation 0/410 current