Thank you for laying out the long-term vision for Planner.
As someone using premium plans to manage a $3M project, I can’t move to a unified plan (currently a basic plan) until it reaches parity with premium for schedule management and reporting. It’s good to see Goals, Timeline and custom fields already carried across, and dependencies listed on the roadmap. But for enterprise delivery, the remaining gaps are significant:
Task dependencies (FS, SS, FF, SF): Can you confirm all four types, plus lead/lag, are in scope, and share a target date? They’re essential for critical path and downstream impact analysis.
Auto-scheduling: - Manually shifting dozens of downstream dates when one deliverable slips isn’t viable at scale.
Baselines: - Critical for governance, variance tracking and reporting slippage against the approved plan.
Milestones: - Needed for phase gates, key deliverables and executive reporting checkpoints.
Reporting: - The move to a fully Azure-based service and the end of investment in Dataverse-based plans raise real questions for Power BI. Today, premium plan data in Dataverse lets us run standardised, automated portfolio dashboards (e.g. via Microsoft’s Power BI template). What’s the equivalent for unified plans? Copilot-generated reports are useful, but they don’t replace a governed data model. If organisations have to build custom pipelines through the (currently beta) Graph APIs or Power Automate to replicate this, that’s substantial overhead.
I appreciate that premium plans remain supported in the interim. A published migration path and timeline for premium-to-unified would help those of us running multi-million-dollar portfolios assess and plan the transition either sideways or to another product/solution.
I see value in the new AI and collaboration features. But for complex delivery, a unified plan isn’t truly unified until it has dependencies, auto-scheduling, baselines, milestones and clear Power BI enterprise reporting support.