Share
Report
2We’re currently exploring how to use Power Platform to deliver services in a managed services model across multiple clients.
The main challenge is around data segregation. The most straightforward option seems to be creating a dedicated production environment for each client. That works for compliance, but it introduces some major pain points in practice:
-
Maintenance overhead – every environment needs to be managed separately, which quickly drives up operational costs.
-
Release management – fixes and updates have to be deployed in every single environment, which adds complexity.
-
Initial setup – each new client requires cloning and configuring the solutions from scratch.
-
Central monitoring – if I want to track processes across all clients, I end up connecting to each Dataverse environment as if they were external systems, even though they all sit within the same infrastructure.
I’d love to hear from anyone who has faced this type of scenario:
- How did you balance the need for strict data segregation with the cost and operational impact?
- Have you found patterns, architectures, or tools that simplify this model while keeping governance and compliance intact?
- Any lessons learned from real-world implementations would be extremely valuable.
All responses (
Answers (
