Specify custom labels to use with the Readiness Toolkit
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\Readiness Toolkit Description
This policy setting allows you to specify up to four custom labels to categorize and filter data in reports created by the Readiness Toolkit for Office. Labels are available in reports that are based on scans of the most recently used Office documents and installed add-ins on the user’s computer. You can specify any string for the custom labels. For example, you can use a label to indicate the user’s department, title, or geographic location. When the Readiness Toolkit runs on the user’s computer, the custom labels are collected and are made available in the reports that are created. For example, you can filter the report to show only data from the Finance Department. Assign labels in a consistent manner, such as always using Label 1 for department. If you enable this policy setting, the custom labels that you specify will be available in reports created by the Readiness Toolkit. If you disable or don’t configure this policy setting, custom labels won’t be available in reports created by the Readiness Toolkit. Note: If you're using the Office Telemetry Dashboard and have already configured tags (labels), the Readiness Toolkit automatically collects those labels during its scan of the user's computer and will make them available in its reports. You don't need to enable this policy setting unless you want to specify different labels. Labels you specify for the Readiness Toolkit won't appear in the Office Telemetry Dashboard.
Registry
software\policies\microsoft\office\readinesstoolkit 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: Specify custom labels to use with the Readiness Toolkit
; State: Enabled
; Supported on: At least Windows Server 2008 R2 or Windows 7
[HKEY_CURRENT_USER\software\policies\microsoft\office\readinesstoolkit]
"tag1"=""
"tag2"=""
"tag3"=""
"tag4"=""More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Specify custom labels to use with the Readiness Toolkit
# 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\readinesstoolkit'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'tag1' -Value '' -Type String
Set-ItemProperty -Path $path -Name 'tag2' -Value '' -Type String
Set-ItemProperty -Path $path -Name 'tag3' -Value '' -Type String
Set-ItemProperty -Path $path -Name 'tag4' -Value '' -Type StringIntune 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: Specify custom labels to use with the Readiness Toolkit
# 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\readinesstoolkit' -Name 'tag1' -Expected '' -Kind String)
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\readinesstoolkit' -Name 'tag2' -Expected '' -Kind String)
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\readinesstoolkit' -Name 'tag3' -Expected '' -Kind String)
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\readinesstoolkit' -Name 'tag4' -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: Specify custom labels to use with the Readiness Toolkit
# 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\readinesstoolkit'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'tag1' -Value '' -Type String
Set-ItemProperty -Path $path -Name 'tag2' -Value '' -Type String
Set-ItemProperty -Path $path -Name 'tag3' -Value '' -Type String
Set-ItemProperty -Path $path -Name 'tag4' -Value '' -Type StringSCCM scripts
# Exported from gporais.com
# Policy: Specify custom labels to use with the Readiness Toolkit
# 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: Specify custom labels to use with the Readiness Toolkit
# 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\readinesstoolkit' -Name 'tag1' -Expected '' -Kind String)
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\readinesstoolkit' -Name 'tag2' -Expected '' -Kind String)
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\readinesstoolkit' -Name 'tag3' -Expected '' -Kind String)
(Test-RegistryValue -Path 'HKCU:\software\policies\microsoft\office\readinesstoolkit' -Name 'tag4' -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: Specify custom labels to use with the Readiness Toolkit
# 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\readinesstoolkit'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'tag1' -Value '' -Type String
Set-ItemProperty -Path $path -Name 'tag2' -Value '' -Type String
Set-ItemProperty -Path $path -Name 'tag3' -Value '' -Type String
Set-ItemProperty -Path $path -Name 'tag4' -Value '' -Type StringBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.