This time round I’m going to delve into Power Automate Desktop (PAD). PAD is a service that allows you to perform activities on a local machine as part of a flow. It’s a service that used to require an extra subscription cost, but it’s now available to everyone included with whatever tier of Power Automate you currently have.
There are any number of reasons why you might want to start or stop your Azure App Service based on other factors. And while there are a number of ways to accomplish this, this time we’re going to cover how to do it in Power Automate with the press of a single button.
In a previous post, we learned how to trigger a Power Automate flow by calling an HTTP endpoint. The best part of this trigger is that it allows you to trigger your flow from anywhere on the internet, be it an application or right in your browser. The trouble is, there isn’t security for that endpoint ‘out of the box’. Anyone who knows the endpoint’s URI can call it. So how do you secure that endpoint so that only someone who is authorized to call the endpoint can get it to run?