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.

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.

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.

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.

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).

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.

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.

So I needed to break out my Azure SPhere Development kit again that I haven’t touched in a very long time. Since then, the tenant my Azure Sphere was registered to has changed, and along with other things like my memory in my aging head, I couldn’t remember for the life of me how to access the kit. So this blog is mainly for me so in 6 months when I need to use my Azure Sphere development kit again I will have a quick and easy reminder.