Office Admin Explorer

Automation Security

Registry value
automationsecurity
Group PolicyAutomation Security
German versionAutomatisierungssicherheit
Intune settings catalogAutomation Security (User)
ScopeUser · HKCU
ADMXoffice16.admx · L_AutomationSecurity
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Security Settings
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Office 2016\Sicherheitseinstellungen

Registry

ValueData
HKCU\Software\policies\microsoft\office\common\security
automationsecurity3 = Disable macros by default · 2 = Use application macro security level · 1 = Macros enabled (default)

Not configured = the value does not exist – the application default applies and users may change the setting.

PowerShell

Check the current value (read-only)

# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\common\security"
foreach ($name in @('automationsecurity')) {
    try   { '{0} = {1}' -f $name, (Get-ItemPropertyValue -Path $key -Name $name -ErrorAction Stop) }
    catch { '{0}: not configured' -f $name }
}

Admin rights needed: HKCU\Software\Policies is read-only for standard users. An elevated session writes to the admin's own HKCU – to set it for another signed-in user, change $root to Registry::HKEY_USERS\<SID>.

Enable

# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

try {
    $key = "$root\Software\policies\microsoft\office\common\security"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'automationsecurity' -PropertyType DWord -Value 3 -Force -ErrorAction Stop | Out-Null   # options: 3 = Disable macros by default, 2 = Use application macro security level, 1 = Macros enabled (default)
    'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }
Reset to Not configured
# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\common\security"
Remove-ItemProperty -Path $key -Name 'automationsecurity' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Automation Security (User)

Settings catalog → Add settings → search for the name above.

Intune Settings Catalog Viewer ↗

Alternative: custom profile (OMA-URI)
OMA-URI
./User/Vendor/MSFT/Policy/Config/office16v2~Policy~L_MicrosoftOfficeSystem~L_SecuritySettings/L_AutomationSecurity
Data typeString
Value<enabled/> · <disabled/>

This policy has options: add one <data id="…" value="…"/> per element after <enabled/>. The element IDs are in the ADMX file.

Cloud Policy

Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Automation Security. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft explanation

This policy setting controls whether macros can run in an Office 2016 application that is opened programmatically by another application.

If you enable this policy setting, you can choose from three options for controlling macro behavior in Excel, PowerPoint, and Word when the application is opened programmatically:

- Disable macros by default - All macros are disabled in the programmatically opened application.

- Macros enabled (default) - Macros can run in the programmatically opened application. This option enforces the default configuration in Excel, PowerPoint, and Word.

- User application macro security level - Macro functionality is determined by the setting in the "Macro Settings" section of the Trust Center.

If you disable or do not configure this policy setting, when a separate program is used to launch Microsoft Excel, PowerPoint, or Word programmatically, any macros can run in the programmatically opened application without being blocked.

Same category: Microsoft Office 2016 › Security Settings

All policies in this category · All 945 policies of office16.admx