One potential workaround - don't sign on as a permie employee, instead arrange to work as a contractor where you bring your own tools instead of using whatever

One potential workaround - don't sign on as a permie employee, instead arrange to work as a contractor where you bring your own tools instead of using whatever standard machine the client would otherwise give you. You may be able to bring your own linux laptop and configure it to work with the client's systems. Downsides of this approach: what you are doing is not officially supported by the client's infra/network/vpn/bureaucracy, so if you run into trouble getting it to work or it breaks after the client changes something you will not get any help, so you are just wasting your own time & money or the client's time and money by going against the grain and doing something the client regards as unusual and unsupported. In many businesses the client may require that contractors do not use their own tools and instead use machines supplied by the client, so this isn't even an option. Also, the whole contractor <-> permie tradeoff (no benefits, no job security, but maybe higher pay - depending what kind of a labour market you're in). I have seen highly competent contractors successfully use linux in a huge old conservative bureaucracy with lots of legacy tech & half-broken network infrastructure that only officially supports windows & half-heartedly supports mac. But the starting position would be that you're the kind of person who can single-handedly triage and fix random network/vpn/authentication issues, perhaps by writing or patching software as necessary, and that you're happy to spend your own unbillable time on this.