Edit

Share via

Set up Developer Compliance components

  • Article

This article helps you to set up the Developer Compliance Center components of the Core and Governance solutions of the CoE Starter Kit.

You can detect frequently used apps and chatbots in your tenant and request that their makers provide more information about them, such as a business justification, data classification, and support plan. The goal is for admins to have better visibility into the solutions built by their makers and support them in making decisions. For example, admins might decide to move highly used applications to a dedicated environment.

Prerequisites

  1. Install the governance components solution.
  2. Set up your environment.
  3. Sign in with the correct identity.

Watch a walk-through of how the compliance process works.

Set up the Developer Compliance components using the Setup Wizard

  1. Open the Center of Excellence - Core Components solution.
  2. Open the CoE Setup and Upgrade Wizard app.
  3. Open the More features page and select Compliance process.

This app guides you through the configuration steps. Screenshot that shows the CoE Starter Kit Setup Wizard compliance process.

Note

The Setup Wizard is currently in preview. If you experience issues with the Setup Wizard, raise them on GitHub and set up the Inventory components manually.

Set up the Developer Compliance request components manually

Configure mandatory environment variables

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

Tip

Learn how to update environment variables: Update Environment Variables.

The Developer Compliance Center URL should be set to the URL for the Developer Compliance Center app.

For more information, see Get App URL – Production Environment.

Exempt environments from the compliance process

You can exempt environments from the compliance process, for example well-managed and dedicated environments or the environment with the CoE Starter Kit. For more information, see Establishing an environment strategy.

You can exempt environments from the compliance process using the Power Platform Admin View app:

  1. Go to make.powerapps.com.

  2. Go to your CoE environment.

  3. Open the Power Platform Admin View app.

  4. Select Environments, then choose the environment you want to exempt.

  5. Set the Excuse From Compliance Flow field to Yes.

  6. Select Save.

    Screenshot that shows where the Excuse From Compliance Flow setting is located.

Turn on flows

Turn on these flows that are installed as part of the Core components solution:

  • Admin: Compliance request complete apps v3
  • Admin: Compliance request complete bots v3
  • Admin: Compliance request complete custom connector v3
  • Admin: Compliance request complete flows v3
  • Admin: Compliance Teams Environment BPF kickoff v3
  • Admin: Compliance Details Request eMail (Apps)
  • Admin: Compliance Details Request eMail (Chatbots)
  • Admin: Compliance Details Request eMail (Custom Connectors)
  • Admin: Compliance Details Request eMail (Desktop Flows)
  • Admin: Compliance Details Request eMail (Flows)
  • Admin: Compliance detail request v3(governance-components.md#admin:-compliance-detail-request-v3)

Share apps with makers

The Governance Components solution contains the Developer Compliance Center app, which is used by makers to update the compliance details of their applications. Share these apps with your Power Platform makers and assign them the Power Platform Maker SR security role.

For more information, see Share an app in Power Apps.

Your app, flow, and bot makers use the Developer Compliance Center app to get more information about the resources they're building. You can get familiar with the audit process and share the app with your makers.

Tip

Consider adding the Developer Compliance Center app to the CoE Maker Command Center for makers to easily find and access.

All environment variables

Here's the full list of environment variables used as part of the compliance process, including environment variables with default values. You might have to update environment variables after import.

Important

You don't have to change the environment variable values during setup. You can change the value you configured during import or when you want to change a default value. Restart all flows after you change environment variables to make sure the latest value is in effect.

Environment variables are used to store application and flow configuration data with data specific to your organization or environment.

Name Description Default Value
Developer Compliance Center URL Set this environment variable to the URL for the Developer Compliance Center app. For more information, see Get App URL – Production Environment n/a
Compliance – Apps – Number Days Since Published If an app is broadly shared and last published this many days ago or older, makers should republish the app to stay compliant. 60
Compliance – Apps – Number Groups Shared If the app is shared with this many or more groups, makers are asked for a business justification. 1
Compliance – Apps – Number Launches Last 30 Days If the app launched at least this many times in the last 30 days, makers are asked for a business justification. 30
Compliance – Apps - Number Users Shared If the app is shared with this many or more users, makers are asked for a business justification. 20
Compliance – Chatbots – Number Launches If the chatbot is launched this many or more times, makers are asked for a business justification. 50

I found a bug with the CoE Starter Kit. Where should I go?

To file a bug against the solution, go to aka.ms/coe-starter-kit-issues.