Trust legacy VBA signatures
| Registry value | trustlegacysignature |
| Group Policy | Trust legacy VBA signatures |
| German version | VBA-Legacysignaturen vertrauen |
| Intune settings catalog | Trust legacy VBA signatures (User) |
| Scope | User · HKCU |
| ADMX | office16.admx · L_TrustLegacySignature |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\vba\security | |
| trustlegacysignature | Enabled = 1 · Disabled = 0 |
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\vba\security"
foreach ($name in @('trustlegacysignature')) {
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\vba\security"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'trustlegacysignature' -PropertyType DWord -Value 1 -Force -ErrorAction Stop | Out-Null # Enabled
'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }Disable
# --- Settings ---
$root = 'HKCU:' # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'
try {
$key = "$root\Software\policies\microsoft\vba\security"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'trustlegacysignature' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null # 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\vba\security" Remove-ItemProperty -Path $key -Name 'trustlegacysignature' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Trust legacy VBA signatures (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_trustcenter241/L_TrustLegacySignature |
| Data type | String |
| Value | <enabled/> · <disabled/> |
Cloud Policy
Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Trust legacy VBA signatures. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting allows you to control how Office loads and verifies legacy Visual Basic for Applications (VBA) signatures.
If you enable or do not configure this policy setting, Office applications can load and verify legacy VBA signatures.
If you disable this policy setting, Office applications can’t load or verify legacy VBA signatures. They can only load and verify agile VBA signatures.
Same category: Microsoft Office 2016 › Security Settings › Trust Center
- Allow mix of policy and user locationsallow user locations
- Trusted Location #1path
- Trusted Location #2path
- Trusted Location #3path
- Trusted Location #4path
- Trusted Location #5path
- Trusted Location #6path
- Trusted Location #7path
- Trusted Location #8path
- Trusted Location #9path
- Trusted Location #10path
- Trusted Location #11path
All policies in this category · All 945 policies of office16.admx