Set Outlook object model custom actions execution prompt
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 | promptoomcustomaction |
| Group Policy | Set Outlook object model custom actions execution prompt |
| German version | Ausführungseingabeaufforderung für Outlook-Objektmodell 'Benutzerdefinierte Aktionen' festlegen |
| Intune settings catalog | Set Outlook object model custom actions execution prompt (User) (Deprecated) |
| Scope | User · HKCU |
| ADMX | outlk16.admx · L_OnExecuteCustomActionOOM |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\outlook\security | |
| promptoomcustomaction | 1 = Prompt User · 2 = Automatically Approve · 0 = Automatically Deny · 3 = Prompt user based on computer security |
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 @('promptoomcustomaction')) {
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 'promptoomcustomaction' -PropertyType DWord -Value 1 -Force -ErrorAction Stop | Out-Null # options: 1 = Prompt User, 2 = Automatically Approve, 0 = Automatically Deny, 3 = Prompt user based on computer security
'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 'promptoomcustomaction' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Set Outlook object model custom actions execution prompt (User) (Deprecated) deprecated in Intune
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_SecurityFormsettings~L_MiscCustomFormSettings/L_OnExecuteCustomActionOOM |
| 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 Set Outlook object model custom actions execution prompt. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting controls whether Outlook prompts users before executing a custom action. Custom actions add functionality to Outlook that can be triggered as part of a rule. Among other possible features, custom actions can be created that reply to messages in ways that circumvent the Outlook model's programmatic send protections.
If you enable this policy setting, you can choose from four options to control how Outlook functions when a custom action is executed that uses the Outlook object model:
* Prompt User
* Automatically Approve
* Automatically Deny
* Prompt user based on computer security. This option enforces the default configuration in Outlook.
If you disable or do not configure this policy setting, when Outlook or another program initiates a custom action using the Outlook object model, users are prompted to allow or reject the action. If this configuration is changed, malicious code can use the Outlook object model to compromise sensitive information or otherwise cause data and computing resources to be at risk. This is the equivalent of choosing Enabled -- Prompt user based on computer security.
Same category: Microsoft Outlook 2016 › Security › Security Form Settings › Custom Form Security
- Allow scripts in one-off Outlook formsenableoneoffformscripts
All policies in this category · All 406 policies of outlk16.admx