Non-internalOnly environment containers require ingress = Accepting traffic from anywhere
re: Protect Azure Container Apps with Web Application Firewall on Application Gateway
ACA Environment is not 'internalOnly'
The instructions successfully connected App Gateway with Container App but fails if I switch Container App ingress to "Limited to Container Apps Environment". Must I connect App Gateway to complete 'internalOnly' environment to achieve this?
I like having the option to pick and choose Container App ingress knowing that API Gateway ingress is handled separately within Azure as a connected service.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 699a4fc7-15aa-285b-f681-028c872574bf
- Version Independent ID: cd29f9c6-bdcf-46d1-6048-352b8bda055d
- Content: Protect Azure Container Apps with Application Gateway and Web Application Firewall (WAF)
- Content Source: articles/container-apps/waf-app-gateway.md
- Service: container-apps
- GitHub Login: @wviriya
- Microsoft Alias: wviriya
@gcrockenberg It would be great if you could add a link to the documentation you are following for these steps? This would help us redirect the issue to the appropriate team. Thanks!!
@mumurug-MSFT Please review it.
Thanks for your feedback and your contribution to Azure docs.
Feedback for this repository is moving away from GitHub to a system specific to the Microsoft Learn platform. Issues for this repository will soon be disabled, and additional comments from GitHub will no longer be possible. However, we are now tracking and triaging this issue in the new feedback system.
To learn more about our feedback systems, please see Provide feedback for Microsoft Learn content.
#please-close