Power Platform Community Forum Thread Details

Best practices for managing the development of multiple solutions

Dear,

We are looking for a better way to organize our development environments.

We are a company that makes custom solutions for different customers. We build these solutions either on a "empty" dataverse environment or on top of D365 Customer Engagement environments.

Currently we setup DEV/TEST/UAT/PROD environments on the tenant of each customer for which we build a solution. That means that whenever we need to develop or test a solution, we have to login to that specific tenant. It also means we need the customers to buy additional licenses to assign to us in order to be able to do our work on their tenant...

We would like to know if there is a better way to organise these DEV/TEST environments in our own tenant. Since we only have the "default" database capacity of around 10GB, we would hit that limit quite fast if we create these environments for a few customers.

We could of course buy additional capacity, but the price (around €30 per month per 1GB) is quite high, knowing that each environments needs a minimum of 1GB...

Secondly, if we are customizing on top of D365, we also need the same license (Sales Pro, Sales Enterprise,....) as the client for which we are working. That means we would need to buy licenses for each type of D365 one of our customers uses, and that for each of our developers...

Any advice on a better way to manage this?

Thanks,

Koen

Quick Links

Leaderboard > Power Apps - Power Apps Pro Dev & ISV