Don't force the user to run Set-MicrophoneAccess disable -confirm:$false

The syntax should be Set-MicrophoneAccess Disable -Force

Setting a false value on a switch parameter is ugly and not something a beginner would understand. But they should understand -Force esp. with help documentation

Another approach would be for Set-MicrophoneAccess to NOT write any output. Instead, add a -Passthru parameter which gives the user options. This is the model PowerShell uses for many Set commands.

Finally, at least for me, you might need to sleep for a second before calling Get-MicrophoneAccess after setting it. Right now you can querying the registry before it has had a change to update.

Are Your iPhone Apps Spying on You? Here's How to Stay Safe from This Digital Threat
#iPhoneSecurity #AppTracking #PrivacySettings #iOSApps #DataProtection #Cybersecurity #LocationTracking #MicrophoneAccess #CameraAccess #AppPrivacy #iPhone #iOS26 #DigitalPrivacy #VPNUsage

1tak.com/protect-pers...

Since Set-MicrophoneAccess has a High confirmation level, which is fine, you should include a -Force parameter to apply the setting without the confirmation. Otherwise, I can never use this in any type of automation.

Is Your Phone Listening? Privacy Concerns in the Digital Age: A Critical Analysis of Data Collection and User Privacy

#Privacy, #DataCollection, #Smartphones, #Advertising, #UserSecurity, #MicrophoneAccess