The Hidden Costs of Staying on Project Online

Every PMO finance review shows the same line item: the Project Online subscription. For a 50-seat Plan 3 deployment it comes to roughly $18,000 per year. That number is clean, auditable, and completely misleading. The real Project Online hidden cost does not live in the renewal invoice; it lives in payroll, in support queues, and in the calendar hours project managers spend not managing projects. This post breaks down the four categories of hidden cost, quantifies each one with worked numbers, and shows what the total looks like next to the figure your CFO actually sees.

TL;DR: The four Project Online hidden cost categories

• PWA administrator labor: 0.25–0.75 FTE at $120K loaded = $30K–$90K per year
• SharePoint team overhead: 5–10% of one SharePoint admin = $6K–$14K per year
• Power BI OData maintenance: 1–3 person-days per report per quarter, 5-report portfolio = $12K–$40K per year
• PM workaround time: 2–5 hours per PM per week, 50 PMs = $60K–$150K per year
• Combined vs. invoice: $126K–$312K per year total versus $18K on the subscription line

Four Categories of Project Online hidden cost

The subscription sits at the top of a five-layer cost stack. The layers below it are real, recurring, and almost universally missing from the software budget. They run through payroll accounts, IT service queues, and discretionary project hours instead, which is exactly why they persist.

The subscription is the only number finance sees. Every other layer is absorbed somewhere else in the organization. That mismatch is the reason PMOs consistently underestimate the cost of staying put.

PWA Administrator: The Half-FTE Nobody Budgets For

Every live PWA instance requires ongoing administration. The tasks are mundane but they do not go away: user provisioning, permission group management, enterprise custom field governance, lookup table maintenance, and opening and closing timesheet periods on schedule. Most organizations assign these duties to an IT generalist or a senior PM who "knows the system," but the hours are real regardless of whose job description they fall under.

A conservative estimate is 0.25 FTE. A PMO that has customized its enterprise custom fields, runs multiple project types with separate permission groups, or has a timesheet compliance problem can easily consume 0.75 FTE. At a $120,000 loaded annual salary, that range is $30,000 to $90,000 per year.

This cost is invisible to finance because it does not appear as a software line item. It appears as salary for an employee whose time is partially consumed by tool administration. The budget owner rarely attributes it to Project Online explicitly.

Common PWA admin tasks that drive the hour count:

• Provisioning new users and assigning them to the correct security groups
• Managing enterprise project types and their associated permission groups
• Governing enterprise custom fields: adding, deprecating, and cleaning up stale values
• Maintaining lookup tables and calendar exceptions
• Opening timesheet reporting periods and chasing compliance

SharePoint Team Overhead

PWA is a SharePoint site collection. That architectural decision means the SharePoint operations team carries recurring Project Online support load whether or not they are aware of it. Common ticket categories include PWA site collection errors, permission inheritance problems, workflow failures tied to SharePoint Designer workflows, and storage quota alerts.

Most SharePoint teams do not track Project Online tickets separately, so this cost is doubly invisible: it is in payroll rather than software budget, and it is not attributed to Project Online even within the IT service catalog.

A reasonable estimate is 5 to 10 percent of one SharePoint administrator's loaded annual cost. At a $120,000 to $140,000 loaded salary range, that is $6,000 to $14,000 per year. Smaller organizations where the SharePoint admin and the PWA admin are the same person will overlap this cost, but larger environments with dedicated SharePoint operations teams carry it separately.

The Power BI Maintenance Treadmill

Project Online's native reporting is limited. Most PMOs build their portfolio dashboards and resource utilization reports in Power BI, connected to the Project Online OData feed. That connection introduces a class of maintenance cost that does not exist with a modern platform.

Three failure modes recur on a roughly quarterly cycle:

Authentication token expiry. OData connections authenticated with user credentials break when the account's password changes or multi-factor authentication policies tighten. Reports stop refreshing. Someone investigates, updates the credentials, and tests the report. That is a half-day minimum per report.

Column schema changes. Microsoft occasionally modifies the OData schema when it updates the Project Online service. A field rename or a new required filter condition silently breaks a report until someone notices the data is wrong. Diagnosis and repair typically runs one to two person-days per affected report.

Throttling. The OData endpoint is rate-limited. Large datasets or frequent scheduled refreshes hit the throttle and return empty or partial data. Working around this requires query restructuring or staggered refresh schedules, which is another category of ongoing maintenance.

For a PMO maintaining five Power BI reports against the Project Online OData feed, annual maintenance labor runs approximately $12,000 to $40,000 per year depending on report complexity and how aggressively Microsoft updates the service schema.

PM Workaround Time: What It Costs in Real Dollars

This is the largest single hidden cost category, and it is the one most likely to be dismissed as "just how Project Online works."

Project managers at organizations running Project Online routinely spend two to five hours per week on activities that exist only because the tool requires it: exporting data to Excel for resource leveling because the PWA resource sheet is too slow, building status reports manually because the reporting interface cannot be filtered to project-level granularity, reconciling plan data against actuals offline because timesheet data lags by a day, and reformatting schedule data for steering committee decks because the native views are not executive-ready.

These are not edge cases. They are the operational reality for most Project Online deployments that have been running for more than two years.

The arithmetic is straightforward. At 50 project managers spending an average of three hours per week on workarounds, at a $120,000 loaded annual salary, the annual cost is:

50 PMs × 3 hours/week × 50 weeks × ($120,000 / 2,000 hours) = $450,000 in gross labor, of which roughly $60,000 to $150,000 is attributable to workaround activity rather than actual project management.

That range reflects the variance in workaround intensity across different PMO configurations. Highly customized PWA deployments with complex permission structures sit at the top of the range. Standard deployments with mature processes sit at the bottom.

If your PMs are spending time on export-and-reformat cycles, the free Schedule Health Check surfaces schedule quality issues that are often the root cause of those workarounds. Degraded schedule quality drives more manual intervention, which drives more workaround time.

Why These Costs Rise as the September 2026 Retirement Approaches

Microsoft has confirmed that Project Online will retire on September 30, 2026. That date is driving each hidden cost category upward, not downward.

PWA admin workload is rising because retirement preparation adds to the normal task list. Admins are running data exports, documenting configurations, and fielding questions from project managers who want to know what happens to their data. None of that replaces normal admin duties; it stacks on top.

SharePoint ticket volume is increasing because aging SharePoint Designer workflows are failing more frequently as Microsoft reduces support investment in the underlying infrastructure. Workflows that ran without incident for three years are now generating tickets on a monthly basis.

Power BI maintenance costs are accelerating because the OData endpoint has become less stable as Microsoft deprioritizes service updates for a retiring product. Schema changes are less carefully communicated; authentication mechanisms are shifting.

PM workaround time is growing because Microsoft is no longer shipping fixes for known usability gaps in Project Online. Issues that would previously have been resolved in a service update are now permanent features of the tool for the remaining months of its life.

Migration consultant rates are also rising. Q3 2026 slots with experienced Project Online migration practices are filling. Organizations that wait until Q2 2026 to start are paying premium rates for accelerated timelines. The cost of ignoring the Project Online retirement deadline compounds monthly.

What Does Project Online Actually Cost to Run?

Here is a worked example for a 50-seat PMO on Project Online Plan 3, with all five cost layers quantified.

Cost Layer	Low Estimate	High Estimate	Notes
Subscription (Plan 3, 50 seats)	$18,000	$18,000	Invoice figure
PWA administrator labor	$30,000	$90,000	0.25–0.75 FTE at $120K loaded
SharePoint team overhead	$6,000	$14,000	5–10% of one SharePoint admin
Power BI OData maintenance	$12,000	$40,000	5-report portfolio, quarterly cycles
PM workaround time	$60,000	$150,000	50 PMs, 2–5 hrs/week
Total annual run cost	$126,000	$312,000

The invoice says $18,000. The real cost is $126,000 to $312,000 per year.

A one-time migration to a modern platform eliminates the PWA admin layer entirely, removes the SharePoint overhead, replaces OData-based reporting with a maintained reporting layer, and reduces PM workaround time to near zero. Migration cost varies by complexity, but for a 50-seat PMO it typically runs $40,000 to $120,000 as a one-time investment. The detailed breakdown is in the cost of migrating from MS Project Online post.

At a $126,000 annual run cost on the low end, a $120,000 migration pays back in under 12 months. At a $312,000 annual run cost on the high end, even a $200,000 migration pays back in under nine months. That is the number to put in front of a CFO. The CFO-proof business case framework covers how to structure the comparison with low/mid/high scenarios and explicit assumptions.

The hidden cost stack does not shrink as the retirement date approaches. It grows. Every month of delay is a month of full run cost with none of the benefit of a modern platform.

Run the Migration Cost Calculator for your PMO Enter your seat count, plan tier, and team size to get a low/mid/high migration estimate and compare it to your current all-in annual run cost. No signup required. Open the Migration Cost Calculator

Microsoft Project Online™ is a trademark of Microsoft Corporation. Onplana is not affiliated with Microsoft.