3 ms·
Nice to see, but unfortunately it's not uncommon for orgs using Outlook/Office to disable Exchange client support and require use of the official clients. It's
by cosmic_cheese 1y ago
Nice to see, but unfortunately it's not uncommon for orgs using Outlook/Office to disable Exchange client support and require use of the official clients. It's highly unlikely and maybe not even possible, but I'd like to see desktop and mobile mail clients implement some kind of workaround.
- stackskipton 1y agoMicrosoft plays wack a mole with 3rd party clients trying to gain access when it's been disabled so it's thankless job for their developers. Not to mention, if I'm disabling your third party access, trying to circumvent is Employee policy violation and you get to talk to HR about why you don't want to play by the rules.
- xigoi 1y ago> Not to mention, if I'm disabling your third party access, trying to circumvent is Employee policy violation and you get to talk to HR about why you don't want to play by the rules. If you want your employees to install malware, maybe you should issue them a company device instead of requiring them to install it on their personal device.
- fsiefken 1y agoI was responsible for third party e-mail clients able to connect to Exchange, it was decided Thunderbird was allowed and support was implemented. It can be done if people are aware of the needs, can implement it securely and can evaluate risks.
- jayknight 1y agoI've been using Outlook Lite on my phone for a long time because I don't want to give my employer admin rights in my phone, and I'm getting messages that that is now deprecated. I guess I'll go back to webmail in Firefox Mobile.