Project Online Governance vs Onplana: After the SharePoint Workflow Shutdown

SharePoint 2013 workflows stopped running on April 2, 2026. That date is already past. If your Project Online governance runs on them, the approval sequences that move project proposals through phase gates have been silently failing for over seven weeks. Whether your PMO has noticed yet depends on how recently anyone tried to trigger an approval and whether the silence was visible enough to escalate.

This is not a hypothetical future problem. It is a problem that has been running in thousands of Project Online tenants since early April. The detailed breakdown of what broke covers the failure mode: governance requests go in, nothing routes, nothing gets approved or rejected, and proposals sit in queue with no forward movement.

The Project Online governance problem and the September 30, 2026 retirement are two separate timelines that have now collapsed into one: if your governance is broken and your migration is still underway, you are running without PMO process controls for the remainder of the window.

What just broke: Project Online governance and the April 2026 shutdown

Project Online's governance model was never a standalone product feature. It was a configuration layer built on top of SharePoint infrastructure: custom SharePoint 2013 workflows that handled the routing logic for project intake, demand management, and phase-gate transitions.

Those workflows sat inside the PWA SharePoint site collection. When a PM submitted a project proposal, a SharePoint 2013 workflow triggered, routed the approval request to the designated approver, waited for a response, and either advanced the project to the next phase or returned it for revision. The workflow engine was the mechanism that enforced the PMO's governance process.

On April 2, 2026, Microsoft retired that engine, as confirmed in Microsoft's SharePoint 2013 workflow retirement announcement. The workflows themselves still exist in the site collection as configuration, but the engine that executes them does not run. A project proposal submitted after April 2 enters the queue and stays there. The approval path that was supposed to move it forward no longer fires.

This does not affect all Project Online tenants equally. PMOs that never customized their governance beyond the default configuration, or that moved their approval workflows to Power Automate before April, have not experienced the same disruption. But PMOs that built their demand-management and stage-gate process on the 2013 workflow engine between 2015 and 2020, which is the majority of large Project Online configurations, have been operating without governance enforcement since April 2.

How Project Online governance actually worked before April 2026

Understanding what broke requires understanding what was there in the first place.

Project Online's governance model was built around several components:

Enterprise Project Types (EPTs). Each EPT defined a project template with associated workflows, custom fields, and phase definitions. When a PM created a new project, they selected an EPT, which determined what governance process applied.

PWA phases and stages. The governance workflow moved projects through defined stages within phases (Create, Select, Plan, Manage, Finish). Each stage had entry requirements. A stage transition required workflow approval before the project could advance.

SharePoint 2013 demand-management workflows. These were the executable logic. They defined who received approval requests, what criteria applied at each gate, and what happened if an approval was denied. Most were built using SharePoint Designer 2013 or Visual Studio.

Project portfolio analysis. Before projects entered the plan phase, portfolio managers could run scenario analysis to prioritize which projects to authorize. This fed into the governance workflow.

The system was powerful but fragile. Governance logic was embedded in SharePoint Designer files that were difficult to version-control, required SharePoint expertise to modify, and ran on an engine Microsoft had committed to retiring. The April 2026 shutdown was not a surprise: Microsoft announced the deprecation timeline years in advance. But many PMOs did not have the capacity to rebuild before the deadline.

What Onplana's governance pipeline ships

Onplana's enterprise governance is not a SharePoint workflow wrapper. It is a native product feature built into the data model, not layered on top of an external workflow engine.

The governance pipeline ships twelve stages by default, covering a full proposal-to-delivery lifecycle:

1. Idea submission
2. Initial review
3. Business case development
4. Business case review
5. Portfolio analysis
6. Authorization
7. Planning gate
8. Execution kickoff
9. Mid-execution review
10. Delivery acceptance
11. Post-delivery review
12. Close

Each stage is configurable: which custom fields are required at entry, which roles must approve the gate, and what documentation is expected. The RACI for each gate is defined within the product, not in a separate SharePoint Designer file. The audit trail is built into the stage transition itself: every approval, rejection, and comment is logged with timestamp and user identity.

The Change Control Board workflow is a separate governance layer for in-flight projects. When a scope or schedule change requires formal approval, the CCB workflow surfaces the change request, routes it to the configured board members, captures the decision, and records the outcome against the project baseline. This is the governance motion that most Project Online configurations tried to replicate with SharePoint workflows, and the reason those workflows were complex.

Project Online governance vs Onplana: side-by-side comparison

Governance capability	Project Online	Onplana
Underlying mechanism	SharePoint 2013 workflows (retired Apr 2026)	Native product feature
Stage-gate pipeline	Via EPTs and PWA phases	12-stage configurable pipeline
Gate approval routing	SharePoint workflow engine	Built-in approval with RACI per gate
Change Control Board	Via custom workflow	Native CCB workflow
Audit trail for approvals	SharePoint list entries	Built-in, timestamped, per-stage
Governance config tool	SharePoint Designer / Visual Studio	Product UI, no external tooling
RACI per gate	Embedded in workflow code	Configured in product per stage
Portfolio analysis integration	PWA Portfolio Analyzer (separate)	Built into pipeline authorization stage
Current status	Broken (SP 2013 engine retired)	Active

The diagram below shows the governance pipeline flow from proposal submission through delivery authorization in Onplana's 12-stage model.

Which PMOs need formal stage-gate governance

Not every PMO needs a 12-stage governance pipeline. The need correlates with three factors: project size, regulatory requirement, and decision authority distribution.

Regulated industries with audit requirements. Pharmaceuticals, aerospace, medical devices, and financial services operate in environments where project governance decisions are audit evidence. A gate approval is not just a process step: it is a documented record that a qualified person reviewed and authorized the project to proceed. This requires a timestamped audit trail, named approvers, and criteria documentation. Project Online's SharePoint-based governance provided this, imperfectly, before April 2026. Onplana's native governance provides it more reliably.

Capital-intensive portfolios. Construction, manufacturing, and energy PMOs typically run projects with high capital commitment at each phase gate. An authorization gate before the plan phase represents a multi-million-dollar commitment decision. The governance process exists to ensure that decision is made deliberately, by the right people, with the right information. Informal approval by email does not scale to the volume of projects a large capital portfolio generates.

Enterprise PMOs managing resource-contended portfolios. When there are more projects than available resources, portfolio analysis at the authorization gate is where trade-off decisions happen. PMOs without a formal authorization gate tend to authorize everything and manage the resource conflict reactively, which produces the overallocation pattern documented in resource overallocation analysis.

Smaller PMOs with simpler delivery. For teams running fewer than twenty projects with low regulatory exposure and simple authority structures, a 12-stage pipeline is overhead without benefit. A lightweight approval at project kickoff and a formal close review may be sufficient. Onplana's pipeline stages are optional: you configure the stages that apply to your PMO and leave the rest inactive.

What to do if you are still running Project Online governance

If your governance workflows stopped running in April 2026 and you are still on Project Online, you have three options:

Option 1: Rebuild in Power Automate, temporarily. Power Automate can replicate most of what SharePoint 2013 workflows did, using the Project Online connector and the Approvals connector. Simple single-step approvals take two to three days to rebuild. Complex multi-stage demand workflows take two to four weeks. This option makes sense if your September 30 migration timeline is compressed and you need governance restored now.

Option 2: Use interim manual governance. Document the approval process and run it via email or Teams approval cards for the remaining migration window. This is operationally painful but faster than rebuilding in Power Automate if you are migrating within 90 days. Keep a log of approvals for audit purposes: the governance event needs to be recorded even if the recording mechanism is manual.

Option 3: Accelerate migration to a tool with native governance. If the governance breakdown is the forcing function, treat it as such. Migrate the highest-priority projects first, configure Onplana's pipeline for those projects, and run governance in Onplana while completing the remaining migration. The PMO Maturity Assessment can help identify which governance capabilities your PMO needs to configure first in the new environment.

Migration considerations for governance-heavy PMOs

Governance is one of the most under-planned areas in Project Online migrations. Most migration checklists focus on schedule data (tasks, dependencies, baselines) and resource data. Governance configuration is usually categorized as "rebuild in the new tool" without a plan for how long that rebuild takes or what happens to in-flight approvals during the transition.

In practice, governance rebuild takes longer than expected because:

Gate criteria require documentation before they can be configured. If your PMO's authorization gate criteria exist only in a SharePoint Designer workflow file and in the institutional knowledge of the PMO admin who built it, rebuilding requires archaeology before configuration. Extract and document the criteria before you start configuring the new tool.

In-flight proposals need a migration path. Projects currently stuck in a broken approval queue need to be resolved before cutover. The options are: manually approve and advance them in Project Online (if the approval authority is willing to do this via an ad-hoc process), or migrate them to the new tool with their current stage preserved and let the new governance pipeline handle the remaining approvals.

Approver training runs parallel to PM training. Most migration training plans focus on PMs. Approvers (steering committee members, portfolio managers, business unit leads) use the tool differently and need separate onboarding. If they are not trained on the approval interface before cutover, gate requests will pile up unapproved in the new tool.

Use the free Migration Preview to scope your migration and identify which projects have governance stage information that needs to be preserved. The tool walks through what migrates automatically from Project Online and where manual configuration is required.

Run the PMO Maturity Assessment The free PMO Maturity Assessment takes about 10 minutes and identifies where your governance process stands relative to your organization's needs. It helps prioritize which governance capabilities to configure first in a new tool. No signup required. Open the assessment

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