One of my employers used o365 with fairly draconian rules. Trying to log in with my free browser of choice yields the lovely, monopolist message:<p>>You can't get there from here
You cannot access the resource from this browser on your device. You need to use Chrome or Edge.<p>> Error Code: 530001
>App name: Office 365 Exchange Online<p>Why? It's a static website in accessibility mode and the "request desktop site" slider works as intended. What reason could be behind this? Didn't the EU literally fine Microsoft for exactly this sort of behaviour?
I have a strong feeling this is a setting your org has enabled. You reference draconian rules, talk to your admins.<p>I can see how this feature might be useful, eg disallowing IE6. But that's taken to the next level of restriction
This is because of "chrome enterprise" more than likely. Chrome is easier to manage with enterprise policies and mdm.<p>Also, I hope that isn't your personal device because you just made it a work device and lost any claim to privacy you could have otherwise had (US).Your work is not your family or friend, they will act in hostility when it benefits them and using a personal device for work is against your interest. At least get a cheap android phone for work if they require byod usage.<p>But to help with your problem, firefox on mobile has extensions one of which is user agent changer which lets you set a chrome agent.
If it requires U2F to login, I don't think firefox for android supports it. Nine (android email client) also can't do google 2FA with firefox, asks for chrome or samsung browser.<p>Add it to the list of things the old Firefox android browser had that current one doesn't <a href="https://github.com/mozilla-mobile/fenix/issues/1340">https://github.com/mozilla-mobile/fenix/issues/1340</a>
Could this be related to Third-Party Cookies and Tracking Protection? I think that's turned "on" by default on Firefox, no?<p>Some Microsoft products refuse to work on Safari and Firefox for me unless you disable the protection.<p>It's not really well documented, I found this info in some forum posts.
Seems to still work for me, but given the nature of Software-as-a-Service.. it's possible that there is a feature that is being A/B tested.<p>It's also possible, as others have mentioned, that this is a policy enacted by your admins.<p>I would be interested to hear why this is the case from their perspective.