You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/load-balancer/backend-pool-management.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -216,9 +216,10 @@ az vm create \
216
216
### Limitations
217
217
* IP based backends can only be used for Standard Load Balancers
218
218
* The backend resources must be in the same virtual network as the load balancer for IP based LBs
219
+
* IP-based load balancers backend instances must still be virtual machines or virtual machine scale sets. Attaching other PaaS services to the backend pool of an IP based Load Balancer is not supported.
219
220
* A load balancer with IP based Backend Pool can’t function as a Private Link service
220
221
*[Private endpoint resources](../private-link/private-endpoint-overview.md) can't be placed in an IP based backend pool
221
-
* IP-based load balancers don't support ACI containers
222
+
* IP-based load balancers doesn't support ACI containers
222
223
* Load balancers or services such as Application Gateway can’t be placed in the backend pool of the load balancer
223
224
* Inbound NAT Rules can’t be specified by IP address
224
225
* You can configure IP based and NIC based backend pools for the same load balancer. You can’t create a single backend pool that mixes backed addresses targeted by NIC and IP addresses within the same pool.
0 commit comments