The entry is listed as In development. Microsoft estimates a preview in October 2026 and general availability in November 2026, for the Worldwide (Standard Multi-Tenant) cloud.
What Microsoft says Update Repair will do
According to Microsoft's roadmap description, Update Repair gives admins four things:
- Detection: It flags Windows devices running Microsoft 365 Apps that are behind on updates or having update problems.
- Triage: Admins can see each device's status and a recommended action in the Microsoft 365 Apps admin center.
- Remote fix: Admins can start an Online Repair remotely, but only on eligible devices.
- Manual guidance: Devices that need attention but can't be repaired remotely get step-by-step remediation guidance instead.
The key detail is what the repair actually does. Microsoft says it reinstalls Microsoft 365 Apps using the latest available build for the device's configured update channel. It doesn't switch channels or let you pick a version. The channel the device is already set to decides which build gets installed. A device on Monthly Enterprise Channel stays there and lands on that channel's current build.
Summary: Update Repair is meant to go from detection to action in one place. Remote repair is promised only for eligible devices. Everything else gets manual guidance, so this isn't a fix-everything button.
Why Online Repair is the logical tool
Anyone who has walked a user through Online Repair over the phone will see the appeal of starting it from a console. Microsoft's own support guidance describes the local version: in the repair dialog, users select Online Repair > Repair to make sure everything gets fixed, and a faster Quick Repair option is also offered. A help guide from Louisville Geek sums up the difference: Online Repair reinstalls Microsoft 365 completely, needs internet and can take 10–30 minutes. That timing comes from a third-party guide, not a Microsoft figure for the new remote feature.
Microsoft's existing cloud update documentation already treats online repair as a way to bring an installation up to date. In explaining why a device in a later rollout wave can show as completed early, Microsoft says this can happen when the device is already up to date when it onboards to cloud update, when an online repair updates the installation, or when the Office Deployment Tool changes the installation and triggers an update. Update Repair appears to turn that side effect into a deliberate admin action. That's our reading of the documentation, not something Microsoft has said about the feature.
How it fits into the admin center
Update Repair is labeled as part of Inventory, which is already the admin center's main view of Office across a fleet. Microsoft's Inventory documentation says it shows the state of Office installations, including devices running older, unsupported builds. Admins can drill into hardware, OS version and build, installed Office apps, the build's release date, update channel, COM add-ins, and the last signed-in user.
The admin center also has health tooling for cloud update. Microsoft documents an Issues tab where devices are grouped by issue with the number of affected devices, the error code, and a description, and selecting an issue opens a details pane that lists impacted devices, offers an export, and links to the Office update troubleshooting article. Until now, those tools mostly showed you the problem and left you to fix it. Update Repair is Microsoft's first roadmap commitment to fixing it from the same console.
Some Inventory behaviors are worth knowing before preview starts:
- Devices appear only after Office is used. Once Inventory is set up, devices show up within an hour after a user launches an app such as Word or Excel.
- Heartbeats drive freshness. Devices check in once a day, and a device that's silent for 30 days is removed from inventory by default. You can extend that interval in Settings.
- Channel reporting lags. Inventory reports the channel based on the installed build. If a channel change is still in progress, it keeps showing the old channel. Since Update Repair installs the latest build for the configured channel, check what that channel actually is before you trigger a repair.
- Missing devices can't be repaired from the console. One admin on Microsoft Q&A reported only 258 devices in cloud update against 490 Windows devices in Intune. The answer explained that inventory is driven by device heartbeats and Cloud Update eligibility; there is no manual "add device" or on-demand rescan capability. That answer was AI-generated on Microsoft's Q&A site, but it matches the heartbeat behavior in Microsoft's documentation.
Summary: Update Repair can only reach devices Inventory can see. If your Inventory numbers don't match your real fleet, sort that out first.
Who's likely eligible, and what's still unknown
The roadmap entry doesn't list licensing or role requirements for Update Repair. The current Inventory requirements are a reasonable baseline, though they don't guarantee anything about the new feature:
| Area | Current Inventory requirement (Microsoft Learn) |
|---|---|
| Recommended role | Office Apps Administrator (Security Administrator and Global Administrator also listed) |
| Limited role | Global Reader is supported but lacks some features, such as cloud update |
| Licensing | Microsoft 365 A3/A5, Business Standard/Premium, Office 365 E3/E5, Microsoft 365 E3/E5 |
| Unsupported clouds | 21Vianet, GCC, GCC High, DoD |
| Platforms | Supported Microsoft 365 Apps on Windows 10/11 and supported Windows Server |
Don't assume the Inventory roles above will automatically be allowed to run remote repairs. Microsoft hasn't said which roles will authorize Update Repair. The roadmap lists "Desktop" and "Web" as platforms, but the described target is Windows devices. "Web" almost certainly means the admin center, not repairing Office for the web.
The roadmap description also leaves out what admins will most want to know:
- What makes a device "eligible" for remote repair
- Whether users are warned, interrupted, or forced to close Office apps
- How long a remote repair takes, and how much bandwidth and disk space it needs
- Whether local settings and COM add-ins survive the reinstall
- Whether repairs can be batched, scheduled, or targeted by Entra group
- Whether there's an audit trail or a way to roll back
Expect those answers to come with preview documentation. Until then, don't assume any of them.
Our take
This is a sensible, overdue feature. The admin center has long been good at telling you which devices are stale. Fixing them meant remote sessions, scripts, or another trip through the Office Deployment Tool. A built-in path from detection to repair could save help desks real time, especially for devices that stopped updating with no obvious cause.
Keep two things in mind, though. An Online Repair is a reinstall, not a quick patch, and reinstalls on production desktops can annoy users and break fragile add-in setups. And roadmap dates are estimates: Microsoft says on the roadmap that all information is subject to change and that items can be postponed or cancelled.
What to do now: Make sure Inventory is set up and your device counts are close to your real fleet. Check which update channel each device group is actually configured for. Pick a few low-risk pilot devices so you can see how Update Repair behaves when preview reaches your tenant.