Try talking to your users instead.
> The more users software has, less skills they have in average to accurately report any issues.
No amount of telemetry will solve that.
It’s easy to argue that if you are a PowerShell user or developer you benefit from no telemetry, but it’s hard to argue that you benefit from the tool you use being sidelined or defunded because corporate thinks nobody uses it. “Talk to your users” doesn’t solve this because there are millions of computers running scripts and no way to know who they are or contact them even if you could contact that many people, and they would not remember how often they launched it.
https://learn.microsoft.com/en-us/powershell/module/microsof...
To take your logic to its extreme, you have a disease and are prescribed pills, and the pharmaceutical company says "we will track when you take the pills - unless you don't want us to?" and you would prefer the researchers get shut down for not knowing whether anyone actually takes the pills, and an unlimited number of people die from treatable diseases that don't get cured.
The connection is clear if your salary doesn't require you to not understand it.
Developers don't opt-in to telemetry? Maybe it's because they don't want to enable that telemetry, your experiments be damned.
Use proper engineering to demonstrate that your scripts work instead of demanding that users be your free software test team.
This telemetry is not about demonstrating that scripts work, as I have said to you multiple times.