The starter kit is crucial in understanding the Power Platform’s current state.
It answers some of the important questions about the platform and people.
- Who is developing solutions?
- Where they are developing solutions?
- How many solutions?
It also answers many other questions about your Power Platform’s current state.
Why checklist?
I have installed/upgraded starter kit over 60 to 70 times in the last few years for multiple tenants.
If you are wondering how come these many times I installed/upgraded?
Last year alone I installed/upgraded over 20 times in Development and Production environments.
I am also responsible for managing the starter kit in my current role.
The checklist helps me avoid mistakes whenever I install/upgrade the kit to a new tenant or maintain the current one.
The goal of this post is to avoid the mistakes you might make.
Below are some key elements to get the starter kit up and running.
Note: This is not a complete list, but having the checklist prevents me from making mistakes later.
1. Cloud export vs BYODL (Preview)
Cloud Export
If you are a small org, you should use Cloud Export.
If you are starting, this option should be used regardless of the number of people using the platform.
BYODL (Preview) – bring your own Data lake is still in preview
It was introduced to support extensive usage and speed up the inventory process. For whatever reason, it is still in preview.
In this guide, I will talk only about the Cloud Export option.
2. Environments
You need at least two environments to start the installation.
Make sure to configure the settings below in each environment.
This can be done from the Admin command center App.
Development environment
FullInventory = No
ProductionEnvironment = No
(This setting prevents people from receiving emails)
Production environment
FullInventory = Yes
ProductionEnvironment = Yes
Optional – You can also use the UAT environment, but it’s overkill.
3. DLP Policy
Create a dedicated DLP policy.
Given the number of connectors needed to get the starter kit up and running, it’s always recommended to have a dedicated policy for CoE.
Make sure you are allowing only starter kit Development and Production environments. Not any other environments.
4. Service account
To configure the starter kit use the service account option.
This is one of the mandatory requirements for the kit to be up and running.
It’s the backbone of platform governance and administration.
You should not use the individual user account, and if the person leaves the org, you will have to configure the kit again.
This should be mail-enabled so you can receive emails when flows get errors.
5. Licensing
The Cloud Export option needs a minimum of the below licenses.
Make sure you assign these to the service account.
- Office 365 E3 (minimum)
- Power Apps premium
- Power Automate premium
- Power BI Pro or per capacity.
6. Office 365 Groups
A makers group is necessary to add people building apps to this group.
Ensure you disable the setting that sends a welcome email when a person is added to the group. Otherwise, people get Spammed when they are added to the group.
You could potentially add the people to the Yammer group as well.
7. App registration
Create an App registration in the Azure portal with sufficient permissions to get the Audit Log info.
8. Documentation
Before you start the installation, start documenting everything.
While you are installing, take the screenshots (Before and After).
Make sure you capture all the steps while installing the kit.
If you get stuck, take a screenshot and capture the error logs.
Once you fix the issue, come back and update the doc with the root cause.
Repeat these every time you upgrade the kit.
This will save you hours and hours.
Also, maintain the details on what version you are installing, the status, and when you installed it.
This helps you track the components you are installing and upgrading.
9. Be Patient
Your tenant’s full inventory could take 24 to 48 hours, if not more. Relax and wait for the flows to complete the initial inventory.
10. Validate
Power Platform Admin view
Open the app and see if the data is getting populated for all the components.
Admin command center App
If you need help getting inventory.
Open this app and check for the Inventory Tab under cloud flows, see each flow’s status, and ensure everything is running without failure.
If there are any failures, fix them or raise a bug with the starter kit Github repository.
Key Notes
You do not have to install and configure all the components.
Start with core components.
And
Most importantly, do not enable all flows, especially the ones that will send emails.
HELPER – Send Email
Adding users to the group
Leverage wizard
You can install individual starter kit components using the Starter ki wizard app.
Again, do not enable all the flows( You could potentially SPAM all users in the company).
Final Thoughts
The CoE starter kit is the backbone of understanding why, what and where.
Also, the critical thing to know is that the Starter kit itself is not enough.
You’re mistaken if you think you have a starter kit and everything is done.
It is just a starter kit and you need more processes and systems to manage the platform.
You need to work with people to create those processes and systems.
CoE starter kit # CoE
Next up, we will talk about common mistakes made by admins while configuring the starter kit.
Is this checklist helpful or do you have a question?
Let me know in the comments below.
References
Github Repo to log issues and get new release updates
Complete guide from MS Learn to Install and configure starter kit
If you liked this post, consider signing up to get future posts.