Skip to main content

Record · Updated October 6, 2026

By Errin O’Connor, Founder & Chief AI Architect, EPC Group · Microsoft Since 1997 consulting · Founded 1997

Microsoft retired Project Online on September 30, 2026. This page is kept as the record of the timeline; what to do now is on the transition offer page. Microsoft announced the retirement on September 5, 2025; end-of-sale was October 1, 2025; new Project Web App (PWA) site creation was blocked April 1, 2026; and every SharePoint 2013 workflow stopped executing on April 2, 2026. Power BI reports built on the Project Online OData feed stopped at cutover. Organizations that still hold Project Online data move to Planner Premium, Power Platform PPM or Project Server Subscription Edition, and confirm current access with Microsoft rather than assume it.

Microsoft retired Project Online on September 30, 2026 (announced Sept 5 2025; end-of-sale Oct 1 2025; new PWA blocked April 1 2026; SharePoint 2013 workflows stopped April 2 2026; Power BI OData reports stopped at cutover). This page is the record of that timeline. Organizations that still hold Project Online data move to Microsoft Planner Premium (the default), Power Platform PPM or Project Server Subscription Edition, and confirm current access with Microsoft rather than assume it.

Key Facts

  • RETIRED: September 30, 2026 (Microsoft-announced Sept 5, 2025; one published date, no separate GCC, GCC High or DoD date)
  • END-OF-SALE: October 1, 2025 (no new Project Online licenses)
  • PWA CREATION BLOCKED: April 1, 2026 (existing sites continue)
  • SHAREPOINT 2013 WORKFLOWS DIED: April 2, 2026 (every classic Project Online workflow already dead)
  • POWER BI ODATA STOPPED: September 30, 2026 (reports on the /pwa/_api/ProjectData endpoint no longer have a source)
  • THREE MIGRATION PATHS: Planner Premium (default for most tenants) · Power Platform PPM (custom high-ceiling) · Project Server SE (on-prem for regulated data residency only)

Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group

The Verified Timeline

  • September 5, 2025 — Microsoft announced the retirement of Project Online via the Microsoft 365 admin center and the Microsoft Roadmap.
  • October 1, 2025 — End-of-sale. Existing Project Online customers can renew but new customers cannot purchase.
  • April 1, 2026 — Creation of new Project Web App (PWA) site collections was blocked across all Microsoft 365 tenants.
  • April 2, 2026 — SharePoint 2013 workflows stopped executing across all Microsoft 365 tenants. Every classic Project Online workflow (SPD2013 approval flows, stage-gate automation, status-report flows) stopped then. Organizations that had not rebuilt them in Power Automate ran Project Online without automation for its final six months.
  • September 30, 2026 — The retirement. Microsoft’s statement: after the retirement “you will no longer be able to access your projects or any associated data within the service”; raw data, the OData feed and the APIs are not available, and PWA-dependent functionality stops “unless the customer has an approved extension.” Every Power BI report sourcing from that endpoint lost its source.
  • After the retirement — Non-PWA SharePoint content in the same site collections (lists, document libraries, pages, subsites) remains accessible through SharePoint, subject to retention and permissions. EPC Group recommends keeping full archival exports for at least 12 months for reconciliation queries, and confirming current access with Microsoft rather than assuming a grace period.

Decision Tree — Which Migration Path?

Choose Microsoft Planner Premium if: Your team plans at the department or business-unit level, you have ≤50 active projects at a time, you do not depend on complex portfolio-level formula rollups, and you are willing to accept the new Fluent UI. Most mid-market Microsoft 365 tenants land here.

Choose Power Platform PPM if: You have deep custom logic (custom formula fields, complex stage-gate flows, integration with third-party ERPs), you already have a Power Platform team, and you want a modernized Dataverse-native PPM. Highest ceiling but requires 12–18 weeks of build.

Choose Project Server Subscription Edition if: You have regulated on-premises data residency requirements (GCC High, ITAR, air-gapped), depend on classic Master Project / Enterprise Custom Fields with formula rollups, or run more than 200 active projects with dedicated portfolio managers. Requires SharePoint Server SE 2019 or later.

What Broke in Power BI

The most under-communicated part of the retirement: every Power BI report sourcing data from the Project Online OData feed (https://<tenant>.sharepoint.com/sites/pwa/_api/ProjectData) stopped on September 30, 2026 when the endpoint stopped responding. Datasets refreshing on the Power BI gateway or Direct Query models pointing at that endpoint no longer have a source. Plan for at least 4–6 weeks of report rebuild work per 20 dashboards, either against Dataverse (Planner Premium / PPM path) or against a new data warehouse (archival path).

The Sequence EPC Group Published on July 3, 2026 (Kept as the Record)

  1. This week — Commission an inventory of active PWA sites, custom fields, dependent Power BI reports, and any surviving classic workflows.
  2. By July 31 — Decide the migration path (Planner Premium / PPM / Project Server SE) based on the decision tree.
  3. By August 15 — Start Power BI report rebuild in parallel with data-model work.
  4. By August 31 — Begin waved cutover of pilot departments.
  5. September 15–29 — Complete cutover, verify all reports refresh cleanly, archive PWA data.
  6. September 30 — The retirement. The sequence above is the record; what to do now is on the transition offer page.

Related EPC Group Services

Project Online Retirement — Frequently Asked Questions

When did Microsoft Project Online retire?

Microsoft retired Project Online on September 30, 2026. Microsoft announced the retirement on September 5, 2025. End-of-sale was October 1, 2025 (no new Project Online licenses could be purchased). Creation of new Project Web App (PWA) sites was blocked on April 1, 2026. On April 2, 2026, all SharePoint 2013 workflows — including every classic Project Online workflow — stopped executing. Microsoft's own statement is that after the retirement "you will no longer be able to access your projects or any associated data within the service"; it publishes no read-only state and no deletion date. Power BI reports built on the Project Online OData feed stopped at cutover.

What are the migration options?

Three practical paths: (1) Microsoft Planner Premium (formerly Project for the Web) — the Microsoft-recommended default for most Project Online tenants, but NOT a feature-parity replacement (portfolio-management features, custom formula fields, and the reporting layer differ substantially). (2) Power Platform PPM — build a custom Project Server-equivalent on Dataverse + Power Apps + Power Automate. Highest ceiling, highest effort. (3) Microsoft Project Server Subscription Edition (SE) — a self-hosted on-premises path, but requires SharePoint Server SE 2019 or later. Best only for organizations that must keep classic scheduling on-prem.

What broke in Power BI at cutover?

Every Power BI report that sourced data from the Project Online OData feed (https://<tenant>.sharepoint.com/sites/pwa/_api/ProjectData) stopped on September 30, 2026 when the endpoint stopped responding; Microsoft says the raw data, OData feeds and APIs do not remain accessible. Datasets refreshing on the Power BI gateway or Direct Query models pointing at that endpoint no longer have a source. Migration includes rebuilding the semantic model against Dataverse (if Planner Premium or PPM path chosen), or against a new data warehouse if PWA data is being archived. Plan for at least 4–6 weeks of report rebuild work per 20 dashboards.

What happens to SharePoint 2013 workflows on Project Online?

On April 2, 2026, SharePoint 2013 workflows stopped executing across every Microsoft 365 tenant. That means every classic Project Online approval workflow, stage-gate automation, and status-report flow is already dead. Organizations that had not rebuilt them in Power Automate ran Project Online without automation for its final six months. This includes portfolio-level workflows, project-server stage transitions, and any SPD2013-created form flows.

How long does a Project Online to Planner Premium migration take?

EPC Group typical scoping: 8–14 weeks depending on tenant size and the reporting layer. Week 1–2: inventory of active PWA sites, custom fields, workflows, and dependent Power BI reports (PowerShell + Graph API). Week 3–4: custom-field-to-Dataverse mapping and the Power BI report rebuild plan. Week 5–8: Power BI report rebuild against Dataverse. Week 9–10: Power Automate flow rebuild for the deprecated SP2013 workflows. Week 11–12: waved cutover by department. Weeks 13–14: post-cutover cleanup and archival of PWA data. See the linked companion page for the step-by-step playbook.

Should we migrate to Planner Premium or Project Server SE?

Decision tree: Planner Premium is right if your organization uses Project Online for team-level task planning, has ≤50 active projects at a time, does not depend on complex portfolio-level formulas, and is willing to accept the new Microsoft Fluent UI. Project Server SE is right if you have regulated on-premises data residency requirements (GCC High, ITAR, air-gapped), depend on classic Master Project / Enterprise Custom Fields with formula rollups, or run more than 200 active projects with dedicated portfolio managers. Power Platform PPM is right if you have deep custom logic and a Power Platform team already in place. Most mid-market Microsoft 365 tenants land on Planner Premium.

What data should have been exported from Project Online before September 30, 2026?

At minimum: (1) PWA site collections (SharePoint site-level export or PowerShell backup), (2) MPP files exported from every active project (Microsoft Project client, File → Save As), (3) Resource pool CSV export, (4) Custom-field definitions as XML, (5) Workflow definitions if you plan to reimplement in Power Automate, (6) Historical Power BI reports as PBIX files. EPC Group recommended completing this archive at least 30 days before the September 30 cutover. If your organization did not export before September 30, 2026, confirm current access with Microsoft: its FAQ says PWA-dependent functionality stops "unless the customer has an approved extension", and EPC Group does not promise a grace period.

What was EPC Group's recommended sequence?

The sequence EPC Group published on July 3, 2026, kept here as the record for organizations that then had an active Project Online tenant: (1) This week — commission an inventory of active PWA sites, custom fields, dependent Power BI reports, and any surviving classic workflows. (2) By July 31 — decide the migration path (Planner Premium / PPM / Project Server SE) based on the decision tree. (3) By August 15 — start Power BI report rebuild in parallel with data-model work. (4) By August 31 — begin waved cutover of pilot departments. (5) September 15–29 — complete cutover, verify all reports refresh cleanly, archive PWA data. (6) September 30 — the cutover. The retirement has now happened; what to do now is on the transition offer page, /services/project-online-migration.

Talk to a Senior Architect

EPC Group is a Microsoft consulting firm founded in 1997 — a Microsoft Gold Partner (2000 until Microsoft retired the program in 2022) — today holding all six Microsoft Solutions Partner Designations, serving organizations across all industries in the United States. We have delivered 216+ M&A tenant-to-tenant migrations and 1.83 million users moved in the 2023–2025 program.

contact@epcgroup.net · 888-381-9725 · www.epcgroup.net

AI assistant — not a human