If to use the feature you are explicitly asked to turn it on, with an option to view a privacy policy, that is “blatantly obvious”. It isn’t hidden or buried under a dozen other settings when you install PowerPoint, it’s done at time of use.
How, exactly, would you want it to be more obvious? A big red box every time the feature is mentioned in the help site? Be realistic here; in terms of user consent this is perfectly fine.
I disagree.
> How, exactly, would you want it to be more obvious? A big red box every time the feature is mentioned in the help site?
Yes, more or less. I would be perfectly happy with a single red box at the top that says this feature sends the contents of your slide to Microsoft. I am not okay with linking to a privacy policy that nobody's going to read and pretending that that's informed consent.
As a user I'd like the ability to opt-in/out of this. I much prefer a privacy policy that captures all of it for the app. Otherwise, I have red boxes showing up non-stop using most apps. Can you imagine the sheer number of red boxes you'd get for Netflix the first few times you use it!
Of course it's impractical in today's environment, but I think we'd be in a much better place if we'd established early on the idea that a piece of software that massively violates your privacy (which is to say, all of them, nowadays) comes laden with a terrifying number of red boxes when you read its privacy policy.
[1] https://slidehunter.com/how-to-automatically-design-slides-w...
In short, I pretty strongly disagree. I think that if you had a hundred users look at that page or click through enabling the feature, and then asked afterwards how many of them thought that the feature was going to send their slides to Microsoft, at least 50 of them would be very surprised.