Do not allow Outlook object model scripts to run for public folders
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 | publicfolderscript |
| Group Policy | Do not allow Outlook object model scripts to run for public folders |
| German version | Outlook-Objektmodellskripts können nicht für öffentliche Ordner ausgeführt werden |
| Intune settings catalog | Do not allow Outlook object model scripts to run for public folders (User) (Deprecated) |
| Scope | User · HKCU |
| ADMX | outlk16.admx · L_DisableOutlookobjectmodelscriptsforpublicfolders |
Group Policy path
Registry
| Value | Data |
|---|---|
HKCU\Software\policies\microsoft\office\16.0\outlook\security | |
| publicfolderscript | Enabled = 0 · Disabled = 1 |
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 @('publicfolderscript')) {
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 'publicfolderscript' -PropertyType DWord -Value 0 -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 'publicfolderscript' -PropertyType DWord -Value 1 -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 'publicfolderscript' -ErrorAction SilentlyContinue 'Policy values removed (Not configured).'
Intune (settings catalog)
Do not allow Outlook object model scripts to run for public folders (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_OutlookOptions~L_Other~L_Advanced/L_DisableOutlookobjectmodelscriptsforpublicfolders |
| 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 Do not allow Outlook object model scripts to run for public folders. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.
Microsoft explanation
This policy setting controls whether Outlook executes scripts that are associated with custom forms or folder home pages for public folders.
If you enable this policy setting, Outlook cannot execute any scripts associated with public folders, overriding any configuration changes on users' computers.
If you disable this policy setting, Outlook will automatically run any scripts associated with custom forms or folder home pages for public folders, overriding any configuration changes on users' computers.
If you do not configure this policy setting, Outlook will not run any scripts associated with public folders by default. Users can configure the setting in the Trust Center by selecting the “Allow script in public folders” check box.
Same category: Microsoft Outlook 2016 › Outlook Options › Other › Advanced
- Do not allow folders in non-default stores to be set as folder home pagesnondefaultstorescript
- Prevent saving sync conflictsdiscardconflicts
- Save RSS conflictssaverssconflicts
- Save calendar sync conflictssavecalendarconflicts
- Turn on logging for all conflictsenableconflictlogging
- Minimize Outlook to the system traymintotray
- Warn before permanently deleting itemswarndelete
- Enable mail logging (troubleshooting)enablelogging
- Use Unicode format when dragging e-mail message to file systemmsgformat
- Do not allow Outlook object model scripts to run for shared folderssharedfolderscript
All policies in this category · All 406 policies of outlk16.admx