Improve Resource Capacity and Baseline Governance in Planner Premium
Microsoft Planner Premium works well for assigning individual users to tasks within a single plan. However, significant limitations appear when organizations move from managing isolated plans to managing programs and portfolios. For Planner Premium to become a truly enterprise-ready project and portfolio management solution, Microsoft should urgently address the following three areas. 1. Cross-plan resource capacity management When a person is assigned to several tasks or multiple plans, Planner Premium can accumulate more work than the person’s actual daily, weekly, or monthly capacity. Although effort can be adjusted manually in the Assignments view, this becomes extremely difficult when managing many tasks, resources, projects, and concurrent assignments. Organizations need a consolidated capacity management capability across all plans, programs, and portfolios. Planner Premium should allow organizations to: Define each person’s available capacity. Allocate people using percentages, such as 20%, 50%, or 75%. Consolidate assignments across multiple plans. Detect overallocations before they affect delivery. Compare demand versus capacity by day, week, and month. Consider vacations, absences, calendars, and reduced availability. Generate warnings or optionally prevent assignments that exceed capacity. Support resource-leveling and workload redistribution. The People view is useful within an individual plan, but portfolio managers need visibility across the entire portfolio. Without cross-plan capacity management, portfolio planning remains incomplete because organizations cannot reliably determine whether they have enough available resources to deliver their commitments. 2. Generic resources and role-based planning Project plans are often created before the final team members are known. At the planning stage, organizations may know that they need a SAP consultant, solution architect, developer, business analyst, or infrastructure specialist, but they may not yet know the specific person who will perform the work. Planner Premium should support generic resources or role-based placeholders that can be assigned to tasks before a named person is confirmed. These resources should include information such as: Required role or profile. Skills and experience level. Required capacity. Planned participation period. Estimated cost or rate. Business unit or location. Staffing status. Once the appropriate person is identified, the generic resource should be replaceable without losing the planned tasks, dates, effort distribution, cost information, or dependencies. This is essential for resource forecasting, staffing requests, project approval, and early-stage portfolio planning. 3. Baseline security and separation of duties The project baseline is the approved reference used to measure schedule and effort deviations. For this reason, baseline creation, replacement, and deletion should not remain freely available to every user who can edit the plan. In many organizations, the project manager maintains the schedule, while the PMO, portfolio administrator, sponsor, or governance committee controls baseline approval. Allowing the same person to modify both the current schedule and the baseline against which performance is measured creates a clear conflict of interest. Planner Premium should introduce optional baseline governance capabilities, including: A dedicated Portfolio Administrator or PMO role. Separate permissions to create, replace, or delete baselines. A baseline change request and approval workflow. Mandatory justification for baseline changes. Complete audit history. Protection or locking of approved baselines. Comparison between the original baseline, current approved baseline, and current schedule. Integration with formal project change-management processes. This should be configurable. Smaller organizations may prefer a simple model, while organizations with mature governance processes need stronger controls and separation of duties. Why this is urgent Microsoft Planner Premium is increasingly being positioned as a solution for project and portfolio management. However, portfolio management requires more than consolidating project status, dates, and progress. It also requires: Visibility of resource demand and availability across multiple plans. The ability to plan resources before individual people are confirmed. Governance controls that protect approved project baselines. These are not minor enhancements. They are foundational capabilities for enterprise project, program, and portfolio management. Microsoft has a major opportunity to make Planner Premium considerably more valuable for PMOs and organizations managing multiple concurrent projects. I strongly encourage the Microsoft Planner product team to prioritize: Enterprise resource capacity management. Percentage-based allocation. Generic resources. Cross-plan workload consolidation. Portfolio-level resource forecasting. Controlled baseline permissions and approvals. These improvements would significantly reduce manual work, prevent resource overcommitment, strengthen governance, and make Planner Premium a much more credible enterprise PPM platform.Guidance on Planner Premium, Dataverse and Power Automate
Hoping this title invites you to share more knowledge around Planner Premium, Dataverse and working with Automate Scenario: I have a user inside our company saying i need access to Dataverse since he wants to automate some task creation with regards to planner premium. I am pretty ok with that, so he needs a Power Automate Premium license. Although looking at the data in the Projects data tables in the default environment their business units are the root BU - getting a little concerned. Are all projects and related data available for all people that can read the Dataverse tables? If you have some insights or experience please comment :) Could they develop that in a development or sandbox environment before piping it to a designated environment? but there are no Projects tables in dev or in sandbox environment. Main problem: there's so much information about planner and power automate that it's impossible to actually find any guidance around this scenario amongst all classic planner hits