Microsoft Project Online retired on 30 September 2026. Here is what changed, what it means for your projects, and the project management lessons every PM should take from it.
On 30 September 2026, Microsoft switched off Project Online.
That isn’t “end of support”, where the software keeps running without patches. It’s retirement. In Microsoft’s own words, once Project Online retires, “you will no longer be able to access your projects or any associated data within the service.”
If your organisation moved off it in good time, you can probably read this with a cup of tea and a certain amount of quiet satisfaction. If it didn’t, or if you aren’t sure, then this week matters rather a lot.
I’d like to explain what has actually happened, clear up a few points people commonly misunderstand, and then look at it the way we’d look at any scenario in a PRINCE2, APM PMQ or PMP exam. What does it teach us about managing projects?
### What Exactly Happened?
Microsoft announced the retirement in September 2025, citing Project Online’s legacy architecture and the deprecation of certain SharePoint Online workflow design tools in 2026. The timeline was published well in advance:
– **1 October 2025:** end of sale of Project Online-only plans to new customers.
– **1 April 2026:** existing customers could no longer create new Project Online tenants.
– **30 September 2026:** official retirement. Project Online is no longer available.
Microsoft issued a final reminder through the Microsoft 365 Message Center on 24 September 2026 (MC1478955). It advised any organisation that would not be fully migrated to contact a Microsoft partner immediately. It also confirmed that the retirement would “happen automatically on the specified dates with no admin action required.”
### What Has *Not* Been Retired
This is where a lot of the confusion comes from, so let’s be precise. Microsoft states the change is exclusive to Project Online and does **not** affect:
– **Project desktop** (Project Standard 2024 and Project Professional 2024 remain available)
– **Project Server Subscription Edition**
– **Planner**, with both its basic and premium capabilities
So if your scheduling skills are built on Microsoft Project desktop, they haven’t become obsolete overnight. What has gone is the cloud-hosted Project Web App environment that many PMOs used for enterprise scheduling, timesheets and portfolio reporting.
### Where Microsoft Is Pointing Organisations
Microsoft offered three main transition paths:
1. **Planner:** Microsoft’s “modern, cloud-first, and AI-powered” option. Its premium features include portfolios, baselines, dependencies and Gantt charts, and Microsoft is building its Project Manager agent (an AI assistant for task creation and status reporting) into it.
2. **Project Server Subscription Edition:** for organisations that need advanced project and portfolio management, or the closest match to Project Online’s feature set, built on SharePoint Server.
3. **Dynamics 365 Project Operations:** aimed at organisations focused on timesheets, resource scheduling and project financials.
The independent market has noticed too. Several vendors have launched or repositioned products specifically as Project Online replacements in recent weeks. That’s a reminder that the “obvious” vendor route isn’t the only option worth evaluating.
### Why This Matters to Project Managers
You might think this is purely an IT matter. I’d argue it’s one of the clearest real-world case studies we’ve had in a long time, because nearly every principle we teach shows up in it.
**First, a known risk became an issue on a fixed date.** In our courses I keep repeating one distinction: something that *might* happen is a risk, and something that *has* happened and now needs action is an issue. For thirteen months, Project Online’s retirement was a risk with a known date, a known impact and published responses. Any organisation that let that risk sit untreated on the register now has an issue, and probably an expensive one.
**Second, it’s a lesson in transition management.** Moving schedules is the easy part. The harder work is moving custom fields, timesheet history, baselines, resource pools, reports and integrations, and then getting people to adopt the new way of working. Microsoft’s own guidance recommended notifying users and updating internal documentation. That’s transition and change management, not software installation.
**Third, it tests the business case.** Choosing a replacement shouldn’t be a panic purchase. The question is the same one we ask at every stage boundary: is continued investment in this option still justified, given its costs, benefits and risks? A like-for-like replacement might be right. Or this might be the moment to simplify your tooling to fit how your projects actually run today, whether that’s predictive, agile or hybrid.
**Fourth, data is a project asset.** Closed projects, lessons, actuals and baselines are your organisation’s memory. They feed estimating, earned value analysis and future business cases. If that history lived only inside a retired service, it’s worth asking why nobody owned it.
### Practical Takeaways
– **Confirm your position this week.** Find out whether any team, programme or PMO in your organisation was still relying on Project Online, and what was exported before 30 September.
– **Don’t assume you have more time.** Microsoft has stated that projects and associated data are no longer accessible after retirement. Plan around what you actually hold, not around hoped-for access.
– **Treat the migration as a project.** Give it a business case, a sponsor, defined scope, a plan, a risk register and clear acceptance criteria.
– **Validate, don’t just export.** Check that schedules, dependencies, baselines and reports behave correctly in the new tool before you declare success.
– **Review your other cloud dependencies.** Every SaaS tool your projects rely on has a lifecycle. Put the important ones on your risk register with an owner.
– **Keep investing in core scheduling skills.** Tools come and go. Critical path, dependencies, baselines and earned value don’t.
### A Final Thought
Project Online’s retirement wasn’t a surprise. It was announced, dated and repeated, which is exactly why it’s such a useful lesson. Projects rarely fail because nobody could see the problem coming. They fail because a visible risk went unowned until it turned into an issue.
So take a moment this week to look at your own risk register and ask a simple question: which of these dates are we quietly hoping will go away?
