Office Admin Explorer

Configure legacy DSA public key size

Registry value
legacydsabits
Group PolicyConfigure legacy DSA public key size
German versionGröße für öffentlichen DSA-Vorversionsschlüssel konfigurieren
Intune settings catalogConfigure legacy DSA public key size (User)
ScopeUser · HKCU
ADMXoffice16.admx · L_SelectDigitalSignatureLegacyDSABits
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Security Settings\Digital Signatures
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Office 2016\Sicherheitseinstellungen\Digitale Signaturen

Registry

ValueData
HKCU\Software\policies\microsoft\office\16.0\common\signatures
legacydsabits0 = 0 · 512 = 512 · 768 = 768 · 1024 = 1024

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\16.0\common\signatures"
foreach ($name in @('legacydsabits')) {
    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\16.0\common\signatures"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'legacydsabits' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null   # options: 0 = 0, 512 = 512, 768 = 768, 1024 = 1024
    '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\16.0\common\signatures"
Remove-ItemProperty -Path $key -Name 'legacydsabits' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Configure legacy DSA public key size (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_DigSig/L_SelectDigitalSignatureLegacyDSABits
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 Configure legacy DSA public key size. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft explanation

This policy setting allows you to configure whether Office displays a digital signature as legacy because of the number of DSA public key bits used in the digital signature.

If you enable this policy setting, you can specify the number of bits that Office treats as legacy in a digital signature. For example: 512, 768, etc.

If you don’t configure this policy setting, Office won’t treat any digital signatures as legacy because of the number of bits in the public key.

Enabling this policy causes the minimum DSA public key size to be the next largest option.

Same category: Microsoft Office 2016 › Security Settings › Digital Signatures

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