Power Apps UG Governance Getting Started Why Power

Power. Apps UG Governance & Getting Started

Why Power. Apps 2019 – 2 billion new phones fueling Demand for apps in the Enterprise Currently In Businesses Not enough skilled mobile developers IT agility and app sharing Business data proliferation

Why Power. Apps Governance CITIZEN DEVELOPERS PRO DEVELOPERS No / Low Code Approach More Code Approach Quickly create apps or prototypes Create larger more complex apps Use built in connections Use more advanced connections within Azure or JSON Work with IT to publish simple to mid level business processes Work in multiple environments using ALM techniques

What is Power. Apps Governance • IT Awareness of Apps and Flow • The setting of a Framework for minimum standards • Defining who can create apps • Understanding who can publish apps – anyone or IT • Who will support App development – training, standards for apps and support documentation • Management of o 365 connectors

IT Awareness • Use the Admin Flow options for alerts on new app / flow creation in your tenant https: //australia. flow. microsoft. com/en-us/connectors/shared_powerappsforadmins/powerappsfor-admins/ • Use the Admin Centres for Power. Apps and Flow – Read the White Paper! • Understand DLP rules for o 365 Connectors • Learning Resources - https: //powerapps. microsoft. com/sv-se/blog/microsoft-powerapps-learning -resources/ • Take a free course - https: //www. edx. org/course/developing-business-applications-withmicrosoft-powerapps-cds-and-flow

Minimum Standards • Branding Components / Consistent Layouts – Build App Templates / App Components • Support Teams / Sponsors / Internal Champions – must have XX hours available • Ensuring Naming Conventions gal. Customers, scrn. Customers, txt. Customers, lbl. Customers • Formula inline mark up //singleline or /* multiline */ • Documentation requirements for releasing an app to All Company • Where to go for help – Yammer?

Who will support • IT or Business Teams ? Intranet Team? • Know what works online / offline • Understand the difference in devices and tools on them – eg Edge and Camera controls or Windows Devices and Offline capability • Co-ownership of apps with IT / use custom Apps Admin Centre • Who will support App development – training, standards for apps and support documentation

Who Can Create, Use , Publish • Align with your defined App support model • IT, Anyone, Special Ninja Teams – read about Virgin Atlantic special ops team • Internal only users (for now) • Understand Printing Workarounds (for now) • Business Builds, IT Publish using Service Accounts – supported by an admin app • Share to All company – or AD sub sets • Management of o 365 connectors – o 365 Admins on Azure Connectors / Emails from the Flow Owner • Don’t do app work in Siloes!

Manage o 365 Connectors • Define what o 365 connectors are available to your App Makers to consume • Note the dependence of some features – eg – Share. Point based apps, may need to send alerts via Outlook or Mail – lock down, but be pragmatic. . • Understand the licensing implications

Summary • Sort your business stance on app usage • Allocate resources accordingly • App builders can now swim quite far before getting into deep water – be ready! • Keep up to date on changes • Understand what your business users need • Spend time learning app possibilities • Ask for help often!