Microsoft Project Online Reaches Its Retirement Date Today

September 30 is Microsoft's published retirement date for Project Online, bringing a long-announced change to the day when organisations need their transition plans to work. Microsoft's official retirement notice says the change applies to Project Online and does not retire Project desktop, Project Server Subscription Edition or Planner.

This is coverage of today's scheduled lifecycle event, not a claim that Microsoft first announced the decision in the last 24 hours. It is also not a report of a newly observed outage. GlobalTechRanks has not inspected customer tenants or independently established when access changes in each environment.

A service deadline has workflow consequences

Microsoft's notice says customers will no longer be able to access their projects and associated data within Project Online after retirement. It identifies transition options including Planner, Project Server Subscription Edition, Dynamics 365 Project Operations and Project desktop, depending on the organisation's needs. Its administration documentation also carries the September 30 retirement warning.

The practical distinction is between retaining a project file and retaining an operational process. Our analysis is that an organisation can preserve a schedule while still needing to replace the way people report progress, obtain approvals and assemble portfolio information.

A hypothetical migration might move all the current plans successfully, yet leave a monthly management report dependent on the old service. Another might preserve tasks while changing who can view or update them. Neither problem is solved merely by confirming that an export exists.

The useful check is whether the replacement works

Teams dealing with the deadline should establish what they actually use, where their retained information is stored and which replacement process owns each activity. The relevant people include project managers, reporting teams, system administrators and staff responsible for integrations.

A concrete review could trace one active project from a team member's update through an approval to a management report. It could also test a historic project needed for an audit or contractual discussion. These are editorial suggestions for evaluating continuity, not a substitute for Microsoft's product-specific migration guidance.

Organisations should use the official notice and their own account or support contacts to resolve tenant-specific questions. This article cannot determine whether a particular export is complete or whether a replacement meets a company's contractual requirements.

An important Big Tech decision beyond the launch cycle

Product retirement is a consequential part of platform strategy. A provider's decision to concentrate investment elsewhere can require customers to change processes built over years. The cost of a service therefore includes the ability to leave it with usable information and a functioning alternative.

Today's Project Online deadline gives that issue an immediate example. The relevant outcome for customers is whether their projects, approvals and reports can continue in the chosen environment. The name of the replacement matters less than evidence that the work and records they depend on have made the transition.

Image: Microsoft