Always use TNEF formatting in S/MIME messages
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 | forcetnef |
| Group Policy | Always use TNEF formatting in S/MIME messages |
| German version | Immer TNEF-Formatierung in S/MIME-Nachrichten verwenden |
| Intune settings catalog | Always use TNEF formatting in S/MIME messages (User) |
| Scope | User · HKCU |
| ADMX | outlk16.admx · L_OutlookTNEFinSMIMEmessages |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\outlook\security | |
| forcetnef | 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 @('forcetnef')) {
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 'forcetnef' -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 'forcetnef' -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 'forcetnef' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Always use TNEF formatting in S/MIME messages (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_OutlookTNEFinSMIMEmessages |
| 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 Always use TNEF formatting in S/MIME messages. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting allows you to specify the formatting when sending S/MIME messages.
If you enable this policy setting, Outlook always uses TNEF formatting when sending S/MIME messages.
If you disable or do not configure this policy setting, Outlook uses the format specified by the user when sending e-mail messages, including when sending S/MIME messages.
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
- 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
- Sign all e-mail messagesalwayssign
All policies in this category · All 406 policies of outlk16.admx