Skip to content

Commit b03a5e8

Browse files
author
Igor Pagliai
authored
Better clarified the HA statement
Better clarified the HA statement
1 parent 4cd0afb commit b03a5e8

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+
Azure Firewall Policy object can be created in any region, and linked globally in all regions, to multiple Azure Firewall instances under the same Azure AD tenant. If the region where the Policy is created will be down, and if a paired region does exist, ARM object metadata will be automatically failed over to the secondary region. During the failover, or while the single-region with no pair will remain in failed state, it will be not possible to modify the Azure Firewall Policy object. Azure Firewall instances linked to the Firewall Policy will 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)