Office Admin Explorer

Fiscal year starts in

Registry value
fiscal year starts in
Group PolicyFiscal year starts in
German versionAnfang des Geschäftsjahrs im
Intune settings catalogFiscal year starts in (User)
ScopeUser · HKCU
ADMXproj16.admx · L_PjFiscalYear
Open in the interactive explorer+ Add to my collection

Group Policy path

User Configuration\Policies\Administrative Templates\Microsoft Project 2016\Project Options\Calendar
Benutzerkonfiguration\Richtlinien\Administrative Vorlagen\Microsoft Project 2016\Projektoptionen\Kalender

Registry

ValueData
HKCU\Software\policies\microsoft\office\16.0\ms project\options\calendar
fiscal year starts in1 = January · 2 = February · 3 = March · 4 = April · 5 = May · 6 = June · 7 = July · 8 = August · 9 = September · 10 = October · 11 = November · 12 = December

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 = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\calendar"
foreach ($name in @('fiscal year starts in')) {
    try   { '{0} = {1}' -f $name, (Get-ItemPropertyValue -Path $key -Name $name -ErrorAction Stop) }
    catch { '{0}: not configured' -f $name }
}

Admin rights needed: HKCU\Software\Policies is read-only for standard users. An elevated session writes to the admin's own HKCU – to set it for another signed-in user, change $root to Registry::HKEY_USERS\<SID>.

Enable

# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

try {
    $key = "$root\Software\policies\microsoft\office\16.0\ms project\options\calendar"
    if (-not (Test-Path $key)) { New-Item -Path $key -Force -ErrorAction Stop | Out-Null }
    New-ItemProperty -Path $key -Name 'fiscal year starts in' -PropertyType DWord -Value 1 -Force -ErrorAction Stop | Out-Null   # options: 1 = January, 2 = February, 3 = March, 4 = April, 5 = May, 6 = June, 7 = July, 8 = August, 9 = September, 10 = October, 11 = November, 12 = December
    'Done.'
}
catch { Write-Error "Failed: $($_.Exception.Message)" }
Reset to Not configured
# --- Settings ---
$root = 'HKCU:'   # other signed-in user (elevated): 'Registry::HKEY_USERS\<SID>'

$key = "$root\Software\policies\microsoft\office\16.0\ms project\options\calendar"
Remove-ItemProperty -Path $key -Name 'fiscal year starts in' -ErrorAction SilentlyContinue
'Policy values removed (Not configured).'

Intune (settings catalog)

Fiscal year starts in (User)

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

Intune Settings Catalog Viewer ↗

Alternative: custom profile (OMA-URI)
OMA-URI
./User/Vendor/MSFT/Policy/Config/proj16v2~Policy~L_Proj~L_ProjectOptions~L_PjCalendar/L_PjFiscalYear
Data typeString
Value<enabled/> · <disabled/>

This policy has options: add one <data id="…" value="…"/> per element after <enabled/>. The element IDs are in the ADMX file.

Cloud Policy

Cloud Policy (config.office.com → Customization → Policy Management) offers many user policies of the Microsoft 365 Apps – search for Fiscal year starts in. It also applies to unmanaged devices and wins over GPO and Intune for the same setting.

Microsoft explanation

Specifies the month that begins the fiscal year.

If you enable this setting, the fiscal year will start on the month you specified.

If you disable or do not configure this setting, the user's default setting is used.

Same category: Microsoft Project 2016 › Project Options › Calendar

All policies in this category · All 140 policies of proj16.admx