A quick note this time over property changes is worth knowing. I was building a new assignment filter and noticed both osVersion and a new operatingSystemVersion property sitting in the list. It turns out that in service release 2608 (week of August 25, 2026) quietly dropped this feature. The property has not disappeared from existing filters and they keep working.
What has actually changed?
Microsoft’s own release note consists of two sentences:
The operatingSystemVersion property in mapping filters is now generally available for managed devices and managed apps... Existing assignments will continue to work without any changes.
Translation: This is not a major change like the ADE Company Portal mess I wrote about. Nothing is taken away from under your nose. But the property drop-down in the filter rule editor now contains the new operatingSystemVersion property, and Microsoft is explicitly calling osVersion deprecated from now on.
What this mean in practice
If you have filters like this in your tenant:
They just keep working. Nobody forces you to migrate.
But the next filter you create should look like this instead:
Same rule editor, same operators -eq, -ge, -le, -startsWith, etc.), same place: Intune → Device → Assignment filters. The difference is under the hood, operatingSystemVersion is designed for actual comparisons of build series, something osVersion has always been a bit fiddly about.
The switch
Nothing urgent. Leave existing osVersion filters alone, they will still work fine. But build your next OS version filter with operatingSystemVersion because that is the one that will actually be invested in in the future.
That is it for now. Until next time. 👋