Merge pull request #237449 from vhorne/fw-pa-ga

Start policy analytics GA

Author: JamesJBarnett

articles/firewall/firewall-preview.md

@@ -38,10 +38,6 @@ With Structured Firewall Logs, you'll be able to choose to use Resource Specific
 
 For more information, see [Azure Structured Firewall Logs (preview)](firewall-structured-logs.md).
 
-### Policy Analytics (preview)
-
-Policy Analytics provides insights, centralized visibility, and control to Azure Firewall. IT teams today are challenged to keep Firewall rules up to date, manage existing rules, and remove unused rules. Any accidental rule updates can lead to a significant downtime for IT teams.
-
 ### Explicit proxy (preview)
 
 With the Azure Firewall Explicit proxy set on the outbound path, you can configure a proxy setting on the sending application (such as a web browser) with Azure Firewall configured as the proxy. As a result, traffic from a sending application goes to the firewall's private IP address, and therefore egresses directly from the firewall without using a user defined route (UDR).

articles/firewall/policy-analytics.md

@@ -1,21 +1,17 @@
 ---
-title: Azure Firewall Policy Analytics (preview)
-description: Learn about Azure Firewall Policy Analytics (preview)
+title: Azure Firewall Policy Analytics
+description: Learn about Azure Firewall Policy Analytics
 services: firewall
 author: vhorne
 ms.service: firewall
 ms.topic: conceptual
-ms.date: 01/26/2023
+ms.date: 05/09/2023
 ms.author: victorh
 ---
 
-# Azure Firewall Policy Analytics (preview)
+# Azure Firewall Policy Analytics
 
 
-> [!IMPORTANT]
-> This feature 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.
-
 Policy Analytics provides insights, centralized visibility, and control to Azure Firewall. IT teams today are challenged to keep Firewall rules up to date, manage existing rules, and remove unused rules. Any accidental rule updates can lead to a significant downtime for IT teams. 
 
 For large, geographically dispersed organizations, manually managing Firewall rules and policies is a complex and sometimes  error-prone process. The new Policy Analytics feature is the answer to this common challenge faced by IT teams.
@@ -26,7 +22,7 @@ You can now refine and update Firewall rules and policies with confidence in jus
 
 ## Pricing
 
-Enabling Policy Analytics on a Firewall Policy associated with a single firewall is billed per policy as described on the [Azure Firewall Manager pricing](https://azure.microsoft.com/pricing/details/firewall-manager/) page. Enabling Policy Analytics on a Firewall Policy associated with more than one firewall is offered at no added cost.
+New pricing for policy analytics is now in effect. See the [Azure Firewall Manager pricing](https://azure.microsoft.com/pricing/details/firewall-manager/) page for the latest pricing details.
 
 ## Key Policy Analytics features
 
@@ -35,48 +31,23 @@ Enabling Policy Analytics on a Firewall Policy associated with a single firewall
 - **Traffic flow analysis**: Maps traffic flow to rules by identifying top traffic flows and enabling an integrated experience.
 - **Single Rule analysis**: Analyzes a single rule to learn what traffic hits that rule to refine the access it provides and improve the overall security posture.
 
-## Prerequisites
-
-- An Azure Firewall Standard or Premium
-- An Azure Firewall Standard or Premium policy attached to the Firewall
-- The [Azure Firewall network rule name logging (preview)](firewall-network-rule-logging.md) must be enabled to view network rules analysis.
-- The [Azure Structured Firewall Logs (preview)](firewall-structured-logs.md) must be enabled on Firewall Standard or Premium.
-
 
 ## Enable Policy Analytics
 
 Policy analytics starts monitoring the flows in the DNAT, Network, and Application rule analysis only after you enable the feature. It can't analyze rules hit before the feature is enabled.  
 
-### Firewall with no diagnostics settings configured
-
 
-1.	Once all prerequisites are met, select **Policy analytics (preview)** in the table of contents. 
+1.	Select **Policy analytics** in the table of contents. 
 2. Next, select **Configure Workspaces**.
 3. In the pane that opens, select the **Enable Policy Analytics** checkbox. 
 4. Next, choose a log analytics workspace. The log analytics workspace should be the same as the Firewall attached to the policy.
 5. Select **Save** after you choose the log analytics workspace.
-6. Go to the Firewall attached to the policy and enter the **Diagnostic settings** page. You'll see the **FirewallPolicySetting** added there as part of the policy analytics feature.
-7. Select **Edit Setting**, and ensure the **Resource specific** toggle is checked, and the highlighted tables are checked. In the previous example, all logs are written to the log analytics workspace.
-
-### Firewall with Diagnostics settings already configured
-
-1. Ensure that the Firewall attached to the policy is logging to **Resource Specific** tables, and that the following three tables are also selected:
-   - AZFWApplicationRuleAggregation
-   - AZFWNetworkRuleAggregation
-   - AZFWNatRuleAggregation
-2. Next, select **Policy Analytics (preview)** in the table of contents. Once inside the feature, select **Configure Workspaces**. 
-3. Now, select **Enable Policy Analytics**.
-4. Next, choose a log analytics workspace. The log analytics workspace should be the same as the Firewall attached to the policy. 
-5. Select **Save** after you choose the log analytics workspace.
-
-   During the save process, you might see the following error message: **Failed to update Diagnostic Settings**
-
-   You can disregard this error message if the policy was successfully updated.
 
 > [!TIP]
 > Policy Analytics has a dependency on both Log Analytics and Azure Firewall resource specific logging. Verify the Firewall is configured appropriately or follow the previous instructions. Be aware that logs take 60 minutes to appear after enabling them for the first time. This is because logs are aggregated in the backend every hour. You can check logs are configured appropriately by running a log analytics query on the resource specific tables such as **AZFWNetworkRuleAggregation**, **AZFWApplicationRuleAggregation**, and **AZFWNatRuleAggregation**.
 
 ## Next steps
 
 
-- To learn more about Azure Firewall logs and metrics, see [Azure Firewall logs and metrics](logs-and-metrics.md).
+- To learn more about Azure Firewall logs and metrics, see [Azure Firewall logs and metrics](logs-and-metrics.md).
+- To learn more about Azure Firewall structured logs, see [Azure Firewall structured logs](firewall-structured-logs.md).