Run in FIPS compliant mode
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 | fipsmode |
| Group Policy | Run in FIPS compliant mode |
| German version | Im FIPS-kompatiblen Modus ausführen |
| Intune settings catalog | Run in FIPS compliant mode (User) |
| Scope | User · HKCU |
| ADMX | outlk16.admx · L_RuninFIPScompliantmode |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\outlook\security | |
| fipsmode | 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 @('fipsmode')) {
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 'fipsmode' -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 'fipsmode' -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 'fipsmode' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Run in FIPS compliant mode (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_RuninFIPScompliantmode |
| 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 Run in FIPS compliant mode. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting controls whether Outlook is required to use FIPS-compliant algorithms when signing and encrypting messages. Outlook can run in a mode that complies with Federal Information Processing Standards (FIPS), a set of standards published by the National Institute of Standards and Technology (NIST) for use by non-military United States government agencies and by government contractors.
If you enable this policy setting, Outlook runs in a mode that complies with the FIPS 140-1 standard for cryptographic modules. This mode requires the use of the SHA-1 algorithm for signing and 3DES for encryption.
If you disable or do not configure this policy setting, Outlook does not run in FIPS-compliant mode. Organizations that do business with the United States government but do not run Outlook in FIPS-compliant mode risk violating the U.S. government's rules regarding the handling of sensitive information.
For more information about FIPS, see FIPS - General Information at http://www.itl.nist.gov/fipspubs/geninfo.htm
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
- 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