Microsoft Office 365 Publisher 2013
Verified with Windows 11 25H2 — updated on July 30, 2026
Supported on: At least Windows Server 2008 R2 or Windows 7
Path in the GPO console
Computer Configuration\Administrative Templates\Windows Components\Microsoft User Experience Virtualization\Applications User Configuration\Administrative Templates\Windows Components\Microsoft User Experience Virtualization\Applications Description
This policy setting configures the synchronization of user settings for Microsoft Office 365 Publisher 2013. Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Publisher 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Publisher 2013 from synchronization between computers with UE-V. If you enable this policy setting, Microsoft Office 365 Publisher 2013 user settings continue to sync with UE-V. If you disable this policy setting, Microsoft Office 365 Publisher 2013 user settings are excluded from synchronization with UE-V. If you do not configure this policy setting, any defined values will be deleted.
Registry
HKLM
Software\Policies\Microsoft\UEV\Agent\Configuration\Applications HKCU
Software\Policies\Microsoft\UEV\Agent\Configuration\Applications This policy sets several registry values:
MicrosoftOffice2013Office365Win32.Publisher Enabled:
MicrosoftOffice2013Office365Win32.Publisher = 1 Disabled:
MicrosoftOffice2013Office365Win32.Publisher = 0 MicrosoftOffice2013Office365Win64.Publisher Enabled:
MicrosoftOffice2013Office365Win64.Publisher = 1 Disabled:
MicrosoftOffice2013Office365Win64.Publisher = 0 MDM / Intune (CSP)
Device
./Device/Vendor/MSFT/Policy/Config/ADMX_UserExperienceVirtualization/MicrosoftOffice365Publisher2013 User
./User/Vendor/MSFT/Policy/Config/ADMX_UserExperienceVirtualization/MicrosoftOffice365Publisher2013 Microsoft Learn documentation Mapping data: Microsoft Learn (CC BY 4.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. ⓘ
Applying both scopes creates an ambiguous configuration (computer takes precedence over user). Only do this intentionally.
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: Microsoft Office 365 Publisher 2013
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: At least Windows Server 2008 R2 or Windows 7
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\UEV\Agent\Configuration\Applications]
"MicrosoftOffice2013Office365Win32.Publisher"=dword:00000001
"MicrosoftOffice2013Office365Win64.Publisher"=dword:00000001More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Microsoft Office 365 Publisher 2013
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Windows Server 2008 R2 or Windows 7
$path = 'HKLM:\Software\Policies\Microsoft\UEV\Agent\Configuration\Applications'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'MicrosoftOffice2013Office365Win32.Publisher' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'MicrosoftOffice2013Office365Win64.Publisher' -Value 1 -Type DWordIntune XML
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/ADMX_UserExperienceVirtualization/MicrosoftOffice365Publisher2013
Data type: String
Value:
<enabled/>Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: Microsoft Office 365 Publisher 2013
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Windows Server 2008 R2 or Windows 7
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 'HKLM:\Software\Policies\Microsoft\UEV\Agent\Configuration\Applications' -Name 'MicrosoftOffice2013Office365Win32.Publisher' -Expected 1 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\UEV\Agent\Configuration\Applications' -Name 'MicrosoftOffice2013Office365Win64.Publisher' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Microsoft Office 365 Publisher 2013
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Windows Server 2008 R2 or Windows 7
$path = 'HKLM:\Software\Policies\Microsoft\UEV\Agent\Configuration\Applications'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'MicrosoftOffice2013Office365Win32.Publisher' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'MicrosoftOffice2013Office365Win64.Publisher' -Value 1 -Type DWordSCCM scripts
# Exported from gporais.com
# Policy: Microsoft Office 365 Publisher 2013
# State: Enabled
# Scope: Computer (HKLM)
# 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: Microsoft Office 365 Publisher 2013
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Windows Server 2008 R2 or Windows 7
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 'HKLM:\Software\Policies\Microsoft\UEV\Agent\Configuration\Applications' -Name 'MicrosoftOffice2013Office365Win32.Publisher' -Expected 1 -Kind DWord)
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\UEV\Agent\Configuration\Applications' -Name 'MicrosoftOffice2013Office365Win64.Publisher' -Expected 1 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Microsoft Office 365 Publisher 2013
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: At least Windows Server 2008 R2 or Windows 7
$path = 'HKLM:\Software\Policies\Microsoft\UEV\Agent\Configuration\Applications'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'MicrosoftOffice2013Office365Win32.Publisher' -Value 1 -Type DWord
Set-ItemProperty -Path $path -Name 'MicrosoftOffice2013Office365Win64.Publisher' -Value 1 -Type DWordBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.