In this blog series I am going to discuss my experiences with MicroK8S, installing it on Windows Subsystem for Linux, and how to connect the cluster to Azure using Azure Arc-Enabled Kubernetes.

The blog will be broken up into the following three sections:

1. Installing MicroK8s on Windows Subsystem for Linux (WSL)
2. Azure Arc-enabled servers: Installing Azure Connected Machine Agent
3. Azure Arc-enabled Kubernetes: Connecting my MicroK8S cluster to Azure

Installing MicroK8s on WSL

In this blog I will discuss my experience with installing Microk8s on Windows Subsystem for Linux (WSL). I will add a short section on how to get WSL 2 installed on Windows 10 which should also work for Windows 11. Then I will go into how to install MicroK8s on WSL. So let the demo begin?

I recently started a new job with a company that isn’t a 100% Microsoft shop. It has been many years since I have worked in a environment that everyone wasn’t drinking the Microsoft Kool-Aid. Not a bad thing if you do, I did and I loved that flavor. However, new job means new challenges and new way of doing things.

In this blog series I am going to discuss my experiences with MicroK8S. Since that is a solution that seems to be one of the favorites in a lot of meetings I am in. So,sit right back and hear my tail, a tail of a fateful experience, that started from my lack of experience, aboard this MicroK8s ship! The blogger a bearded and burly man, a learning, eager and pure. Many people will try to read this blog, for a 3 hour technical deep dive for sure. (Thanks Gilligan! I am guessing just my older readers will understand this one?)

At MMS this year one of the sessions, in fact the very last session I attended was about Home Automation using Home Assistant. I have been itching to get started playing with Home Assistant but just haven’t had the time. However, I have a need now to do some home automation and now it has become important.

My Use case

I have a T9 Honeywell Thermostat at home that is connected to the Resideo app to control my A/C. I also have kids and a wife that can’t seem to shut the front door. So I need a way to shut off the A/C if someone leaves the door open for more than 1 minute or so. I also have some “Smart” fans in every room of my house. I put Smart in quotes because the app that manages them isn’t the best but I did read that there are ways that Home Assistant can control these fans as well. So my goal here, is to get window and door sensors that I can use to tell when a window or door is open, and if it is open for more than a minute, turn off the A/C. I don’t want to cool off the Texas heat this summer.

There are times even your customers can teach you something. Recently while onboarding Microsoft Sentinel for a customer I ran into one of those times. I had been asked by the customer to integrate Microsoft Sentinel with Freshservice. Fresh service is one of many cloud based ITSM that I have run along my fun career. I personally don’t know much about Freshservice out side of the fact that my customer used it and had a use case where they wanted Sentinel to open a ticket in their system. Just like with all or most of my blogs, I write these in hopes that others can find a solution they are looking for but also, as I get older I forget a lot more than I remember. This way I can search Bing once again in 6 months or a year and find my blog I wrote on this subject.

So recently I have been dragged kicking and screaming into the security world. Well, not really dragged, if you know me I am a large guy and it would be more like fork lifting me kicking and screaming? Anyway, I actually love working with security products like Microsoft Sentinel, Defender for Cloud and the many other Defender for.. Products Microsoft offers, along with Identify solutions like Entra Permissions Management and more.

So, I am very interested in What cross-tenant synchronization is and what it could do for me and maybe for customers? Since I have a number of tenants I thought it would be good to at least try this preview feature and blog about my experience.

Also, this blog originally started out as a single blog but as I started to write it it grew and grew and grew. I wanted to refocus myself and break it up into smaller parts. The first part will focus on a single source to a single target topology. That is all explained below.

I guess this will be part II of another blog I wrote called What! My Azure Percept DK Devices Are Being Retired???. In that blog I mentioned how the Percept devices that were not cheap are now going into “retirement.” The only way to keep using them for other things is to install the last “Unsupported” firmware update before March 30th. This is my blog about how to install this update since you can no longer do OTA updates on existing devices at this time.

Since I failed terribly at getting my old Azure Sphere Development kit up and running as documented in previous blogs I decided to move on to my Vision AI DevKit. This has been a trusty workhorse for me in the past assisting with many demos. However, just like my other devices, I haven’t used this in a while, now I need to reset it and set it up again.

The process

The first thing I did was install the Android Debug Bridge (ADB). I used Chocolatey again to install this needed tool. The command is:

In a previous blog I wrote about having to recover my Azure Sphere Development Kit. So I decided to right one on what to do with it once I have recovered it. So this blog continues from My Azure Sphere Needs Reset?

However……….

According to Microsoft’s documentation on how to claim the device there is a call out:

Claiming a device is a one-time operation that you cannot undo even if the device is sold or transferred to another person or organization. A device can be claimed only once. Once claimed, the device is permanently associated with the Azure Sphere tenant.

So recently I started working on another IoT project which lead me to breaking out all my old development kits. I previously wrote a blog called My Azure Sphere Needs Reset where I walked through recovering an old Azure Sphere Development Kit I had. So I decided to write another few blogs following how I had to do the same with all my devices since I couldn’t really remember any of the configurations and some of these devices had been configured for long gone IoT Hubs and tenants that don’t exist anymore.