Don’t Get Locked Out: Ensuring PWA Access Through the Project Online Retirement Transition

Don’t Get Locked Out: Ensuring PWA Access Through the Project Online Retirement Transition

As we all know, Microsoft Project Online is gracefully heading toward retirement on September 30, 2026. But while that date might feel far off, there is a much closer milestone you need to have on your radar.

Microsoft recently announced that starting April 1, 2026, new restrictions will take effect regarding Project Web App (PWA) sites. And no, this isn’t an April Fools’ joke, it’s a critical step in the transition to modern project management.

What is changing?
Beginning April 1, 2026, Microsoft will begin enforcing the following changes to streamline the retirement process:

  • No New PWA Sites: The ability to create new PWA site collections will be blocked entirely.
  • Inactivation of Unused Sites: Any existing PWA site that does not contain at least one project will be blocked and become inaccessible.
  • Non-PWA Content is Safe: If you have documents or lists stored on a PWA site that doesn’t have a project, you can still access that non-PWA content, but the PWA functionality itself will be gone.

Does this affect my active projects?
If you are actively using Project Online, don’t panic. Any PWA site that contains one or more projects will continue to function normally until the final retirement date in September. Microsoft is simply “cleaning house” to reduce unused resource consumption and help organizations focus on their transition to the Power Platform and Project for the web.

Your Pre-April Checklist
To ensure your team doesn’t lose access to important environments, we recommend taking these steps now:

  1. Audit Your Environments: Review your existing PWA sites. Identify which ones are active and which are empty shells used for testing or “just in case.”
  2. The “One Project” Rule: If you have an empty PWA site that you must keep active for future use or historical reference, ensure it has at least one project created within it before April 1.
  3. Clean Up Early: If a site is truly unused, now is a great time to decommission it voluntarily.
  4. Update Your Workflows: If your internal provisioning process involves creating new PWA sites, those workflows will need to be retired or updated by the spring.

Looking Beyond the Horizon
While these changes are manageable, they serve as a clear signal: the era of Project Online is sunsetting. Transitioning to modern PPM solutions isn’t just about avoiding a deadline; it’s about unlocking better collaboration, better reporting, and a more integrated Microsoft 365 experience.

Note: No admin action is required to “enable” these changes—Microsoft will flip the switch automatically on April 1, 2026.

We’re Here to Help
Navigating the road to retirement can be tricky, but you don’t have to do it alone. Whether you need help auditing your current PWA sites or you’re ready to start mapping out your migration to a modern PMO, PPM Works has the expertise to get you there smoothly.

Would you like us to run a health check on your current Project Online environment to see which sites are at risk? Book time with us or contact us today!