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
Is your business still running on paper trails, sprawling Excel files, or ageing Access databases? There's a better way — and I can show you exactly what it looks like.
I'm the Technical Director of Vantage 365, a Microsoft solutions consultancy working with clients across the UK, the Netherlands, and worldwide.
For over 30 years I've been turning messy, manual business processes into clean, automated systems that save time, reduce errors, and give teams the visibility they need to make better decisions.
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