Skip to content

Commit 4e99aeb

Browse files
committed
acrofixes
1 parent 5cc1ece commit 4e99aeb

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/web-application-firewall/ag/upgrade-ag-waf-policy.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,13 @@ Azure Web Application Firewall (WAF) provides centralized protection of your web
1616

1717
Azure Application Gateway WAF v2 natively supports WAF policy. You should upgrade your legacy WAF configuration to WAF policies.
1818

19-
- Policies offer a richer set of advanced features like newer managed rule sets, custom rules, per rule exclusions, bot protection, and the next generation of WAF engine. These advanced features are available to you at no additional cost.
19+
- Policies offer a richer set of advanced features. This includes newer managed rule sets, custom rules, per rule exclusions, bot protection, and the next generation of WAF engine. These advanced features are available to you at no extra cost.
2020
- WAF policies provide higher scale and better performance.
2121
- Unlike legacy WAF configuration, WAF policies can be defined once and shared across multiple gateways, listeners, and URL paths. This simplifies the management and deployment experience.
22-
- The latest features and future enhancements will only be available via WAF policies.
22+
- The latest features and future enhancements are only available via WAF policies.
2323

2424
> [!IMPORTANT]
25-
> No further investments will be made on legacy WAF configuration. You are strongly encouraged to upgrade from legacy WAF configuration to WAF Policy for easier management, better, scale, and a richer feature set at no additional cost.
25+
> No further investments will be made on legacy WAF configuration. You are strongly encouraged to upgrade from legacy WAF configuration to WAF Policy for easier management, better scale, and a richer feature set at no additional cost.
2626
2727
## Upgrade Application Gateway Standard v2 to Application Gateway WAF v2
2828

@@ -36,7 +36,7 @@ You can upgrade existing Application Gateways with WAF v2 from WAF legacy config
3636

3737
# [Portal](#tab/portal)
3838

39-
1. Logon to the Azure portal and select the Application Gateway WAF v2 that has a legacy WAF configuration.
39+
1. Sign in to the Azure portal and select the Application Gateway WAF v2 that has a legacy WAF configuration.
4040
1. Select **Web Application Firewall** from the left menu, then select **Upgrade from WAF configuration**.
4141
1. Provide a name for the new WAF Policy and then select **Upgrade**. This creates a new WAF Policy based on the WAF configuration. You can also choose to associate a pre-existing WAF Policy instead of creating a new one.
4242
1. When the upgrade finishes, a new WAF Policy incorporating the previous WAF configuration and rules is created.
@@ -53,7 +53,7 @@ See [Upgrade Web Application Firewall policies using Azure PowerShell](migrate-p
5353

5454
## Upgrade Application Gateway v1 to WAF v2 with WAF policy
5555

56-
Application Gateway v1 does not support WAF policy. Upgrading to WAF policy is a two step process:
56+
Application Gateway v1 doesn't support WAF policy. Upgrading to WAF policy is a two step process:
5757

5858
- Upgrade Application Gateway v1 to v2 version.
5959
- Upgrade legacy WAF configuration to WAF policy.

0 commit comments

Comments
 (0)