Open in the explorer

Require that application add-ins are signed by Trusted Publisher

Type
User
GPO path
User Configuration › Policies › Administrative Templates › Microsoft Publisher 2016 › Security › Trust Center
Supported on
At least Windows Server 2008 R2 or Windows 7
ADMX file
pub16.admx
Internal name
pub16/L_RequirethatApplicationExtensionsaresigned

Explanation

This policy setting controls whether add-ins for this applications must be digitally signed by a trusted publisher.

If you enable this policy setting, this application checks the digital signature for each add-in before loading it. If an add-in does not have a digital signature, or if the signature did not come from a trusted publisher, this application disables the add-in and notifies the user. Certificates must be added to the Trusted Publishers list if you require that all add-ins be signed by a trusted publisher. For detail on about obtaining and distributing certificates, see http://go.microsoft.com/fwlink/?LinkId=294922. Office 2016 stores certificates for trusted publishers in the Internet Explorer trusted publisher store. Earlier versions of Microsoft Office stored trusted publisher certificate information (specifically, the certificate thumbprint) in a special Office trusted publisher store. Office 2016 still reads trusted publisher certificate information from the Office trusted publisher store, but it does not write information to this store. Therefore, if you created a list of trusted publishers in a previous version of Office and you upgrade to Office 2016, your trusted publisher list will still be recognized. However, any trusted publisher certificates that you add to the list will be stored in the Internet Explorer trusted publisher store. For more information about trusted publishers, see the Office Resource Kit.

If you disable or do not configure this policy setting, this application does not check the digital signature on application add-ins before opening them. If a dangerous add-in is loaded, it could harm users' computers or compromise data security.

Registry

HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\publisher\security
Value name
requireaddinsig
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: pub16/L_RequirethatApplicationExtensionsaresigned
$k = 'HKCU:\software\policies\microsoft\office\16.0\publisher\security'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'requireaddinsig' -Value 1 -Type DWord

Disable

# Disable: pub16/L_RequirethatApplicationExtensionsaresigned
$k = 'HKCU:\software\policies\microsoft\office\16.0\publisher\security'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'requireaddinsig' -Value 0 -Type DWord

Revert to "Not configured"

# Revert to "Not configured": pub16/L_RequirethatApplicationExtensionsaresigned
$k = 'HKCU:\software\policies\microsoft\office\16.0\publisher\security'
Remove-ItemProperty -Path $k -Name 'requireaddinsig' -ErrorAction SilentlyContinue

Application

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

Official templates downloaded on November 12, 2026.