Skip to content

Commit b82dad4

Browse files
Merge pull request #307246 from thisisanniefang/patch-345972
Remove frontend tag requirement
2 parents 72203f4 + 1ce09e6 commit b82dad4

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/load-balancer/cross-subscription-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ This table illustrates some of the possible scenarios cross-subscription load ba
3333
| Load Balancer and Frontend IP address | Backend pool resources |
3434

3535
## Cross-subscription frontend IP configurations
36-
Cross-subscription frontends allow the frontend IP configuration to reside in a different subscription other than the load balancer’s subscription. To enable cross-subscription frontend IP configurations, the following tag needs to be set to true: `IsRemoteFrontend: True`, and the `SyncMode` property needs to be enabled on the backend pool.
36+
Cross-subscription frontends allow the frontend IP configuration to reside in a different subscription other than the load balancer’s subscription. To enable cross-subscription frontend IP configurations, all backend pools need to have the `SyncMode` property configured.
3737

3838
### Public frontend IP configurations
3939
Public IP addresses utilized by an Azure Load Balancer can reside in different subscription than the load balancer. If multiple public IP addresses are attached to a load balancer, each IP address can come from a different subscription. For example, if we have a Load Balancer (deployed in subscription C) with two frontend IPs, the first IP address can reside in subscription B and the second IP address can reside in subscription A.

0 commit comments

Comments
 (0)