Specify custom labels to use with the Readiness Toolkit
Explanation
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
HKEY_CURRENT_USER\software\policies\microsoft\office\readinesstoolkit- Value name
- not defined in the ADMX
Enable / disable values: not defined in the ADMX (see the options below).
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: office16/L_OfficeReadinessToolkitCustomTags
$k = 'HKCU:\software\policies\microsoft\office\readinesstoolkit'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Label 1
Set-ItemProperty -Path $k -Name 'tag1' -Value '<value>' -Type String
# Label 2
Set-ItemProperty -Path $k -Name 'tag2' -Value '<value>' -Type String
# Label 3
Set-ItemProperty -Path $k -Name 'tag3' -Value '<value>' -Type String
# Label 4
Set-ItemProperty -Path $k -Name 'tag4' -Value '<value>' -Type StringDisable
# Disable: office16/L_OfficeReadinessToolkitCustomTags
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": office16/L_OfficeReadinessToolkitCustomTags
$k = 'HKCU:\software\policies\microsoft\office\readinesstoolkit'
Remove-ItemProperty -Path $k -Name 'tag1' -ErrorAction SilentlyContinue
Remove-ItemProperty -Path $k -Name 'tag2' -ErrorAction SilentlyContinue
Remove-ItemProperty -Path $k -Name 'tag3' -ErrorAction SilentlyContinue
Remove-ItemProperty -Path $k -Name 'tag4' -ErrorAction SilentlyContinueOptions (4)
| Label | Control | Registry value | REG type | Constraints / details |
|---|---|---|---|---|
| Label 1:L_OfficeReadinessToolkitCustomTagsTag1 | Text boxtext | tag1 | REG_SZ | Max length: 64 |
| Label 2:L_OfficeReadinessToolkitCustomTagsTag2 | Text boxtext | tag2 | REG_SZ | Max length: 64 |
| Label 3:L_OfficeReadinessToolkitCustomTagsTag3 | Text boxtext | tag3 | REG_SZ | Max length: 64 |
| Label 4:L_OfficeReadinessToolkitCustomTagsTag4 | Text boxtext | tag4 | REG_SZ | Max length: 64 |
Application
Microsoft 365 Apps / Office (Microsoft) — November 2026 templates
Official templates downloaded on November 12, 2026.