Skip to content

Commit 13f3375

Browse files
authored
made note to address a limitation on AppGW PowerShell (#26473)
1 parent 2867f60 commit 13f3375

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

src/Network/Network/help/New-AzApplicationGateway.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,9 @@ An application gateway requires the following:
139139
A listener has a front-end port, front-end IP address, protocol (HTTP or HTTPS) and Secure Sockets
140140
Layer (SSL) certificate name (if configuring SSL offload).
141141

142+
> [!NOTE]
143+
> 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.
144+
142145
## EXAMPLES
143146

144147
### Example 1: Create an application gateway

0 commit comments

Comments
 (0)