CoE Starter Kit - Frequently asked questions

This article answers frequently asked questions (FAQs) and tips on setting up and using the Microsoft CoE Starter Kit.

Installing a solution in a production environment

1. Go to make.powerapps.com.

2. Go to your CoE environment. In this example image, we're importing to the environment named Contoso CoE.

   

3. On the left pane, select Solutions.

4. Select Import, and then select Browse.

5. Select the solution from the CoE Starter Kit download.

6. To activate your solution, establish connections. If you create a new connection, select Refresh. Your import progress remains intact.

7. Update environment variable values. These environment variables store application and flow configuration data specific to your organization or environment. By setting the value once per environment, it appears across all necessary flows and applications within that environment.

8. Select Import.

Set flow run-only users properties

1. Remove unmanaged layers for all flows.
2. Go to the Details page, and then select the Run only users edit button.
3. You see all the connections in the child flow. For each one except Microsoft Dataverse, change the value to Use this connection (userPrincipalName@company.com). For Microsoft Dataverse, leave the value blank.
4. If there's no connection for any of the connectors, go to Data > Connections, and create one for the connector.
5. Once you updated all run-only users, you can enable the child flow.

Find a users Security Roles in an Environment

To find the security roles of a user in an environment, you can use the product UX:

1. Go to Power Platform admin center environments.
2. Select your environment.
3. Go to Settings on your navigation bar.
4. From Users + Permissions, select Users.
5. Locate the user and select their name to view their properties. You see their security roles under the Roles section.

Import a Flow

Occasionally, we deploy a one-time flow to address specific issues. When these flows are made available, the first step is to import them.

Import your flows:

1. Go to make.powerautomate.com
2. Select your target environment. For this example, we choose our CoE Environment.
3. Select My flows > Import > Import Package (Legacy)
4. Select and upload your flow.
5. Create any needed connections and then select Import.
6. Select Open flow to view.
7. Return to the previous view to see package details.
8. Turn on your flow.

Setting up CoE for a subset of environments

You might want to monitor and govern only certain environments using the CoE Starter Kit. For example, if you set up the CoE Starter Kit for individual business units managing their own smaller Centers of Excellence, or if you wish to include your Dynamics 365 environments in the CoE Starter Kit processes.

You can selectively enable CoE Starter Kit processes for specific environments:

Important

A starter kit process isn't a security feature and doesn't implement data privacy or row-level security. The process is solely intended to facilitate the monitoring and management of environments for organizational units.

1. After you import the Core components and before you turn on flows, set the value of the is All Environments Inventory environment variable to No. For more information, see Update environment variables.
2. Continue with the inventory setup and turn on all inventory flows.
3. Wait for the first inventory run of Admin | Sync Template v3 to complete. All environments in the tenant are added as excluded from inventory.
4. Add the environments you want to monitor and manage to the inventory by selecting No for the Excuse From Inventory configuration.
5. Wait for the next inventory run to complete. The run automatically picks up and monitors inventory for the selected environments.

Running a full inventory

To reduce API calls, the inventory flows don't update all objects with every sync flow. The flows only update objects modified since the last inventory.

Note

Inventory flows don't check each object every day to see if its modified date is more recent than the date in inventory.

Inventory flow actions:

1. Gets all objects. For example, the flow calls Get Apps as Admin.
2. Filters the returned list of objects to get objects where the modified date is greater than seven days old (configurable via InventoryFilter_DaysToLookBack).
3. Checks each object in the filtered result to see if its current modified date is more recent than the inventory date.
4. Updates these objects with the more recent modified by date.

If your sync flows are turned off for longer than seven days, you can only get the inventory updates you missed by modifying the InventoryFilter_DaysToLookBack environment variable. For more information, see Update environment variables.

To fully update your entire inventory again, change the Full inventory environment variable:

1. Set the value of the Full inventory environment variable to Yes. For more information, see Update environment variables.
2. Run the Admin | Sync Template v4 (Driver) flow.
3. Wait until the flow finishes running.
4. Set the Full inventory environment variable to No.

Update inventory for a selected app or flow

Force inventory on Objects

To reduce API calls, the inventory flows don't update all objects with each synchronization run. Instead, the flows only update objects modified since the last inventory. However, if you want to force the inventory for an individual object, you can use the Inventory Me flag. All objects have this flag.

Here's an example of how to set this flag using Cloud Flow objects.

1. Go to Power Apps and select your CoE environment.
2. Open the Power Platform Admin View app.
3. Select Flows.
4. Select the flow for which you want to force inventory from the view.
5. Select Settings.
6. Change the Inventory Me flag to Yes.

Once this flag is set to Yes, the next inventory run updates the object, even if it isn't recently modified. The flag is then set back to No.

Force inventory on cloud flow action details

We gather details about the flow actions in a long running flow called Admin | Sync Template v3 (Flow Action Details).

To force inventory to run for your flow, you can use the Inventory My FlowActionDetails flag.

1. Go to Power Apps and select your CoE environment.
2. Open the Power Platform Admin View app.
3. Select Flows.
4. Select the flow for which you want to force flow action detail inventory from the view.
5. Select Settings.
6. Change the Inventory My FlowActionDetails flag to Yes.

Update environment variables

Limitations for environment variables

The following limitations apply when updating environment variables:

• You can't update the values for environment variables from within the imported solution.
• Always add or update the current value, not the default value, as the default value is overwritten when you install an upgrade.
• You can't update Azure Key Vault secret environment variables using the CoE Admin Command Center. Instead, update them via the Default Solution.

Update CoE Starter kit specific environment variables

To update environment variables used in the kit, you can use the CoE Admin Command Center:

1. Go to Power Apps and select your CoE environment.
2. Open the CoE Admin Command Center app.
3. Select the Environment Variables screen.
4. Select an environment variable to update, then select Edit from the navigation bar.

Ensure flows that use environment variables aren't cached

At times, Power Automate caches old values for environment variables. If you don't see the expected behavior after changing an environment variable, restart the impacted flows after setting the environment variable.

1. Go to Power Automate.
2. On the left pane, select Solutions.
3. Select the Default Solution, and change the filter to show Environment variables.
4. Select a variable that you want to update and select its overflow menu to choose Advanced > Show dependencies.
5. Look at the Used by tab and the Object type process.
6. Turn off all these flows and then turn them back on.

Environment variables outside the kit

If you aren't using the CoE Admin Command Center app, you can update environment variables outside the kit. You can update environment variables directly in the environment. Updating through the environment is the only way to update Azure Key Vault secret environment variables.

1. Go to Power Automate.
2. On the left pane, select Solutions.
3. Select the Default Solution, and change the filter to show Environment variables.
4. Select a variable that you want to update, and then configure its Current Value.
5. If you're updating an Azure Key Vault secret environment variable, enter the following information:
   • Azure Subscription ID: The Azure subscription ID associated with the key vault.
   • Resource Group Name: The Azure resource group where the key vault that contains the secret is located.
   • Azure Key Vault Name: The name of the key vault that contains the secret.
   • Secret Name: The name of the secret located in Azure Key Vault.

Tip

The subscription ID, resource group name, and key vault name can be found on the Azure portal Overview page of the key vault. The secret name can be found on the key vault page in the Azure portal by selecting Settings > Secrets.

Update connection references

1. Go to Power Automate.
2. On the left pane, select Solutions.
3. Select the Default Solution, and change the filter to show Connection References.
4. Select a connection reference.
5. Set the value by selecting an existing connection from the dropdown or by creating a new connection.
6. Select Save and confirm you want to save the changes.

Monitor and customize emails

All emails sent as part of the CoE Starter Kit are stored in the Customized Emails table. To customize the emails, you don't need to modify the flows or apps that send the emails. Instead, you can use the CoE Admin Command Center app.

1. Go to Power Apps, and then select your CoE environment.
2. Open the CoE Admin Command Center app.
3. Select Customized Emails.
4. Select the email you want to customize, and then select Edit.
5. By default, all emails are provided in English. You can add localized versions of the email by selecting Add language.

Share an app from a production environment

1. Go to Power Apps and select your CoE environment.

2. On the app that you want to share, select the overflow menu ... > Share.

3. Select the Dataverse security role. The CoE Starter Kit makes three security roles available:

   • Power Platform Admin SR for sharing an app with admins
   • Power Platform Maker SR for sharing an app with your makers
   • Power Platform User SR for sharing an app with users

4. Select Share.

Get a Power Apps URL from a production environment

1. Go to Power Apps and select your CoE environment.
2. Select Apps.
3. Select the app that has the URL you need.
4. Select the overflow menu ... > Details.
5. Select the Web link.

Handling backend throttling during inventory runs

Some users might encounter throttling by the product backends, such as updating records in Dataverse, during their inventory process, resulting in 429 errors. To address this issue, there's an environment variable that adds a delay at the beginning of each individual inventory action. This delay prevents actions from running concurrently. While this approach mitigates concurrency issues, it might prolong the inventory process.

To use this environment variable, change DelayObjectInventory to Yes.

For more information, see How to update environment variables.

Cross tenant connection identities

In the Power Platform Admin View app, you can see where we highlight cross tenant connection identities. How do we configure what is considered cross tenant?

How to configure what is a local connection identity

By default, only the host domain of the identity running the inventory flows are considered to be a local identity. To configure this identity, you can use the Host Domains environment variable.

Enter any hosts you wish to add to this environment variable as a comma-separated string.

For more information, see How to update environment variables.

How to update data to respect configured local tenants

Tip

Changing the Host Domains environment variable doesn't retroactively update old data in tables. Since this setting change is infrequent, we don't regularly compare it to avoid additional API hits. Therefore, you need to update this environment variable manually.

You can update manually with custom flows, the Excel add-in, or through plugins. The underlying logic remains consistent, allowing you to choose the method that best suits your needs.

For this example, we use the Excel Add-In, which is ideal due to its speed and minimal API impact.

1. Browse to the Connection Reference Identity table and Edit data in Excel.

2. Select Enable Editing

3. Select Accept and Continue, if prompted, then sign in as your CoE Admin identity.

4. Filter the accountName field by the domain you added to the Host Domains environment variable.

5. Set the NoneOrCrossTenantIdentity to No.

6. Remove the filters and publish.

How to activate Business Process Flows?

Occasionally, users encounter disabled Business Process Flows (BPFs) within the kit due to installation issues.

To use features relying on these BPFs, you can activate them manually:

1. Browse to the solution with the BPFs and select to view Processes.

2. Find BPFs that are turned off and select a name to open.

3. Select Activate to turn on the BPF.

Which license should I assign to the user that's running the CoE Starter Kit flows?

Before installing the CoE Starter Kit, the user must have a Power Automate Per User license, or the flows must be covered with a Per Flow license.

Often, a combination of these licenses is required to run the CoE Starter Kit successfully. The specific combination depends on factors such as the number of resources (apps, flows, environments) in your tenant, your number of makers, and how frequently new resources are created and modified.

Different Power Automate license types have different API limits and enforcements. If your license type isn't sufficient, the flow might be throttled or run for an extended period.

This guide helps you determine which license to select:

1. Understand the Power Automate request limits.
2. Start by assigning a Power Automate Per user license and turn on all required flows. Monitor the flows with CLEANUP, Sync Template (Flows), and Sync Template (Apps) in the name. The options might consume a high number of API requests. You can use action analytics to monitor the API requests of these flows.
3. If the flow runs too many actions, change the flow owner to a different account with a Power Automate Per User license. This load balances the API requests.
4. If the flow continues to execute too many actions, consider assigning a Per Flow plan to it. This action allocates capacity and API requests specifically for the flow.