Skip to content

Commit 36658f9

Browse files
authored
Update APIM Load Balancer AI documentation
Clarified the use of Application Gateway and Azure Load Balancer for MSFT Foundry APIs, emphasizing their roles in traffic distribution and API management.
1 parent 04d4d41 commit 36658f9

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,12 +42,16 @@ Last updated: 2026-01-22
4242
| **Hub-and-Spoke** | One central hub, multiple spokes | Easier to manage, centralized policies | Hub becomes a critical dependency |
4343

4444
> [!NOTE]
45-
> 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.
45+
> 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.
46+
> - If your Foundry deployments are directly consumed as APIs (which they usually are), Application Gateway is the right fit because it understands HTTP/S and integrates naturally with APIM.
47+
> - If your Foundry workloads are wrapped inside VM/container clusters and you just need raw traffic distribution, Load Balancer is simpler and faster. But you’d still need APIM or Gateway in front for API‑level features.
4648
4749
<img width="567" height="383" alt="image" src="https://github.com/user-attachments/assets/bb67fc6c-5407-49b2-8a1f-52963689d37d" />
4850

4951
From [What is Azure Web Application Firewall?](https://docs.azure.cn/en-us/web-application-firewall/overview)
5052

53+
54+
5155
## Unified Gateway with APIM
5256

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

0 commit comments

Comments
 (0)