Blog Post

Project Blog
1 MIN READ

Flexible Deployment for Project for the web is here!

Microsoft Project Team's avatar
Microsoft Project Team
Bronze Contributor
Feb 18, 2021

We are pleased to announce the availability of Flexible Deployment for Project for the web.  As a part of the Microsoft Dataverse (formerly known as Common Data Service (CDS)) platform, Flexible Deployment enables you to create different environments based on organizational, business unit, or teams needs. 

 

In addition to the existing Default environment,  you now have more choices to spin up different kinds of Dataverse environments for the Project for the web:  Production and Sandbox.  With Production, your organization can create specific environments such as limiting access to data for the HR department, deploying different customizations for different sets of users, or staying compliant on data residency requirements if your users and tenant are not located in the same country. The Sandbox environment allows for Application Lifecycle Management to develop and test customized solutions for Project before rolling out to production. 

 

You can use Flexible Deployment with Project Plan 1, Project Plan 3, and Project Plan 5. Each subscription comes with a certain amount of storage

 

The choice of deployment gives you the flexibility and extensibility to stay on top of business needs while reducing complexity for your IT group.  Please refer to the links below to find out more.

  1. Learn how to get started in Deploying Project.
  2. Help end users learn how to get started with the Project Power App.
  3. Learn about the new Project for the Web Security Roles.
  4. If you have additional questions, check out Frequently Asked Questions.
Updated Feb 18, 2021
Version 1.0

2 Comments

  • TCHMS's avatar
    TCHMS
    Copper Contributor

    Hi Microsoft Project Team ,

    Deploying project for the web on a non-default environment does not provide access to the same features supported in an instance deployed on a default environment.

    There are things that you can do with Project for the web in the Default Environment that you cannot do in any other environment.

    I am looking for a clarification from MS Project Team about this unexpected behaviour of project for the web in named environnement. Is there any update on the product roadmap to repair the gap in user experience and to get parity in default and named Power Platform environments ?

    Can anyone from Microsoft provide some guidance on this?

     

  • TijnTacke's avatar
    TijnTacke
    Copper Contributor

    This is fantastic news! We've been eagerly awaiting this feature. Will make Application Lifecycle MAnagement for Project for Web possible and open up a whole new range of possibilities.