Since Thursday, several Ubuntu clients running 22.04, 24.04, and 26.04 have been unable to check in with Intune. The local logs report errors such as "Failed to Check in with Intune. Failed to update device inventory" with HTTP 500 responses, along with some 400 and 404 errors. The latest versions of intune-portal and microsoft-identity-broker are installed, and downgrading them did not resolve the problem.
New enrollments either create a device only in Entra ID, or create it in both Entra ID and Intune without inventory information. Entra ID reports the operating system correctly, while Intune shows a blank version or 0.0.0.0. As a result, devices do not receive the expected compliance policy and users are blocked from signing in to Microsoft 365 apps.
The device registration status appears correct locally. However, manually starting a sync or signing in through the Intune portal application immediately produces a registration error. Existing enrolled devices are also failing check-ins and portal-app sign-ins, although users on devices that are still marked compliant can continue using Microsoft 365.
There is an active Microsoft service issue about outdated device inventory and update status information. Has anyone else seen this behavior, found a workaround, or confirmed whether it is related to a recent Intune service or Linux client release?
3 Answers
We’re seeing the same problem across our Ubuntu 24.04 fleet. It appears to be a service-side Intune issue rather than a local package problem. Linux support has been unreliable for us, but we still depend on it for compliance requirements and audits.
Update: The device-inventory error has stopped, but new registrations still fail later with HTTP 400. One possibility is a version mismatch: our tenant appears to be on Intune release 2608 while the newest Linux Intune portal client is still 2607. I can’t find public release notes for 2608, so it may be a backend rollout that the client does not fully support yet.
We’re seeing the same behavior on an EU tenant that is also reporting release 2608.
We’re experiencing the same failures and have already opened a Microsoft support case, but there hasn’t been a useful response yet. Multiple organizations reporting identical errors makes a tenant-wide or service-side problem seem likely.
Are your Linux systems AD-joined as well? We’ve also seen AD-joined Ubuntu machines stop performing their scheduled hourly check-ins, even when registration initially succeeds.