Blog > Microsoft Project Online Is Retiring in 2026 – What Should You Do Next?

Microsoft Project Online Is Retiring in 2026 – What Should You Do Next?

May 26, 2026 8 min read

Project Online now has a firm retirement date. Microsoft’s official Project Online retirement announcement confirms that the platform will retire on September 30, 2026. To prepare for this transition, sales of new Project Online-only SKUs already ended on October 1, 2025.

This deadline is a significant milestone because countless teams still rely on the service for project scheduling, executive reporting, custom integrations, and portfolio management. 

While there is no need to panic, thinking about structuring a plan wouldn’t hurt. PMO leaders must inventory current system usage, categorize projects by planning depth, compare their next Microsoft licensing options, and choose a path forward before the deadline forces a rushed migration.

In this guide:

  • The difference between Project Online and Project for the web, especially since Microsoft retired Project for the web in 2025 and moved those features into Planner.

  • The difference between Project Online and Project for the web, especially since Microsoft retired Project for the web in 2025 and moved those features into Planner.

  • The primary Microsoft migration paths to evaluate, including basic Planner, advanced Planner subscriptions, and Project Server Subscription Edition.

  • Where BrightWork 365 fits for organizations needing a native Microsoft 365 solution for project intake, templates, portfolio reporting, and structured governance.

Keep in mind: Project for the web often gets mixed up in these discussions. Microsoft actually retired the standalone Project for the web experience in August 2025, redirecting those users into Microsoft Planner.

That transition is separate from the Project Online retirement. While Planner updates provide helpful context for the future of Microsoft work management, they do not serve as a direct replacement plan for a complex Project Online environment.

What Microsoft Has Confirmed

The official transition path includes several key dates and product modifications:

  • Project Online will retire on September 30, 2026.

  • Sales of Project Online-only SKUs ended on October 1, 2025.

  • Current Project Online accounts remain fully active and supported until the final retirement date.

  • The Project desktop client will remain available and supported, subject to the lifecycle rules of each specific version.

  • Project Server Subscription Edition remains fully supported for on-premise setups.

  • Project for the web retired in August 2025, with users transitioning to Planner for the web and Planner in Teams.

  • The active Microsoft plan names are now Planner Plan 1, Planner and Project Plan 3, and Planner and Project Plan 5.

  • Project Online OData endpoints and integrations will remain operational until the September 2026 retirement date.

These product names are important because many teams still search for outdated Project labels and miss the current subscription options. Navigating the retirement requires understanding these dates, updating your licensing language, and choosing a work model that meets your PMO needs long after the deadline passes.

What This Means For Current Project Online Customers

If your PMO currently runs on Project Online, you still have some runway. The service is not shutting down tomorrow. The real challenge is evaluating your options and choosing your next platform before you are forced to make a hasty migration.

For Microsoft-first PMOs, this decision is rarely about finding a new scheduling tool. Instead, it is about establishing a clear, sustainable operating model. Teams starting a PMO on Microsoft 365 need reliable portfolio dashboards, standardized templates, and reporting structures that make the new system easy for employees to adopt.

To make this decision easier, try splitting your current PMO activities into three distinct buckets:

  • Task coordination – Managing individual to-do lists, assigning ownership, and tracking basic task dates.

  • Scheduling and delivery control – Tracking project dependencies, timelines, resource workloads, and critical paths.

  • PMO and portfolio reporting – Managing intake requests, consolidating multi-project status updates, and delivering executive dashboards.

Some teams only require basic task tracking. Others need advanced scheduling capabilities. Most PMO leaders require deep portfolio reporting. Project Online handled far more than task lists, so replacing it with a basic board will likely leave a massive gap in your governance.

If you are weighing your software options, evaluate Microsoft 365 and standalone tools based on your long-term reporting, security permissions, and user adoption goals.

What Stays Supported

The Project desktop client remains a viable option, depending on your version-specific lifecycle dates. Organizations running Project Server Subscription Edition also remain fully supported. This is vital for teams with on-premise environments, custom databases, or complex legacy integrations that cannot be retired quickly.

Why Project For The Web Is A Separate Story

Project for the web and Project Online are entirely different products. Microsoft retired Project for the web in August 2025, folding its capabilities directly into Microsoft Planner. Microsoft’s documentation explains that premium scheduling features now live inside Planner for the web and Planner in Teams.

This distinction is important when researching your options. A standard article on Planner can help you coordinate tasks, but it won’t solve complex migration, data reporting, or portfolio governance challenges.

The Main Paths To Review

Use the next path based on what Project Online currently does for your organization. A lightweight task tool may work for simple coordination, but PMOs that rely on schedules, portfolio dashboards, approvals, and governance need a more structured replacement.

Planner For Lighter Coordination

Planner is ideal for groups that need visual task boards, clear task ownership, basic deadlines, and a high-level view of progress. It is a great fit for lightweight coordination that lives inside Microsoft Teams and does not require a formal PMO.

If this matches your team’s style, check out the Microsoft Planner plans and pricing page to compare the current plans and subscription groups.

Planner works well when you simply need to keep work moving. It is not designed for project intake, portfolio governance, cross-project reporting, or structured change management.

Planner And Project Plan 3 Or 5 For More Scheduling Depth

Many engineering and construction teams need more than a task board and a checklist. They require interactive Gantt charts, strict task dependencies, timeline views, and resource allocation tracking.

While basic Planner handles simple task management, the premium Planner and Project plans add advanced features like Timeline, critical path dependencies, custom fields, and workload tracking. This option keeps your planning data inside the Microsoft cloud, serving project managers who need comprehensive scheduling power.

PMOs can use this path to keep scheduling inside the native Microsoft stack. However, you will still need to establish secondary processes or custom reporting databases if your PMO requires formal portfolio governance.

Project Server Subscription Edition

Project Server Subscription Edition remains fully supported by Microsoft. For certain organizations, this on-premise option is necessary to maintain custom databases, run legacy reports, or manage a migration path that cannot move directly to the cloud.

This route makes sense for teams that are not ready to migrate their project controls to a cloud-based Microsoft 365 PMO layer. While it is a supported path, it utilizes a different operating model and is best viewed as a continuity strategy rather than a modernization plan.

BrightWork 365 For Microsoft 365 PMOs

BrightWork 365 is designed for teams that want comprehensive project and portfolio management built directly inside their Microsoft 365 environment. The platform deploys inside your own tenant, utilizing Microsoft Teams, SharePoint Online, Power Apps, Power Automate, Power BI, and Dataverse.

This solution is highly effective if your Project Online setup was used for formal intake, portfolio reporting, governance, repeatable templates, and resource tracking. BrightWork 365 consolidates these PMO capabilities into a single, structured operating model.

Where The Replacement Gaps Appear

Replacing Project Online typically reveals two major operational gaps: managing how new work gets approved, and managing how the new software gets rolled out. 

BrightWork 365 addresses these challenges directly. It uses project request management to control intake and approvals, while Start Service provides guided coaching to help teams transition away from Project Online. The platform is less relevant for groups that only need basic, self-serve task lists.

Project Online Retirement Planning Checklist

  • List every active Project Online site, plan, owner, and user permission level.

  • Document all existing integrations, OData reports, Power BI dependencies, and custom workflows.

  • Categorize your current work into task coordination, scheduling, and portfolio reporting.

  • Identify which projects only require lightweight task lists and which need formal schedules.

  • Compare Microsoft Planner, Project Plan 3 or 5, Project Server, and BrightWork 365 against your categorization.

  • Appoint a dedicated migration owner to lead planning, coordinate stakeholders, and secure approvals.

  • Establish a firm decision deadline well in advance of the September 30, 2026 retirement.

  • Choose the replacement path that best supports your security, reporting, governance, and user adoption needs.

Plan Your Project Online Retirement Next Steps

The Project Online retirement timeline gives PMO leaders enough time to make a deliberate, strategic decision, but you cannot afford to wait until the final months. 

Start by inventorying your current sites, identifying the projects that require advanced scheduling or portfolio reports, and selecting a replacement path that protects your reporting and governance.

For PMOs committed to keeping their project portfolios inside the Microsoft ecosystem, BrightWork 365 integrates intake, templates, dashboards, and rollout support into the tools your staff uses daily.

Review the BrightWork 365 platform to see how it aligns with your Project Online requirements by watching the demo that shows the system in action.

Categories
Billy Guinan​​
BrightWork Demand Generation Manager

Billy has nearly 15 years of experience in B2B SaaS project portfolio management, specializing in Microsoft 365, Teams, the Power Platform, and SharePoint. He focuses on collaborative and template-driven project management. Outside work, he enjoys reading, golf, and walking his pug, Nova.

Ready to Centralize Your PMO? See BrightWork 365 in Action