I read the Ignite 2026 Book of News so you don't have to.
The Intune patching story isn't in the Intune section, it's in Microsoft Perception. Agents assess, Intune patches, IT keeps control. Read that part twice.
📰 burgerhou.tj/p45zmk#MVP#MSIgnite#MSIntune
Intune at Ignite 2026: the big theme is AI agents running on your endpoints, and Intune becoming the place where you control them.
I went through the full Book of News and pulled out everything relevant for Intune and endpoint admins. Most of it is preview or private preview, so treat this as a roadmap, not a list of things to roll out on Monday.
Governing local AI agents (preview)
- Agent 365 shows which AI agents are running on your managed devices
- Devices with unapproved agents can be marked noncompliant through Intune software compliance policies
- Conditional Access then blocks those devices from company data
- For approved agents, Intune policies define what they can access and do, enforced through Microsoft Execution Containers
- Entra Global Secure Access adds network control over how local agents reach internet, SaaS and private resources
New Windows and Intune capabilities
- Windows Endpoint Security Platform: generally available. A safer way for approved security products to protect devices, with better reliability
- Declarative device management for Windows: preview. You define the desired state, Windows applies and maintains it
- Windows baseline protection: private preview. Critical security settings applied and kept in place from boot
- Enterprise App Management: private preview of automatic updates for all Windows apps, not only the ones IT deployed
- Experience controls: private preview. Bring new Windows features in on your own schedule
- OS reliability reporting in Windows Autopatch: private preview. Stop error trends, recurring failures and affected devices
- Intune and Autopatch support for Windows Server 2028 in client-like scenarios: private preview
Windows 365
- Windows 365 admin assistant in Intune: preview. AI help for Cloud PC health, investigation and troubleshooting
- Windows MAM: preview. Protection policies on the Windows App while the device accessing the Cloud PC stays unmanaged
- Context-based redirections: generally available. Clipboard, drive, printer and USB redirection based on Entra authentication context
Patching with agents in the loop
- The Microsoft Perception Risk Reduction Agent can coordinate patching through Intune, with IT keeping control of deployment (preview)
- An AI Readiness initiative for monthly Windows vulnerabilities assesses exposure and coordinates remediation through Intune (preview in January)
My take: the local agent governance story is the one to watch. Compliance, Conditional Access and network controls are tools we already know, now pointed at agents instead of only users and devices. Declarative device management and automatic updates for all Windows apps are the two I am most curious to test hands on.
Full Book of News: news.microsoft.com/events/ig…#MSIgnite#Intune
New sponsor episode: Keeran Mistry of Patch My PC on third-party patching at Patch Tuesday speed. youtu.be/CqR1tvUrGAQ
🎬 Audio & video production by Michel van Vliet
Have you seen what we have just announced at Microsoft Ignite from our Intune product group??
✅ Windows Server Management in Intune (Insider Preview)
✅ Windows Autopatch support for eligible servers
✅ AI Agent Governance with Software Compliance Policies
✅ Microsoft Execution Containers (MXC) for AI agent containment
✅ App Protection for Copilot, ChatGPT, Claude, and GitHub Copilot
✅ Vulnerability Remediation Agent with AI-assisted remediation workflows
✅ Device-level App Inventory
✅ CIS Benchmark Auditing in Intune Advanced Analytics
✅ AI-powered investigations through Microsoft Perception
✅ Improved Windows Autopilot and endpoint visibility experiences
techcommunity.microsoft.com/…
Maintenance Windows are BACK in Microsoft Intune!!
Remember this feature?
Back in March, I wrote about Microsoft's plans to introduce Maintenance Windows for Windows OS and driver updates.
Finally, a way to control WHEN Windows is allowed to install updates and restart, instead of just relying on Active Hours. But then something strange happened...
Microsoft quietly removed the Maintenance Windows announcement from the Intune roadmap. Was the feature canceled? Delayed? Nobody really knew. Well... guess what's back!
Microsoft has now officially announced Maintenance Windows in the November 2026 Intune What's New!
And this time, we're getting a dedicated Maintenance Windows section in Intune, where we can configure when update actions are allowed to run.
In my latest blog, I take a closer look at what Microsoft announced, how these policies work, and what the new configuration experience could look like.
And yes, I included some mockups based on Microsoft's documentation to show what we might expect!
Want to read the previous chapters of this story?
Part 1: Maintenance Window Settings for OS, Drivers, and Updates
patchmypc.com/blog/maintenan…
Part 2: Maintenance Window Settings Catalog… And It's Gone
patchmypc.com/blog/maintenan…
Part 3: The Return of Maintenance Windows!
patchmypc.com/blog/the-retur…
Looks like Maintenance Windows finally found their way back into Intune!
#MSIntune#WindowsUpdate#PatchMyPC#Windows11
Another security improvement in Microsoft Intune! CIS Audit is here!
A few weeks ago, I wrote about the new STIG Audit baseline in Microsoft Intune and how Windows uses the Device Inventory Agent to check the device configuration against the DISA benchmark.
Well... it looks like STIG is no longer alone! The CIS Microsoft Intune for Windows 11 Benchmark (Audit Only) is now also showing up in Intune!
This means we now have two security benchmarks available for auditing Windows 11 devices: STIG and CIS.
And the interesting part? These are audit baselines. They check how Windows is configured and report findings without changing settings.
Want to know what happens behind the scenes when you create one of these audit baselines?
I already covered the complete STIG journey, from assigning the policy to the Device Inventory Agent evaluating the settings and reporting the results back to Intune.
Read the blog here:
patchmypc.com/blog/intune-st…#MSIntune#Windows11#CIS#STIG#EndpointSecurity#Intune
Can we automate Windows Autopilot pre-provisioning?
I got this question a couple of times at @mmsmoa and MMS Midway, and it made me wonder how much of the technician flow we could automate with one not-so-simple PowerShell script.
You know the flow... Press the Windows logo key five times, select Pre-provision with Windows Autopilot, click Next, and wait for the device to enroll. Then come back when the screen is green and click Reseal.
I wanted to run one command and walk away.
The script checks the Autopilot profile Windows has already downloaded, starts pre-provisioning, and lets Windows show the Enrollment Status Page as usual.
The tricky part was the reboot. I added a temporary Windows service that restarts the monitor during the Windows setup session. The monitor verifies that Device ESP succeeded for this run, then presses the actual Reseal button once.
I tested it on a physical Windows 11 device. The green screen appeared, a few seconds passed, and the laptop shut itself down. That was the moment I knew the whole flow worked.
Who is Interested?
#WindowsAutopilot#Intune#MSIntune#Windows11@abetterpc@ramseygyoutu.be/0yAcjO-kp4o
More Intune Latency Improvements!!!
Microsoft announced two more improvements that should make Intune a LOT more responsive. And the best part? They're live now!
-PowerShell scripts are getting faster!
Remember waiting for the next 8-hour polling cycle before Intune picked up changes to your scripts?
Well, Intune now uses IC3 to notify devices about script changes, allowing them to check in much sooner instead of waiting for the next scheduled poll!
-And compliance is getting faster too!
The moment we change a Compliance policy, it will result in a Push Notification asking the device to check in and perform a compliance check
That means fixing a compliance issue no longer necessarily means waiting for the next scheduled check-in before Intune notices something has changed.
Two more improvements that might sound small, but can make a HUGE difference in how quickly Intune responds to changes.
And when you combine these with the recent improvements to Win32 app delivery and all the other things they implemented, it's becoming pretty clear that Microsoft is seriously tackling Intune latency.
Read the blogs on @PatchMyPC ... and for now, check out the video if you don't believe me about how fast Intune is!
#Intune#MSIntune#Windows11youtu.be/5LX2-C-MsGI
🔒 𝗦𝗲𝗰𝘂𝗿𝗲 𝗕𝗶𝘁𝘀 💡
𝗡𝗧𝗟𝗠 𝗦𝗶𝗴𝗻𝗶𝗻𝗴: 𝗡𝗲𝘄 𝗪𝗶𝗻𝗱𝗼𝘄𝘀 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗖𝗵𝗮𝗻𝗴𝗲𝘀
With the November 2026 Patch Tuesday updates, Microsoft introduced new NTLM signing protections addressing 𝗖𝗩𝗘-𝟮𝟬𝟮𝟲-𝟭𝟭𝟴𝟳𝟯𝟳.
The goal is to ensure NTLM authentication establishes a cryptographic session key and negotiates actual message signing instead of relying on the legacy ALWAYS_SIGN behavior ⚠️.
The changes are being introduced in two phases:
🔹 𝗡𝗼𝘃𝗲𝗺𝗯𝗲𝗿 𝟮𝟬𝟮𝟲: Windows clients offer NTLM signing by default, while servers continue accepting connections without signing.
🔹 𝗠𝗮𝘆 𝟮𝟬𝟮𝟳: Windows servers will require NTLM signing by default. Clients that don't negotiate signing will be rejected.
🔎 𝗛𝗼𝘄 𝘁𝗼 𝗰𝗵𝗲𝗰𝗸 𝘆𝗼𝘂𝗿 𝗲𝗻𝘃𝗶𝗿𝗼𝗻𝗺𝗲𝗻𝘁?
With 𝗡𝗧𝗟𝗠 𝗘𝗻𝗵𝗮𝗻𝗰𝗲𝗱 𝗟𝗼𝗴𝗴𝗶𝗻𝗴 enabled, you can inspect the following events in Microsoft-Windows-NTLM/Operational:
• 𝗖𝗹𝗶𝗲𝗻𝘁: Events 4020 and 4021
• 𝗦𝗲𝗿𝘃𝗲𝗿: Events 4022 and 4023
• 𝗗𝗼𝗺𝗮𝗶𝗻 𝗖𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗲𝗿: Events 4032 and 4033 (same-domain authentication)
In the 𝗡𝗧𝗟𝗠 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 section, check:
✅ 𝗡𝗲𝗴𝗼𝘁𝗶𝗮𝘁𝗲𝗱 𝗙𝗹𝗮𝗴𝘀: SIGN (0x10) and KEY_EXCH (0x40000000) should be present according to Microsoft's readiness criteria.
✅ 𝗦𝗲𝘀𝘀𝗶𝗼𝗻 𝗞𝗲𝘆 𝗦𝘁𝗮𝘁𝘂𝘀: Present
⚠️ 𝗗𝗼𝗻'𝘁 𝗿𝗲𝗹𝘆 𝗼𝗻 𝘁𝗵𝗲 𝗘𝘃𝗲𝗻𝘁 𝗜𝗗 𝗼𝗿 𝗪𝗮𝗿𝗻𝗶𝗻𝗴 𝗹𝗲𝘃𝗲𝗹 𝗮𝗹𝗼𝗻𝗲. Event 4023 can appear even when NTLM signing is negotiated. Similarly, Channel Binding: Not Supported does not mean NTLM signing is missing.
The screenshot shows a successful NTLM negotiation with both flags and a session key present. One complication is that 𝗡𝗲𝗴𝗼𝘁𝗶𝗮𝘁𝗲𝗱 𝗙𝗹𝗮𝗴𝘀 is a hexadecimal bitmask. You won't necessarily see 0x10 directly in the event.
You need to decode the value to check whether the SIGN bit is set. Microsoft provides a PowerShell script in 𝗞𝗕𝟱𝟭𝟯𝟱𝟱𝟱𝟳 to identify authentications where the SIGN bit is missing.
🔎 Start auditing NTLM usage now and identify clients that may be affected when enforcement begins in May 2027.
📚 Microsoft KB5135557 in the comments.
#NTLM#WindowsSecurity#ActiveDirectory#PatchTuesday
In which I chat with the legendary @AndrewPlaTech about #MMSMidway, "death planning" for your digital assets, the value of community, and a little bit about AI. A fun chat for the first half of this week's PowerShell Podcast: youtube.com/watch?v=ZIc_AStv…