Do not force push bing as the default search engine
Do not force push bing as the default search engine. This is what mal-ware does, not what you expect from your office suite.
Thank you for your feedback on Roadmap ID 59917. Based on customer feedback we’re making some changes to how this feature will roll out
For more information see this article: https://techcommunity.microsoft.com/t5/office-365-blog/update-to-microsoft-search-in-bing-through-office-365-proplus/ba-p/1161030
Just as I was considering buying Office 365 for personal use. As I like the Microsoft ecosystem. But not with this nonsense.
Stop it, Microsoft. You are not doing your users a favor with this. This would only create new methods to circumvent your settings. Isn't Windows 10 enough of forcing Bing down to users? The OS I can pass, but other browsers out of your reach and name? What are you trying to accomplish? Distrust and lawsuits?
This brings to mind all the reasons I resented and avoided Windows 10. Heavy-handed, benefits MS at my expense, and papered over with a bogus rationale.
I suggest you avoid tainting Office with the same kind of moves.
It's been a while since I've seen Microsoft lose miserably in an anti-trust case. I'll bring some popcorn!
If this comes out, I'm dropping every Microsoft product I can easily get rid of. I'll keep using windows and Azure...that's it. Office 365 is getting the kick though, so is Microsoft Edge (just as it's gotten good too), I'm blocking bing in the company firewall, and other things I can't think of off the top of my head.
For me the biggest problem is the *horrifying* practice of telling corporate users that mixing important internal documents with their internet searching is ok.
The forced install of an extension is a big number 2 though. In both senses of the word.
If the users in my organizations want to use Bing, they will choose to use it. Forcibly changing their browser settings puts Bing and Office in the same category as malware, and reinforces the idea that Bing is a horrible product that someone would only use if forced.
You know how you couldn't force people to use Edge? Same applies here. Either make Bing into a good product or concede defeat. Forcing it on people has the opposite effect than your intention.
If you still trust Microsoft after this, you're nuts.
Eugene Ng commented
An Opt in option must be implemented.
and you need admin to remove it...
Software should not forcibly change the settings of other company's software. That's malware. No ifs, ands, or buts.
Genuinely hoping the EU jumps on this fast, Google blocks the extension, and maybe someone at Microsoft can introduce some sanity here. This strategy is exactly the definition of browser hijacking.
This will cause huge backlash amongst my entire staff. DO NOT DO THIS!
This will literally cause hundreds of help desk calls to get search back... please DO NOT do this.
This would cause more problem than provide solutions for us. I would suggest reconsidering this change.
Chris Eaton commented
I can't even imagine what Microsoft is thinking here, but straight up hijacking my browser is a 90s era shady move that I thought as a company you had grown out of. It's deeply disappointing coming from a Microsoft that has made such great strides and become so much easier to work with over the years.
This needs to be killed immediately and whoever approved it asked some questions about just what they are thinking.
Micheal Espinola commented
Forcing anything regarding how people browse and search the web is a historically bad idea. You should know better than this. Pushing this will do nothing but sow confusion and ultimately hate.
Don't interfere with 3rd party software. Doing so will cause Office 365 to be classified as malware, and I will NOT subscribe to malware.
Throwing my hat in the ring here, terrible idea. I want to add this nugget:
The patch/"feature" starts rolling out in February. The nice simple button in Intune to disable this "feature" wont be available till late-February, as per MS documentation.
So the only way to prevent this from happening to my tenant is to build and test an XML based deployment to replace my existing Configuration Designer deployment.
Poor form on many levels.
Jonathan K Myers commented
I work for a MSP/CSP. We service 100s of cloud-only customers. They don't have Intune, a classic AD domain for Group Policy, or any other management tools.
If you continue down this path, me and the rest of the support staff here are going to have Very Bad Days.
This smacks of a Microsoft we used to know, one we wanted to avoid. Kill this change now.