This presentation was used at SPS London 2019. Daniel Laskewitz and myself went into how admins can be in control with the PowerPlatform without frustrating the citizen developer (to much).

2. Our Sponsors

3. Citizen
development
Admin & compliance

4. Daniel Laskewitz (citizen dev)
Business productivity consultant
Sogeti Netherlands
Microsoft MVP Business Solutions
International speaker
Blog: https://www.o365dude.com/
Twitter: @Laskewitz
Mail: Daniel.Laskewitz@sogeti.com

5. Albert Hoitingh (admin)
Solution Architect
Motion10
Microsoft MVP Enterprise Mobility
Microsoft Certified Security Administrator Associate
International speaker
Blog: https://Alberthoitingh.com
Twitter: @Alberthoitingh
Mail: Albert.Hoitingh@Motion10.com

6. Today’s agenda
Three real-life scenario’s
• From the citizen dev.’s perspective
• From the admin’s perspective
• The theory behind the scenario
Additional information

7. Scenario one – He creates a (relatively)
simple Flow…
Let’s go…

8. Environments in Flow
Data region & security
• System administrator (aka. Environment Admin)
• Users
• P2 license required for multiple environments
• Watch out with Default
Data loss prevention (DLP)
• Works “on save” – for now
• Suspends Flow until restriction is lifted
• Can be worked-around (connect using different accounts)
• Call Microsoft!

9. DLP roadmap
But also: real-time DLP!
https://docs.microsoft.com/en-us/business-applications-release-
notes/April19/microsoft-flow/data-loss-prevention-enhancements

10. Scenario two – He’s still on it…
Let’s go…

11. Admin-connectors
• Specific management connectors
• Powerplatform, Security Graph, Microsoft Cloud App
Security
• Used for reporting and actions
• During the demo we used a Flic to trigger the Flow

12. PowerPlatform connector
Used for: Automating administrative tasks on the PowerPlatform
Possible triggers:
Possible actions:
• Create an environment
• Create a DLP rule
• Delete an environment

13. Flow admin connector
Used for: Managing Flows using Flow 
Possible triggers: Any (for example a button)
Possible actions:
• List Flows
• Stop a Flow (as shown)
• Create a Flow
Similar connector: PowerApps for Admins

14. Microsoft Graph Security connector
Used for: Using signals from the Microsoft Graph Security.
Possible triggers: Any alert available in the graph
Possible actions:
• Get alerts
• Update alerts
• Get subscriptions

15. Microsoft Cloud App Security
Works both ways:
• Create a Flow based on an alert in MCAS
Or
• Trigger a Flow from an MCAS policy
For example:

16. Scenario three – Will he never stop?
Let’s go…

17. Bug or working as designed?
• Going around the tenant has been a “work-around”
• For quite some time now….
• Only option at this moment: “Call Microsoft”

18. What if I need more options?
• Powerplatform admin-center
• Office 365 audit-log and alerts
• PowerShell
• Multifactor authentication

19. PowerPlatform admincenter
Now in preview
Custom (3rd party) also available

20. Office 365
• Auditlog
• Requires the correct permissions
• Info retained for 90 (E3) or 365 (E5) days
• Custom admin-dashboard

21. https://powerapps.microsoft.com/en-
us/blog/powerapps-enterprise-deployment-
whitepaper/
References

22. References
Environments: http://tinyurl.com/y8mu2zzv
Connectors: http://tinyurl.com/y75x4y4c
PowerShell: http://tinyurl.com/yafhxh6w
Connector Browser App: http://tinyurl.com/y75x4y4c
Custom admin dashboard: http://tinyurl.com/y66bwe75
Sample Flow for reports: http://tinyurl.com/y4yno8vm
Auditlog: http://tinyurl.com/yaxt87te
GDPR: http://tinyurl.com/y3sa6cwm

23. Thank you so much!
Albert
Blog: https://Alberthoitingh.com
Twitter: @Alberthoitingh
Daniel
Blog: https://www.o365dude.com/
Twitter: @Laskewitz

24. Back-up - licenses
Set-MsolCompanySettings -AllowAdHocSubscriptions $false

25. Back-up - licenses