This post is all about how to block unmanaged customizations within production environments. I’m going to assume that you have followed the advice of creating a Development, Test, UAT and Production environment. And that each of these environments should be treated in a very different way.
Author: Pieter Veenstra
Business Applications Microsoft MVP working as the Head of Power Platform at Vantage 365. You can contact me using contact@sharepains.com
Recently I needed to deploy parts of a solution to a test environment. I also had to be able to rollback the solution. Solution Patches within the Power Platform can help with this. In this post I’m looking at how Solution patches work.
![[REDACTED] message when turning on a Power Automate flow](https://i0.wp.com/sharepains.com/wp-content/uploads/2026/04/image-8.png?resize=800%2C450&ssl=1 "image 8")
We all like useful error messages. How about the [REDACTED] Message when you turn on a flow? In this post you will find the steps to fix this issue.
How often do you want to find a flow, but you can’t remember which environment you created the flow in? It can be quite a
Recently I worked on a project using Microsoft Fabric where I needed to create a connection to an API that used Bearer tokens to access
Load More