Update waf-sensitive-data-protection-configure-frontdoor.md

Removing preview disclaimer. Adding CLI and PS references to table.

Author: Miskatonic-Electronic

articles/web-application-firewall/afds/waf-sensitive-data-protection-configure-frontdoor.md

@@ -10,10 +10,6 @@ ms.date: 04/09/2024
 
 # How to mask sensitive data on Azure Web Application Firewall on Azure Front Door (preview)
 
-> [!IMPORTANT]
-> Web Application Firewall on Azure Front Door Sensitive Data Protection is currently in PREVIEW.
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
-
 The Web Application Firewall's (WAF) Log Scrubbing tool helps you remove sensitive data from your WAF logs. It works by using a rules engine that allows you to build custom rules to identify specific portions of a request that contain sensitive data. Once identified, the tool scrubs that information from your logs and replaces it with _*******_.
 
 > [!NOTE]
@@ -39,7 +35,7 @@ For more information, see [What is Azure Web Application Firewall on Azure Front
 
 Use the following information to enable and configure Sensitive Data Protection.
 
-### Portal
+#### [Portal](#tab/browser)
 
 To enable Sensitive Data Protection:
 
@@ -56,6 +52,22 @@ To configure Log Scrubbing rules for Sensitive Data Protection:
 
 Repeat to add more rules.
 
+#### [PowerShell](#tab/powershell)
+
+Use the following Azure PowerShell commands to [create]() and [configure]() Log Scrubbing rules for Sensitive Data Protection:
+
+```azurepowershell
+text
+```
+
+#### [CLI](#tab/cli)
+
+Use the following Command Line Interface commands to [create and configure](cli/azure/network/front-door/waf-policy) Log Scrubbing rules for Sensitive Data Protection:
+
+```CLI
+text
+```
+
 ## Verify Sensitive Data Protection
 
 To verify your Sensitive Data Protection rules, open the Front Door firewall log and search for _******_ in place of the sensitive fields.