Admin may have seen status cards displaying "Unknown" instead of the expected summary counts in Intune admin center.
- Status
- Wiederhergestellt
- Funktion
- Microsoft Intune
- Region
- Nicht angegeben (alle Regionen)
- Beginn
- 07.10.2026, 01:17 Uhr
- Behoben
- 13.10.2026, 23:51 Uhr
- Dauer
- 6 Tage 22 Std.
Mehr Informationen
Admins were impacted when accessing the Home, Apps, Devices, and Troubleshooting Blades.
As a workaround, admins could have clicked the "Unknown" status, which allowed access to the data.
Betroffen
This issue might have affected any admin who accessed the Intune admin center from Home, Apps, Devices, and Troubleshooting Blades.
Ursache
An incorrectly scoped Microsoft Graph flight changed the response format for batch requests across production. Some Intune UX experiences (Home, Apps, Devices, Troubleshooting) rely on the previous Base64-encoded behavior and couldn't parse the JSON response, resulting in status cards displaying "Unknown."
Next steps:
- We're further analyzing the offending misconfigured service update to help us improve our pre-deployment testing and validation processes.
This is the final update for the event.
Abschluss
Following our change reversion process, our internal service telemetry has verified that the impact has been remediated.
Verlauf
Alle Updates von Microsoft zu dieser Meldung, das neuste zuoberst.
- 13.10.2026, 23:58 Uhr
Following our change reversion process, our internal service telemetry has verified that the impact has been remediated.
- 13.10.2026, 23:00 Uhr
We've identified a recent misconfigured service update that is producing unexpected status card displays for admins in the Intune admin center. We're conducting our change reversion process to remove the offending change and to remediate the impact.
- 13.10.2026, 21:27 Uhr
We've identified an issue that is preventing expected status cards for admins accessing the Home and Troubleshooting Blades in the Intune admin center. We're analyzing system logging and recent updates to the service, as we isolate the source for this event and determine our next troubleshooting steps for remediating the impact.