risk-based patching ...
Microsoft recommends prioritizing Windows Server updates based on risk rather than fixed cycles. The [MC1535667](https://mc.merill.net/message/MC1535667) message from November 2, 2026, refers to a post on the [Windows Server Blog](https://www.microsoft.com/windows-server/blog/?p=21878). There is no new feature or deadline. The message states: "This guidance is available now."

What Microsoft recommends
Four criteria are decisive: exploit activity, system exposure, workload criticality, and business impact. According to the announcement, the goal is to respond more quickly to critical vulnerabilities while disrupting operations as little as possible. The problem with fixed cycles is obvious: a monthly patch day treats an actively exploited vulnerability on an internet-facing server the same as a flaw on an isolated file server.
The report breaks this down into four tasks. First, assess the risk with an inventory of servers, workloads, dependencies, and exposure. Second, set priorities and establish three paths: routine, accelerated, and emergency. Third, prepare for the emergency with documented and tested steps for deployment, validation, and rollback. Fourth, review tools: Azure Update Manager, Azure Arc, and the supported Hotpatch features of Windows Server.
Compliance: NIS2 and ISO 27001
The compliance note in the message is the most useful part for German environments. Microsoft recommends reviewing patch policies against applicable security and compliance requirements and documenting risk-based deadlines, approval processes, exceptions, alternative measures, and evidence of successful updates.
This is exactly what an auditor wants to see. A policy like 'all servers 14 days after Patch Tuesday' provides no justification for exceptions, whereas a path with a defined emergency window does.
What you can do with it
Start with the inventory, because without exposure and criticality per server, there is no prioritization. Define the three paths with deadlines that your operations can meet, and test the rollback before the first emergency. Document exceptions, including the workaround, such as a firewall rule until the patch.
Conclusion
The recommendation is not new, but it provides an official basis for discussions with management and auditors. Those who replace fixed patch cycles with three pathways—inventory, emergency plans, and evidence—better meet the expectations of NIS2 and ISO 27001 because they can justify their decisions.
Microsoft lists the tools but not the terms. Check the licensing and prerequisites for Azure Update Manager and hotpatching before integrating them into your process.
additional links
| Source | URL |
| Microsoft Message Center MERILL | https://mc.merill.net/message/MC1535667 |
| Windows Server Blog | https://www.microsoft.com/windows-server/blog/?p=21878 |
💬 Comments
0 commentsBe the first to start the discussion with a helpful comment.
Leave a comment
Comments are reviewed briefly before they are published — factual, respectful and to the point is just right here.