Promote Level 2 errors as errors, not warnings
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 | promoteerrorsaswarnings |
| Group Policy | Promote Level 2 errors as errors, not warnings |
| German version | Fehler der Ebene 2 als Fehler, nicht als Warnungen, höher stufen |
| Intune settings catalog | Promote Level 2 errors as errors, not warnings (User) |
| Scope | User · HKCU |
| ADMX | outlk16.admx · L_Promotingerrorsaswarnings |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\outlook\security | |
| promoteerrorsaswarnings | 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\office\16.0\outlook\security"
foreach ($name in @('promoteerrorsaswarnings')) {
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 'promoteerrorsaswarnings' -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\office\16.0\outlook\security"
if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
New-ItemProperty -Path $key -Name 'promoteerrorsaswarnings' -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\office\16.0\outlook\security" Remove-ItemProperty -Path $key -Name 'promoteerrorsaswarnings' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Promote Level 2 errors as errors, not warnings (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/outlk16v2~Policy~L_MicrosoftOfficeOutlook~L_Security~L_Cryptography~L_SignatureStatusDialog/L_Promotingerrorsaswarnings |
| 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 Promote Level 2 errors as errors, not warnings. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting allows you to treat Level 2 errors as warnings instead of errors. Level 2 errors occur when the message signature appears to be valid, but there are other issues with the signature.
If you enable this policy setting, Level 2 errors will be treated as warnings.
If you disable or do not configure this policy setting, Level 2 errors will be treated as errors
When you specify a value for PromoteErrorsAsWarnings, note that potential Level 2 error conditions include the following:
- Unknown Signature Algorithm
- No Signing Certification Found
- Bad Attribute Sets
- No Issuer Certificate found
- No CRL Found
- Out-of-date CRL
- Root Trust Problem
- Out-of-date CTL
Same category: Microsoft Outlook 2016 › Security › Cryptography › Signature Status dialog box
- Retrieving CRLs (Certificate Revocation Lists)usecrlchasing
- Missing CRLssigstatusnocrl
- Missing root certificatessigstatusnotrustdecision
- Attachment Secure Temporary Folderoutlooksecuretempfolder
All policies in this category · All 406 policies of outlk16.admx