How can we improve Project?

← Project for the web

Project for the web: Change licensing to allow for extensibility at a sensible price

Currently extending Project for the Web with the Power Platform requires a Project Plan P3/P5 subscription. This very expensive given that you already have to pay for a PowerApps subscription as well. This is especially drastic if you need to provide access for team members. Their numbers are normally much higher than the PMs.

112 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Trutz-Sebastian Stephani shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • James Boman commented  ·   ·  Flag as inappropriate

    Other O365 workloads like SharePoint Online, Dynamics, etc. come with the PowerApps and Flow "Seeded" capabilities for those workloads.

    i.e.
    - If you have SharePoint you can use PowerApps and Flow against SharePoint.
    - If you have Dynamics you can use PowerApps and Flow against Dynamics.

    Unfortunately Project doesn't follow this strategy, and requires both a high-level product SKU (P3) and standalone PowerApps licensing (per App or Per user - or in pre Oct 2019 terminology PowerApps P1 or P2). To use the Power BI content pack included with Project also requires additional licensing.

    This pricing appears extreme and needs to improve to make extensibility possible.

  • Michael commented  ·   ·  Flag as inappropriate

    As long as you are allowed to configure the existing PowerApps without requiring an additional license I feel this is ok as is.

Project for the web: Project

Categories

Feedback and Knowledge Base

(thinking…)