Using a Developer type environment as part of ALM

Like (0) Share

Report

Posted on 24 Aug 2023 10:46:16 by Mattb-Motive

195

I've seen some MS docs talking about using the Developer Environment as part of an ALM strategy (e.g. project-for-the-web/customize-pmo-accelerator-managed-solution).

What are people's thoughts/opinions about using a Developer type environment as the Dev (and Test) environments?

Apart from capacity limitations are there any other cons? Should Developer type environments only be for personal use still? Is it better to use sandbox for the Dev environment?

Categories:

Environment

All responses (1)

Answers (1)

Verified answer

joe_hannes_col 1,843 Super User 2024 Season 1 on 24 Aug 2023 at 13:43:09

Like (1)

Report

Re: Using a Developer type environment as part of ALM

Hello @MattB_Motive,
We are using developer environments for both development and testing, and in testing environments we frequently have multiple users. We have integrated them into our DevOps pipelines without any issues.
And according to the documentation by Microsoft, using the environments with multiple users for development and test purposes is explicitly supported: "The ability to share apps with team members for development and testing purposes." (Source).
However, according to another page, developer environments are for personal use only: “[The] developer environment is intended for use by only the owner of the environment.” (Source).
Since it's working, I'm sticking to the more liberal interpretation 🙂

Regarding other limitations: You don't have AI Builder credits in dev environments.