Microsoft has not retired classic Windows Autopilot, and nothing in the documentation behind this post carries an end-of-life date for it. What the September Intune Customer Success post did say is that device preparation is now the recommended path for user-driven Entra join and that future engineering investment goes there. That is a direction, not a deadline, and it matters because the transition costs money before any deadline appears: every new Windows 11 device provisioned the old way is another one to migrate later, Windows 10 and hybrid-joined fleets have no device preparation path at all, and pre-association only converts devices at their next natural reset. Start with the population that qualifies rather than the whole estate.
Windows 11 26H2 Is an Enablement Package — 24H2 Home/Pro End October 13
Windows 11 26H2 (Build 26300.9278) is in Release Preview as an enablement package on the 24H2/25H2 servicing branch. Do not treat it as the October 13 fix. 24H2 Home, Pro, Pro Education, and Pro for Workstations lose updates that day. Enterprise 24H2 lasts until October 12, 2027. 25H2 is already GA if you cannot wait for 26H2.
I’d Run Omarchy Everywhere if Intune Would Manage It
I have been running Omarchy on my own laptop and it is the most fun I have had with a computer in years. Arch, Hyprland, agents wired in. Then I held it up against the Intune Linux support matrix: Ubuntu 24.04 or 26.04 LTS, RHEL 9 or 10, GNOME documented as required, x86/64, Edge plus the Intune app. My machine is LUKS-encrypted with Secure Boot and a TPM, and Intune still rejects it at the platform and package layer. Here is what Intune actually does on Linux, and what I evaluated as a way around it.
Windows Autopilot device association can retire the rename script
If Autopilot device preparation is already your main path, you still rename with a script. Windows Autopilot device association in the Aug 27 preview CU (KB5120998) adds a name template during OOBE. The tax is a DeviceLink CSV, one device at a time, on physical TPM hardware.
Block Device Code Flow in Conditional Access
Device code phishing uses the real microsoft.com/devicelogin page. MFA succeeds, the attacker gets the tokens. Block Authentication flows > Device code in Conditional Access, report-only first.
Intune Device Page Becomes Default in September
The Intune device page you have been clicking through retires in the September 2609 release. Legacy view is gone. Flip the preview toggle this week and retake the helpdesk screenshots.
Another one: Grok Bot, OpenBot, Hermes, Buzz, and Herdr
Another one. Grok Bot shipped, OpenBot cloned the idea a week later, and Hermes, Buzz, and Herdr were already in the shop. They all sell an AI that does the work. They are not the same layer. Here is the map we use before we clone anything.
Entra memberOf Rules Freeze November 3
Entra memberOf does not error on November 3. Dynamic groups, admin units, and entitlement policies just stop updating and keep last week’s members. Export the rules now.
Ai Automation: Assessing Microsoft Copilot Integration and Stability Risks
Most firms are chasing Ai features while ignoring the broken data pipelines beneath them. True automation requires a clean architectural foundation, not just a shiny API wrapper. Stop buying tools and start fixing your data strategy. 🛠️📉
#Ai #DigitalTransformation #EnterpriseArchitecture
Power Platform Data Grid Goes GA — Plus a New Way to Share Flow Licenses
The data grid control is now GA for canvas apps: Fluent UI, built-in search and sort, and accessibility — a migration option for dense tables, not a forced replacement. Meanwhile Power Automate flow groups let you share one process license across up to 25 flows. Both are worth planning around if you build or maintain Power Platform solutions.
