Allowed severity of self-harm content to and from the Alternative Text scenario for the user.
Explanation
This local content safety policy setting adjusts the allowed severity of self-harm content to and from the Alternative Text scenario for the user. The allowed severity may range from 0 to 7.
0 means allow no self-harm content.
7 means allow all self-harm content.
For more information on content safety severities, please refer to the following documentation:
https://learn.microsoft.com/en-us/azure/ai-services/content-safety/concepts/harm-categories?tabs=definitions
For local content safety policy, scenario-specific settings are prioritized over general settings and computer settings are prioritized over user settings.
If a higher priority policy setting is not configured, then:
- If this policy setting is not configured, the allowed severity of self-harm content to and from the Alternative Text scenario is determined by lower priority policy settings.
- If this policy setting is not configured and lower priority policy settings are also not configured, the allowed severity of self-harm content to and from the Alternative Text scenario defaults to 2.
For this policy setting, the order of priority is:
1. Allowed severity of self-harm content to and from the Alternative Text scenario for the computer.
2. Allowed severity of self-harm content in general for the computer.
3. Allowed severity of self-harm content to and from the Alternative Text scenario for the user.
4. Allowed severity of self-harm content in general for the user.
Registry
HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\common\ai\contentsafety\specific\alternativetext- 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_AllowedSelfHarmContentSpecificAlternativeTextUser
$k = 'HKCU:\software\policies\microsoft\office\16.0\common\ai\contentsafety\specific\alternativetext'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Allowed severity of self-harm content
Set-ItemProperty -Path $k -Name 'allowedselfharmcontent' -Value 2 -Type DWord # between 0 and 7Disable
# Disable: office16/L_AllowedSelfHarmContentSpecificAlternativeTextUser
# No value is written in the "Disabled" state (nothing defined in the ADMX)Revert to "Not configured"
# Revert to "Not configured": office16/L_AllowedSelfHarmContentSpecificAlternativeTextUser
$k = 'HKCU:\software\policies\microsoft\office\16.0\common\ai\contentsafety\specific\alternativetext'
Remove-ItemProperty -Path $k -Name 'allowedselfharmcontent' -ErrorAction SilentlyContinueOptions (1)
| Label | Control | Registry value | REG type | Constraints / details |
|---|---|---|---|---|
| Allowed severity of self-harm contentL_AllowedSelfHarmContentSpecificAlternativeTextUserDecimal | Numeric boxdecimal | allowedselfharmcontent | REG_DWORD | Min: 0 · Max: 7 · Default (UI): 2 |
Application
Microsoft 365 Apps / Office (Microsoft) — November 2026 templates
Official templates downloaded on November 12, 2026.