Recently I was investigating removing a component in a production environment, that stubbornly remained. It had me thinking for longer than it should, but after first diving down a couple of rabbit holes, I realised what the issue was. The […]
The Power Platform provides immense flexibility in connecting apps and automating workflows with APIs. A common scenario is using a Canvas App to trigger a Power Automate flow, which in turn, uses the HTTP connector to interact with external APIs.
One of the powerful features available when creating a new Power Platform environment, is the ability to create custom environments tailored to specific business needs. An often overlooked but valuable customisation is assigning an environment custom URL. Why Assign an
Flow Ownership In my recent articles, Notes on Flow Ownership and Flow Execution Ownership I discussed in whose name the different types of flow are run. Instant flows run in the name of the user who triggers them as “Run-only”
Flow execution ownership is important because understanding in whose name a Power Automate flows runs is crucial for both functionality and security. In this post, we will dive into the concepts of “Run-only users” for instant flows and explore the
It can take a while for newly created or newly shared environments to show up for users. The Microsoft guidance says it may take up to 10 minutes for them to become available in the Power Platform developer studios and
Sharing model-driven apps is slightly different to sharing canvas apps. In this post I’m going to briefly cover what you need to be aware of, together with some supplementary info that will help make the process clearer. How is Sharing
Nested JSON This is how to extract data into an array from a JSON that contains nested components. This is typically something you may need to do when formatting the response received from an API call. JSON is a data
App Sharing Under certain circumstances, it may be useful to allow App Makers to create Power Apps, but restrict them from sharing the app they create with others. The security role that Makers are given to create Power Apps is
Flow Ownership When you create a flow, you are the primary owner of the flow. The primary owner can be changed, but only if the flow is inside a solution. Co-owners can be added to the flow, and co-owners have
This is a follow-on from from my previous post Power Platform Environments Demystified and If not already done so, I recommend reading that article before this one. In this post, I’ll cover the different ways an app can be shared with users.
Power Platform Environments In this post, I’m discussing how to create Power Platform environments, and in particular, how to provide user access to environments, which can be a little confusing when doing it for the first time. I’ve added some
