Listen in the Podli app 🎧
Follow your favourite podcasts, listen offline and in the car with CarPlay and Android Auto, and always pick up where you left off. Free to try.
Most teams still treat Windows patching as a monthly event, while updates now run continuously and exploits arrive within days. This episode walks IT admins through Windows Update for Business, Intune update rings, feature update policies, Windows Autopatch, expedited updates, drivers, reporting and troubleshooting. You will leave with an operating model that turns patching into governed, measurable change.
In this episode- 00:00 – Patching is not an event
- 01:12 – The old model and why it breaks
- 06:04 – Desired state and Windows Update for Business
- 15:56 – Update rings, deadlines and feature update policies
- 32:33 – What Windows Autopatch actually is
- 49:18 – Expedited updates and drivers
- 59:50 – Failures, reporting and metrics
- 83:47 – From patching devices to governing change
Key takeaways- Modern Windows updates run as a continuous, client-side system: Intune declares the policy and Windows Update for Business delivers, wherever the device is.
- Design staged rings with real deadlines, pin feature versions deliberately against the support calendar, and use Autopatch to automate execution, not accountability.
- Measure exposure windows and time to patch instead of a single compliance percentage, and give policy, pilots and exceptions named owners with a monthly review.
Worth quoting“Patch Tuesday was never meant to be a deadline. It was a signal. Microsoft was telling you that new updates were available and that the clock had started.” – Mirko Peters (01:59)
“The cost of delay is invisible. Nothing happens until it does. And when it does, it's not a ticket. It's an incident.” – Mirko Peters (05:35)
Explore more on M365.FM- Episode page: the full episode with chapters, quotes and FAQ on Windows update management
- Microsoft Intune – the policy plane where update rings, feature update policies, expedites and reports live
- Microsoft Entra ID – devices must be Entra ID joined or hybrid joined before Windows Autopatch accepts them
- Governance – the closing argument that continuous change needs continuous governance with named owners
- Mirko Peters – host of this episode, who asks listeners for their next topic in the outro
- Related episode: Group Policy - Simply Explained
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast:
https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
This episode includes AI-generated content.
