Skip to content

Commit 09bb041

Browse files
Merge pull request #263532 from igorpag/patch-11
Better clarified the HA statement
2 parents f1d8c8b + 4c84a06 commit 09bb041

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/firewall-manager/policy-overview.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,8 +68,7 @@ With inheritance, any changes to the parent policy are automatically applied dow
6868
## Built-in high availability
6969

7070
High availability is built in, so there's nothing you need to configure.
71-
72-
Azure Firewall Policy is replicated to a paired Azure region. For example, if one Azure region goes down, Azure Firewall policy becomes active in the paired Azure region. The paired region is automatically selected based on the region where the policy is created. For more information, see [Cross-region replication in Azure: Business continuity and disaster recovery](../reliability/cross-region-replication-azure.md#azure-paired-regions).
71+
You can create an Azure Firewall Policy object in any region and link it globally to multiple Azure Firewall instances under the same Azure AD tenant. If the region where you create the Policy goes down and has a paired region, the ARM object metadata automatically fails over to the secondary region. During the failover, or if the single-region with no pair remains in a failed state, you cannot modify the Azure Firewall Policy object. However, the Azure Firewall instances linked to the Firewall Policy continue to operate. For more information, see [Cross-region replication in Azure: Business continuity and disaster recovery](../reliability/cross-region-replication-azure.md#azure-paired-regions).
7372

7473
## Pricing
7574

0 commit comments

Comments
 (0)