Office Admin Explorer

Enable Minimizing VBA Project Digital Signature Invalidation

Registry value
minimizevbaresign
Group PolicyEnable Minimizing VBA Project Digital Signature Invalidation
German versionMinimierung des Ungültigmachens von digitalen VBA-Projektsignaturen aktivieren
Intune settings catalogEnable Minimizing VBA Project Digital Signature Invalidation (User)
ScopeUser · HKCU
ADMXoffice16.admx · L_EnableMinimizeVbaResigning
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\vba\security
minimizevbaresignEnabled = 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 @('minimizevbaresign')) {
    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 'minimizevbaresign' -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 'minimizevbaresign' -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 'minimizevbaresign' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Enable Minimizing VBA Project Digital Signature Invalidation (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_EnableMinimizeVbaResigning
Data typeString
Value<enabled/> · <disabled/>

Cloud Policy

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

Microsoft explanation

This policy setting allows you to reduce the number of actions in Office that will result in a document's VBA digital signature becoming invalidated.

The VBA project may be modified in certain ways that change the project storage but that do not invalidate the source code digital signature. With this setting turned off, these actions will lead to the VBA digital signature being invalidated, and the signature dropped on save if the user does not have the private key available to resign.

With this setting on, we will only perform a resign of the project if the source code signature has changed, and will keep the existing signature in other cases. If the VBA project storage is changed and saved, but the old signature retained under this feature, this can lead to an invalidation of the saved compiled VBA project state. If this happens, the VBA project will be forced to recompile each time the document is loaded. This may have negative performance impacts for larger VBA projects. Once a document is in this state, the state will persist until the VBA project is resigned.

Same category: Microsoft Office 2016 › Security Settings

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