Looking for a way to stream and analyse IoT data with Azure? Look no further, you’re in the correct place. In this blog post, I’ll demonstrate how to stream and analyse IoT data with Azure for ten euros or so per month.

We all know how rapidly all public cloud providers like to introduce new features and services. At the same time some of the old stuff needs to go. It’s sometimes hard to keep up and follow all the communication channels to ensure you’re not running any services or features that are about to get the boot.

I assume we all acknowledge the importance of following your cloud spend. And although Azure Portal’s Cost Management and Billing is a great tool for monitoring, allocating and optimizing Azure costs, sometimes there are needs to export the underlying data to be used in another external tool.

Sometimes I need access to a proxy server, and in most cases the proxy should be located in a certain country or region. This is where all public cloud providers come in handy.

Remember one of my older blog post where I built a site-to-site vpn between Azure and my home office using Raspberry Pi? If you’ve been following me in social media, you would already know what happened a day later.

Remember my previous blog post where I was spinning up Azure Data Explorer Kusto emulator in WSL? During the test I had problems ingesting data from https sources. Let’s see if we can fix that.

The Kusto emulator was released back in September 2022. Encapsulating the Kusto Query Engine and making it available on local compute in a Docker Container. Until June 2023 the emulator was only available as a Windows Container.

There are times when I need to use or test something in Azure using a private and secure connection from my home office. This is where VPN connections come into the picture.

I know this blog post is long overdue. No excuses. Been to busy lazy. Thanks for being here, let’s start with 101 on AKS defaults, nodes, pods and stuff.

I’m going to write some blog posts about my Kubernetes adventures, and the first thing I wanted to do, was to set up some scripts to build up a simple Kubernetes environment to play with.

In this blog post I will show you how to configure custom 404 error page, for a Hugo site hosted in Azure Static Web Apps. (In case you don’t know what 404 (Not Found) error is, it’s an HTTP status code which means that the page you were trying to reach on a website couldn’t be found on the server, altough the server itself is reachable.

TL;DR. Azure Static Web Apps Preview offers staging (pre-production) environments for applications. What is a staging environment and why should I care? Staging environment is a fully-functional staged version of your application.

Actually I think that the title should include one more word, finally. Anyways, the site is live and kicking! And in this post I’ll briefly explain how we got here.