The Project Online Landscape in 2026
Microsoft's project management portfolio has undergone significant consolidation since 2020. Project Online — the SharePoint-hosted, legacy cloud project management platform — coexists with Project for the web (the modern, Dataverse-backed platform) and the newly unified Microsoft Planner. Understanding which platform is appropriate for which use case, and which licence covers which platform, is prerequisite to any commercial decision about Microsoft project management licensing.
The headline fact that most procurement teams do not know: Project Online and Project for the web are different products, licensed under the same plan names. A Project Plan 3 licence covers both Project for the web and Project Online access. But the two platforms have different architectural foundations, different capability profiles, and different migration implications — and Microsoft's product roadmap investment is heavily weighted toward Project for the web, not Project Online.
This matters commercially because organisations that purchased Project Online licences years ago are frequently paying for a platform that Microsoft is de-emphasising, when a migration to Project for the web (included in the same plan) would provide a better capability-to-cost ratio and a stronger long-term foundation.
Project Online vs Project for the web: Project Online is the legacy platform — SharePoint-based, complex, feature-rich for traditional project management. Project for the web is the modern platform — Dataverse-backed, Teams-integrated, simpler to use, and the platform receiving Microsoft's active development investment. Both are included in Project Plan 3 and Plan 5 licences. For new deployments in 2026, Project for the web should be the default choice unless specific Project Online features (like earned value management or on-premises Project Server integration) are required.
Project Online Plan Comparison
Project Online has three subscription plans. Each is a superset of the previous, but the commercial logic for each tier differs significantly in practice.
| Plan | List Price | EA Price (approx) | Key Capabilities | Best For |
|---|---|---|---|---|
| Project Online Essentials | ~£7.70/user/month | ~£5.80–6.50/user/month | Task management, timesheet submission, team collaboration, read project schedules | Team members who need to submit timesheets and view project status — not build or manage projects |
| Project Online Professional (Plan 3) | ~£21.60/user/month | ~£16.30–18.50/user/month | All Essentials + full project creation and management, resource management, Project desktop client | Project managers who create, build, and manage projects full-time |
| Project Online Premium (Plan 5) | ~£30.50/user/month | ~£22.80–26.00/user/month | All Professional + portfolio management, resource optimisation (demand management), advanced analytics, Project Server integration | Portfolio managers and PMO leadership requiring portfolio-level analysis and demand management |
The Essentials Tier: Frequently Underused
Project Online Essentials is the most commonly overlooked tier. At approximately £5.80–6.50/user/month at EA pricing, it provides sufficient capability for the majority of project team members — people who need to view project plans, update task status, submit timesheets, and participate in project discussions. They do not need to create or manage projects; they need to be active participants in projects managed by others.
In most enterprise project portfolios, 60–70% of Project Online users are team members in this category, not project managers. Yet the majority of organisations licence their entire project user population at Professional or Premium tier — paying 2.5–4x more than required for the majority of users.
The Essentials-to-Professional cost differential for a 500-user Project Online deployment is significant: if 350 users are team members who need Essentials, the annual saving from correct tiering is approximately (£18.50 − £6.50) × 350 × 12 = £50,400/year. Over a three-year EA term: £151,200 — without any reduction in capability for the users involved.
The Professional Tier (Plan 3): The Core PM Licence
Project Online Professional (now called Project Plan 3) is the primary licence for project managers who create, build, and actively manage project schedules. It includes the Project desktop client — which many organisations assume is the primary justification for the higher price, but which is frequently underutilised by PMs who primarily work in the web interface.
The Plan 3 licence also includes access to Project for the web — meaning organisations that have already migrated to Project for the web are paying for the Project Online platform they no longer use. This does not represent waste in the same sense as an unused licence (the licence covers both platforms), but it does mean that the desktop client entitlement — which is the primary premium justification for Plan 3 over Planner Premium — is delivering less value for the incremental cost than it appears.
The Premium Tier (Plan 5): Justified for Portfolio Management Only
Project Online Premium (Plan 5) adds portfolio management and advanced resource demand management to the Professional capabilities. These are specifically relevant to PMO leadership managing a portfolio of projects across the organisation — evaluating which proposed projects to approve based on resource availability and strategic priority, optimising resource allocation across active projects at portfolio scale, and performing earned value analysis for project performance reporting.
In most enterprises, fewer than 15–20 individuals require Plan 5 capabilities. The remaining Project Online users — project managers and team members — are best served by Plan 3 and Essentials respectively. Blanket Plan 5 deployment for all project management staff is one of the most consistent instances of Microsoft project management over-spend we observe in client engagements.
Project Online vs Planner Premium: The Emerging Substitution
The 2024 consolidation of Microsoft Planner introduced Planner Premium (formerly Project for the web standalone) at approximately £8.30/user/month — positioned explicitly as a lighter-weight project management tool that sits between basic task management and full Project Online functionality.
Planner Premium provides: Gantt charts, dependencies, baselines, sprint planning, custom fields, timeline views, and Teams integration. It does not provide: the Project desktop client, full resource management, portfolio management, earned value reporting, or Project Online/Project Server integration.
For organisations whose project management needs are primarily at the team-level — individual project tracking, agile sprint management, simple Gantt scheduling — Planner Premium at £8.30/user/month represents a 55% cost reduction versus Project Plan 3 at £18.50/user/month at EA pricing. The substitution is not appropriate for all users, but for the population of "project managers" who run relatively simple projects and do not use advanced scheduling or resource management features, Planner Premium is frequently the commercially optimal choice.
| Feature | Planner Basic (M365 included) | Planner Premium (~£8.30) | Project Plan 3 (~£18.50) | Project Plan 5 (~£26.00) |
|---|---|---|---|---|
| Basic task management | Yes | Yes | Yes | Yes |
| Gantt chart | No | Yes | Yes | Yes |
| Dependencies & baselines | No | Yes | Yes | Yes |
| Resource management | No | Basic | Full (Project Online) | Full + demand management |
| Project desktop client | No | No | Yes | Yes |
| Portfolio management | No | No | No | Yes |
| Project Server integration | No | No | Via Project Online | Yes |
| Copilot for Project | No | No | Requires M365 Copilot add-on | Requires M365 Copilot add-on |
The Project Online to Project for the Web Migration Consideration
Microsoft's active development platform is Project for the web, not Project Online. New features — Teams integration, Copilot capabilities, improved reporting — are being built into Project for the web. Project Online receives security patches and maintenance but is not receiving new capability investment at the same pace.
Organisations running Project Online today have a migration decision to make, and that decision has licensing implications. Project for the web is included in the same Plan 3 and Plan 5 licences as Project Online — there is no additional licence cost for migration. However, Project for the web stores data in Dataverse rather than SharePoint, which means migration from Project Online to Project for the web requires data migration work and generates Dataverse storage consumption.
For licensing purposes, the migration decision affects two cost drivers. First, Dataverse storage: Project for the web stores project data in Dataverse, consuming database and file storage that may require add-on capacity depending on project volume and data retention policies. Second, the Project desktop client: if project managers migrate from Project Online (where the desktop client is heavily used) to Project for the web (which is browser-only), the justification for Plan 3 over Planner Premium weakens for a subset of the PM population.
Project Online End of Life planning: Microsoft has signalled that Project Online is on a maintenance path rather than an investment path. While there is no announced End of Life date for Project Online as of early 2026, organisations with significant Project Online deployments should be planning their migration to Project for the web within the next 24–36 months. Waiting until a forced migration reduces negotiating flexibility and increases migration cost — plan proactively and use the migration as a commercial lever at EA renewal.
EA Negotiation Strategy for Project Online
Right-Size Before Renewal
The most impactful commercial action for most organisations is a formal user classification exercise before EA renewal. Classify all current Project Online users into three categories: team members (Essentials tier or Planner Basic), project managers (Plan 3), and portfolio managers/PMO leadership (Plan 5). In most organisations, the Essentials population is larger than expected and the Plan 5 population is smaller than the current licence count.
Conduct this classification 12–18 months before renewal — not at the point of renewal when there is time pressure. The classification output becomes your renewal commitment baseline and your benchmark for what the correct licence count should be, which is the starting position for your renewal negotiation.
Use the Migration Decision as Leverage
If your organisation is planning or evaluating migration from Project Online to Project for the web, this decision is a commercial lever in EA negotiations. A commitment to migrate — reducing Project Online usage and increasing Project for the web adoption — can be exchanged for improved renewal pricing or enhanced Plan 3 terms. Microsoft values Project for the web adoption as a commercial signal; use this to extract pricing concessions at renewal.
Benchmark Against Alternatives
The enterprise project management market is competitive. Smartsheet, Wrike, monday.com, and Asana all compete directly with Microsoft Project Online at lower price points for comparable capability in the SME-to-mid-market segment. For very large enterprises with complex resource management and portfolio requirements, Project Online/Plan 5 remains differentiated — but for the majority of project management use cases, the competitive alternatives are commercially viable and genuine pricing pressure can be applied.
The negotiation application: obtain commercial quotes from two competitive alternatives before entering Project Online renewal discussions. Present these as part of your competitive posture alongside the right-sizing analysis. Account teams with a renewal at risk will negotiate more aggressively than those who believe Project Online is the only viable option.
Negotiate Volume Tier Alignment
Project Online licences should be priced at the tier applicable to your total Microsoft EA volume, not to the Project Online licence count in isolation. If you have 5,000 M365 E3 users and 400 Project Online users, the 400 Project licences should benefit from the volume tier derived from 5,000+ total users. Ensure your price sheet reflects this — and if your account team presents Project Online pricing at a lower tier, escalate to ensure the EA volume discount applies consistently.
Microsoft M365 Licensing Intelligence — Weekly Briefing
Project management licensing changes, M365 cost optimisation, and EA negotiation tactics — from 20 years of independent Microsoft advisory.
No spam. Unsubscribe at any time.
Common Project Online Licensing Mistakes
Mistake 1: Licensing All Project Users at the Same Tier
Team members who need to submit timesheets and view project plans require Essentials. Project managers who create and manage projects require Plan 3. Portfolio managers who need demand management and advanced analytics require Plan 5. Applying a single tier to the entire population is the most common and most expensive Project Online licensing error. Right-size by role, not by organisational convenience.
Mistake 2: Paying for the Project Desktop Client That Nobody Uses
Plan 3 includes the Project desktop client — but a meaningful proportion of project managers have migrated to the web interface and no longer install or use the desktop application. Before renewing at Plan 3, audit actual desktop client installation and usage data. Users who exclusively use the web interface may be candidates for Planner Premium at significantly lower cost, provided they do not require advanced resource management features.
Mistake 3: Ignoring the Planner Premium Option
Planner Premium was introduced as a direct competitor to lightweight Project Online usage. At approximately 55% of Plan 3 cost, it covers the majority of project management use cases for organisations not running complex resource management or portfolio analysis workflows. Evaluate Planner Premium explicitly for any Project Online user population before committing to Plan 3 renewal.
Mistake 4: Not Connecting Project Online to the Broader M365 Negotiation
Project Online is typically negotiated in isolation from the broader M365 EA conversation. This is a missed opportunity. The Project Online licence volume is a component of your total M365 commitment and should contribute to your volume tier calculation. Include Project Online in the total M365 commercial discussion, not as a separate standalone product negotiation.
Mistake 5: Failing to Plan for the Project Online Transition
Organisations that continue to renew Project Online without a migration plan are committing to a platform that will require transition at some point. Each renewal without a migration plan delays the inevitable and increases the eventual migration cost. Begin migration planning now — even if execution is 24–36 months away — and use the planned migration as leverage in the upcoming renewal negotiation.
Frequently Asked Questions
Does Project Online Essentials include the Project desktop client?
No. Essentials provides web-based access to project data — task status updates, timesheet submission, and project viewing — but does not include the Project desktop client. The desktop client is included in Plan 3 and Plan 5 only.
Is Project Online included in any M365 plan?
No. Project Online at any tier is not included in M365 E1, E3, E5, or any Business plan. It is always an additional subscription. Planner Basic is included in M365 plans and covers basic task management — but it is not Project Online.
Can Essentials users be team members on projects managed by Plan 3 users?
Yes. This is the intended use case for Essentials. A Plan 3 user creates and manages the project; Essentials users are assigned as team members, update task status, and submit timesheets. The combination of Plan 3 for PMs and Essentials for team members is the commercially optimal mix for most enterprise project deployments.
What happens to our Project Online data if we migrate to Project for the web?
Project for the web stores data in Dataverse, not SharePoint. Migration from Project Online to Project for the web requires data migration tooling and may involve some data transformation. Microsoft provides migration guidance and tooling, but the effort involved depends on the complexity and volume of your Project Online data. Engage your implementation partner to assess migration scope before committing to a migration timeline.
For independent analysis of your Project Online licence mix and EA negotiation strategy, engage our team. We provide right-sizing analysis, competitive benchmarking, and EA negotiation support for Microsoft project management licensing across all plan tiers and portfolio sizes.