The hardest thing to adjust to is the product pipeline moving from "let's fix the issues the most users face" to "we need to fix these issues, for this important customer".
Product led organizations often have a _very_ hard time adjusting to this, I personally recommend you carve out specific product and engineering teams for your effort, as getting into the backlog of consumer oriented product teams is going to completely torpedo any chance you have of closing big deals that depend on product changes. And just about every big deal is going to require changes at first, you can't fool yourself into thinking you'll get to a point where that's not true any time soon. You really won't, and if you have goals that assume you will, you're already set to fail.
However, I would also venture that prioritizing "power-user" requests may end up helping your enterprise product, given the overlap between IT teams and power users. There is a lot of functionality that was lost in the interests of simplification. Even some of the appearance - such as the awful "let's add bouncy curves to every UI element" in your latest rollout - can have a very solid impact on how people perceive your product. Enterprise is a different sensibility than average user.
Speaking of working, in my experience, there is a considerable number of enterprise websites and web applications out there that don't work well or not at all(!) in Firefox. (Prime example: outlook.office365.com hasn't worked for me in years – I always end up in a redirect loop unless I clear all cookies, and I heard the same story from others.) Needless to say, such issues might cause new Firefox users to switch back to Chrome/Edge rather quickly. (A friend of mine recently stopped using Firefox for his work because of that.)
Any idea what to do about this? Of course with AI one could go as far as adding a "Report this site doesn't work in Firefox" button that magically sends a report (+ suggested fix) to the people operating the website/app. But I can think of dozens of reasons why this wouldn't work well at all (let alone be a good idea) in practice…
Not sure if you're aware, but this button does actually exist in the help menu, at least for getting a public report filed. I looked through our tracker and didn't find any report similar to yours though (..and Office365 has a ton of webcompat bugs on file...), so I'd recommend you and "others" to actually file those bugs.
Finding and fixing those bugs in websites (unless they're behind a login that you can't easily sign up for) typically isn't the issue, but getting ahold of the site owner sometimes is.
If we can't get ahold of the website operator, or they're slow or unwilling to fix it, we can ship compatibility shims in the browser.
Take a look at about:compat to get some idea.
Wow, I feel very stupid now. Thanks so much, I'll give it a try!
Just a note: While I cannot speak for the past years, it seems like the website works for me using Firefox - without clearing any cookies. Tested on NixOS + Windows
A centralised admin platform that integrates easily with others is of course also great. Currently Chrome is a bit of a mess to manage in enterprise with a mix of more oldschool GPO admx style policies (which are very detailed and robust however) and the cloud managed Google Workspace stuff.