Message Formats
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 | msgformats |
| Group Policy | Message Formats |
| German version | Nachrichtenformate |
| Intune settings catalog | Message Formats (User) |
| Scope | User · HKCU |
| ADMX | outlk16.admx · L_MessageFormats |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\outlook\security | |
| msgformats | 1 = S/MIME · 2 = Exchange · 20 = Fortezza · 3 = S/MIME and Exchange · 21 = S/MIME and Fortezza · 22 = Exchange and Fortezza · 23 = S/MIME, Exchange, and Fortezza |
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 @('msgformats')) {
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 'msgformats' -PropertyType DWord -Value 1 -Force -ErrorAction Stop | Out-Null # options: 1 = S/MIME, 2 = Exchange, 20 = Fortezza, 3 = S/MIME and Exchange, 21 = S/MIME and Fortezza, 22 = Exchange and Fortezza, 23 = S/MIME, Exchange, and Fortezza
'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 'msgformats' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Message Formats (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_MessageFormats |
| 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 Message Formats. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting controls which message encryption formats Outlook can use. Outlook supports three formats for encrypting and signing messages: S/MIME, Exchange, and Fortezza.
If you enable this policy setting, you can specify whether Outlook can use S/MIME (the default), Exchange, or Fortezza encryption, or any combination of any of these options. Users will not be able to change this configuration.
If you disable or do not configure this policy setting, Outlook only uses S/MIME to encrypt and sign messages. If you disable this policy setting, users will not be able to change this configuration.
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 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