MDM Monthly: September 2026 Intune, Jamf, Apple Updates

This is my monthly roundup of mobile device management (MDM) and unified endpoint management (UEM) news for September 2026, covering Apple iOS and macOS, Microsoft Intune and Windows 11, Jamf, Omnissa Workspace ONE, Android Enterprise and Ivanti.

September was the month Apple’s OS 27 landed and took legacy software update management with it. Windows 11 26H2 shipped with two lifecycle dates close behind it, Jamf and Omnissa spent their conferences on AI governance, and Intune closed the month with a large service release. Apple also patched one actively exploited zero-day on the 28th, which is the security item to act on first. The details follow.

Executive Summary

Apple fixed an exploited CoreGraphics flaw (CVE-2026-86950) on September 28. Devices still on iOS or iPadOS 26.x, macOS Tahoe or Sequoia need 26.7.1 or 15.8.1.
OS 27 shipped September 14 and legacy Apple software update management stops working on 27.0, and Windows 11 24H2 Home and Pro reach end of updates on October 13.
Jamf and Omnissa announced AI governance roadmaps, much of it due in Q4 2026 or 2027 with no pricing stated, and Omnissa’s MCP server is generally available.

Executive view: cost and risk

Opex: Neither Jamf’s nor Omnissa’s announcements state pricing, so get it from the vendors before your budget cycle. Moving off legacy Apple update policies and handling the Entra passkey default are planned labor, and the passkey default adds helpdesk volume.
Capex: Devices that can’t run iOS 18, the new Intune minimum for standard management, or can’t take OS 27 or Windows 11 26H2 are refresh candidates, as are 24H2 Pro devices on October 13. Omnissa Cloud PC has no availability date, so don’t plan spend around it yet.
Enterprise impact: Apple says the exploited CoreGraphics flaw was used against specific targeted individuals on iOS before 27, so high-risk roles go first. An AI client with write access to a UEM can wipe, lock or push to a group, so its blast radius is your fleet.
Decision needed: Adopt a same-day patch policy for flaws Apple or CISA marks as exploited. Set read-only as the default for any AI client connected to a UEM, and hold AI governance budget until vendors state availability and pricing.

Download the one-page executive brief (PDF)

Apple ships OS 27, and legacy update management stops working

Apple released iOS 27, iPadOS 27, macOS Golden Gate 27 and the rest of the OS 27 family on September 14. Its enterprise release notes say legacy software update management no longer functions on any 27.0 operating system. That covers software update commands and queries, recommended cadence settings, and update restrictions such as deferrals. Apple points IT teams to declarative software update management, and the notes add that updates can now be enforced on a supervised device after a Return to Service erase.

The rest of the management changes are worth a read: a consolidated consent prompt for default privacy permissions, declarative VPN, DNS and relay configurations, restrictions for Siri AI, Visual Intelligence and Natural Language Calendar Event Editing, legacy MDM profiles delivered as declarative assets, new status items for enrollment type and Lockdown Mode, remote AppleCare log collection on supervised devices, and a way to skip the new Liquid Glass setup pane. Apple followed with 27.0.1 on September 28, which has no published CVE entries.

The vendors are responding. Microsoft said in March that Intune will end creation of legacy iOS/iPadOS and macOS update policies, and its September service release added the OS 27 Setup Assistant skip key for the Device features tour in ADE profiles. Jamf Pro 11.32 added OS 27 inventory attributes, and 11.32.1 added Jamf Remote Assist support for macOS 27.

September’s Apple zero-day: CoreGraphics, CVE-2026-86950

Apple shipped one fix in September for a flaw it says was exploited. On September 28 it released iOS 26.7.1, iPadOS 26.7.1, macOS Tahoe 26.7.1 and macOS Sequoia 15.8.1, each carrying a single CVE: CVE-2026-86950, an out-of-bounds write in CoreGraphics. Opening a maliciously crafted file can lead to arbitrary code execution. Apple fixed it with improved bounds checking and credits Meta Product Security.

Apple’s wording is that it is aware of a report that the issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 27. The macOS advisories repeat that statement but tie the exploitation report to iOS. Apple hasn’t named the targets, the delivery method or when the attacks began. CISA added the flaw to its Known Exploited Vulnerabilities catalog on September 29 with a federal due date of October 2.

The scope matters for how you triage. iOS 27.0.1 and macOS Golden Gate 27.0.1 shipped the same day with no published CVE entries, and Apple’s text puts the exploitation on iOS before 27. Anything still on iOS or iPadOS 26.x, or macOS Tahoe or Sequoia, needs the 26.7.1 or 15.8.1 update, and that includes devices held back by deferral settings or a slow OS 27 rollout. The September 14 releases (126 CVEs in iOS 27, 82 in iOS 26.7) carried no exploitation notes, and the iOS 26.6.2 build on September 8 had no CVE entries at all.

Windows 11 26H2 is out, with two lifecycle dates close behind

Windows 11 26H2 reached general availability on September 29. Microsoft delivers it as an enablement package for devices on 25H2 and 24H2, so the move is a small update and a restart rather than a full upgrade. Per Microsoft’s release health page, 26H2 gets updates until October 10, 2028 on Home and Pro and until October 9, 2029 on Enterprise and Education.

The dates behind it matter more right now. Windows 11 24H2 Home and Pro reach end of updates on October 13, ten days from this writing, and 23H2 Enterprise and Education follow on November 10.

Microsoft’s 26H2 page lists changes to test before a broad push. Default trust for cross-signed drivers is removed, WMIC is gone on 24H2 and later, and Windows settings backup, app-specific taskbar actions and File Explorer enhancements are on by default for eligible commercial devices. Administrator protection and built-in Sysmon are available but off by default. Intune had day-zero Settings Catalog support for the validated 26H2 settings in its September service release.

Intune: deployment plans and a large September release

In the week of September 21, Microsoft added deployment plans, a Deployments experience for rolling out apps and policies in stages across rings with Multiple Admin Approval built in. It covers Win32 apps, Enterprise App Catalog apps, Settings catalog policies and Endpoint security policies. The week before, a preview of faster compliance updates for Windows arrived: supported devices request reevaluation when signals like firewall, BitLocker or Defender status change instead of waiting for the next check-in.

Service release 2609, in the week of September 28, carried the bulk of the month’s changes:

Minimum version: iOS/iPadOS 18 or later is now required for standard device management, Company Portal and app protection.
Device page: The new single device page is the default for all admins, and the previous page is gone.
Android Enterprise: Tenants bound with a Gmail account can upgrade the connection to a managed Google domain. Assignment filters now apply to Android Settings Catalog policies. Microsoft Defender can launch during COBO and COPE setup.
Windows apps: Win32 changes use push notifications so devices check in sooner, and the Intune Management Extension checks for assignments right after the Enrollment Status Page completes.
Security: A new Windows endpoint security template adds Defender for Endpoint AI agent runtime protection in Audit or Block mode. Compliance partners can now onboard their own connectors with self-service.
Government cloud: Cloud PKI and Remote Help are available in GCC High. Neither is supported in DoD.

Jamf Pro 11.32, JNUC 2026 and the Keep Aware acquisition

Jamf Pro 11.32 shipped September 8, tested against the OS 27 betas, with inventory attributes that give real-time enrollment and health visibility and cut reliance on MDM queries. They need OS 27 or later. Jamf Pro 11.32.1 followed on September 17 with fixes for several third-party library vulnerabilities, a fix for Entra ID device compliance failing to register devices when interactive MFA is on, and a fix for a 409 error in the identity-first Platform SSO workflow when an Okta allow list contains com.microsoft. Jamf isn’t mass deploying 11.32.1 to Standard Cloud, so manual upgrade is the route there. The 11.33.0 beta opened September 18 with OIDC single sign-on for end users.

At JNUC in Kansas City on September 23, Jamf announced a broad AI governance and automation roadmap. By availability:

Available now: AI visibility and governance on managed Macs, the Platform API Gateway, a Terraform provider, Jamf Device Checker, and BYOD for iOS and Android.
Q4 2026: Deeper AI activity insights, AI usage and cost insights, browser AI governance, on-device AI via Blueprints, mobile AI governance, automated app lifecycle, App Insights, and Apple-native endpoint data loss prevention.
Q1 2027: Routines on a Jamf-hosted automation engine in GA, with public betas of AI-powered self-service diagnostics, device health insights, automated ring deployments and Jamf Tap.

The same day, Keep Aware announced that Jamf has acquired it. Keep Aware does browser security and AI usage control. Terms weren’t disclosed, and no integration timeline was given.

Omnissa Workspace ONE: MCP server, new agents and Elara

On September 29 at Omnissa ONE in Orlando, Omnissa announced a hosted MCP server, now generally available, that lets MCP-capable AI clients work with Workspace ONE UEM under the same role-based access controls and audit trail as any admin. It also described phased deployment extensions with DEX-based rollout progression, Smart Groups 2.0 with multi-step rules and nested AND/OR logic, and two UEM features marked as coming with no dates: dual admin approval and root-of-trust resource signing for apps and profiles.

Elara, an AI governance layer, is in beta. It covers shadow AI detection, usage limits through the Omnissa AI Gateway, and change control that can route high-impact changes to an approver. Omnissa’s press release also introduced Omnissa Cloud PC, which runs on AWS first, Horizon Delegate, and agents for digital experience, vulnerability defense and Windows app lifecycle, all without availability dates.

Android Enterprise: September security bulletin and roadmap

Google’s September Android Security Bulletin, published September 8 and updated September 16, carries two patch levels, 2026-09-01 and 2026-09-05, and roughly 180 issues, 31 of them critical. The most severe is a critical remote code execution flaw in System that needs no extra privileges and no user interaction. The bulletin doesn’t note exploitation, and devices at 2026-09-05 or later include every fix.

Google’s September 23 post on Android Enterprise is the roadmap. Unified Update Controls brings OEM updates, Mainline and Google Play system services into one system with peak-hour and freeze windows, and a Feedback API for rollout visibility follows later this year. Admins can restrict or disable AI automation fleet-wide. XR devices, including the Samsung Galaxy XR, are managed through the same EMM consoles, with the XREAL Aura due in Q4, and policies stay enforced when a device drives an external display. Admins can pre-approve local network permission prompts, and Attestable Identifiers for verifying hardware identity arrive later this year.

Also on the radar

Ivanti: The September 8 security update covers Endpoint Manager Mobile (CVE-2026-18851), Sentry (CVE-2026-83527) and Neurons for ITSM. Ivanti has no evidence of exploitation and says other products are unaffected.
Microsoft Entra: Per Microsoft’s schedule, passkeys became the default sign-in experience starting September 1 in the public cloud. Users enabled for SMS or voice are enabled for passkeys and prompted at their next MFA sign-in. Telecom provider selection opens October 30, and native SMS and voice authentication ends February 1, 2027.

What to watch

October 13: Windows 11 24H2 Home and Pro reach end of updates. 23H2 Enterprise and Education follow on November 10.
October 30: Microsoft opens telecom provider selection for Entra SMS and voice authentication. Native SMS and voice sign-in ends February 1, 2027.
Jamf’s roadmap: Jamf’s list for Q4 2026 includes deeper AI activity insights, browser AI governance, automated app lifecycle and Apple-native data loss prevention. Routines on Jamf’s hosted automation engine is slated for Q1 2027. The 11.33 beta, which adds OIDC single sign-on for end users, should reach release in the coming weeks. Jamf has given no integration timeline for Keep Aware.
Omnissa’s open items: Dual admin approval and root-of-trust signing for apps and profiles are listed as coming with no dates. Elara is in beta, and Omnissa Cloud PC and the new agents have no availability dates.
Android Enterprise: Google says a Feedback API for Unified Update Controls and Attestable Identifiers are due later this year, and the XREAL Aura arrives in Q4.
Apple OS 27: Legacy software update management is already dead on 27.0. Watch how quickly your vendors retire their legacy update policies, since Microsoft has said Intune will stop creating them.
Intune minimum OS changes: Per Microsoft’s plan-for-change notices, Intune, the Company Portal and the management agent will support macOS 15 and later shortly after macOS 27 releases, which has now happened. Enrolled Macs on macOS 14 or earlier stay enrolled, but new enrollments on those versions are blocked. Intune will also remove its legacy Apple software update workloads after Apple retires the underlying commands, and you should move any remaining update scenarios to declarative management first.
October 31: Microsoft says Google Play Strong Integrity enforcement reaches Android 13 and later devices that have had no security update in the past 12 months. Those devices can drop to Device Integrity, which can trigger conditional launch blocks or noncompliance. Review your minimum OS and minimum patch level settings in app protection and compliance policies.
In development at Microsoft, no dates given: Apple OS 27 status data in device inventory (enrollment type, Return to Service, Lockdown Mode), declarative VPP app downloads in the Company Portal, Enforce Routes in VPN profiles, a setting to disable MAC address randomization on Wi-Fi for macOS 15 and later, noncompliance for prohibited local AI agents on Windows, quality update approvals for Quick Machine Recovery in Windows Autopatch (listed as “soon”), and scoped permissions moving to general availability. Before that last one becomes the default, run the Permissions Assessment Report under Tenant administration.
Apple’s OS 27 checklist: Per Apple’s WWDC26 device management notes, management services need TLS 1.2 or later with cipher suites and certificates that meet the new App Transport Security requirements or connections may fail. The AssetCache profile is deprecated in macOS 27 in favor of a declarative content caching configuration. Backups no longer restore enrollment, management or supervision state on iOS, iPadOS and visionOS 27, so restored devices re-enroll through Automated Device Enrollment.
Apple volume purchasing, later this year: Apple says IT will be able to buy and assign auto-renewing app subscriptions to users, and free apps will stop requiring license quantities, per its WWDC26 services update.

My take

My position: Treat the AI governance announcements as roadmaps and spend October on the deadlines that are real. For any AI client connected to a UEM, role design is the control that matters.

September’s headlines were about AI governance. Jamf and Omnissa each built a conference around it, and both announced ways to see AI use on managed devices. I’d read those announcements as roadmaps. Much of Jamf’s list lands in Q4 2026 or 2027, Elara is in beta, and neither announcement states pricing, so budget conversations will need a sales call. The deadlines that are real today are plumbing: legacy Apple update management is gone on OS 27, and Windows 24H2 Home and Pro stop on October 13.

The item that deserves a security review is the MCP server. Omnissa’s is generally available and lets AI clients act on Workspace ONE UEM under the same roles and audit trail as any admin. That’s a sensible design, and it makes role design the control that matters. Start an agent with read-only access, keep write roles narrow, and require approval for anything that can wipe, lock or push to a group. Dual admin approval, which Omnissa lists as coming, is the feature I’d wait for before granting write access.

My prediction: by the second quarter of 2027 every major UEM will ship an MCP server and AI-usage discovery, and buyers will stop comparing those checkboxes. The comparison will move to approval workflows, audit quality and rollback. In the meantime the best use of October is unglamorous: finish the declarative update migration, move Windows devices to 26H2 in rings, and patch.

What to do next

Confirm every iPhone, iPad and Mac still on OS 26 or earlier is at iOS/iPadOS 26.7.1, macOS Tahoe 26.7.1 or Sequoia 15.8.1. Pull any deferral that is holding those builds back, and flag people in high-risk roles for a same-day check.
Inventory every Apple software update policy by vendor and tenant, flag anything still on legacy commands, and move to declarative updates before OS 27 reaches production devices.
Report Windows devices by edition and version. Get Pro devices off 24H2 before October 13 and 23H2 Enterprise and Education before November 10, and pilot 26H2 with driver and WMIC checks.
In Intune, find devices below iOS/iPadOS 18, pilot deployment plans, and look at the managed Google domain upgrade if your Android Enterprise binding uses a Gmail account.
Move self-hosted Jamf Pro to 11.32.1 or later, apply the Ivanti EPMM and Sentry fixes, and check Android fleets for patch level 2026-09-05.
In Entra, confirm every user has a phishing-resistant method, and decide before October 30 whether you need a telecom provider for SMS or voice.
Before connecting any AI client to a UEM, define a read-only role and an approval path for writes.

Sources

I’m TJ Singh, a managing principal in mobility and endpoint management with more than 20 years of global experience in the device management field.

About me · Start here · Predictions

AI tools may have been used to conduct research for this article.