It wasn't an MS product, or supported, and they still took the time to help. I'd be surprised if one didn't find similar responsiveness from at least some of the o365 developers. More often than not, something is "unsupported" not because it doesn't or shouldn't work, but because it doesn't have the dedicated testing resources and in case there is an edge case bug that would be excessively costly to fix (ex: dealing with stupid flexbox issues with the current version of Safari on mac).
In any case, it doesn't matter, the response was a bad, canned response that doesn't take into account the troubleshooting the person reporting it already did.
"Supported" in this context is clearly "we want more money from your despite you already having paid the agreed amount for this product".
[1] https://www.reddit.com/r/linux/comments/60nj67/office_365_on...
I then go and let the person who owns that product know. Half the time, they say "that's not a supported usecase and it's a pain to change, so it's not happening". The other half of the time, they shrug and say "Put a ticket in, if I can fix it easily I will, I'll take a look when I have time".
Unsupported doesn't mean "no", it means "we're not going to invest noticeable effort into it, and it's lowest priority". Easy fixes may happen, but results are not guaranteed.
The charitable hypothesis someone else raised is that there's a bug in how onedrive handles unknown user agents. Neither you nor I have any idea how much effort that will take to fix. You'd hope not a lot but you should never make assumptions about another man's stack. But if it is low effort to fix, Microsoft could get a small land-slide of partial compatibility with one change, which is good PR even if they don't officially support the platforms. It's definitely worth asking nicely rather than giving up and moping about it.