To extend project for the web via cds, this is only achievable via leveraging the default CDS instance. The default instance is not designed to be production therefore creating a powerapp for end users leveraging this is not a good idea (as the whole company has environment maker access). We need the ability to create a production instance for CDS for project for the web.
I think the ability to install P4tW to new CDS environment would solve this.
That way we could set up a standard Dynamics UAT model with managed solutions etc.
Yes following the centre of excellence's best practice guidelines I agree Michael!
As part of the governance best practice guidelines from the Power Platform team, the default environment should never be used for line of business applications. Instead it should be considered to be a "Personal productivity" environment. Among the reasons for this is that it is automatically created by the first user who accesses the Common Data Service in the region closest to them. For large global clients this means that the default instance might be in an inappropriate data center. Security is also harder to control with the default instance. When new users sign up to a trial license of Power Apps they are automatically added to the Maker role within the default instance.