Before setting up the CoE Starter Kit

Članak
05/05/2022
8 min. za čitanje

The Center of Excellence (CoE) Starter Kit is a collection of components and tools that are designed to help you get started with developing a strategy for adopting and supporting Microsoft Power Platform, with a focus on Power Apps and Power Automate. More information about individual components: CoE Starter Kit explained

This article will prepare you to install the CoE Starter Kit and provides guidance on:

The identity with which to install and run the solutions.
The environment type to use for your solutions.
All pre-requisites needed to use the CoE Starter Kit.

It will also help you understand how to extend the CoE Starter Kit, how to apply upgrades, and where to post issues.

What identity should I install the CoE Starter Kit with?

The CoE Starter Kit requires access to your tenant's Power Platform environments. Therefore, the identity you set up for the CoE Starter Kit needs the following:

Microsoft Power Platform service admin, global tenant admin, or Dynamics 365 service admin.
Power Apps Per User license (non-trial) and Microsoft 365 license.
Power Automate Per User or Per Flow license (non-trial).
The identity must be email-enabled.
If you'd like to collect telemetry information, such as app launches and unique users per app, the identity must have access to the Microsoft 365 audit log.

These roles and licenses must be available to this user continuously; if admin access is granted only temporarily via Privileged Identity Management (PIM), this won't be sufficient to run the CoE Starter Kit.

Additionally, if you'd like to share the Power BI report that's part of the CoE Starter Kit, this identity needs to have the Power BI Pro license.

How will you communicate with your admins, makers, and users?

You should consider how you'll communicate with different groups of people before you start the setup.

In particular, consider the following:

Admin persona
- Power Platform admins to communicate with each other.
- Power Platform admins to be contacted by your Power Platform makers.
Maker persona
- Power Platform makers to be contacted by Power Platform admins.
- Power Platform makers to communicate with each other.
User persona
- Power Platform users to be contacted by Power Platform admins.

We recommend using three Microsoft 365 groups for this, one for each persona. This group type is an email-enabled security group and can be associated with a Microsoft team for collaboration between the people in the group.

Prepare your environment

Decide what environment type to use (production or Dataverse for Teams)

The CoE Starter Kit can be used in both production environments and Dataverse for Teams environments. Where you install it will depend on your organizational setup, your adoption of Microsoft Power Platform so far, and what you want to achieve with the CoE Starter Kit. Before you decide, compare Dataverse vs. Dataverse for Teams and review the impact on CoE Starter Kit features based on where you install it.

Important

The governance and nurture solutions of the CoE Starter Kit have a dependency on the core solution and need to be installed in the same environment.

Feature	Dataverse for Teams environment	Production environment
Syncing inventory to Dataverse tables	Yes, will require a Power Automate Per User/Per Flow license due to action request limits and pagination settings	Yes, will require a Power Automate Per User/Per Flow license due to action request limits and pagination settings
Data capacity	2 GB	Unlimited through capacity purchases
Collecting telemetry information from the audit log	No	Yes
Power Platform admin view to view and filter resources	Canvas app	Model-driven app
Power BI Dashboard	Yes	Yes
Canvas apps part of core components (DLP Editor, Set App Permissions and Set Flow Permissions apps)	Yes	Yes
Apps and flows part of governance components	Yes	Yes
Apps and flows part of nurture components	Yes	Yes
Sharing the Developer Compliance Center with makers	Share with colleagues who have a Microsoft 365 license in Teams	Sharing requires users to have a Power Apps Per User or Per App license or for the environment to be covered with pay-as-you-go.
Sharing the App Catalog app	Share with colleagues who have a Microsoft 365 license in Teams	Sharing requires users to have a Power Apps Per User or Per App license or for the environment to be covered with pay-as-you-go.
Sharing the Training in a day app	Share with colleagues who have a Microsoft 365 license in Teams	Sharing requires users to have a Power Apps Per User or Per App license or for the environment to be covered with pay-as-you-go.
Sharing the Admin - Command Center app	Sharing requires users to have a Power Apps Per User or Per App license	Sharing requires users to have a Power Apps Per User or Per App license or for the environment to be covered with pay-as-you-go.
Power BI Dashboard	Yes	Yes, using the Dataverse connector only
Data Permissions	Team members have full access, and pre-built table permissions can be applied to colleagues with access	Granular permissions through Dataverse security roles that can be tailored to your requirements
Sharing apps	Share with colleagues who have a Microsoft 365 license in Teams	Sharing requires users to have a Power Apps Per User or Per App license or for the environment to be covered with pay-as-you-go.
Accessing apps	Apps can only be accessed within Microsoft Teams	Apps can be viewed in the browser or mobile app
Application Lifecycle Management	No	Yes

Create your environment

If you decide to use a production environment:

Create an environment with a database.
Don't add sample apps and datasets.
Don't restrict environment access with a security group, because some parts of the CoE Starter Kit use approval actions and require makers to be able to interact with the environment.

If you decide to use a Dataverse for Teams environment:

Decide which team to add the CoE Starter Kit solution to, or create a new team.
Install the Power Apps personal app in Microsoft Teams.
Create your first app. At least one app is required in the environment to enable the solution import experience.

Validate data loss prevention (DLP) policies

The DLP policy applied to your CoE Starter Kit environment needs to allow the following connectors to be used together in the business group:

Note

The CoE Starter Kit collects information about who owns a resource, such as an app or a flow. If the resource is owned by an interactive user, the Office 365 Users connector is used to get those details. If the resource is owned by a service principal (application user), the HTTP with Azure AD connector is used to make a call to Microsoft Graph to get the name of the application user to correctly mark ownership of resources and avoid resources being marked as orphaned (without an owner).

The HTTP and HTTP with Azure AD connectors connect to https://graph.microsoft.com. You can set up DLP endpoint filtering for these connectors to only allow the https://graph.microsoft.com endpoint. If your tenant is in GCC, GCC High or DoD, check your service root endpoint for Microsoft Graph.
If you're using the audit log solution, the custom connector used to connect to the Microsoft 365 audit log also must be allowed in your business group. Configure the https://manage.office.com/ endpoint in the business group of your tenant-level policy. Learn more: Configure custom connector endpoints in tenant-level policies.
Check that no other DLP policies apply to this environment. Learn more: Combined effect of multiple DLP policies
If you're using the ALM Accelerator for Power Platform components, the environment must have a DLP policy that allows Dataverse (legacy), Power Apps for Makers, HTTP with Azure AD, and the ALM Accelerator Custom DevOps connector to be used together. Those connectors must be in the business data–only bucket of the DLP policy for this environment.

Download the solution

Download the CoE Starter Kit solution and Power BI dashboard files to your device. The entire content package can be downloaded directly at aka.ms/CoEStarterKitDownload.

The content package contains various files that support different features of the CoE Starter Kit. The setup instructions will walk you through when to use each file, and below table will give you an overview of the purpose of each file:

File Name	Description
ALMAcceleratorForMakers_x.x.yyyymmdd.x_managed.zip	ALM Accelerator for Makers solution file. Required during setup of the ALM Accelerator for Makers components.
CenterofExcellenceALMAccelerator_x.x.yyyymmdd.x_managed.zip	ALM Accelerator for Power Platform solution file. Required during setup of the ALM Accelerator for Power Platform components.
CenterofExcellenceAuditComponents_x.xx_managed.zip	Governance components solution file. Required during setup of the Governance components. Has a dependency on Core components being installed first.
CenterofExcellenceAuditLogs_x.xx_managed.zip	Audit Log components solution file. Required during setup of the Audit Log components. Has a dependency on Core components being installed first.
CenterofExcellenceCoreComponents_x.xx_managed.zip	Core components solution file. Required during setup of the Core components in a Production environment.
CenterofExcellenceCoreComponentsTeams_x.xx_managed.zip	Core components solution file. Required during setup of the Core components in a Dataverse for Teams environment.
CenterofExcellenceInnovationBacklog_x.xx_managed.zip	Innovation Backlog components solution file. Required during setup of the Innovation Backlog components.
CenterofExcellenceNurtureComponents_x.xx_managed.zip	Nurture components solution file. Required during setup of the Nurture components. Has a dependency on Core components being installed first.
MakerAssessmentStarterData.xlsx	Provides a set of starter questions and answers for the Maker assessment app. Required during configuration of the Maker Assessment app.
Production_CoEDashboard_MMM2022.pbit	CoE Dashboard Power BI template file used when the CoE solutions are installed in a Production environment. Required during configuration of the Power BI dashboard
Pulse_CoEDashboard.pbit	Pulse survey Power BI template file. Required during configuration of Pulse survey components.
Teams_CoEDashboard_MMM2022.pbit	CoE Dashboard Power BI template file used when the CoE solutions are installed in a Dataverse for Teams environment. Required during configuration of the Power BI dashboard
Theming_x.xx_managed.zip	Theming components solution file. Required during setup of the Theming components.
ToolIcons.zip	Provides a set of starter icons for the Innovation Backlog. Required during configuration of the Innovation Backlog

Next step: Set up inventory components