Office Admin Explorer

Upgrade Office 2019 to Microsoft 365 Apps for enterprise

Registry value
vltosubscription
Group PolicyUpgrade Office 2019 to Microsoft 365 Apps for enterprise
German versionUpgrade von Office 2019 auf Microsoft 365 Apps for Enterprise
Intune settings catalogUpgrade Office 2019 to Office 365 ProPlus
ScopeComputer · HKLM
ADMXoffice16.admx · L_VLtoSubscription
Open in the interactive explorer+ Add to my collection

Group Policy path

Computer Configuration\Policies\Administrative Templates\Microsoft Office 2016 (Machine)\Updates
Computerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Office 2016 (Computer)\Aktualisierungen

Registry

ValueData
HKLM\Software\policies\microsoft\office\16.0\common\officeupdate
vltosubscriptionEnabled = 1 · Disabled = 0

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 = 'HKLM:'   # needs an elevated session

$key = "$root\Software\policies\microsoft\office\16.0\common\officeupdate"
foreach ($name in @('vltosubscription')) {
    try   { '{0} = {1}' -f $name, (Get-ItemPropertyValue -Path $key -Name $name -ErrorAction Stop) }
    catch { '{0}: not configured' -f $name }
}

Admin rights needed: HKLM values require an elevated PowerShell.

Enable

# --- Settings ---
$root = 'HKLM:'   # needs an elevated session

try {
    $key = "$root\Software\policies\microsoft\office\16.0\common\officeupdate"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'vltosubscription' -PropertyType DWord -Value 1 -Force -ErrorAction Stop | Out-Null   # Enabled
    'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }
Disable
# --- Settings ---
$root = 'HKLM:'   # needs an elevated session

try {
    $key = "$root\Software\policies\microsoft\office\16.0\common\officeupdate"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'vltosubscription' -PropertyType DWord -Value 0 -Force -ErrorAction Stop | Out-Null   # Disabled
    'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }
Reset to Not configured
# --- Settings ---
$root = 'HKLM:'   # needs an elevated session

$key = "$root\Software\policies\microsoft\office\16.0\common\officeupdate"
Remove-ItemProperty -Path $key -Name 'vltosubscription' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Upgrade Office 2019 to Office 365 ProPlus

Settings catalog → Add settings → search for the name above.

Intune Settings Catalog Viewer ↗

Alternative: custom profile (OMA-URI)
OMA-URI
./Device/Vendor/MSFT/Policy/Config/office16v2~Policy~L_MicrosoftOfficemachine~L_Updates/L_VLtoSubscription
Data typeString
Value<enabled/> · <disabled/>

Cloud Policy

Not available: Cloud Policy only applies user policies, this is a computer policy (HKLM).

Microsoft explanation

This policy setting allows you to upgrade volume licensed versions of Office Professional Plus 2019 to Microsoft 365 Apps for enterprise.

Note: For the user to be able to use Microsoft 365 Apps for enterprise, you must have purchased an Office 365 or Microsoft 365 plan that includes Microsoft 365 Apps for enterprise, and you must have assigned the user a license to use Microsoft 365 Apps for enterprise.

If you enable this policy setting, the installed volume licensed version of Office 2019 on the user's computer will be upgraded to Microsoft 365 Apps for enterprise. We also recommend that you use Group Policy to specify an update path and an update channel for Microsoft 365 Apps for enterprise.

Note: If there are volume licensed versions of Visio and Project on the user's computer, those won't be upgraded to subscription versions of Visio and Project.

If you disable or don't configure this policy setting, Office 2019 isn't automatically upgraded to Microsoft 365 Apps for enterprise. But, you can initiate the upgrade by using some other method, such as by using the Office Deployment Tool.

Same category: Microsoft Office 2016 (Machine) › Updates

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