Use the Sensitivity feature in Office to apply and view sensitivity labels
Verified with Microsoft 365/Office 5568.1000 — updated on September 4, 2026
Supported on: At least Windows Server 2016, Windows 10
Path in the GPO console
User Configuration\Administrative Templates\Microsoft Office 2016\Security Settings Description
This policy setting controls whether sensitivity labels configured by an admin can be applied and viewed by using sensitivity labels in an Office app, such as Word. It applies only to subscription versions of Office, such as Microsoft 365 Apps for enterprise. This setting has been updated for newer versions of M365 Apps. For more information about this setting and how it applies to versions of M365 Apps, see https://go.microsoft.com/fwlink/p/?linkid=2207430. For newer versions of M365 Apps: If you enable this policy setting, or don’t configure this policy setting, sensitivity labels that are built into Office apps can be used to apply and view sensitivity labels. If you disable this policy setting, sensitivity labels that are built into Office apps can’t be used to apply or view sensitivity labels. If the Microsoft Azure Information Protection unified labeling client is installed and you want to use the add-in from that client for labeling, you must also configure the policy setting "Use the Azure Information Protection add-in for sensitivity labeling". For prior versions: If you enable this policy setting, labels built into Office apps can be used to apply and view sensitivity labels. If the Microsoft Azure Information Protection unified labeling client is installed, we also recommend you block that client’s add-in from loading in Word, Excel, PowerPoint, and Outlook. If you disable this policy setting, or don’t configure this policy setting, labels built into Office apps can’t be used to apply and view sensitivity labels. If the Microsoft Azure Information Protection unified labeling client is installed, the add-in from that client can be used to apply and view sensitivity labels in Office apps.
Registry
software\policies\microsoft\office\16.0\common\security\labels Value name: useofficeforlabelling
Enabled: useofficeforlabelling = 1
Disabled: useofficeforlabelling = 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: Use the Sensitivity feature in Office to apply and view sensitivity labels
; State: Enabled
; Supported on: At least Windows Server 2016, Windows 10
[HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\common\security\labels]
"useofficeforlabelling"=dword:00000001More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Use the Sensitivity feature in Office to apply and view sensitivity labels
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
# 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\common\security\labels'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'useofficeforlabelling' -Value 1 -Type DWordIntune 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: Use the Sensitivity feature in Office to apply and view sensitivity labels
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
# 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\common\security\labels' -Name 'useofficeforlabelling' -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: Use the Sensitivity feature in Office to apply and view sensitivity labels
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
# 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\common\security\labels'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'useofficeforlabelling' -Value 1 -Type DWordSCCM scripts
# Exported from gporais.com
# Policy: Use the Sensitivity feature in Office to apply and view sensitivity labels
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
# 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: Use the Sensitivity feature in Office to apply and view sensitivity labels
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
# 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\common\security\labels' -Name 'useofficeforlabelling' -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: Use the Sensitivity feature in Office to apply and view sensitivity labels
# State: Enabled
# Supported on: At least Windows Server 2016, Windows 10
# 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\common\security\labels'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'useofficeforlabelling' -Value 1 -Type DWordBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.