Signature Warning
Classic Outlook only. The new Outlook for Windows ignores most of these Office policies – it is configured through Exchange Online (OWA mailbox policy) instead.
| Registry value | warnaboutinvalid |
| Group Policy | Signature Warning |
| German version | Signaturwarnung |
| Intune settings catalog | Signature Warning (User) (Deprecated) |
| Scope | User · HKCU |
| ADMX | outlk16.admx · L_SignatureWarning |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\outlook\security | |
| warnaboutinvalid | 0 = Let user decide if they want to be warned · 1 = Always warn about invalid signatures · 2 = Never warn about invalid signatures |
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\outlook\security"
foreach ($name in @('warnaboutinvalid')) {
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\outlook\security"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'warnaboutinvalid' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null # options: 0 = Let user decide if they want to be warned, 1 = Always warn about invalid signatures, 2 = Never warn about invalid signatures
'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\outlook\security" Remove-ItemProperty -Path $key -Name 'warnaboutinvalid' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Signature Warning (User) (Deprecated) deprecated in Intune
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/outlk16v2~Policy~L_MicrosoftOfficeOutlook~L_Security~L_Cryptography/L_SignatureWarning |
| Data type | String |
| 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 Signature Warning. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting controls how Outlook warns users about messages with invalid digital signatures.
If you enable this policy setting, you can choose from three options for controlling how Outlook users are warned about invalid signatures:
- Let user decide if they want to be warned. This option enforces the default configuration.
- Always warn about invalid signatures.
- Never warn about invalid signatures.
If you disable or do not configure this policy setting, if users open e-mail messages that include invalid digital signatures, Outlook displays a warning dialog. Users can decide whether they want to be warned about invalid signatures in the future.
Same category: Microsoft Outlook 2016 › Security › Cryptography
- Replies or forwards to signed/encrypted messages are signed/encryptednocheckonsessionsecurity
- Required Certificate Authorityrequiredca
- Minimum encryption settingsminenckey
- S/MIME interoperability with external clientsexternalsmime
- Always use TNEF formatting in S/MIME messagesforcetnef
- Message Formatsmsgformats
- Message when Outlook cannot find the digital ID to decode a messageneedencryptionstring
- Do not provide Continue option on Encryption warning dialog boxesdisablecontinueencryption
- Run in FIPS compliant modefipsmode
- Use UserIssuerSerialNumberuseissuerserialnumber
- Do not check e-mail address against address of certificates being usedsupressnamechecks
- Encrypt all e-mail messagesalwaysencrypt
All policies in this category · All 406 policies of outlk16.admx