Check for the user's private key when the user sends an encrypted email that includes the user as a recipient
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 | allowprivatekeycheck |
| Group Policy | Check for the user's private key when the user sends an encrypted email that includes the user as a recipient |
| German version | Auf den privaten Schlüssel des Benutzers überprüfen, wenn dieser eine verschlüsselte E-Mail sendet, die den Benutzer als Empfänger enthält |
| Intune settings catalog | Check for the user's private key when the user sends an encrypted email that includes the user as a recipient (User) |
| Scope | User · HKCU |
| ADMX | outlk16.admx · L_AllowPrivateKeyCheck |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\outlook\security | |
| allowprivatekeycheck | 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 @('allowprivatekeycheck')) {
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 'allowprivatekeycheck' -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 'allowprivatekeycheck' -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 'allowprivatekeycheck' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Check for the user's private key when the user sends an encrypted email that includes the user as a recipient (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/outlk16v5~Policy~L_MicrosoftOfficeOutlook~L_Security~L_Cryptography/L_AllowPrivateKeyCheck |
| 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 Check for the user's private key when the user sends an encrypted email that includes the user as a recipient. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting controls whether Outlook checks for the user's private key when the user sends an encrypted email and the user is included as a recipient of the email. The user can be included as recipient either directly or as a member of a distribution list.
If you enable this policy setting, Outlook checks for the user's private key.
If you disable this policy setting, Outlook doesn't check for the user's private key.
If you don't configure this policy setting, Outlook checks for the user's private key.
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