Office Admin Explorer

Control Blogging

Registry value
disableblog
Group PolicyControl Blogging
German versionSteuerelementbloggen
Intune settings catalogControl Blogging (User)
ScopeUser · HKCU
ADMXoffice16.admx · L_ControlBlogging
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Office 2016\Miscellaneous
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Office 2016\Verschiedenes

Registry

ValueData
HKCU\Software\policies\microsoft\office\common\blog
disableblog0 = Enabled · 1 = Only SharePoint blogs allowed · 2 = All blogging disabled

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\common\blog"
foreach ($name in @('disableblog')) {
    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\common\blog"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'disableblog' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null   # options: 0 = Enabled, 1 = Only SharePoint blogs allowed, 2 = All blogging 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\common\blog"
Remove-ItemProperty -Path $key -Name 'disableblog' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Control Blogging (User)

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/office16v2~Policy~L_MicrosoftOfficeSystem~L_miscellaneous437/L_ControlBlogging
Data typeString
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 Control Blogging. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft explanation

This policy setting controls whether users can compose and post blog entries from Word.

If you enable this policy setting, you can choose from three options for controlling blogging:

* Enabled - Users may compose and post blog entries from Word to any available blog provider. This is the default configuration in Word.

* Only SharePoint blogs allowed - Users can only post blog entries to SharePoint sites.

* Disabled - The blogging feature in Word is disabled entirely.

If you disable or do not configure this policy setting, the behavior is the equivalent of setting the policy to Enabled-Enabled.

Same category: Microsoft Office 2016 › Miscellaneous

All policies in this category · All 945 policies of office16.admx