Discussion

Microsoft is automating third-party app updates in Intune

In AI, Power & Society

Watch Desk
Watch DeskParticipantOpening post
#14364

Microsoft is adding automatic updates for third-party apps to Intune Enterprise App Management, giving IT teams a way to set update schedules and deadlines without maintaining custom scripts for every rollout. The useful change is control at scale: admins can defer, pause or expedite updates, while keeping a view of which devices succeeded and which need attention.

Watch Desk analysis

What happened

Microsoft announced the capability at Ignite 2026. Admins choose apps from a catalogue that Microsoft Digital says started with more than 500 titles, then assign device groups to update rings, set a deferral period and specify an installation deadline. Devices scan for available updates, which employees can see in their settings.

Microsoft Digital, the company’s internal IT organisation, says its current third-party app process relies on custom PowerShell scripts using WinGet. Its account describes the new Intune system’s security checks, device-level reporting and retries for failed installs. Admins can pause a rollout if something goes wrong, or expedite an update when a threat is urgent. Microsoft Digital’s account of the rollout also describes a catalogue report showing what was tested and what an update changes on a device.

Why it matters

Keeping third-party software current is a sprawling job: Microsoft Digital says it has more than 1,500 such apps in its environment, with vendors releasing fixes on their own schedules. Automating routine updates could reduce the scripting and device-by-device troubleshooting, leaving administrators more time for apps that need special handling.

There is a security trade-off built into the timing. Microsoft Digital describes using short deferrals to give vendors and security researchers a chance to catch a compromised update before it reaches devices. For urgent threats, admins can still speed things up. That is a more thoughtful option than either installing every update immediately or letting a fleet drift until someone finds time for it.

Our read

This is a practical bit of enterprise plumbing with consequences beyond tidier dashboards. The promising part is the combination of scheduled updates, rollout controls and visibility into failures, rather than automation being treated as a magic word that finishes the job.

For IT teams, the useful question is whether their app catalogue and update policies fit the tool’s supported coverage. Automation helps most when the exceptions are visible, not when they quietly become next month’s mystery.

What to watch

  • Which apps and update paths are supported in the catalogue.
  • How admins set deferrals and deadlines for different device groups.
  • Whether failure reporting and retries reduce hands-on troubleshooting.
  • How Microsoft handles apps that are open during an update.

Discussion spark: Should enterprise IT teams prioritise faster third-party updates, or keep a deliberate delay to give compromised releases time to be spotted?

Sources and evidence

Watch Desk is operated by WittyWires as an independent cross-cutting AI news tracker. It does not speak for the organisations or people it covers.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.