Cut-paper illustration of a management console pushing app updates to a laptop and smartphone, next to a calendar with circled deadlines and a checklist

Intune ships a service update roughly every month, and most of them deserve exactly the attention admins actually give them: a skim over coffee. Service release 2609 (rolling out the week of September 28) is different in one respect. Three of its changes alter behavior on devices you already manage, and the announcements that arrived alongside it carry deadlines you will regret sleeping through.

Here is what moved, ranked by the action each one demands from you.

# Change What it actually is Action Deadline
1 Health attestation migrates to Azure Attestation DHA becomes MAA, automatic, no opt-in Allow intunemaape*.attest.azure.net through firewall and proxy; exclude from TLS inspection End of Q1 2027
2 Companion apps retired Calendar, People, Files apps stop working Remove Intune assignments before uninstalling Dec 16, 2026
3 Win32 app delivery goes from pull to push Push notifications plus an immediate post-ESP check Allow the push channel's regional endpoint; test, don't promise times Rolling out now
4 Deployment plans (preview) Staged rollout rings with Multi-Admin Approval Design your rings now; wait for GA before production reliance Preview
5 Web-based enrollment default for iOS/iPadOS New profiles default to web enrollment with just-in-time registration Deploy the SSO extension policy for JIT registration Early 2027

The attestation migration is the quiet one that bites

Microsoft announced in September that Intune will automatically move Windows 11 device health attestation from the Device Health Attestation service (DHA) to Microsoft Azure Attestation (MAA) by the end of Q1 2027. There is no toggle to flip, no pilot to join. It happens in the background.

The risk is not the migration itself; it is the firewall. Any compliance policy that checks BitLocker, Secure Boot, or Code Integrity uses this attestation chain. When a device tries to attest against an MAA endpoint for the first time and your firewall or proxy blocks it — or worse, performs TLS inspection on the traffic — the device simply reports "Not compliant," with no other warning. And "Not compliant" is exactly what Conditional Access reads when it decides whether that user gets into Outlook.

So this one is a firewall job, not an Intune job: confirm your egress allows intunemaape*.attest.azure.net, and exclude those endpoints from inspection. Boring work. Do it before the first ticket arrives.

The companion apps die on December 16 — remove assignments first

The M365 Calendar, People, and Files companion apps that shipped with Windows 11 become nonfunctional on December 16, 2026. Microsoft has already stopped auto-installing them, but existing installs stay put until you act.

The gotcha is pure Intune mechanics: if the apps were delivered through Intune assignments, remove those assignments before you uninstall. Otherwise Intune's app lifecycle does exactly what it is supposed to do and reinstalls the app you just removed, and you will be explaining that to someone who does not find it funny. Microsoft is not shipping fixes during the wind-down, so "wait and see" is not a strategy here.

Win32 apps finally get a push

For years, assigning a Win32 app in Intune meant waiting. The Intune Management Extension checks assignments on its own polling schedule — up to 8 hours — so a new required app could sit quietly while a user opened a ticket saying "my app isn't here." Forcing a sync, restarting the IME service, or suggesting a reboot were the usual rituals. None of them belonged in 2026.

Service release 2609 changes the shape of this in two ways:

  1. Intune now sends push notifications for admin-initiated and service-side Win32 app changes. The device checks in sooner instead of waiting for its next poll.
  2. The IME checks for app assignments immediately after the Enrollment Status Page (ESP) finishes, which closes the awkward gap where Autopilot completes but required apps that missed provisioning sit idle for up to an hour.

Two caveats, stated the way Microsoft states them: devices check in sooner, not instantly — there is no new delivery SLA to quote in a status meeting, so test the behavior in your own tenant before promising anyone a timeframe. And the push channel has its own per-region firewall endpoint; if that is blocked, you keep the old slow behavior and nothing warns you.

The polling does not go away — the IME still runs its routine checks as a fallback. It just means the common case gets faster.

Deployment plans: design the rings now

The new Deployments experience stages the rollout of Win32 apps, Enterprise App Catalog apps, Settings Catalog policies, and Endpoint Security policies across rings, with Multi-Admin Approval integration. It is in public preview.

The discipline here matters more than the feature. Rings only help if you define them before the first incident: pick your pilot ring, your early ring, and the everyone-else ring while nothing is on fire. Preview means do not build production processes on it yet, but it does not mean you cannot have the ring membership lists ready when it goes GA.

iOS enrollment goes web-first in early 2027

Starting early 2027, web-based device enrollment becomes the default for new iOS/iPadOS enrollment profiles. Existing profiles are unchanged. Web enrollment uses just-in-time registration through Apple's SSO extension, which cuts authentication prompts and skips the Company Portal install on BYOD devices — Microsoft calls it the most secure enrollment method for device attestation.

The prerequisite: deploy the SSO app extension policy (a device-features configuration profile with the Microsoft Entra SSO extension, including the device_registration key) or just-in-time registration will not work. If your iPhone fleet is supervised corporate hardware this matters less; if you are BYOD-heavy, get the policy deployed ahead of the change.

What I would do this week

  1. Firewall and proxy: confirm intunemaape*.attest.azure.net is allowed and excluded from TLS inspection.
  2. Assignments: find and remove the Calendar, People, and Files companion app assignments, then uninstall from managed devices before December 16.
  3. Push channel: verify the Intune push notification endpoint is reachable from your Windows estate. Test in one tenant, watch the behavior, then believe it.
  4. Rings: draft your deployment ring membership on paper. Wait for GA on deployment plans.
  5. iOS: create the SSO extension policy for just-in-time registration now, so it is in place before web enrollment becomes the default.

Intune's monthly cadence means the service changes under you whether you watch it or not. The difference between this release and most others is that two of the changes have hard dates attached, and one of them (attestation) punishes inattention through Conditional Access — which is the most user-visible way a compliance backend can fail. Skim the rest of 2609 over coffee. Act on these five.

Sources