Make Project on the Web available in new Environments
Power Platform supports multiple environments (Automate and Apps). It should be possible to have a separate Project environment also. The default environment is not enough for global organizations and multiple, different entities. Make it possible to create Project environments just like Automate (Microsoft Flow) and Power Apps.
We’re working on it!
By March of next year, you will be able to deploy Project for the web to different environments. Thank you all for submitting this idea to User Voice and voting on it!
Here’s the official update to the M365 roadmap. https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=Microsoft%20Project%2CIn%20development
Dennis Gaida commented
And your wish was heard: https://www.microsoft.com/de-de/microsoft-365/roadmap?featureid=67156&rtc=1&market=de
Hello, we would use Project for the Web immediately across the company if we had the option to select the environment project specific. Without this flexibility, such as that offered by Forms Pro, it is impossible for us to use Project for the Web.
Legally not possible!
We use the default environment across the group, 300 thousand employees for personal use.
Structurally not possible!
We have over 800 individual companies throughout the group that have to separate their data, in some cases very strictly, due to legal requirements.
Without the option to distribute project data to different environments, the product is unfortunately not usable for us.
..we would really like to use it ;-)
Yes, much needed feature. Integration with Dynamics is key and Dynamics in the default environment is a no-no. Please fix asap.
Is there a solution for this problem right now ?
We need multiple environments in order to use P4W in our international company. Project for the web is unusable for enterprise customers until it can be managed in multiple/separate non-default environments. Until this is done, we are on hold.
Project for the web is unusable for enterprise customers until it can be managed in multiple/separate non-default environments. Until PftW can be turned on in non-default environments, the CDS/PowerApps extendibility and customization features are also unusable.
MS don't even like it when people import unmanaged solutions. It goes against all best practices to be making changes in the live production environment. If you're going to use the CDS, do it right!
One option while we are waiting for proper ALM for PftW is to create a year long demo tenant and use that for creating your managed solutions for importing into your default solution.
Enterprise wide deployments will require more than environment.
Tamara Frey commented
Being able to develop and test on a separate org or providing different customizations to different departments in one tenant using named orgs is a must have!
With the news that PSA now uses PftW and this will install on named orgs, but only in the PSA context, makes me wonder what the issue is with providing this to non-PSA users.
The current functionality requires making changes to production environment. There should be support for multiple environments to support dev life cycle.
Same view, having own environment instance for project web only, detailed Project for web Dynamics requirements (CDS) are not allowed from security on the dynamic default instance, one reason