Philipp Emanuel Meran Consultant

I’ve encountered a limitation in the Power Platform when trying to assign different access levels (read/write) for different user groups to a specific solution within a single development environment. After researching and consulting Microsoft Support, it seems this is expected behavior.

The current recommendation is to create a dedicated environment per solution. However, managing 10+ environments for separate development and testing efforts introduces significant administrative overhead and complexity.

Suggestion:

Introduce the ability to share an entire solution, including all its components (connection references, environment variables, etc.), within a single environment, similar to how Power Apps or Power Automate flows can be shared.

This would greatly improve flexibility, reduce environment sprawl, and simplify governance, especially for teams managing multiple solutions in parallel.

Am I missing a critical reason why per-solution environments are preferred or necessary?