Skip to content

Commit

Permalink
made note to address a limitation on AppGW PowerShell (Azure#26473)
Browse files Browse the repository at this point in the history
  • Loading branch information
reyjordi authored Oct 26, 2024
1 parent 2867f60 commit 13f3375
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions src/Network/Network/help/New-AzApplicationGateway.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,9 @@ An application gateway requires the following:
A listener has a front-end port, front-end IP address, protocol (HTTP or HTTPS) and Secure Sockets
Layer (SSL) certificate name (if configuring SSL offload).

> [!NOTE]
> There is a limitation that does not allow users to deploy a V2 application gateway that utilizes customer key vault for certificate storage and has a WAF policy associated to it. In the four parameter sets provided by the New-AzApplicationGateway cmdlet, the `-Identity` switch never coincides with the `-FirewallPolicy` or `-FirewallPolicyID` switch. Therefore, this cannot be done in one operation. The workaround is to have this done in multiple operations. Users must deploy a standard V2 Application Gateway with the managed identity, then change the sku to WAF_v2 and add the WAF policy.
## EXAMPLES

### Example 1: Create an application gateway
Expand Down

0 comments on commit 13f3375

Please sign in to comment.