Sure, Edge can be configured by domain policies and that is easy too. For example disallowing https exceptions is a popular recent policy (that gets reverted pretty quickly).
Sure, Edge can be configured by domain policies and that is easy too. For example disallowing https exceptions is a popular recent policy (that gets reverted pretty quickly).
Especially for any web shop... Firefox is even less relevant than Microsoft now and forcing it as a primary internal browser is a great way to alienate your company from end user experiences.
It already has, sadly.
> Can you centrally administrate Google accounts? Because employees certainly aren't allowed to use their privat ones.
Yes, definitely. For non Microsoft shops, Google is a very common option (eg academia).
I use chrome for important stuff for that reason.
From personal experience I know that Teams definitely has some Firefox-only bugs.
Outside of corps ideologically opposed to using Office, like IBM and Oracle, I've almost never seen anybody that didn't run on Outlook. At least since Notes became abandonware anyway.
(edit: to be clear, wasn't trying to be snarky. Genuinely surprised. Thought Microsoft intranets were a thing of legacy dinosaur companies, didn't know that modern enterprises still did that. But I don't work in enterprise, only in small biz, where nobody can afford dedicated sys admins and everything is in the cloud. From what I hear though, the UX of Outlook these days is better than Gmail and gcal (which isn't saying much, I know). Might be worth trying again someday...)
In the small dev world it's kinda the opposite. Linuxy servers beget Mac dev machines, so AD is mostly out, leaving Apple enterprise stuff (shitty) or Google (OK, but nowhere near as powerful as Microsoft).
GDocs becomes the lowest common denominator and many people don't have Word anymore. Data is either cloud native (json, csv) or else imported into Gsheets.
I suspect some of this is due to the modern educational pipeline too, with gsuite (or Google Workspace, or whatever it's called these days) producing a generation of young workers who grew up on that stuff. It's caused quite a generation gap at my current workplace, where the older workers use Microsoft and the younger ones use Google and stuff keeps getting converted back and forth. And once in a while someone sends a PDF and both sides go nooooo...
Also, I'd be willing to believe your average Google Workspace, preconfigured by Google, is more secure out of the box than your average Microsoft LAN administered by somebody who once took a certification course twenty years ago.
But when something breaks on self-hosted Microsoft stuff, at least you can hire someone to fix it. When something breaks on Google Workspace, hey, it's a free vacation day for the whole staff!
Sounds like they ported over all the best features from Skype! ;)
Lack of corp support is one of the things that harmed FF from what I saw. Until a few years ago it was not as easy to control FF via group policy¹ as it was Chrome, so FF didn't get a look in. Telling infrastructure managers “but you can do X instead and it is just as easy or easier” would fall on deaf ears because while as convenient in isolation it is still something different instead of integrating with what they did for everything else they permitted on their user machine builds.
¹ This has changed since, but too late.