Set up governance components

Multiple governance components are provided in the Center of Excellence (CoE) Starter Kit; each will require some configuration to install. The installation instructions in this article have been segmented based on the set of components that should be grouped and installed together, and dependencies on other segments are outlined in each section.

Important

You cannot use the archival solution if you have secured the environment with security groups. Please see Security groups and approvals

Initialize flow approval tables in your environment

These flows in the solution use the built-in Approval actions of Power Automate and therefore require it having been installed on the environment.

  • Admin | Archive and Clean Up v2 (Start Approval for Apps)

  • Admin | Archive and Clean Up v2 (Start Approval for Flows)

  • Admin | Archive and Clean Up v2 (Check Approval)

  • Admin | Archive and Clean Up v2 (Clean Up and Delete)

    If you are installing the solution in a new environment, or one in which Approvals have not been used in the past, then the Approval tables must be initialized before you can install the solution. The easiest way to do this is to create a "dummy" approval flow.

  1. Go to flow.microsoft.com and select your CoE environment.

  2. Select + New > Instant (From Blank).

  3. Pick manually trigger a flow as the trigger, and enter Admin | Dummy Approval Flow as the name.

    Build an instant flow.

  4. Select + New Step to add an approval action to the flow, and then search for and select Create an approval.

  5. Select a dummy title, and enter your email address under Assigned To.

    Approval flow.

  6. In the upper-right corner, select Test, and then select I'll perform the trigger action.

  7. Select Save & Test

  8. Select Run Flow

    Note

    This flow can take up to ten minutes to run initially. After it runs, you can delete the flow because it won't be needed anymore.

  9. Select Solutions on the left side panel, and you should now see two new Flow Approvals solutions. Note that the presence of these solutions was the point of this step, and the way you know it succeeded.

    Flow Approval solutions.

Import the solution

The Core Components solution is required for the Governance Components solution, or any other component in the starter kit, to work.

  1. Follow the instructions detailed under Set up core components to import the solution either into your Production or your Dataverse for Teams environment.

  2. Import the CenterOfExcellenceAuditComponents_x_x_x_xx_managed.zip file.

  3. Select a connection for all connectors. Import the Center of Excellence - Governance components solution.

  4. Select Import without adding values to the Environment Variables, these will be updated later - see update environment variables

Update environment variables

This step should be completed after you import the solution. Environment variables are used to store application and flow configuration data. This means that you only have to set the value once per environment and it will be used in all necessary flows and apps in that environment..

All flows in this solution depend on all environment variables' being configured.

Tip

Learn how to update environment variables for Production and Dataverse for Teams environments: Update Environment Variables.

  1. Select See Environment Variables to set the values as described in the following table.

    Name Description
    Auto Delete On Archive Determines whether apps andd flows are deleted when they're approved for deletion in the following flow: Admin | App Archive and Clean Up - Check Approvals and Archive.
    Value must be Yes or No. A default value of Yes is provided.
    Exclude Default environment from Compliance Requests Determines if the default environment is excluded in the Compliance Details request flow.
    Value must be Yes or No. A default value of No is provided.
    ProductionEnvironment Determines if the environment is Production or Dev/Test. True (the default) will mean that the approvals are sent to app/flow owners. False will send those approvals to the admin email.
    Cleanup Old Objects App URL (Optional) Link to the Cleanup Old Objects canvas app included in this solution.
    If included, communication about old objects which are considered no longer useful will include the link to make cleanup easier
    Flow Approvals URL (Optional) Link to Power Automate's Approval page for your CoE Environment
    If included, communication about old objects which are considered no longer useful will include the link to make cleanup easier.
    To get the URL Browse to flows.microsoft.com for your CoE Environment > Action Items > Approvals.
    URL should end in approvals/received

Activate the flows

This Governance Components solution contains flows that you'll need to manually turn on as soon as you're ready to use them.

Update Run only users

There are three child flows which will need their Run only users properties updated.

  • HELPER - CanvasAppOperations Gov
  • HELPER - CloudFlowOperations Gov
  • HELPER - ObjectOperations Gov
  • Request Orphaned Objects Reassigned (Child)

For all three of these flows, go to the details page and click the Run only users edit button.

You will see all the connections in the child flow. For each one, change the value to Use this connection (userPrincipalName@company.com). If there is no connection for any of the connectors, go to Data > Connections, and create one for the connector.

Find setting for run only users. Configure run only users.

Update the variables and flows back in Core

  1. Get the URL for the Developer Compliance Center
    Browse to Details page of the Developer Compliance Center and grab the Web link Setup Compliance Components1.

  2. Browse to Default Solution, filter to Environment Variables, edit the Developer Compliance Center URL variable and add the URL from step 1 as a current value Setup Compliance Components2.

  3. Return to the Core Solution and turn on Admin | Compliance detail request v3 Setup Compliance Components3.

Share apps with makers

The Governance Components solution contains one app, which is used by makers to update the compliance details of their applications.

Developer Compliance Center

Your app, flow, and bot makers will use the Developer Compliance Center app to provide further information about the resources they're building. Get familiar with the audit process and share the app with your makers. Your makers must have a Power Apps Premium license to use this app.

In addition to sharing the app, you'll also need to share the data by providing data permissions to the user.

Share the app from a Production environment

  1. Go to make.powerapps.com and select the app.

  2. Select ... > Share.

  3. Select the Dataverse data permissions.

    Sharing Data 1.

  4. Select the Power Platform Maker Security Role.

    Sharing Data 2.

  5. Select Share.

Share the app from a Dataverse for Teams environment

You will share the app with your colleagues that don't belong to your CoE team.

More information: Sharing for broad distribution apps

  1. Open to the Power Apps app in Teams, select Build, and select the Team you have added the solution to.

  2. Select Installed apps.

  3. Assign table persmissions to share the data with your colleagues.

    1. Select See all for Center of Excellence - Core Components.
    2. Select Tables from the left pane.
    3. Select PowerApps App > Manage Permissions.
    4. Select Colleagues with access.
    5. Set the permission to Full Access. Sharing data with colleagues.
    6. Repeat these steps for the Environment, Flow, PVA, Desktop flow tables.
    7. Repeat these steps for the COE Settings table, but grant Reference permission only.
  4. Select Build and select Share with colleagues to share the app with your colleagues. You must be a Team Owner to see this option.

    Sharing with colleagues.

  5. Search for, and select the security group you want to share the apps and tables with. Select the Developer Compliance Center app.

    Search for a security group.

  6. Select Save.