Advent of Code 2021 – Day 1, Puzzle 1
I’m participating in the Advent of Code 2021 (@adventofcode). Here’s my solution for Day 1, Puzzle 1 – Measuring depth increases
I’m participating in the Advent of Code 2021 (@adventofcode). Here’s my solution for Day 1, Puzzle 1 – Measuring depth increases
Once you’ve built up some content, one of the ways to keep your social media presence more active is to re-share your older blog posts. For long time followers, it can remind them of previous content. And it can help bring in new followers who didn’t see that content previously.
In part I of this post, I demonstrated how to create a custom connector. Now, we’ll follow up with a short post on how to use that custom connector in a flow.
For those with the higher tier licenses, along with being able to use the premium connectors, you also have the ability to create your own custom connectors that you can use to connect to just about any API on the web.
Another feature AI Builder in Power Automate offers is the ability to recognize objects in an image. This time we’re going to look at how to set up AI Builder to identify dice.
One of the more complex features of Power Automate is the ability to train it to pull data out of scanned images of invoices and automatically import the information.
I delivered two presentations at Community Summit NA 2021. As part of that, I provided a number of demos. Below you can find some of the flows I used in my presentation.
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?