Azure Functions is an awesome serverless offering from Microsoft. It lets you deploy a small piece of code as a “function” without having to worry about any underlying infrastructure. A function will then execute on a given event, which for example could be an event from an event service like Event Grid or Event Hubs, a message on a queue like Azure ServiceBus or Azure storage queues, a direct HTTP request like an API call or a webhook, or a timer.
Intro Have you ever wanted to query an API that uses access tokens from Azure Active Directory (AzureAD) from a PowerShell script?
There are a lot of solutions for this that uses an application in AzureAD and authenticates using its client-id and secret. If I have a web application or a non-interactive service this is the way to go. My friend and colleague Emanuel Palm wrote a great post on Microsoft Graph API with PowerShell for that scenario.
Intro I deployed an Azure function using ARM template and then tried to manually add an application setting in the portal.
Got the following error message:
Updating web app settings
The specified container size is not supported. Use one of these container sizes: 128, 192, 256, 320, 384, 448, 512, 576, 640, 704, 768, 832, 896, 960, 1024, 1088, 1152, 1216, 1280, 1344, 1408, 1472, 1536.
Searched on the internet, found this issue: https://github.
tl;dr I’ve migrated my blog from WordPress to a static web site hosted on Azure storage. It was way easier than I thought it would be and I don’t regret it for a second! Now I’m hosting this blog on an Azure storage account using static pages generated from MarkDown-files by Hugo. I still have a few things to figure out in regards to web-page optimization, SEO and CI/CD pipeline to make blogging as effortless as possible, but so far my only regret is that I didn’t go down this path sooner.