– Why Manage environments and most importantly when to enable. – What is available now – Preview features – Starter kit and how it works with Managed environments And a demo of how it all works together.
As you read, a starter kit will be an integrated part of managing the platform and other tools such as PowerShell and BYODL.
Based on the content planned, is there anything else I should add?
With the release of the groups and rules (Preview), it is important to consider the developer environments as part of the strategy.
Below is the list of pros and cons(Limitations).
I also added a few things you need to take into consideration.
Pros
Every developer environment comes with a message that indicates the purpose of the environment.
When the user tries to share the apps, it shows the below message to the App owner.
Users can create up to 3 developer environments. If they start developing solutions, you don’t have to manage/provision for them every time.
Newly created developer environments can become managed environments. This is to support the environment routing. This feature is currently in preview.
With routing, you can apply preconfigured settings such as Sharing Limits, Solution Checker, Usage Insights, and Maker welcome message.
New makers don’t need to know which environment they need to work on.
Cons (Limitations)
You will have less control over the naming conventions of the environments.
Flow runs/month (750) and capacity limits up to 2 GB.
Environments created using the Power Apps Developer Plan that have been inactive for the last 90 days will be deleted after the environment owners are notified.
There are a few more things to consider
You must enable Tenant level settings (Developer environment assignments) to leverage the developer environments.
You do not need to make default as a managed environment to enable the routing.
All developer environments created through environment routing are managed environments, as are all environments in a group. These environments require premium licenses to run Microsoft Power Platform assets.
Please create the comms to communicate the consequences with users, which will help you manage it properly.
Developer environments add more values once the environment routing becomes GA.
In the last post, I shared 10 things to consider before installing the CoE starter kit.
If you do not consider those things, you will have a lot of issues managing the starter kit.
Also, people make common mistakes while maintaining the starter kit.
I have made some of these mistakes and seen others make similar mistakes.
Hopefully, after reading these, you can learn from our mistakes and not repeat them.
But you need to ask why they are happening.
Why are mistakes happening when upgrading the CoE starter kit?
The starter kit is not a simple tool to manage.
Here is why.
We are trying to automate the environment request process.
I was struggling to automate adding environments to DLP.
I am trying the Power Platform admin V2 connector action.
But my teammate said we have it already as part of the tool.
I was like what? How did I miss it?
Then we used the child flow to complete the automation.
You might have faced similar kinds of challenges.
To put this in context, how large was the starter kit?
At a high level, there are three main components
1) core components
2) Audit or Governance components
3) Nurture components
I am ignoring the other one for now (Innovation backlog). This component didn’t get much attention.
As of April 2024 release
Core components got
423 Total Objects
49 Tables
15 Power Apps
110 Cloud Flows
63 Pages
Audit components
42 components
1 Table
3 Power Apps
12 Cloud Flows
8 Pages
Nurture components
74 components
15 Tables
3 Power Apps
8 Cloud Flows
7 Pages
Note: I will try to update this metric once a quarter. Let me know if you read this article in the future and it hasn’t been updated for over three months.
Starter is a great tool that adds value to managed environments.
But it needs effort from the Power Platform team to manage it.
It is easy to make mistakes if you do not know what you are customizing.
If you do not know how to use the kit efficiently,
Now you know why. Let us get into the list of these mistakes.
The list below is not in any particular order.
Immediate CoE starter kit upgrade Post-Release
The starter kit team releases the updates once a month.
If you upgrade to a new release without waiting for initial bugs to be identified and fixed. It can cause issues if there are any critical problems present.
Give yourself a few days to a week to check that the kit updates are not significantly flawed.
Not doing Testing
Not testing newly released components in the development environment before production use can introduce unexpected issues.
This happens mainly because of the lack of a dedicated development environment.
You need to have a development environment to test the released updates.
If you use any email functionality, enable an admin account email and start testing with a few users. Make sure the emails are working as expected. You do not want to email everyone in the organization even by mistake.
Overlooking Starter Kit’s Full Functionality
Failing to invest time in understanding all solutions and components in the starter kit can lead to building custom solutions that are not required.
Make sure you give yourself time to understand all the components. If not, you will build something not required.
Not updating the starter kit frequently
You must update the CoE starter kit at least once every three months.
Otherwise, managing the starter kit may experience many unexpected issues.
It’s even better to upgrade the starter kit at least once every two months.
Document everything, and this makes it easier to do future upgrades.
Too many customizations and not having conversations with the Starter kit team
People customizing the starter kit functionality is common.
While customization, it’s always better to be in touch with a starter kit to understand the roadmap rather than building a custom component.
The component you are building might already be planned in a few months, and then you can always wait and focus on other areas.
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?