Decoding the Microsoft Project Online Retirement Announcement: What It Commits To and What It Leaves Open

The most dangerous assumption in a Project Online migration plan is that the July 2024 Microsoft Project Online retirement announcement answered all the questions. It announced a date. It named successors. It offered migration guidance documentation. It did not answer the questions that actually drive migration planning: how long is the read-only window after September 30, what happens to the OData endpoint, can PWA governance customizations move to Planner Premium, and what does Microsoft's PPM roadmap look like after the retirement.

The announcement said enough to create urgency. It left enough open to create bad plans built on unexamined assumptions.

This post decodes the announcement line by line: what Microsoft committed to explicitly, what it left ambiguous, and what your PMO should infer about Microsoft's PPM strategy through 2026 and beyond.

TL;DR Microsoft's July 2024 announcement confirmed September 30, 2026 as a hard retirement date and named Planner and Project for the Web as successors. It did not specify the exact post-retirement read-only window, provide a migration tool, or address what happens to PWA governance customizations. The successors Microsoft positioned lack enterprise PMO features. The practical inference: Microsoft is exiting the heavyweight PPM space, and mid-market PMOs need to pick an independent migration target rather than assuming Microsoft's recommended path fits their use case.

What Microsoft Actually Said in July 2024

The retirement announcement appeared in the Microsoft Project Blog on TechCommunity in July 2024 and was simultaneously posted to the Microsoft 365 Message Center for tenant administrators. Microsoft's Project Online service description on Microsoft Learn is the authoritative documentation of what the platform covers and what the lifecycle commitments are.

The core commitments in the announcement, stated explicitly:

• The retirement date is September 30, 2026. Microsoft was unambiguous about this. The service will stop accepting requests on that date. Existing licenses can be used through September 30, 2026.
• Existing subscriptions continue. Organizations on Project Plan 3 or Project Plan 5 can continue their subscriptions and access Project Online through the retirement date. No forced early migration.
• Microsoft 365 continues. The M365 subscription itself is not affected. SharePoint, Teams, and other M365 services continue normally. Only the Project Online components retire.
• Migration guidance will be provided. Microsoft committed to publishing migration documentation and resources to help customers move to successor products.

The announcement also named the recommended successors: Microsoft Planner (which had been rebranded from Microsoft Project for the Web to Planner Premium by the time of the announcement) and Project for the Web as alternatives, depending on use case complexity.

The Commitments That Are Precise and the Ones That Are Not

Reading the announcement carefully, a pattern emerges: the commitments about what stops are precise; the commitments about what continues afterward are not.

Precise: September 30, 2026 is a hard date. Microsoft has not wavered on this in any subsequent communication. Every question about an extension has received the same answer: the date stands. Design your plan around September 30, 2026 as a deadline with no buffer from Microsoft's side.

Not precise: the post-retirement read-only window. Microsoft's language around post-retirement data access has varied across communications. The general commitment is that read access to data will be available for "a period" after the retirement date before tenant access is fully terminated. What "a period" means has not been specified with a number of days or a specific cutoff date. Onplana's working assumption, based on Microsoft's historical behavior with other product retirements, is 90 days of read access after the September 30 cutover. Plan to complete all data export by August 1, 2026 rather than relying on any specific post-retirement window.

Not addressed: the OData endpoint lifecycle. The Project Online OData feed (/_api/ProjectData) is the data backbone for Power BI dashboards, Excel connections, and custom reporting across most enterprise PMO deployments. The retirement announcement did not specify whether the OData endpoint continues into the read-only window or shuts down simultaneously with the PWA interface. This distinction matters enormously: if the OData endpoint shuts down on September 30, every reporting tool that reads from it breaks on September 30, regardless of any read-only window for PWA. Plan for OData to stop on September 30; treat any post-retirement OData access as a bonus, not a dependency.

The diagram below shows what the announcement addressed versus what it left open across the dimensions that matter most for migration planning.

The Successor Problem: What Microsoft Positioned vs. What Enterprise PMOs Need

The most consequential gap in the announcement is the mismatch between the successors Microsoft named and the capabilities enterprise PMOs depend on.

Microsoft positioned Planner Premium and Project for the Web as the path forward. Both are real products with genuine use cases. Neither is a drop-in replacement for Project Online at enterprise scale.

Planner Premium hard limits. Planner Premium (Microsoft's rebranded Project for the Web) caps plans at 3,000 tasks. It supports 10 custom fields. It has no Enterprise Resource Pool. It has no portfolio rollup. It has no OData reporting endpoint. It has no timesheet capability. A PMO that runs Project Online with 500 active projects, 150 custom fields, and a Power BI reporting stack built on OData cannot move to Planner Premium without fundamentally redesigning its PMO operating model.

Project for the Web is a lighter tool, not a successor. Project for the Web (the Dataverse-backed product, distinct from Planner Premium) is a lightweight task management tool appropriate for single-project teams. It lacks the multi-project portfolio capabilities, resource management, and governance infrastructure that enterprise PMOs use.

Microsoft's suggested migration path works for smaller organizations running Project Online as a slightly-heavier-than-Planner task tracker. It does not work for the enterprise PMO segment: 50-plus projects, real critical-path scheduling, resource pool management, governance stages, and BI reporting.

What the Announcement Reveals About Microsoft's PPM Strategy

Reading the announcement against Microsoft's product investments since 2020, a strategic direction becomes clear: Microsoft is not planning a next-generation enterprise PPM platform to replace Project Online. It is exiting the heavyweight PPM space.

The investment signals point in the same direction. Copilot integration has been added to Planner and Teams, not to a rebuilt enterprise PPM product. Project for the Web runs on Power Platform rather than a purpose-built scheduling engine. The absence of announced investment in a deep-schedule, enterprise-resource-pool successor to Project Online is not an oversight; it reflects a product strategy decision.

This inference changes how PMO directors should frame their migration choice. Microsoft's recommended path (Planner Premium, Project for the Web) is not a temporary holding pattern until a better Microsoft product arrives. It is Microsoft's long-term answer for the use case Project Online served. If that answer does not fit your PMO's needs, the migration target selection is not "which Microsoft product" but "which non-Microsoft product."

The Ambiguities That Produce Bad Migration Plans

Three specific ambiguities in the announcement have produced migration plans with structural problems.

The "read-only window" assumption. Some migration plans schedule the final data export for October or November 2026, treating the post-retirement read-only window as usable buffer time. The problem: the length of that window is not guaranteed, and the OData endpoint may not remain accessible during it. Export all critical data by August 1, 2026. Treat anything accessible after September 30 as uncertain.

The "Microsoft will provide migration tools" assumption. The announcement committed to migration guidance documentation, not migration tools. Some PMO teams read "migration support" as implying automated tooling. The actual migration guide covers export procedures (OData, .mpp export) and documentation of the successor products. The engineering work of transforming exported data into a format the destination tool accepts is not covered. Plan for this data-transformation work as a significant line item.

The "we'll decide on the destination tool later" assumption. The announcement named two successor options. Some PMOs interpreted the announcement as "we have time to evaluate tools later." For a mid-sized PMO (50 to 150 active projects), the tool evaluation, pilot migration, and full cutover takes 12 to 16 weeks. If tool selection has not happened by May 2026, the timeline is dangerously tight. Tool selection is overdue; it is not something to begin in Q3.

The One Sentence That Changes Your Migration Timeline

Microsoft's announcement contained one sentence that most readers skimmed: the note that Project Online will stop accepting new subscriptions before the retirement date (Microsoft began blocking new Project Online subscriptions in 2024, before the full retirement). While this primarily affects new customer acquisition, the operational implication for existing customers is this: Microsoft's execution of this retirement is moving on schedule and there is no indication the vendor is providing escape valves.

The announcement confirmed what the date alone implies: September 30, 2026 is fixed, and the preparation window is finite. For the 90-day migration plan to work, it needs to start by July 1, 2026 at the latest. For the full Microsoft Project Online end-of-life checklist to be completed without crisis, the inventory work needs to be running now.

The migration planning hub has the framework for the evaluation and tool-selection work that the announcement assumes organizations are already doing.

Run the free Migration Preview Upload a .mpp file and see which features survive the boundary between Project Online and your destination tool in 30 seconds. No signup. Run it before selecting a migration target. → Open Migration Preview

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