My issue with this is that it feels less like a new toy to play with and more like a new worm that is meant to hook me, my workflow, and my data into their silo. I'd like to see better demarcation in windows tooling when it comes to how they're managing user data. Similar to how developers tend to colour code DEV and PROD environments so that they don't accidentally alter PROD. I'd like to see colour coding on microsoft tooling that delineates "local data that is processed locally, and is 100% private" processes from "local data that will be processed in the cloud and possibly stored for training later without you being able to know" processes. The moment data leaves my local network, I assume it is compromised, so having clearer delineation will help me know what tools to avoid.