[hirsin]

Yup - Microsoft employee here but unaffiliated with that team. I love it, frankly. For large orgs that have thousands of SharePoint sites going back years(1), it's pretty fantastic. What would have been a dozen emails across two days to find some random doc explaining how to do something is now five to ten minutes of poking things into Bing.

1. TAM for this may be on the order of triple digits only for all I know, but if you work in a 50k+ knowledge worker org it's great.

[wernercd]

Customer here... and, frankly, I hate it...

Now, not only is Microsoft weaponizing windows updates... they are weaponizing Office to push services without being asked?

I detest these dark patterns and decisions.

It's amazing how a company can make so many good decisions (IE: Open Source direction of .net) while also making such detestable decisions.

[jbreiding]

This may be difficult to grasp. But likely where you are seeing this feature is in a corporate setting where you are the "end user", not the paying customer. The corporate entity that is making use of this feature is who you should be protesting the use to, not Microsoft.

[wernercd]

There's nothing "difficult to grasp" - these are shit decisions and dark patterns.

A feature that's MAYBE useful in a corporate setting to a hand full of people should not be a default defacto setting forced upon EVERYONE.

The issue isn't the feature... it's the default settings that enable invasive features.

[w0m]

is it the default to everyone or just o365 customers with intranet search content indexed?