Microsoft 365 PPM 2026: Project for the Web + Power Apps Enterprise Implementation Guide

TL;DR

• The Microsoft 365 Project Portfolio Management (PPM) platform in 2026 is fundamentally different from the SharePoint-based Project Online and Project Server world that enterprises ran for the previous decade. The replacement stack is Project for the Web + Microsoft Dataverse + Power Apps + Power BI + Roadmap.
• For enterprises with active Project Online deployments, the migration path is now well-defined but non-trivial. Project Online is on a published end-of-life trajectory, and the migration to the new stack is the dominant PMO modernization project for 2026.
• Project for the Web is the day-to-day project planning experience for project managers. Tasks, dependencies, resources, schedules — the familiar surface, modernized on the Power Platform.
• Power Apps PPM is the configuration layer that turns Project for the Web into an enterprise portfolio management capability — custom intake forms, gating workflows, capacity planning, demand management.
• Power BI is the reporting layer over the Dataverse-backed portfolio data, providing executive portfolio dashboards, resource utilization views, and milestone tracking.
• Roadmap is the high-level visualization layer for portfolio-level program timelines.
• This guide is for PMO leaders, Microsoft 365 architects, and enterprise data teams designing a modern PPM platform on Microsoft 365.

Executive Summary

For 15 years, enterprises ran their PMO on Microsoft Project Online (and before that, Microsoft Project Server). The architecture was familiar — SharePoint as the data layer, Project Web App as the user interface, Project Professional desktop as the planning tool. Hundreds of Fortune 500 PMOs were built on this stack.

That world is ending. Microsoft has placed Project Online on an end-of-life trajectory. The replacement architecture is built on the Power Platform: Project for the Web as the planning surface, Microsoft Dataverse as the data layer, Power Apps as the configuration and customization surface, Power BI as the analytics layer, and Roadmap as the portfolio visualization.

For enterprises running an active Project Online deployment, the migration to the new stack is the dominant PMO modernization project of 2026. For enterprises building a PMO from scratch on Microsoft 365, the new stack is the destination — there is no reason to build new capabilities on the deprecated Project Online platform.

This guide walks through the architecture, the migration sequencing, the customization patterns, and the EPC Group implementation framework for a modern Microsoft 365 PPM deployment.

Why the Architecture Changed

The previous PPM architecture was a creature of its time. Project Server launched in 2003 on SharePoint 2003; Project Online was the SaaS evolution starting in 2013. The architecture's strengths — deep integration with Project Professional desktop, the Project Web App scheduling experience — were attached to limitations that mattered more over time:

1. SharePoint as a data layer is the wrong abstraction. SharePoint lists were never designed for the row-level CRUD performance that PPM workloads require. Performance degraded for enterprises with thousands of active projects.

2. Project Professional desktop is a 30-year-old code base carrying limitations that are increasingly difficult to address.

3. Custom Project Server extensibility was a dead end. EPM extensibility patterns (event handlers, custom fields, custom workflows) were tied to the SharePoint and Project Server APIs, and Microsoft's investment focus shifted to the Power Platform extensibility model.

4. Power BI integration was bolt-on, not native. Reporting on Project Online required ODATA connectors, complex DAX, and frequent refresh issues.

The new architecture solves these issues:

• Dataverse is purpose-built for line-of-business application data. Row-level performance, relational integrity, schema versioning, and standard APIs.
• Project for the Web is a modern web application built on Microsoft's modern stack. It does not depend on the Project Professional desktop code base.
• Power Apps is the extensibility model, not a custom code surface. Customizations are configurable and durable across product versions.
• Power BI integrates natively with Dataverse — no ODATA workarounds.

The Stack Components

Project for the Web

The project manager's primary surface. Provides:

• Task management. Hierarchical task lists with start dates, durations, dependencies, assignments.
• Three views. Grid (task list), Board (Kanban-style), and Timeline (Gantt-style).
• Resource assignment. Each task can have one or more assigned resources from the Dataverse resource pool.
• Microsoft Teams integration. Project for the Web can be embedded as a Teams tab; project members can collaborate within Teams while the schedule data lives in the Project for the Web back end.
• Conditional formatting and filters. Visual organization of large project schedules.

Project for the Web is accessed via web browser; there is no required desktop installation.

Microsoft Dataverse

The data layer underneath Project for the Web. Standard Dataverse capabilities:

• Tables. Projects, Tasks, Assignments, Resources, and a configurable set of custom tables for organizational extensions.
• Relationships. Foreign-key relationships maintain referential integrity across project entities.
• Security. Dataverse security model with business units, security roles, field-level security, and row-level security via owner teams.
• APIs. Standard Dataverse Web API for integration.
• Audit. Standard Dataverse audit log for changes to project data.

The Dataverse environment hosting PPM should typically be a dedicated environment (separated from CRM or other Power Apps workloads) to allow for PPM-specific configurations and security.

Power Apps for PPM customization

The extensibility surface for the PPM solution. Common customizations:

• Project intake forms. A model-driven Power App that captures new project proposals with the metadata (sponsor, budget, business case, gating stage) the organization needs.
• Stage-gate workflow. Power Automate cloud flows that move projects through approval gates with conditional logic.
• Resource demand management. A model-driven app or canvas app for resource managers to review demand against capacity.
• Custom fields. Dataverse columns added to the Project, Task, or Resource tables for organization-specific metadata.

Power BI for portfolio analytics

The reporting layer. Common portfolio analytics:

• Portfolio dashboards showing the entire portfolio of projects, status, milestone health, budget vs. actual.
• Resource utilization views showing capacity vs. demand by role, by department, by time period.
• Schedule risk views flagging projects with at-risk milestones.
• Budget views showing portfolio-level financial tracking.

Power BI semantic models built on Dataverse via the native Dataverse connector. Refresh cadence depends on the operational tempo — typically daily or sub-daily.

Roadmap

The high-level portfolio visualization. Roadmap is a separate experience from Project for the Web, focused on aggregating multiple projects or programs into a single visualization for executive consumption.

The Migration from Project Online

For enterprises with active Project Online deployments, the migration to the new stack is the dominant 2026 PMO project. The migration spans several dimensions:

Data migration

Project Online data lives in SharePoint lists and the Project Server Reporting database. The migration to Dataverse involves:

1. Inventory the source data. Projects, tasks, resources, custom fields, project sites, project workflows.
2. Map source schema to Dataverse schema. Standard mappings are documented by Microsoft; organization-specific custom fields require explicit mapping.
3. Stage the data extraction. Extract project, task, assignment, resource, and custom field data into a staging environment.
4. Transform. Standard transformations: ID remapping, lookup resolution, date format normalization, calculated field rebuilds.
5. Load. Dataverse Web API or bulk-import tools to populate the target environment.
6. Validate. Comparison reports between source and target verify data integrity.

For organizations with hundreds of active projects, the data migration is typically 4–8 weeks of dedicated work depending on data complexity and custom field count.

Customization migration

Project Online customizations — custom fields, custom workflows, custom event handlers — do not migrate to the new stack as-is. Each customization requires a rebuild on the Power Platform.

The rebuild is typically a simplification opportunity: many customizations in Project Online accumulated over years are no longer needed, or can be replaced with simpler Power Platform patterns. EPC Group's typical pattern is to inventory the customizations, classify each as Keep / Rebuild / Retire, and design the new-state customization surface around the Keep and Rebuild categories.

User adoption

Project for the Web is a different user experience from Project Web App. Project managers who have spent years in PWA need training and adoption support to be productive in the new surface.

The adoption work runs in parallel with the migration: pilot a business unit on the new stack, train, harvest feedback, refine, then expand.

Customization Patterns

Project intake

A standard pattern: a model-driven Power App that presents a project intake form, captures the required metadata, and triggers a stage-gate workflow.

The form fields typically include:

• Project name, sponsor, requested manager, requested start date.
• Strategic alignment (program, portfolio, strategic initiative).
• Initial budget request and funding source.
• Business case summary (or attachment).
• Initial scope and high-level deliverables.
• Risk and dependency information.

The intake form's data lands in a custom Dataverse table (typically epc_ProjectRequest or similar) and a Power Automate flow handles the routing.

Stage-gate workflow

A standard pattern: Power Automate cloud flows that move project requests through approval stages (Idea → Concept → Charter → Approved → Active → Closed). Each gate has a defined approver and required artifacts.

The Dataverse Business Process Flow surface can visualize the gate progression on the project record.

Resource capacity vs. demand

For PMOs with explicit resource capacity planning:

1. Capacity is configured in the resource table (FTE per resource, calendar exceptions).
2. Demand is derived from task assignments across all active projects.
3. A Power BI report compares capacity vs. demand by role, by time period.
4. A Power App provides resource managers a UI to rebalance assignments.

Financial tracking

For PMOs tracking budget vs. actual:

1. Budget data per project is captured at project creation.
2. Actual costs are integrated from the financial system (Dynamics 365 Finance, SAP, or similar) via Dataverse virtual tables or scheduled imports.
3. Variance analysis runs in Power BI.

Power BI Portfolio Dashboards

Standard dashboard patterns

EPC Group's typical Power BI dashboard suite for a Microsoft 365 PPM deployment:

1. Portfolio Heat Map. All projects by stage, with status indicators (Green / Yellow / Red) and last-update freshness.
2. Milestone Calendar. Upcoming milestones across the portfolio, color-coded by criticality.
3. Resource Utilization. Allocation percentage by resource, by role, by department.
4. Budget Variance. Budget vs. forecast vs. actual by project, with portfolio aggregates.
5. Schedule Performance. Earned value-style schedule tracking.
6. Risk Register. Open risks across the portfolio, with severity heat-mapping.
7. Stage-Gate Throughput. Projects flowing through gates over time, identifying bottlenecks.

Semantic model design

The Power BI semantic model backing these dashboards is a star schema over the Dataverse PPM tables:

• Fact tables: Tasks, Assignments, Time Entries, Cost Records, Risks.
• Dimension tables: Projects, Resources, Calendar, Departments, Programs.
• Measures: Standard PMO measures (Schedule Variance, Cost Variance, Earned Value, % Complete, Resource Utilization).

The semantic model can run on DirectLake mode if the Dataverse data is mirrored to OneLake (a 2026 capability), or on Import mode with daily refresh for most deployments.

EPC Group Implementation Framework

For a Fortune 500 PMO migrating from Project Online or building a new PPM platform on Microsoft 365, the standard EPC Group pattern:

Weeks 1–4: Discovery and architecture.

• Current-state PMO process inventory.
• Project Online customization inventory (if migration).
• Target-state architecture design.
• Dataverse environment design.
• Power Platform license plan.

Weeks 5–10: Foundation build.

• Dataverse environment provisioning.
• Standard PPM solution deployment (the Microsoft-provided PPM application).
• Custom Dataverse tables for organization-specific fields.
• Security role design and assignment.
• Initial Project for the Web pilot setup.

Weeks 11–16: Customization build.

• Project intake Power App.
• Stage-gate workflows in Power Automate.
• Custom forms and views.
• Resource capacity/demand views.
• Financial integration if applicable.

Weeks 17–22: Power BI portfolio analytics.

• Semantic model design on Dataverse.
• Dashboard suite implementation.
• Distribution and access setup.

Weeks 23–26: Data migration (if migrating).

• Project Online data extraction.
• Transformation and validation.
• Load to Dataverse.
• Cutover preparation.

Weeks 27–30: Adoption and rollout.

• PMO training program.
• Pilot business unit rollout.
• Feedback incorporation.
• Broader rollout.

Weeks 31–34: Stabilization and handover.

• Production hardening.
• Operational runbooks.
• PPM Center-of-Excellence stand-up.
• Documentation handover.

The 34-week timeline is for a Fortune 500 PMO with hundreds of active projects and a substantial Project Online migration. Smaller PMOs run shorter; greenfield deployments without migration can compress to 20 weeks.

Common Pitfalls

Across the Microsoft 365 PPM implementations EPC Group has guided, the recurring problem patterns:

1. Trying to migrate every Project Online customization 1:1. Many Project Online customizations are no longer needed. Use the migration as a simplification opportunity.

2. Under-investing in user adoption. Project for the Web is a different experience from Project Web App. Project managers need training and support.

3. Skipping the Dataverse security role design. Default Dataverse security is permissive. Enterprise PMO deployments need a deliberate role design.

4. Mixing PPM with CRM or HR Power Apps in the same Dataverse environment. PPM workloads have specific characteristics that benefit from a dedicated environment.

5. Forgetting about Project Online retirement timeline. The migration timeline should be set against Microsoft's published Project Online end-of-support dates, not assumed indefinite availability.

6. Power BI semantic-model design as an afterthought. The reporting design should be part of the Dataverse schema design from week one, not bolted on at week 22.

7. Inadequate financial integration scope. If budget tracking is part of the PPM scope, the integration with the financial system needs explicit attention. Manual budget data entry is a known failure mode.

Frequently Asked Questions

What is Microsoft 365 PPM in 2026?

Microsoft 365 Project Portfolio Management in 2026 is the stack consisting of Project for the Web (project planning), Microsoft Dataverse (data layer), Power Apps (customization layer), Power Automate (workflow), Power BI (analytics), and Roadmap (portfolio visualization). It replaces the previous Project Online and Project Server architecture.

Is Project Online being retired?

Microsoft has placed Project Online on a published end-of-life trajectory. Specific end-of-support dates are documented in the Microsoft 365 service description; verify the current dates against the Microsoft documentation for your tenant's planning timeline. Most enterprises are completing migrations during 2026.

What is Project for the Web?

Project for the Web is the web-based project planning experience that replaces Project Web App. It provides Grid, Board, and Timeline views over project schedules; integrates with Microsoft Teams; and stores data in Microsoft Dataverse.

Does Project for the Web require Project Professional desktop?

No. Project for the Web is a browser-based experience. Microsoft Project Plan 1 and Plan 3 licenses include Project for the Web access. Microsoft Project Plan 5 also includes the desktop client for users who prefer it.

What is the Microsoft Dataverse?

Microsoft Dataverse is the data platform underneath Microsoft Power Platform applications. For PPM, Dataverse stores all project, task, resource, and assignment data with a relational schema, standard APIs, audit logging, and security model.

How does Power BI integrate with PPM?

Power BI connects to Microsoft Dataverse via the native Dataverse connector. Semantic models can be Import or DirectQuery; with the 2026 Dataverse-to-OneLake mirroring, DirectLake mode is also possible for high-performance scenarios.

What is Roadmap?

Roadmap is the portfolio visualization experience in Microsoft 365. It aggregates multiple projects or programs into a high-level timeline view for executive consumption.

How long does a typical Project Online to Microsoft 365 PPM migration take?

For a Fortune 500 PMO with hundreds of active projects and substantial customization, the migration is typically 30–34 weeks. Smaller PMOs run shorter; greenfield deployments without migration can complete in 20 weeks.

Can I customize Project for the Web?

Customization happens through Power Apps and Power Automate, not within Project for the Web itself. Custom Dataverse tables, custom forms via model-driven Power Apps, custom workflows via Power Automate, and custom analytics via Power BI provide the customization surface.

How does the new stack support resource capacity planning?

Resource capacity is captured in the Resource table in Dataverse. Demand is calculated from task assignments across projects. Power BI reports compare capacity vs. demand, and Power Apps provides resource managers a UI to rebalance.

What about scheduling? Can I manage dependencies and critical paths?

Yes. Project for the Web supports task dependencies (finish-to-start, start-to-start, finish-to-finish, start-to-finish) and calculates schedule paths. Complex schedule analysis features may still be richer in the Project Professional desktop client.

What is the relationship between Project for the Web and Microsoft Planner?

Microsoft Planner is a lightweight task management tool intended for team-level work. Project for the Web is for project-level work with structured schedules, dependencies, and resource management. The two products serve different scopes and can coexist in the same tenant.

How do I migrate Project Online project templates?

Project Online project templates do not migrate as-is. Equivalent templates are configured in the new stack via a combination of standard Project for the Web templates and Power Apps configurations. The template strategy is part of the foundation-build phase of the migration.

What licensing do users need for Microsoft 365 PPM?

Project Plan 1 is the entry-level license for occasional project consumers. Project Plan 3 includes Project for the Web full functionality. Project Plan 5 adds portfolio capabilities and the desktop client. Resource managers and PMO leaders typically use Plan 3 or Plan 5. Verify the current license matrix against the Microsoft 365 service description for your tenant's planning.

How does EPC Group support Microsoft 365 PPM implementations?

EPC Group works with Fortune 500 PMOs on Microsoft 365 PPM implementations and Project Online migrations. The standard pattern is a 30–34 week engagement covering discovery, foundation, customization, analytics, migration (if applicable), adoption, and stabilization. Our consultants — including Microsoft Press bestselling author Errin O'Connor — bring direct PPM implementation experience and compliance-native delivery for regulated-industry PMOs.

Does the new PPM stack work for hybrid project methodologies (waterfall + agile)?

Yes. Project for the Web supports both Grid (waterfall-style) and Board (Kanban / agile-style) views over the same project data. Hybrid methodologies are common — strategic milestones tracked at the project level, execution tracked at the sprint level in Azure Boards or DevOps and rolled up to the portfolio.

Next Steps

If your enterprise is operating Project Online or planning a new PMO platform on Microsoft 365, the practical next steps:

1. Review Microsoft's published Project Online end-of-support timeline against your migration plan.
2. Inventory current Project Online customizations and classify each as Keep / Rebuild / Retire.
3. Design the target Dataverse environment and security role model.
4. Pilot Project for the Web with a single project team to validate the experience.
5. Engage a partner with deep Microsoft 365 PPM implementation experience to compress the planning timeline.

EPC Group has 29 years of enterprise Microsoft consulting experience and is Microsoft Solutions Partner with the core designations. We were historically the oldest continuous Microsoft Gold Partner in North America from 2016 until the program's retirement. Our consultants — including Microsoft Press bestselling author Errin O'Connor — bring direct PPM implementation experience across hundreds of engagements including Fortune 500 PMO migrations and regulated-industry deployments. To discuss your PPM modernization, contact EPC Group for a 30-minute discovery call.