Merge pull request #231991 from vhorne/fw-net-rule-name-log-ga

Remove network rule name logging from preview

Author: v-shils

.openpublishing.redirection.json

@@ -11503,6 +11503,11 @@
             "redirect_url": "/azure/firewall/ftp-support",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/firewall/firewall-network-rule-logging.md",
+            "redirect_url": "/azure/firewall/firewall-diagnostics",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/security/governance-in-azure.md",
             "redirect_url": "/azure/governance/",

articles/firewall/firewall-network-rule-logging.md

@@ -27,16 +27,6 @@ This article will be updated to reflect the features that are currently in previ
 
 The following features are available in preview.
 
-### Network rule name logging (preview)
-
-With this new feature, the event logs for network rules adds the following attributes:
-   - Policy name
-   - Rule collection group
-   - Rule collection
-   - Rule name 
-
-For more information, see [Azure Firewall network rule name logging (preview)](firewall-network-rule-logging.md).
-
 ### Structured Firewall Logs (preview)
 
 With Structured Firewall Logs, you'll be able to choose to use Resource Specific tables instead of an existing AzureDiagnostics table. Structured Firewall Logs is required for Policy Analytics. This new method helps you with better log querying and is recommended because:

articles/firewall/firewall-preview.md

@@ -112,7 +112,6 @@ Azure Firewall Standard has the following known issues:
 |DNAT rule for allow *any* (*) will SNAT traffic.|If a DNAT rule allows *any* (*) as the Source IP address, then an implicit Network rule matches VNet-VNet traffic and will always SNAT the traffic.|This is a current limitation.|
 |Adding a DNAT rule to a secured virtual hub with a security provider isn't supported.|This results in an asynchronous route for the returning DNAT traffic, which goes to the security provider.|Not supported.|
 | Error encountered when creating more than 2000 rule collections. | The maximal number of NAT/Application or Network rule collections is 2000 (Resource Manager limit). | This is a current limitation. |
-|Unable to see Network Rule Name in Azure Firewall Logs|Azure Firewall network rule log data doesn't show the Rule name for network traffic.|Network rule name logging is in preview. For for information, see [Azure Firewall preview features](firewall-preview.md#network-rule-name-logging-preview).|
 |XFF header in HTTP/S|XFF headers are overwritten with the original source IP address as seen by the firewall. This is applicable for the following use cases:<br>- HTTP requests<br>- HTTPS requests with TLS termination|A fix is being investigated.|
 |Can't upgrade to Premium with Availability Zones in the Southeast Asia region|You can't currently upgrade to Azure Firewall Premium with Availability Zones in the Southeast Asia region.|Deploy a new Premium firewall in Southeast Asia without Availability Zones, or deploy in a region that supports Availability Zones.|
 |Can’t deploy Firewall with Availability Zones with a newly created Public IP address|When you deploy a Firewall with Availability Zones, you can’t use a newly created Public IP address.|First create a new zone redundant Public IP address, then assign this previously created IP address during the Firewall deployment.|

articles/firewall/overview.md

@@ -73,8 +73,6 @@ items:
       href: logs-and-metrics.md
     - name: Structured Firewall Logs
       href: firewall-structured-logs.md
-    - name: Network rule name logging
-      href: firewall-network-rule-logging.md
     - name: Threat intelligence
       href: threat-intel.md
     - name: Policy rule sets