Merge pull request #217785 from thisisanniefang/patch-45

Add RBAC min permissions

Author: prmerger-automator[bot]

articles/load-balancer/gateway-overview.md

@@ -65,7 +65,7 @@ Gateway Load Balancer consists of the following components:
 
 * **Tunnel interfaces** - Gateway Load balancer backend pools have another component called the tunnel interfaces. The tunnel interface enables the appliances in the backend to ensure network flows are handled as expected. Each backend pool can have up to two tunnel interfaces. Tunnel interfaces can be either internal or external. For traffic coming to your backend pool, you should use the external type. For traffic going from your appliance to the application, you should use the internal type.
 
-* **Chain** - A Gateway Load Balancer can be referenced by a Standard Public Load Balancer frontend or a Standard Public IP configuration on a virtual machine. The addition of advanced networking capabilities in a specific sequence is known as service chaining. As a result, this reference is called a chain.
+* **Chain** - A Gateway Load Balancer can be referenced by a Standard Public Load Balancer frontend or a Standard Public IP configuration on a virtual machine. The addition of advanced networking capabilities in a specific sequence is known as service chaining. As a result, this reference is called a chain. In order to chain a Load Balancer frontend or Public IP configuration to a Gateway Load Balancer that is cross-subscription, users will need permission for the resource provider operation "Microsoft.Network/loadBalancers/frontendIPConfigurations/join/action". For cross-tenant chaining, the user will also need Guest access.
 
 ## Pricing