Office Admin Explorer

Publisher Automation Security Level

Registry value
automationsecuritypublisher
Group PolicyPublisher Automation Security Level
German versionPublisher-Automatisierungssicherheitsstufe
Intune settings catalogPublisher Automation Security Level (User)
ScopeUser · HKCU
ADMXpub16.admx · L_PublisherAutomationSecurityLevel
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Publisher 2016\Security
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Publisher 2016\Sicherheit

Registry

ValueData
HKCU\Software\policies\microsoft\office\common\security
automationsecuritypublisher1 = Low (enabled) · 2 = By UI (prompted) · 3 = High (disabled)

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 @('automationsecuritypublisher')) {
    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 'automationsecuritypublisher' -PropertyType DWord -Value 1 -Force -ErrorAction Stop | Out-Null   # options: 1 = Low (enabled), 2 = By UI (prompted), 3 = High (disabled)
    '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 'automationsecuritypublisher' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Publisher Automation Security Level (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/pub16v2~Policy~L_MicrosoftOfficePublisher~L_Security/L_PublisherAutomationSecurityLevel
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 Publisher Automation Security Level. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft explanation

This policy setting controls whether macros opened programmatically by another application can run in Publisher.

If you enable this policy setting, you may choose an option for controlling macro behavior in Publisher when the application is opened programmatically:

- Low (enabled): Macros can run in the programmatically opened application.

- By UI (prompted): Macro functionality is determined by the setting in the "Macro Settings" section of the Trust Center.

- High (disabled): All macros are disabled in the programmatically opened application.

If you disable or do not configure this policy setting, Publisher will use the default Macro setting in Trust Center.

Same category: Microsoft Publisher 2016 › Security

All policies in this category · All 41 policies of pub16.admx