Updates from reviews

Author: edarzins

Diff for: content/nginxaas-azure/app-protect/_index.md

@@ -1,5 +1,5 @@
 ---
-title: NGINX App Protect WAF (Preview)
+title: NGINX App Protect WAF
 weight: 200
 url: /nginxaas/azure/app-protect/
 ---

Diff for: content/nginxaas-azure/app-protect/configure-waf.md

@@ -114,15 +114,18 @@ To create a custom security policy in the Azure Portal:
 3. Select **Custom Policies**
 4. Select **Add Custom Security Policy** to open the policy editor
 
-In the policy editor, enter the **Name**, **File path**, your policy content, and then select **Save**.
+In the policy editor, enter the **Name**, **File path**, your policy content, and then select **Save**. The **File path** is optional and will default to the policy **Name** with a ".json" extension if not specified. The **Name** must have a ".json" extension.
 
    {{< img src="nginxaas-azure/custom-policy-editor.png" alt="NGINXaaS Custom Policy Editor." >}}
 
 After your policy has been saved, you can then reference it in your NGINX configuration the same as you did for precompiled policies. For more information on policy configuration and syntax, refer to the NGINX App Protect [configuration guide](https://docs.nginx.com/nginx-app-protect-waf/v5/configuration-guide/configuration/).
 
 {{<note>}}The **name** field within the security policy must be unique among the policies referenced in your NGINX configuration.{{</note>}}
-{{<note>}}Referencing both custom and precompiled policies in you NGINX configuration is not supported at this time.{{</note>}}
+{{<note>}}Referencing both custom and precompiled policies in your NGINX configuration is not supported at this time. See the [Known issues]({{< ref "/nginxaas-azure/known-issues.md" >}}) for a workaround for this limitation.{{</note>}}
 
+The **Custom Policies** tab shows the status of your custom policies (Compilation and Application Status). Custom Policies are automatically compiled when created or modified. Policies that are applied to the NGINX configuration cannot be deleted until they are first removed from the configuration. 
+
+   {{< img src="nginxaas-azure/custom-policies.png" alt="NGINXaaS Custom Policies." >}}
 
 ## What's next
 

Diff for: content/nginxaas-azure/app-protect/enable-waf.md

@@ -14,7 +14,7 @@ This guide explains how to enable F5 NGINX App Protect WAF on a F5 NGINX as a Se
 ## Before you start
 - NGINX App Protect WAF can only be enabled on NGINXaaS for Azure deployments with the **Standard v2** [plan]({{< ref "/nginxaas-azure/billing/overview.md" >}})
 
-## Enable NGINX App Protect (Preview)
+## Enable NGINX App Protect
 NGINX App Protect is disabled by default and needs to be explicitly enabled on an NGINXaaS deployment. Follow these steps:
 
 ### Using the Microsoft Azure Portal

Diff for: content/nginxaas-azure/changelog.md

@@ -13,6 +13,14 @@ To see a list of currently active issues, visit the [Known issues]({{< ref "/ngi
 
 To review older entries, visit the [Changelog archive]({{< ref "/nginxaas-azure/changelog-archive" >}}) section.
 
+## April 17, 2025
+
+### What's New
+
+- {{% icon-feature %}} **NGINX App Protect WAF is now generally available**
+
+  NGINX App Protect WAF is now generally available and is no longer a Preview feature and will therefore be billed as specified in the [Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/f5-networks.f5-nginx-for-azure?tab=PlansAndPrice)
+
 ## March 31, 2025
 
 ### What's New

Diff for: content/nginxaas-azure/known-issues.md

@@ -9,6 +9,12 @@ url: /nginxaas/azure/known-issues/
 
 List of known issues in the latest release of F5 NGINX as a Service for Azure (NGINXaaS).
 
+### {{% icon-bug %}} Custom and precompiled security policies cannot both be referenced in an NGINX configuration 
+
+When using NGINX App Protect WAF, you can only reference default or custom security policies in your NGINX configuration, not both.
+
+**Workaround**: Make a copy of the default policy you want to use, then add it as a custom policy with a different name.  
+
 ### {{% icon-bug %}} Terraform fails to apply due to validation errors, but creates "Failed" resources in Azure (ID-4424)
 
 Some validation errors are caught later in the creation process, and can leave behind "Failed" resources in Azure. An example initial failure might look like: