Skip to content

Commit 04d4d41

Browse files
authored
Update APIM Load Balancer AI documentation
Added note on using Application Gateway for MSFT Foundry APIs and clarified the role of Azure Load Balancer.
1 parent 01932f3 commit 04d4d41

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

0_Azure/3_AzureAI/AIFoundry/demos/13_APIM_LoadBalancer_AI.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -44,6 +44,10 @@ Last updated: 2026-01-22
4444
> [!NOTE]
4545
> For **MSFT Foundry APIs**, you can use **Application Gateway** because it’s HTTP/S‑aware, integrates with APIM, and provides advanced routing + [WAF](https://docs.azure.cn/en-us/web-application-firewall/overview) security. Azure Load Balancer is useful for **internal, low‑level traffic distribution**, but not sufficient on its own for developer‑facing Foundry workloads.
4646
47+
<img width="567" height="383" alt="image" src="https://github.com/user-attachments/assets/bb67fc6c-5407-49b2-8a1f-52963689d37d" />
48+
49+
From [What is Azure Web Application Firewall?](https://docs.azure.cn/en-us/web-application-firewall/overview)
50+
4751
## Unified Gateway with APIM
4852

4953
`Applications only call APIM endpoints, not individual Foundry instances. This simplifies SDKs and client logic.`

0 commit comments

Comments
 (0)