Trying to remove Supervisory Review Policy getting workbench error?

Hi John Wilt,
The behavior you’re seeing is expected with the current public PowerShell surface: Remove-SupervisoryReviewPolicyV2 does not expose a -Workbench parameter, so adding -Workbench $true will always fail with “parameter cannot be found.”

Use only the supported parameters and confirm you’re targeting the right policy identity:

# Verify the policy exists and get the exact Identity/Name
Get-SupervisoryReviewPolicyV2 -Identity "Sensitive information"
# Try removal using supported switches only
Remove-SupervisoryReviewPolicyV2 -Identity "Sensitive information" -ForceDeletion

-ForceDeletion is the supported “force” switch for this cmdlet; -WhatIf can be used to preview.

If you still get the WorkbenchSupervisionPolicyException even with supported syntax, then you’ve hit a backend “workbench” policy type that PowerShell can’t currently modify via this cmdlet, because the required “workbench” flag isn’t exposed in the public cmdlet. In that case, delete/manage it from the Microsoft Purview portal UI (Communication Compliance / policy management) or raise a support request for backend cleanup. Microsoft also notes that PowerShell isn’t supported for creating/managing Communication Compliance policies, which is consistent with “workbench” policies being UI-managed.
this happens
Remove-SupervisoryReviewPolicyV2 does not have -Workbench, so that parameter will always fail. Use only supported syntax (-Identity + optional -ForceDeletion). If the workbench exception still appears, it’s a UI-managed/workbench policy type that PowerShell can’t modify with this cmdlet—delete it from the Purview portal (Communication Compliance) or

Microsoft references

• Remove-SupervisoryReviewPolicyV2 (ExchangePowerShell) [learn.microsoft.com]
• Set-SupervisoryReviewPolicyV2 (ExchangePowerShell) | Microsoft Learn [learn.microsoft.com]
• Create and manage Communication Compliance policies [learn.microsoft.com]
• Trying to remove Supervisory Review Policy getting workbench error? [learn.microsoft.com]

Remove-SupervisoryReviewPolicyV2 does not have a -Workbench parameter. The error message about needing -Workbench $true is coming from the underlying workbench supervision policy logic, but the public cmdlet surface does not expose such a switch, which is why adding -Workbench produces the “parameter cannot be found” error.

The cmdlet supports only these relevant parameters:

Remove-SupervisoryReviewPolicyV2 
    -Identity <PolicyIdParameter>
    [-Confirm]
    [-ForceDeletion]
    [-WhatIf]

To remove the policy, use only the supported parameters, for example:

# Remove by name
Remove-SupervisoryReviewPolicyV2 -Identity "Sensitive information" -ForceDeletion

# Or, if needed, preview first
Remove-SupervisoryReviewPolicyV2 -Identity "Sensitive information" -WhatIf

Ensure the following:

1. The session is connected to Security & Compliance PowerShell (not Exchange Online PowerShell only), because this cmdlet is available only there.
2. The account has the required permissions in the Microsoft Purview compliance portal as described in “Permissions in the Microsoft Purview compliance portal”.
3. The -Identity value exactly matches the policy identity (name or ID) of the supervisory review policy to be removed.

If the workbench-related error persists even when using only supported parameters, the issue is likely backend-side and requires support, since there is no documented -Workbench parameter that can be used from PowerShell.

References:

• Remove-SupervisoryReviewPolicyV2