New
#1
What's wrong with just turning the switch off? Unless you don't have Admin rights???
I can do that but I have a bunch of registry tweaks that automatically do stuff after a clean installation so I don't forget to disable settings manually. Of course I can manually do that without a problem, but I don't want to forget to do it so I would prefer a registry edit that I can include with my current list of registry tweaks.
If you have Pro there is a Group Policy to do that: Computer Configuration > Administrative Templates > Windows Components > App Privacy > Let Windows apps make phone calls.
This policy setting specifies whether Windows apps can make phone calls. When Enabled...
You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.....
...If you choose the "Force Deny" option, Windows apps are not allowed to make phone calls and employees in your organization cannot change it.
As you can see Bree answered your question via use of Group Policy.
Good luck.
For those who may want a reg edit for this, I found that this will work:
Code:[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\AppPrivacy] "LetAppsAccessPhone"=dword:00000002
Yes, all Group Policies are just a template for registry changes. Most (with a few notable exceptions) will work in Home as well as Pro. You can download a 'Group Policy Settings Reference Spreadsheet' that lists the registry values used by each policy. The latest I know of is for 1809 HERE.
That confirms your findings, that this applies to 1703 and above, and that there are three other values available for use: LetAppsAccessPhone_UserInControlOfTheseApps, LetAppsAccessPhone_ForceAllowTheseApps and LetAppsAccessPhone_ForceDenyTheseApps .