Power Platform
When a Power Automate flow should become a proper service
Automation that started as a convenience can become an unmonitored dependency. Signals that it is time to promote it.
Article ยท Power Platform
Low-code governance that does not block delivery
A Centre of Excellence should make good practice the easy path. When governance becomes an approval queue, makers route around it.
Power Platform governance usually starts after an incident: a business-critical app owned by someone who has left, or a flow moving personal data to a personal account. The instinct is to introduce approval before anything can be built. That instinct is understandable and usually counterproductive.
Tier by consequence
Not all applications carry the same risk. A three-tier model handles the vast majority of cases and lets scrutiny follow consequence rather than volume.
| Tier | Typical scope | Governance applied |
|---|---|---|
| Personal productivity | One maker, no shared data | Environment policy and data loss prevention only |
| Team solution | A team, non-sensitive data | Registration, named owner, standards guidance |
| Business critical | Cross-department or sensitive data | Architecture review, lifecycle management, support model, formal ownership |
Make the compliant path the fastest path
- Provide a starter solution with connection references, environment variables and a working deployment pipeline. Makers use it because it saves time.
- Publish component libraries and a branded theme so the correct visual result requires no effort.
- Automate registration: an app appearing in a managed environment prompts its maker for owner and tier, rather than waiting for a governance meeting.
Plan for succession
The most common low-code failure is not a security breach. It is an orphaned application: business-critical, undocumented, owned by a departed employee. Ownership records, co-owner requirements and periodic attestation cost little and prevent the situation entirely.
Written by
Daniel Osei
Daniel designs and delivers Dynamics 365 and Power Platform solutions, with a strong bias towards configuration, explicit process design and data quality controls that hold up long after go-live. He has spent much of his career untangling CRM implementations that recorded administration rather than supporting work.
- Dynamics 365
- Dataverse
- Power Apps
- Process design
- CRM data quality
Relevant industries
- Financial Services
- Government and Public Sector
- Healthcare