Merge pull request #302465 from sujamiya/fix/policy-overview-doc

Update Azure Firewall Manager policy overview documentation

Author: prmerger-automator[bot]

articles/firewall-manager/policy-overview.md

@@ -1,12 +1,12 @@
 ---
 title: Azure Firewall Manager policy overview
 description: Learn about Azure Firewall Manager policies.
-author: duongau
+author: sujamiya
 ms.service: azure-firewall-manager
 services: firewall-manager
 ms.topic: concept-article
-ms.date: 03/06/2024
-ms.author: duau
+ms.date: 07/09/2025
+ms.author: sujamiya
 ---
 
 # Azure Firewall Manager policy overview
@@ -21,7 +21,7 @@ A policy can be created and managed in multiple ways, including the Azure portal
 
 You can also migrate existing Classic rules from Azure Firewall using the portal or Azure PowerShell to create policies. For more information, see [How to migrate Azure Firewall configurations to Azure Firewall policy](migrate-to-policy.md). 
 
-Policies can be associated with one or more virtual hubs or VNets. The firewall can be in any subscription associated with your account and in any region.
+Policies can be associated with one or more firewalls deployed in either a Virtual WAN (creating a Secured Virtual Hub) or a Virtual Network (creating a Hub Virtual Network). Firewalls can reside in any region or subscription linked to your account.
 
 ## Classic rules and policies
 
@@ -31,7 +31,7 @@ Azure Firewall supports both Classic rules and policies, but policies is the rec
 | Subject | Policy  | Classic rules |
 | ------- | ------- | ----- |
 |Contains     |NAT, Network, Application rules, custom DNS and DNS proxy settings, IP Groups, and Threat Intelligence settings (including allowlist), IDPS, TLS Inspection, Web Categories, URL Filtering|NAT, Network, and Application rules, custom DNS and DNS proxy settings, IP Groups, and Threat Intelligence settings (including allowlist)|
-|Protects     |Virtual hubs and Virtual Networks|Virtual Networks only|
+|Protects     |Virtual Hubs (VWAN) and Virtual Networks|Virtual Networks only|
 |Portal experience     |Central management using Firewall Manager|Standalone firewall experience|
 |Multiple firewall support     |Firewall Policy is a separate resource that can be used across firewalls|Manually export and import rules, or using third-party management solutions |
 |Pricing     |Billed based on firewall association. See [Pricing](#pricing).|Free|
@@ -51,17 +51,19 @@ Azure Firewall supports Basic, Standard, and Premium policies. The following tab
 
 ## Hierarchical policies
 
-New policies can be created from scratch or inherited from existing policies. Inheritance allows DevOps to create local firewall policies on top of organization mandated base policy.
+New firewall policies can either be created from scratch or inherited from existing policies. Inheritance allows DevOps to define local firewall policies on top of organization mandated base policies.
 
-Policies created with non-empty parent policies inherit all rule collections from the parent policy. The parent policy and the child policy must be in the same region. A firewall policy can be associated with firewalls across regions regardless where they're stored.
+When a new policy is created with a non-empty parent policy, it inherits all rule collections from the parent. Both the parent and child policies must reside in the same region. However, a firewall policy, regardless of where it is stored, can be associated with firewalls in any region.
 
-Network rule collections inherited from a parent policy are always prioritized over network rule collections defined as part of a new policy. The same logic also applies to application rule collections. However, network rule collections are always processed before application rule collections regardless of inheritance.
+### Rule inheritance ###
+Network rule collections inherited from the parent policy are always prioritized over network rule collections defined as part of a new policy. The same logic also applies to application rule collections. Regardless of inheritance, network rule collections are processed before application rule collections. 
 
-Threat Intelligence mode is also inherited from the parent policy. You can set your threat Intelligence mode to a different value to override this behavior, but you can't turn it off. It's only possible to override with a stricter value. For example, if your parent policy is set to **Alert only**, you can configure this local policy to **Alert and deny**.
+NAT rule collections are not inherited, as they are specific to individual firewalls. If you want to use NAT rules, you must define them in the child policy.
 
-Like Threat Intelligence mode, the Threat Intelligence allowlist is inherited from the parent policy. The child policy can add more IP addresses to the allowlist.
+### Threat Intelligence mode and allowlist inheritance ###
+Threat Intelligence mode is also inherited from the parent policy. While you can override this setting in the child policy, it must be with a stricter mode - you cannot disable it. For example, if your parent policy is set to **Alert only**, the child policy can be set to **Alert and deny**, but not to a less strict mode.
 
-NAT rule collections aren't inherited because they're specific to a given firewall.
+Similarly, the Threat Intelligence allowlist is inherited from the parent policy, and the child policy can append additional IP addresses to this list.
 
 With inheritance, any changes to the parent policy are automatically applied down to associated firewall child policies.