Open in the explorer

Disable connection fallback between protocols

Type
User
GPO path
User Configuration › Policies › Administrative Templates › Microsoft Outlook 2016 › Account Settings › Exchange
Supported on
At least Windows Server 2008 R2 or Windows 7
ADMX file
outlk16.admx
Internal name
outlk16/L_DisableRpcTransportFallback

Explanation

This policy setting allows you to control the connection transport fallback behavior in Outlook when it attempts to connect to a Microsoft Exchange Server.

This policy setting applies if you are using Outlook Anywhere (RPC over HTTP) to connect to a Microsoft Exchange Server. There are two Outlook profile settings on the Microsoft Exchange Proxy Settings dialog box (accessed through the Control Panel or Account Settings), that configure the default connection transport fallback behavior.

- On fast networks, connect using HTTP first, then connect using TCP/IP
- On slow networks, connect using HTTP first, then connect using TCP/IP

For example, if you are on a fast network and you enable the “On fast networks, connect using HTTP first, then connect using TCP/IP” setting in the Microsoft Exchange Proxy Settings dialog box, Outlook first attempts to connect to the Exchange Server using HTTP. If Outlook is unable to connect using HTTP, then it attempts to connect using TCP/IP.

If you enable this policy setting, if Outlook connection attempts with Microsoft Exchange Server fail, Outlook does not fallback to the TCP/IP protocol, regardless of what is specified in the Microsoft Exchange Proxy Settings dialog box.

If you disable or do not configure this policy setting, Outlook connection attempts with Microsoft Exchange Server can fallback from either TCP/IP to HTTP, or HTTP to TCP/IP, depending on the settings specified in the Microsoft Exchange Proxy Settings dialog box.

Registry

HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\outlook\rpc
Value name
disablerpctcpfallback
StateValue written
EnabledREG_DWORD = 1
DisabledREG_DWORD = 0

PowerShell

PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.

Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.

Enable

# Enable: outlk16/L_DisableRpcTransportFallback
$k = 'HKCU:\software\policies\microsoft\office\16.0\outlook\rpc'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'disablerpctcpfallback' -Value 1 -Type DWord

Disable

# Disable: outlk16/L_DisableRpcTransportFallback
$k = 'HKCU:\software\policies\microsoft\office\16.0\outlook\rpc'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'disablerpctcpfallback' -Value 0 -Type DWord

Revert to "Not configured"

# Revert to "Not configured": outlk16/L_DisableRpcTransportFallback
$k = 'HKCU:\software\policies\microsoft\office\16.0\outlook\rpc'
Remove-ItemProperty -Path $k -Name 'disablerpctcpfallback' -ErrorAction SilentlyContinue

Application

Microsoft 365 Apps / Office (Microsoft) — November 2026 templates

Official templates downloaded on November 12, 2026.