All my posts about Microsoft Azure

Generating an Azure Storage Account SAS token using Azure Logic and Function apps
Don’t you just love it when you open your laptop first thing on a Monday morning, a fresh cup of coffee at the ready and you think to yourself … This should be a straight-forward five-minute job to start the week with … and it turns out to be anything but? That is exactly what happened to me this week, I won’t go into too much detail, but I was working on an Azure Logic App that had to interact with an external service and pass it a a fully signed SAS URL for an Azure Storage Account so that it could send some quite large files there. You would assume that the Azure Blob connector↗ would be able to do this, and you would be correct as there is a “Create SAS URI by path (V2)” action: ...