Microsoft.PowerShell.LocalAccounts confirm impact
the confirm impact on the Remove* cmdlets in the Microsoft.PowerShell.LocalAccounts module is not set to high.
I think removing a local group or user (especially when the pipeline is involved) should have Confirm impact set to high to prevent accidental mass deletion
We considered marking these cmdlets with ConfirmImpact = High. The problem is we've gotten a lot of negative feedback around the experience for ConfirmImpact = high which requires the user to specify -Confirm:$false for every invocation of the cmdlet. You have to specify it exactly as -Confirm:$false - this syntax unfortunately trips up / confuses a lot of users. So while we agree in principle with the suggestion, we don't like the resulting experience. We've been increasingly judicious with our usage of ConfirmImpact and only add it in extreme cases.
It would be great to have a separate UV item to improve the experience for ConfirmImpact.