Trusted Catalog Location #5
Verified with Microsoft 365/Office 5568.1000 — updated on September 4, 2026
Supported on: At least Windows Server 2008 R2 or Windows 7
Path in the GPO console
User Configuration\Administrative Templates\Microsoft Office 2016\Security Settings\Trust Center\Trusted Catalogs Description
This policy setting sets the URL location of a Trusted SharePoint Catalog or Shared Folder Catalog. All web add-ins at this location are trusted so that users can work with these add-ins in their documents. However, the user cannot insert these add-ins into an Office document. If you enable this policy setting and set the URL, users can work with web add-ins from the SharePoint Catalog or Shared Folder Catalog at that URL. Shared Folder Catalogs at that URL will be ignored if the policy to allow users to control the Trusted Shared Folder Catalogs is enabled. If you disable this policy setting, users will not be able to work with any web add-ins on Internet zone catalogs, and they will be prompted before they start web add-ins from any other catalogs. If the policy to allow users to control the Trusted Shared Folder Catalogs is enabled, users can set their own Trusted Shared Folder Catalog locations and web add-ins in the their Trusted Catalogs locations will be started without a trust prompt. If you do not configure this policy setting or any other policy settings in the Trusted Catalogs folder, users can set their own Trusted Sharepoint Catalog and Shared Folder Catalog locations
Registry
software\policies\microsoft\office\16.0\wef\trustedcatalogs\catalog05 This policy sets several registry values:
id id = catalog05 flags flags = 0 Export Builder
BETAConfigure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.
These exports write the registry — this is not a managed GPO. ⓘ
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: Trusted Catalog Location #5
; State: Enabled
; Supported on: At least Windows Server 2008 R2 or Windows 7
[HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\wef\trustedcatalogs\catalog05]
"id"="catalog05"
"flags"=dword:00000000
"url"="" More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Trusted Catalog Location #5
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
# Warning: In SYSTEM context (the Intune default), HKCU targets the SYSTEM profile. Run this script using the logged-on credentials.
$path = 'HKCU:\software\policies\microsoft\office\16.0\wef\trustedcatalogs\catalog05'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'id' -Value 'catalog05' -Type String
Set-ItemProperty -Path $path -Name 'flags' -Value 0 -Type DWord
Set-ItemProperty -Path $path -Name 'url' -Value '' -Type String Intune XML
No direct Policy CSP / OMA-URI mapping for this policy. Use the Intune Remediation tab, or ingest the ADMX in Intune. Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: Trusted Catalog Location #5
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
# Warning: In SYSTEM context (the Intune default), HKCU targets the SYSTEM profile. Run this script using the logged-on credentials.
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\16.0\wef\trustedcatalogs\catalog05' -Name 'id' -Expected 'catalog05' -Kind String)
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\16.0\wef\trustedcatalogs\catalog05' -Name 'flags' -Expected 0 -Kind DWord)
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\16.0\wef\trustedcatalogs\catalog05' -Name 'url' -Expected '' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Trusted Catalog Location #5
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
# Warning: In SYSTEM context (the Intune default), HKCU targets the SYSTEM profile. Run this script using the logged-on credentials.
$path = 'HKCU:\software\policies\microsoft\office\16.0\wef\trustedcatalogs\catalog05'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'id' -Value 'catalog05' -Type String
Set-ItemProperty -Path $path -Name 'flags' -Value 0 -Type DWord
Set-ItemProperty -Path $path -Name 'url' -Value '' -Type String SCCM scripts
# Exported from gporais.com
# Policy: Trusted Catalog Location #5
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
# SCCM Configuration Item guidance:
# Create a Configuration Item of type "Setting: Script".
# Discovery script: use the Detection script below.
# Remediation script: use the Remediation script below.
# Compliance rule: the Discovery script output equals 'Compliant'.
# === Detection script ===
# Exported from gporais.com
# Policy: Trusted Catalog Location #5
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
# Warning: In SYSTEM context (the Intune default), HKCU targets the SYSTEM profile. Run this script using the logged-on credentials.
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
$checks = @(
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\16.0\wef\trustedcatalogs\catalog05' -Name 'id' -Expected 'catalog05' -Kind String)
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\16.0\wef\trustedcatalogs\catalog05' -Name 'flags' -Expected 0 -Kind DWord)
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\16.0\wef\trustedcatalogs\catalog05' -Name 'url' -Expected '' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Trusted Catalog Location #5
# State: Enabled
# Supported on: At least Windows Server 2008 R2 or Windows 7
# Warning: In SYSTEM context (the Intune default), HKCU targets the SYSTEM profile. Run this script using the logged-on credentials.
$path = 'HKCU:\software\policies\microsoft\office\16.0\wef\trustedcatalogs\catalog05'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'id' -Value 'catalog05' -Type String
Set-ItemProperty -Path $path -Name 'flags' -Value 0 -Type DWord
Set-ItemProperty -Path $path -Name 'url' -Value '' -Type String Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.