Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 416/439 docs · checked 18:51 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft 365 Apps Group Policy settings

2,420 settings · 5568.1000 · 10 Aug 2026

3 folders · 13 settingsCSV
Back to the list

Microsoft Office 2016 › Security Settings

ActiveX Control Initialization

UserNeeds changes for IntuneL_ActiveXControlInitialization

Supported on SUPPORTED_Windows7 (defined in the Windows templates)

What it does

This policy setting specifies the Microsoft ActiveX® initialization security level for all Microsoft Office applications. ActiveX controls can adversely affect a computer directly. In addition, malicious code can be used to compromise an ActiveX control and attack a computer. To indicate the safety of an ActiveX control, developers can denote them as Safe For Initialization (SFI). SFI indicates that a control is safe to open and run, and that it is not capable of causing a problem for any computer, regardless of whether it has persisted data values or not. If a control is not marked SFI, it is possible that the control could adversely affect a computer--or it could mean that the developers did not test the control in all situations and are not sure whether it might be compromised in the future. If you enable this policy setting, you can set the ActiveX security level to a number between 1 and 6. These security levels are as follows: 1 - Regardless of how the control is marked, load it and use the persisted values (if any). This setting does not prompt the user. 2 - If SFI, load the control in safe mode and use persisted values (if any). If not SFI, load in unsafe mode with persisted values (if any), or use the default (first-time initialization) settings. This level is similar to the default configuration, but does not prompt the user. 3 - If SFI, load the control in unsafe mode and use persisted values (if any). If not SFI, prompt the user and advise them that it is marked unsafe. If the user chooses No at the prompt, do not load the control. Otherwise, load it with default (first-time initialization) settings. 4 - If SFI, load the control in safe mode and use persisted values (if any). If not SFI, prompt the user and advise them that it is marked unsafe. If the user chooses No at the prompt, do not load the control. Otherwise, load it with default (first-time initialization) settings. 5 - If SFI, load the control in unsafe mode and use persisted values (if any). If not SFI, prompt the user and advise them that it is marked unsafe. If the user chooses No at the prompt, do not load the control. Otherwise, load it with persisted values. 6 - If SFI, load the control in safe mode and use persisted values (if any). If not SFI, prompt the user and advise them that it is marked unsafe. If the user chooses No at the prompt, do not load the control. Otherwise, load it with persisted values. If you disable or do not configure this policy setting, if a control is marked SFI, the application loads the control in safe mode and uses persisted values (if any). If the control is not marked SFI, the application loads the control in unsafe mode with persisted values (if any), or uses the default (first-time initialization) settings. In both situations, the Message Bar informs users that the controls have been disabled and prompts them to respond. Important - Some ActiveX controls do not respect the safe mode registry setting, and therefore might load persisted data even though you configure this setting to instruct the control to use safe mode. This setting only increases security for ActiveX controls that are accurately marked as SFI. In situations that involve malicious or poorly designed code, an ActiveX control might be inaccurately marked as SFI.

What it writes

Hive
HKEY_CURRENT_USER
Registry key
software\policies\microsoft\office\common\security
Why it needs changes for Intune
  • Policy references a Windows supportedOn definition.
  • ADMX-INTUNE-WINDOWS-SUPPORTEDON-REFERENCE

Security baselines

Microsoft's Microsoft 365 Apps for Enterprise 2512 sets this to Enabled, in its GPO “MSFT Microsoft 365 Apps v2512 - User”.

ActiveX Control Initialization
Set to “6” (6).

Read from the registry.pol files in the baselines' GPO backups, downloaded from Microsoft's Security Compliance Toolkit. All baselines

Options

OptionTypeRegistry valueAllowed values
ActiveX Control InitializationDefault: 1 Drop-down list uficontrols
  • 11
  • 22
  • 33
  • 44
  • 55
  • 66

Configure and deploy

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

State
Options used when Enabled

Enabled · User · template defaults

Registry file (.reg)

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\software\policies\microsoft\office\common\security]
"uficontrols"=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: ActiveX Control Initialization
# Name: L_ActiveXControlInitialization
# Scope: User
# State: Enabled
# Source: office16.admx

Set-RegistryValue -Path 'Registry::HKEY_CURRENT_USER\software\policies\microsoft\office\common\security' -Name 'uficontrols' -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.

ADMX profile candidate (OMA-URI)

./User/Vendor/MSFT/Policy/Config/ADMX_office16/L_ActiveXControlInitialization

ADMX SyncML candidate

<SyncML xmlns="SYNCML:SYNCML1.2">
  <SyncBody>
    <Replace>
      <CmdID>1</CmdID>
      <Item>
        <Meta>
          <Format>chr</Format>
          <Type>text/plain</Type>
        </Meta>
        <Target>
          <LocURI>./User/Vendor/MSFT/Policy/Config/ADMX_office16/L_ActiveXControlInitialization</LocURI>
        </Target>
        <Data>&lt;enabled/&gt;
&lt;data id="L_ActiveXControlInitializationcolon" value="1"/&gt;</Data>
      </Item>
    </Replace>
    <Final/>
  </SyncBody>
</SyncML>
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: ActiveX Control Initialization
# Name: L_ActiveXControlInitialization
# Scope: User
# State: Enabled
# Source: office16.admx

$isMatch = Test-RegistryValueEquals -Path 'Registry::HKEY_CURRENT_USER\software\policies\microsoft\office\common\security' -Name 'uficontrols' -Kind 'DWord' -Expected 1
if (-not $isMatch) {
    $reasons.Add('Value mismatch: HKEY_CURRENT_USER\software\policies\microsoft\office\common\security\uficontrols') | 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: ActiveX Control Initialization
# Name: L_ActiveXControlInitialization
# Scope: User
# State: Enabled
# Source: office16.admx

Set-RegistryValue -Path 'Registry::HKEY_CURRENT_USER\software\policies\microsoft\office\common\security' -Name 'uficontrols' -PropertyType 'DWord' -Value 1

History 1 retained release

  1. 5568.100010 Aug 2026
    • Already present in the first release ChangeIntel keeps.

Template

Internal name
L_ActiveXControlInitialization
Namespace
office16.Office.Microsoft.Policies.Windows
Template file
office16.admx
Release
Microsoft 365 Apps 5568.1000 · file set 8be05d876aae137d…
Definition, editor controls and support

Definition

<policy Area="Security Baseline" AreaCategory="ActiveX" class="User" displayName="$(string.L_ActiveXControlInitialization)" explainText="$(string.L_ActiveXControlInitializationExplain)" key="software\policies\microsoft\office\common\security" name="L_ActiveXControlInitialization" presentation="$(presentation.L_ActiveXControlInitialization)" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
      <parentCategory ref="office16.Office.Microsoft.Policies.Windows:L_SecuritySettings" />
      <supportedOn ref="Microsoft.Policies.Windows:SUPPORTED_Windows7" />
      <elements>
        <enum id="L_ActiveXControlInitializationcolon" valueName="uficontrols">
          <item displayName="$(string.L_1)">
            <value>
              <decimal value="1" />
            </value>
          </item>
          <item displayName="$(string.L_2)">
            <value>
              <decimal value="2" />
            </value>
          </item>
          <item displayName="$(string.L_3)">
            <value>
              <decimal value="3" />
            </value>
          </item>
          <item displayName="$(string.L_4)">
            <value>
              <decimal value="4" />
            </value>
          </item>
          <item displayName="$(string.L_5)">
            <value>
              <decimal value="5" />
            </value>
          </item>
          <item displayName="$(string.L_6)">
            <value>
              <decimal value="6" />
            </value>
          </item>
        </enum>
      </elements>
    </policy>

Editor controls

<presentation id="L_ActiveXControlInitialization" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
        <dropdownList defaultItem="0" noSort="true" refId="L_ActiveXControlInitializationcolon">ActiveX Control Initialization:</dropdownList>
      </presentation>

Supported platforms and category

office16.Office.Microsoft.Policies.Windows:category:L_MicrosoftOfficeSystem
<category displayName="$(string.L_MicrosoftOfficeSystem)" name="L_MicrosoftOfficeSystem" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions" />
office16.Office.Microsoft.Policies.Windows:category:L_SecuritySettings
<category displayName="$(string.L_SecuritySettings)" name="L_SecuritySettings" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
      <parentCategory ref="office16.Office.Microsoft.Policies.Windows:L_MicrosoftOfficeSystem" />
    </category>
office16.Office.Microsoft.Policies.Windows:unresolved:Microsoft.Policies.Windows:SUPPORTED_Windows7
<unresolved reference="Microsoft.Policies.Windows:SUPPORTED_Windows7" />
office16.Office.Microsoft.Policies.Windows:category:L_MicrosoftOfficeSystem
<category displayName="$(string.L_MicrosoftOfficeSystem)" name="L_MicrosoftOfficeSystem" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions" />
<strings><string id="office16.Office.Microsoft.Policies.Windows:L_MicrosoftOfficeSystem">Microsoft Office 2016</string></strings>
office16.Office.Microsoft.Policies.Windows:category:L_SecuritySettings
<category displayName="$(string.L_SecuritySettings)" name="L_SecuritySettings" xmlns="http://schemas.microsoft.com/GroupPolicy/2006/07/PolicyDefinitions">
      <parentCategory ref="office16.Office.Microsoft.Policies.Windows:L_MicrosoftOfficeSystem" />
    </category>
<strings><string id="office16.Office.Microsoft.Policies.Windows:L_SecuritySettings">Security Settings</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 20 Oct 18:51 UTC · 258 of 260 readable · 256 fully read · documentation 416/439 current