{"id":763,"date":"2018-01-04T01:00:36","date_gmt":"2018-01-04T09:00:36","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/powerapps-administrator-app\/"},"modified":"2018-01-04T01:00:36","modified_gmt":"2018-01-04T09:00:36","slug":"powerapps-administrator-app","status":"publish","type":"power-apps","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-apps\/powerapps-administrator-app\/","title":{"rendered":"PowerApps Administrator App"},"content":{"rendered":"

PowerApps Administrator App<\/h2>\n

In August 2018, we announced new Power Platform admin and maker connectors for PowerApps and Flow.\u00a0 These connectors provide access to the resources in the admin or maker scope.<\/p>\n

This allows you to more easily gain both insight, and control over your Power Platform estate. Using these connectors makes it possible to build a solution that matches your exact enterprise governance, administration and maintenance requirements.<\/p>\n

Recently, I built a PowerApp using these connectors that demonstrates how to manage environments, apps and app compliance. The aim of this app is to address a few common requirements that I ran into whilst working with various customers:<\/p>\n

    \n
  1. (Governance) Easily identify apps where the app maker has not digitally signed a company PowerApps policy, and to be able to send a reminder to the app maker & their line manager.<\/li>\n
  2. (Maintenance) Easily identify apps that have not been published within the past 60 days.<\/li>\n
  3. (Administration) Identify apps by form factor.<\/li>\n<\/ol>\n

    The App<\/h3>\n

    Lets take a look at the administrator app.<\/p>\n

    \"Screenshot<\/p>\n

    The screenshot above shows the app landing page. The pane on the left had side lists the environments in my tenant. When I click\/ select an environment the page updates by returning a list of all apps within the environment and some basic information about the environment itself.<\/p>\n

    App details & administrative features<\/h3>\n

    Each app in the environment is represented by an app tile.\u00a0 The tile contains information about the app, such as the title, app maker, governance compliance and form factor.\u00a0 Clicking on an app tile updates the user interface to provide more detailed information about the app:<\/p>\n

    \"Screenshot<\/p>\n

    The screenshot above shows the app details.\u00a0 There is detailed information about the app and an area for administrative features (lower right). Each administrative feature or policy compliance has an indicator, quickly drawing your attention to any actions for this app.\u00a0 The screenshot shows a red indicator showing that the app was last published 72 days ago.\u00a0 This has been flagged as outside the enterprise policy, hence is highlighted with a red icon.<\/p>\n

    Next to each administrative feature is an action, in the example we can resolve the publishing issue by clicking the ‘Publish App’ button.\u00a0 This will re-publish the app.<\/p>\n

    Governance policy signing<\/h3>\n

    The app indicates if the app author has agreed to a governance and usage policy. How does this work?<\/p>\n

    To achieve this, I utilized a number of O365 applications:<\/p>\n