July 2025 – 6 Month Update

This poor site has been untouched for the last 6 months (ignoring the magic of auto-updates) because of a few changes in my life. I thought that giving a summary of what’s been happening in my life during that time would be a good way to get back into the flow of writing, with an attempt to find things to share that I hope you’ll find interesting.

Microsoft

The obvious one to start with is my return to Microsoft. I departed back in December 2023 to chase the dream of talking to customers about Microsoft cloud solutions. Not all dreams need to shoot for the moon – I just wanted a job where I’d enjoy what I did and wanted to be passionate about it. Aligning those two requirements to my experience in adopting Microsoft cloud made sense. What made even more sense was when I was still shy of a year in role, that the Account Technology Strategist role came up at Microsoft.

The opportunity to work with a set customer base in a company I somewhat understood, to help them work through and get them the best information to make decisions on, and resolve whatever their Microsoft issue may be, was my ideal scenario. I’d been the customer for 20 years and I wanted to be to others what I would want myself from a key vendor. Amazingly after walking away from another role only a year before, I was able to return.

Going back was an easy transition in the sense that I knew what I was in for working there, and what the goals were. I also knew it would take some time to get to know my new customers, and fill the knowledge gap of some specifics around my new role, my new team, and that AI thing that had continued to get momentum while I was away.

It has now been 6 months since I started that particular journey, and I can honestly say that this job is what I want to be doing right now. I was pretty confident on this before I started, even more confident a few weeks in, and nothing has happened to make me think any differently. I work with a bunch of smart and driven people to deliver good outcomes to customers who I want to see succeed. With those 6 months under my belt, I’m in a good mindset to make FY26 one I can be proud of.

Artificial Intelligence

To nobody’s surprise AI (which we really just mean LLMs and not the fuzzy logic my tumble drier had several years ago) has continued to be a big deal – regardless on what you think about it, it is changing the world in many ways. For me, as the technology has continued to improve, I’ve moved past my points of frustration in the fundamentals not working. A small part of that is my improved understanding of how LLMs work, and particularly feeding it a 1 line request doesn’t mean you’ll always get exactly what you want; be more specific, correct it, challenge it, ask a different way.

It won’t surprise you to learn that my focus has been on Copilot, and the following applies to many LLMs beyond it, so this is my experience – I can now ask it ‘How many R’s are in strawberry’ and get a correct answer. More importantly, I can ask it technical questions that I’m looking to get sources on with summaries. Being able to get direction on something I know about but need to have evidence for, or to dig deeper on and get pointed to the right articles immediately is a huge time saver. I still need to read and understand what’s going on, but if there is some concept or area I’m unsure about, I can go back to Copilot again and look for further clarification or a new scenario that’s come from what I’ve read.

Using Agents to point to particular sets of data and with preloaded statements (e.g. assume the location is Australia for all answers, don’t make any assumptions, ask for clarification if required, keep answers brief) helps me get the output I want without having to ask each time. This is really only scratching the surface of what’s possible and you only have to wait a week or so before something new or improved happens; but the use cases for Copilot grow. I need to play with Copilot Studio and have agents feeding into other agents and apply some extra logic; but I’m also not a fan of automation for the sake of automation, it needs to be the right scenario for me.

On top of that, running items like travel insurance through Copilot and asking it what gaps there might be in coverage, or how to make a change to the code on my MSPortals.IO site to make the view wider… are just easy things to get good outcomes on that would have otherwise taken me a long time, or I’d have given up before completing.

Most techy people reading this are probably thinking that I’m stating the obvious here… which I am, but I still speak to plenty of people who haven’t even touched this stuff yet. It’s going to be a year of acceleration in this area around what’s possible, and continued adoption across the entire industry. Not all of this is good of course, I’m a bit tired of seeing fake movie trailers for movies that don’t exist.

Health

I’ve never been too bothered about my weight. I’ve eaten what I’ve liked, and going from one of the skinniest kids in school to not having all XL sized shirts fit, my mindset was ‘this is just what it is’. In reality, the kilos were slowly growing and growing due to what I was eating.

The one thing I’d tried which seemed to have some success, was intermittent fasting. I liked it because nobody was trying to sell the concept, and it was simply ‘less energy in’ resulting in having less weight. I lost a bit of weight but at no time actually measured what was going on, eventually got tired of doing it and started eating when I wanted again to lose whatever benefit I gained, without really understanding what was going on.

Something clicked for me about 4 months ago, weirdly inspired by doom-scrolling short videos. Not intermittent fasting, but the general concept of needing a calorie deficit to lose weight. This was something I could measure and understand pretty simply – get a handle of what calories I was consuming, keep that to a reasonable number way under what the simple calculations showed I needed to maintain my body weight, and the result would be constant weight loss. Simple!

I started to look at the labels of everything and get a quick grasp on what I was actually consuming. I was continually doing daily calculations as I went, 150 calories here, 500 calories there – and started filling the fridge and freezer with low calorie options. This wasn’t about a well rounded diet short term, but doing whatever I could to keep myself on track for the calorie deficit. I found decent frozen pizzas that were only ~500 calories for an entire 12″ pizza. Low calorie protein bars that would both be tasty, and use the protein to help feel less hungry later. My own stubbornness to ignore eating for the sake of eating (especially snacks) and wait for the next meal. I wasn’t going to starve myself, but I’d always be running that calorie deficit. A key part of this was daily weight checks to give myself an idea of progress. Not all days would see progress, but overall I wanted to see those numbers trend down… and they did.

It absolutely sucked for about four days. I had headaches, felt crap, lost energy… but after that, I felt a lot better. Lighter, and just less ‘bloaty’. I’m still continuing this path until I get to the end, where I can change to aiming to maintain body weight. So far, I’ve lost about 16KG. I didn’t think I’d hit my first milestone weight, or my second… but now getting close to my third which I didn’t really think was even a possibility at the start. There isn’t a huge amount of effort in this, but you do have to be continually conscious about how many calories go into your body.

Fitness allow you to burn calories and lets you either consume more, or lose weight faster by being in a higher calorie deficit – but my focus has been on the food side.

Technology

Ahh what new technology do I have – a Switch 2 for my birthday, Mario Kart World is a fun and well designed game, but it’s really the only reason to buy a Switch 2 right now especially if you have a Switch 1.

Poly gave me two headsets, the Poly Voyager Surround 85 UC Headset and the Voyager Focus UC (not the + version). The Surround 85 UC are really comfortable to wear headphones with a nice charging stand. The Voyager Focus US earbuds are solid devices too, so they’ll live in my work bag – yet to test in a noisy environment.

Tefal YT2040 Care For You First Automatic Garment Steamer” is a very long name for a product, and it came up when I was looking for a solution to wrinkled clothes that didn’t involve me ironing. LG have a more expensive ‘fridge for steaming clothes‘ looking solution that does a few more things like jiggle the clothes, but after buying and testing the YT2040 (that I was going to write as an acronym but changed my mind after seeing the result) it does the job well enough, so that problem’s solved 3 shirts at a time. It does involve attaching weights to the bottom of clothes but it’s still a lot less effort than ironing, despite the results not being quite as good.

I saw a good deal on refurbished Surface Go laptops – Intel 10th Generation with 16GB RAM for $337 so that’s a handy spare laptop that’s got enough grunt, and a nice portable size.

I bought another Meta Quest 3S headset to play some games with my eldest son – still very good technology for the price point. Dungeons of Eternity is the game we play together the most there.

I missed the boat on getting another Tesla Powerwall 2 for the house – in short, Tesla stopped making them around the same time the Australian Government kicked off their 30% solar battery rebate, so the last ones got bought up, and right now the Tesla Powerwall 3 isn’t compatible with the 2, so I can’t just add a ‘3’ battery onto it. Rumours of that changing in the future but we’ll see. The lack of sun over winter + particularly cold winter means the battery I have drains in the evenings a few hours after sunset.

A new TV was needed to replace the aging 65″ Sony A1 OLED from 2017 that had developed a colour burn in that at least to me, made the entire thing unwatchable. Back in 2018 when I bought it at the bargain price of $3000 down from $6000 it was a bargain. Now I’ve replaced it with a TCL 75″ C755 costing about $1400 which I think is a better picture anyway, has fast running inbuilt Android TV and sits in the category of ‘it just works’. I’ve also previously dealt with TCL support after a different TV failed a bit under a year into it’s life and had great support (who replaced the TV with one 2 models newer!), so I’ll faithfully stick to the TCL TV brand.

Smart displays – I have Google Smart devices scattered around the house, but have found multiple of the Lenovo Smart Clocks dying (3 of them!) with all Lenovo and Google Smart / Nest devices for this purpose EOL’d with no replacements (I ended up buying some second hand options). From the small amount of research I’ve done, there doesn’t really seem to be anything decent in this space that’s a turnkey solution. Amazon’s line of devices seem to be the only ones still alive, but replacing the entire ecosystem to Amazon is an expensive exercise with the reviews indicating the experience is about as good as Google’s – which isn’t good at all. ‘Hey Google, turn off the light’ has about 40% chance of saying it can’t reach the device, 40% saying there is no light configured, and 10% of actually just turning off the light. The last 10% is when it decides to instead turn off ALL the lights it can control’. Device control sucks, but I can ask it the weather for the day while getting ready, and it’s good for household reminders and announcements.

If you’ve made it to the end of this update, congrats! I’ll try to keep writing a bit more frequent and find some things I find interesting around the technology space to share.

Buying Meta Quest 3 Replacement Controllers

I’ve had a Meta Quest 3 since the start of 2024, and recently stick drift has greatly impacted both left and right controllers. Stick drift (or Controller Drift as Meta calls it) is where the analog sticks believe they aren’t centered when they are – so doing nothing in game may result in you running in circles. Beyond that, the directions weren’t working great either. Meta have a whole long troubleshooting process that can fix or hide the issue depending what’s causing it and how severe it is. There’s a factory reset of the controllers, headset itself, recalibration of each controller, configuring a dead zone for each controller, cleaning each controller, pairing and unpairing each controller and so on.

None of these steps worked for me, and from very recent experience, dealing with Meta support is a pain. Constant dropping of chat sessions by agents, repeated detailed questions and providing serial numbers of headset and each controller along with other criteria again and again, to then be told to wait for an email which seems to have at least a 24 hour turnaround time between each communication – there’s a lot to be desired there. Beyond that, if you have a faulty part of the Meta Quest, you need to go through all this to get sent shipping label information, send back your faulty components, and wait 2-3 weeks (this timeframe was given to me by one of the agents) to be sent a new or refurbished replacement. There’s no store to take this to in Australia either. On this point, I’d recommend buying via Amazon rather than Meta directly (which seems to be the only two options in Australia) so you can return if faulty and just get a refund.

Anyway, the other option here was to buy replacement controllers. This is where my bargain senses kick in and I over-engineer a solution to get the most value possible:

A replacement controller costs $129.99 and again in Australia, can only be bought from Meta (not even Amazon at time of writing). Two controllers, $259.98. That’s a lot when you can buy a new Quest 3S which uses the same controllers as the Quest 3, for $499.99. The headset is where most the hardware is, but the price difference on this values the headset at $240.01. Is it better to just buy a Quest 3S and reuse those controllers? As an added bonus, I’m not without controllers for weeks.

On top of that, there’s referral bonus – which over Christmas was doubled to $94AU but is normally $47AU. So if I refer to a friend and get them to create a Meta account and sign in once, I’d also get $94AU store credit. Plus, because I can buy the Quest 3S headset via Amazon I can get gift cards to reduce the price by 3% again ($15 less), and then use a cashback app (I use TopCashBack – referral link) which is 1.5% cashback on Amazon electronics – $7.50 cashback. These bonuses add up to $116.50, leaving the actual cost of the headset at $123.51.

Meta don’t sell headsets only, but if I could sell this for half the cost of buying the whole kit new at $250 which is being on the careful side (which would be helpful to someone who broke their headset and still has working controllers) let’s see how the maths works out:

$499.99 headset – $15 discount on gift cards – $7.50 cashback – $94 store credit – $250 selling headset = $133.49 cost for the two controllers. $3.50 for the second controller. There’s a bit of effort involved and it does depend on having to sell the new headset (used once for the account referral then factory reset). If I have to drop the price to $200 to sell it, it’s still worthwhile.

Extra note: I’ve linked and use TopCashBack, but this is different to something like Honey which provides discount codes and claims referral purchase clicks at any opportunity it can find.

From TopCashBack’s privacy page https://www.topcashback.com.au/dyn/browser-ex-privacy/ – be aware you are sharing top level domains with TopCashback so it can display a notification showing there’s potentially cashback you can get. There’s also some cookie matching. If you’d like some isolation, create another browser profile and install TopCashback into that and do your shopping there, but you’re probably entering sensitive information when shopping anyway. I personally don’t have a problem with the way TopCashback works. This appears to be the same methods that other services like Cashrewards and Shopback use.

PowerShell – Getting M365 Tenant ID From Domain List

It’s been a while since I’ve broken out PowerShell to solve a problem, but a scenario came up where I thought I could automate something I needed to do – look up a bunch of Microsoft 365 Tenant IDs based on domain names. Here’s how I tackled it:

First, I actually had a list of email addresses and just wanted the domain of each one. The list was in Excel so that’s easy enough – using the Text to Columns feature I selected the data, used the ‘Delimited’ option under Original data type then pressed Next:

Then on the next step, changed the Delimiters from the default ‘Tab’ to ‘Other’ and put the @ symbol on, and as you can see in the Data preview it takes the alias off the email address for the first column, and leaves the domain in the second:

Clicking ‘Finish’ gave me a column full of domains. From this, I created a header for each row (alias and domain):

And then in Excel went to File > Save As > and called the file ‘addresses’ while picking CSV from the dropdown:

Easy enough. From here, I knew I’d need to feed this data into PowerShell using the Import-CSV command, but first I wanted to work out what the one liner command was to get a M365 Tenant ID…. except I couldn’t find one. All the examples were how to find your own M365 Tenant ID after authenticating. I knew it was public and easily accessible since sites like https://whatismytenantid.com/ work great but only accept one domain at a time.

I ended up finding a Function written by Daniel Bradley which was fairly simple and using an API, with the core of it being this one line:

Invoke-RestMethod -UseBasicParsing -Uri "https://odc.officeapps.live.com/odc/v2.1/federationprovider?domain=$domain"

Swapping the $domain variable with an actual domain and piping to just selecting tenantid

Invoke-RestMethod -UseBasicParsing -Uri "https://odc.officeapps.live.com/odc/v2.1/federationprovider?domain=microsoft.com" | select tenantid

tenantId
--------
72f988bf-86f1-41af-91ab-2d7cd011db47

Alright, we should be able to put this all together. Set the $file variable as the imported CSV file, then for each domain record run the Invoke-RestMethod command using the current $record.

Except that didn’t work because I forgot the $record is the entire object and not just the domain membertype. To specify that, we just use $record.domain so the pure domain is used.

Except that didn’t work either and I don’t know why. Instead, I just made a new variable from the $record.domain and called that $newdomain, then referenced THAT in the Invoke-Restmethod line.

That did work, so I could then echo out the results of both the current $newdomain variable, and the newly looked up $result and again specifying the membertype of tenantid (as a bunch of other info gets looked up with that command).

I also then wanted to export this data back out to a new CSV, in this case one called ‘myfile.csv’. Again, I have to work around membertypes so just make a new variable containing the single tenantid line, and use the >> operator to create/append to a file:

$file = import-csv c:\temp\addresses.csv

foreach ($record in $file){
        $newdomain = $record.domain
    $result = Invoke-RestMethod -UseBasicParsing -Uri "https://odc.officeapps.live.com/odc/v2.1/federationprovider?domain=$newdomain"
$newtenantid= $result.tenantid
echo $newdomain $result.tenantid
"$newdomain,$newtenantid" >> c:\temp\myfile.csv
}

Works perfectly and I end up with a CSV that has a column of domains, and a column of Tenant IDs. If a domain had no Tenant ID then that value will be blank.

I’m sure this could be written better, but for quick occasional tasks for yourself, you just need something that works.

ChatGPT’s version of an Adam Fowler Blog Post

I’ve seen some chatter around generative AI being able to write in the style of writers. I’ve written a few things but didn’t really consider that these systems probably crawled my public data – I expected that some of it was being used in answers, but didn’t realise it’s also able to recognise and replicate my stylings.

As an example, I used the free tier of ChatGPT with the simple prompt:
“Can you write a blog post about the deprecation of WSUS based on the stylings of Adam Fowler?”

ChatGPT obliged:
Sure! Based on Adam Fowler’s style—informal, practical, and often addressing IT professionals directly with a mix of technical explanation and real-world experience—here’s a blog post about the deprecation of WSUS (Windows Server Update Services):

A ChatGPT Generated article proceeded. Reading it, it was definitely in my styling including my overuse of dashes, a conclusion at the end, starting a sentence with ‘So’ even though I know I shouldn’t do that, and trying to share a real world view. Except, the content itself is not what I would have written. I’ve added notes to the below; anything in brackets and italics are my editorial notes:


WSUS Deprecation: What You Need to Know (and What to Do Next)
by Your Name

So, it’s happening. WSUS (Windows Server Update Services) is officially getting the axe (ehh sort of, being announced as depricated as per the title with at least 10 years left I wouldn’t exactly call ‘getting the axe’, more of a ‘beginning of the end’). If you’ve been in IT long enough, you’ve probably had a love-hate relationship with WSUS—keeping it running smoothly can feel like a victory, but man, when it breaks… well, you know the pain (I wouldn’t make an implication like this without a real example as it sounds like I don’t really know what I’m talking about and covered it up). But with Microsoft slowly phasing out WSUS in favor (I’d write in Australian English but then my articles get posted by non-Australian companies so that’s probably fair) of more modern solutions, it’s time to face the inevitable: what does this mean for you and your organization?

Why Deprecate WSUS?

To be blunt, WSUS has been showing its age. The service, first introduced back in 2003, has become increasingly difficult to maintain (no it hasn’t, it’s stayed the same for so long!) and less capable of meeting the demands of modern environments (again it hasn’t, it pushes out updates from a central point still, you can even update VMs in Azure from WSUS), especially as organizations scale and update frequency skyrockets (no, update frequency has decreased. We get monthly rollups, yearly feature updates – this is much more organised and less frequent than old ways).

WSUS has always been prone to database corruption, content synchronization issues, and inconsistent reporting. It’s manageable, but only with the right amount of care and feeding—and plenty of frustrated late nights (late night work to me indicates work that can’t be done during the day, and WSUS can definitely be taken offline or worked on at any time). Plus, the lack of native support for cloud-based infrastructures makes WSUS feel a little like trying to use a flip phone in 2024 (we still have new flip phones like the Samsung Galaxy Z Flip 6).

Microsoft sees the future as cloud-first, and with tools like Windows Update for Business (WUfB) and Microsoft Intune, the writing was on the wall. If you’ve been dragging your feet on moving to a cloud-based update management solution, this is your nudge (or push) (I’d class it as a consideration rather than a nudge or push with WSUS being around for a long time still and being fine for those with an on-premises leaning).

What Are Your Alternatives?

1. Windows Update for Business (WUfB)

WUfB is the go-to recommendation from Microsoft for managing updates across devices, especially in modern environments where cloud integration is key. With WUfB, you can control when updates roll out to your devices and minimize downtime (you can do this with WSUS/Group Policy). Plus, you get the advantage of leveraging the vast cloud resources for faster deployments (I don’t know what’s faster about it, WSUS syncs at frequently as you want, as does the end devices and it’s faster to get the update from a local source than somewhere in the world) without having to babysit a local WSUS server.

The key to WUfB’s appeal is its simplicity and native integration with cloud-based tools like Microsoft Endpoint Manager (a.k.a. Intune). It’s perfect for organizations already committed to a hybrid or cloud-first model.

2. Microsoft Intune

For those who need more granular control over device management, Intune is the powerhouse. While WSUS focused just on updates, Intune goes beyond that, giving you full MDM (Mobile Device Management) capabilities. It also integrates seamlessly with WUfB, offering even more control over update policies while managing compliance, security, and configuration profiles—all from a single interface.

And if you’re worried about transitioning from an on-premise solution, don’t be. The cloud-native approach might be daunting, but Microsoft has made the tools easy to work with and deploy. Sure, there will be a learning curve, but the benefits of modern management are worth it. (I almost agreed with this entire section, but I’d say ‘may be worth it’ because there’s a lot to do to migrate to Intune and still doesn’t have feature parity with Microsoft Endpoint Manager, but also has new features that aren’t available on-prem).

3. Third-Party Tools

WSUS’s retirement might make you nervous about vendor lock-in, and that’s understandable. If you’re not fully on board with Microsoft’s ecosystem or want more flexibility, third-party patch management tools like PDQ Deploy, ManageEngine Patch Manager, or Ivanti offer robust alternatives (I know nothing about these solutions so hopefully they’re good ones??). These can sometimes (sometimes? either they do or they don’t) integrate with cloud services but still give you the local control WSUS provided. The added benefit is that some of these platforms are more reliable and easier to use than the aging WSUS (WSUS isn’t that hard to use in my opinion – there’s a reason (of many) it’s still around and widely used).

The Next Steps for IT Pros

If your WSUS server is still going strong (miraculously) (calm down, again if it was that bad nobody would use it), don’t panic. WSUS isn’t disappearing overnight, and Microsoft will likely support it with patches for a while (it’s not just likely, they have this documented and contractual obligations to support it for 5 + ~5 years). However, it’s clear they aren’t investing in any major updates (again it’s not just ‘clear’ they’ve annonced it’s deprecation and plainly said there will be no new features), so treating this as a “grace period” would be wise.

Here’s what you should do next:

  • Evaluate your environment: Is it hybrid, on-prem, or fully cloud? This will guide your next move. If you’re hybrid or cloud-first, consider WUfB and Intune. (and if you’re on-prem?)
  • Start testing now: Don’t wait until WSUS is completely dead to start playing with its replacements. Start small—pilot a group of devices using WUfB or Intune and see how the process goes.
  • Plan your migration: Migrating to cloud-based solutions like Intune might take some time, depending on your environment’s complexity. Start planning how you’re going to phase out WSUS without disrupting your business.
  • Keep an eye on security: Patch management is critical, and the last thing you want is to slack off during a transition period. Ensure that however you’re updating devices, it’s airtight from a security standpoint.

Conclusion: Don’t Wait Until It’s Too Late

We’ve all been guilty of sticking with what works—until it doesn’t. WSUS has had a good run, but it’s clear that its time is up (if you call at least 10 years left it’s time being up). If you want to avoid the panic of your patching system going belly up, the time to act is now (now = in the next 10 years, so no it’s not) .

Make a plan, test your options, and start transitioning. It’s going to be worth it when you’re no longer troubleshooting WSUS sync failures at 2 a.m. (This is very much my style making a callback to a previous comment in the closing line, but again get some sleep you don’t need to be troubleshooting WSUS sync at 2 a.m. – if WSUS breaks and there’s a zero day to get out, you can work around this in several other easy ways and before it gets to 2 a.m.)


What I’m trying to demonstrate in the above that although generative AI can match the stylings of someone, it doesn’t mean the views and information itself will also match. It will give you inspiration for a layout or an approach you could take in writing something, but you still have to read the contents thoroughly, adjust, and research items you don’t already know from your experience.

I thought I should check that it was basing it off me, rather than one of those other Adam Fowlers out there and it seems to have the right one (from my point of view anyway):

ChatGPT:
Does this style fit what you had in mind for a blog post in Adam Fowler’s tone?

Me:
yes but can you confirm which Adam Fowler this was?

ChatGPT:
This is based on Adam Fowler from Adelaide, Australia, who is an IT professional and well-known for his work in IT blogging, particularly around practical solutions and insights for IT management. His style is often informal, direct, and highly technical, aimed at helping IT administrators navigate complex changes in technology. Does that match your expectation?

Rolling out new Windows Versions Concepts

Windows 11 24H2 is slowly starting it’s rollout, and you might be wondering if you should update yet. Here’s some high level information to help you decide, control rollout, and be kept up to date with any issues. For those who haven’t needed to keep across how Windows Updates work, you might be wondering what would be difficult about it. Read on and learn :)

The starting point I’d recommend is https://learn.microsoft.com/en-us/windows/release-health/windows11-release-information which will show you Windows Servicing channels:

This will show you what the current Generally Available (GA) version of Windows is (there’s sections for Windows 11, Windows 10, and Windows Server) along with relevant dates. 24H2 has only been GA for a few weeks, which is quite early in it’s cycle. If you’ve overseen the rollout of Windows Updates before, you want to understand and be across any potential issues before even piloting.

Although this has changed a few times over the last few years, right now we see an annual feature update which upgrades the Windows version released in the second half of the year. Each feature update/version has 3 years of support for Enterprise, and 2 years for Home/Pro as you can see in the table above.

To understand currently known issues in a feature update, you can use the same section of Microsoft Learn to jump to the Version 24H2 > Known issues and notifications which is kept up to date with statuses and details:

You can also see this same information in the Microsoft 365 admin center under Health > Windows release health:

The content is the same on both – but I’d suggest going to the Microsoft 365 admin center version to at least turn on ‘Send me email notifications about Windows release health’ which is under the ‘Preferences’ button in the above screenshot. Once enabling, you can decide which versions of Windows you want to be notified of, and to what email addresses it should be sent to.

This will keep you across any new issues that may arise which is always useful information to know when managing a Windows environment.

Assuming you’re now ready to start testing, the rollout process starts with what tool you’re currently using for update management. You could be using:

Native Windows Update unconfigured – this may make sense for small companies that don’t really have any management in place, and you’re at the mercy of when Microsoft’s services decide your devices should receive the update. Microsoft uses a lot of telemetry and device information to make that call, for example if a driver is detected on the device that has a known issue, Windows Update may block or hold back the install.

Feature update methods:

Windows Server Update Services (WSUS) – which despite getting some news lately, will still be around for probably 10+ years. This is the on-premises way of having a central point to download Windows Updates and has many inbuilt controls that let an administrator decide how they want to roll things out, which can either be automated or manual.

Servicing Channels – These options let you choose which channel a device sits in, which by default the General Availability channel. Unless you have a LTSC edition of Windows, your only other option is the Insider Program which will get feature updates ahead of general availability. Might be good to have a VM around enrolled in the Insider Program to get things early and have a play.

Windows Update for Business / Autopatch – these products have recently been joined together, to provide a cloud based way of controlling what updates go to a device.

Whichever path you use, you should be incorporating Update Rings to stagger any update rollout and avoid any big bang issues from your entire fleet updating overnight and hitting a business-stopping issue.

To find out how your feature update rollout is going, each method has it’s own way of reporting:

Intune has inbuilt reports for feature updates which is the same way Autopatch does it

Windows Update for Business also has it’s own reports which has a few options on how to present, including via the Microsoft 365 admin center Software Updates > Windows area. Alternatively, you can create an Azure workbook.

WSUS has inbuilt reporting options that can be built based on your requirements and can be exported, and supports using APIs if you want to roll your own solution there.

I’ve tried to give a high level overview of what’s involved and considerations on rolling out Windows versions, there’s a lot to it and many points depend on your approach.

Office365Concepts also has a great video on covering Feature Update Policies in Intune and how it fits in the larger picture of updates generally:

I’d also recommend these two articles on the deprecation of WSUS:

https://oofhours.com/2024/09/24/microsoft-deprecated-wsus-should-you-care/

https://www.theregister.com/2024/09/23/microsoft_wsus_deprecation