Restricting solutions in environment

(0) Share

Report

Posted on by ChristianDA

Hi,

We currently have a setup in our organization where our environments are separated based on departments (rather than dev/test/prod), but we would still like to incorporate at least a dev environment before publishing to prod.

We still want to keep the environments separate, so is there any way to keep development separate as well without having to create a new dev environment for each prod environment (which is around 10)?

I have tried to use business units to restrict/hide solutions across the departments in one environment, but as far as I can tell this is not possible, as solutions are managed on organizational level.

Is there any other way that this can be achieved?

All responses (1)

Answers (1)

Verified answer

ChrisPiasecki 6,389 Most Valuable Professional on at

Like (0)

Report

Re: Restricting solutions in environment

Hi @ChristianDA,

I'm afraid creating separate environments is the only way to prevent makers from modifying each others components.

You should look to implement source control management and automation so that each unmanaged solution can be stored in a repository. This way you can delete the dev environment when there is no active development occurring, then spin up one on-demand and import the unmanaged solution back in. You can also follow the same with test environments and only have them around when active testing is needed. This way you'll keep your storage under control and limit the number of environments to manage.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.