Skip to content

Commit c1d9efe

Browse files
Merge pull request #127438 from lukemurraynz/patch-4
Update policy-overview.md - Changed AzureAD to Entra
2 parents 147a61d + 84d53a1 commit c1d9efe

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/firewall-manager/policy-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Policies can be associated with one or more firewalls deployed in either a Virtu
2525

2626
## Classic rules and policies
2727

28-
Azure Firewall supports both Classic rules and policies, but policies is the recommended configuration. The following table compares policies and classic rules:
28+
Azure Firewall supports both Classic rules and policies, but policies are the recommended configuration. The following table compares policies and classic rules:
2929

3030

3131
| Subject | Policy | Classic rules |
@@ -70,7 +70,7 @@ With inheritance, any changes to the parent policy are automatically applied dow
7070
## Built-in high availability
7171

7272
High availability is built in, so there's nothing you need to configure.
73-
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(Azure Resource Manager) 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 can't 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).
73+
You can create an Azure Firewall Policy object in any region and link it globally to multiple Azure Firewall instances under the same Entra ID tenant. If the region where you create the Policy goes down and has a paired region, the ARM(Azure Resource Manager) 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 can't 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).
7474

7575
## Pricing
7676

0 commit comments

Comments
 (0)