Power Platform, set up to scale
Separate Dev, Test and Prod environments, service accounts instead of personal connections, and SOPs and RACI, so a growing team can ship automation safely.
- WhenBuild in Dev
- ThenTest with real scenarios
- ThenPromote to Prod
- ResultRuns under a service account
- Power Platform
- Power Automate
- Microsoft Planner
- Microsoft Entra ID
The problem
Flows built in personal accounts break when people change roles or leave, and without separate environments, experiments sit right next to production.
What I set up
- Dev, Test and Prod environments in Power Platform
- A dedicated service account for connections, so automations don’t depend on any one person
- A Microsoft Planner structure with SOPs and RACI for every active project
Why it matters
Automation becomes a practice the whole team can run, not a pile of personal flows.
Where it fits
- Teams growing past a few flows
- IT departments
- Regulated industries
- Automation practices