This document discusses establishing governance for Power Platform low-code development. It outlines why governance is important, including addressing shadow IT and cost control issues. It then covers key aspects of governance like defining environments, permissions, and data loss prevention policies. It also discusses compliance processes, project documentation standards, and monitoring maker behavior. Finally it discusses strategies for enabling citizen developers through training, communities, and support. The overall goal is to create a safe environment for low-code development while maintaining visibility and control.

1. Power Platform
Governance
W I T H

2. AGENDA
P o w e r P l a t f o r m G o v e r n a n c e
01. Intro
02. Why Low Code
03. Governance
04. Enablement
05. Discussion

3. ABOUT ME
Industrial engineer with enthusiasm for digital processes.
At AONIC since 2019 as consultant, trainer, project and product manager.
Constantin Seidel
Product manager Runpipe

4. ABOUT US
OUR MISSION
Runpipe offers a win-win environment, where businesses accelerate digital
transformation by gaining the independence they need from IT, information
security, and compliance departments. This win-win paradigm promotes data
culture by enabling risk free IT self-service, while retaining full visibility and
control.
 SaaS Startup, Part of AONIC GmbH
 Vast experience in adoption and governance
of Microsoft’s Power Platform
 Focus on enterprise customers

5. ABOUT YOU
How far are you establishing a governance in your organization?
• What is a governance?
• We want to establish a governance!
• We are in the setup!
• We already established a governance!
,

6. AGENDA
P o w e r P l a t f o r m G o v e r n a n c e
01. Intro
02. Why Low Code
03. Governance
04. Enablement
05. Discussion

7. • Everyone can use it*
• It is fast
• Development through User Interface
• Seperation of UI and Code
• Possibility to enhance Low Code
Solutions with actual Code
WHY LOW CODE?

8. LOW-CODE Solutions

9. POWER PLATFORM COMPONENTS
Power Apps Power Automate Power BI Power Virtual Agents
+
>700

10. LOW-CODE CHALLENGES
P A I N P O I N T S
IT
FINANCE
BUSINESS
Shadow IT & Fragmented
Purchases
Loss of Cost-Control
Feature & Service Over-
Purchasing
New Support & Operating
Model for Self-Service IT
Treating Cost Optimization
as a One-Time or
Time-Bound Exercise
Ungoverned App Spread
& Missing User Support
IT- Security / Data Loss
Privacy / GDPR

11. AGENDA
P o w e r P l a t f o r m G o v e r n a n c e
01. Intro
02. Why Low Code
03. Governance
04. Enablement
05. Discussion

12. Building a
Governance
is about
creating a
safe space
for Makers

13. ENVIRONMENTS BY AUDIENCE
Environment

14. ENVIRONMENT STRATEGY (1)
Environment

15. ENVIRONMENT STRATEGY (2)
Environment

16. ENVIRONMENT STRATEGY
• Default Environment should be the most restrictive one (Personal Productivity)
• Restrict Environment creation to Administrators
• Create Environments for audiences (e.g NA, EMEA etc. OR Controlling, Sales etc.)
• Create Environments for staging (e.g. Dev_NA, Prod_NA)
• Create dedicated Environments for critical Projects
• Implement a process for requesting access or creation of environments

17. DATA LOSS PREVENTION
POLICIES

18. Data Classifications
Environment

19. DATA LOSS PREVENTION
POLICIES
Environment
• Data loss prevention policies (DLP) enforce rules for which connectors can be use together
• DLPs defined by Administrators
• Policies can be applied to all Environments or specific Environments
• Connectors are classified as: Business Data, Non-Business or Blocked
• Classified Connectors can only used together with connectors in the same group.
• Blocked connectors cant be used at all
• Granular DLP Policies for Non-O365 Connectors
• Multiple DLPs can apply to one Environment.

20. Monitor Maker Behaviour
• Who are your App Maker?
• Which Connectors are Used?
• Identify Business Critical Applications
• Identify orphaned Apps & Flows
• Monitor Low Code Adoption
• Track the monetary benefit of the
Projects
• Ensure Documentation of Projects

21. WHAT IS IN, WHAT IS NOT?
• Data Loss Prevention Policies
• Environments
• Permissions
• Tenant Isolation
• Solutions (for ALM)
• Compliance Processes
• Project Documentation
• Business Value of Projects
• Provisioning requests
• Monitoring
• Guidance / Training
Available out of the Box Not Available out of the Box

22. LOW-CODE STRATEGIES
CENTRAL
DEVELOPMENT
CITIZEN
DEVELOPMENT
Compliance
Documentation
Support
Community
Financial opt.
Documentation
Support
DevOps

23. PROJECT BASED APPROACH
A Project consists of various Project Items
• Apps
• Flows
• Dashboards
• Logic Apps
• Others
Documentation consists of
• Concept
• Business Impact
• Technical Description

24. COMPLIANCE & APPROVALS

25. RUNPIPE POLICIES & APPROVALS
1. Establish Risk Alerts
1. Identify Risks such as broken Apps
and Flows (deprecated connectors)
2. Identify orphaned Apps and Flows
2. Implement Approval Workflows
1. Access to new or existing
Environments
2. Allocation of Premium Licenses
3. GDPR & IT Security Approval

26. AGENDA
P o w e r P l a t f o r m G o v e r n a n c e
01. Intro
02. Why Low Code
03. Governance
04. Enablement
05. Discussion

27. MAKER JOURNEY
Awareness
Ideation
Education
Project
Approval
Development
Testing
Production
Support

28. AWARENESS (KION)

29. Workshop Bundle
Power Up!
IDEATION & EDUCATION (KION)

30. SUPPORT
1. Maker helps Maker
2. Ask me Anything Sessions
3. Ticketing

31. ENABLE YOUR CITIZEN
DEVELOPER
1. Build your Community
2. Identify Heroes
3. Promote Citizen Development
4. Provide Live and On Demand Training
Material
5. Use a Wiki to gather company specific
knowledge

32. AGENDA
P o w e r P l a t f o r m G o v e r n a n c e
01. Intro
02. Why Low Code
03. Governance
04. Enablement
05. Discussion

33. GET IN TOUCH
Constantin.seidel@runpipe.com
+49 171 5513017
Darmstadt, Germany
@GetRunpipe