Add regional load-balancer frontends to the correct global backend pool

Source facts

Microsoft’s global load balancer tutorial starts with two Standard regional load balancers and their backend pools in different regions. It then adds the regional frontend resource identifiers to the global load balancer’s backend pool. The example therefore links the global layer to regional frontends, rather than directly adding the application virtual machines there. Microsoft Learn.

Applicability

Use this review for the cross-region design described by the tutorial. Identify both regional resources, the specific frontend configuration on each, and the global frontend and rule. Check the current supported home regions before planning deployment.

DSE recommendation

DSE recommends a layer-by-layer resource map that connects the global backend entries to regional frontends and then to application backends. Have another operator verify the resource identifiers before applying a change. Include ownership for regional health and application readiness so a correct global association is not treated as proof that the underlying service is ready.

Verification

Inspect the deployed global pool and reconcile each entry with the intended regional frontend. Test the regional application paths, then the global address, using approved clients and observation windows. Record which layer each result validates. Investigate an incorrect resource association before changing individual VM membership in an otherwise correct regional pool.

Official references

Microsoft Learn: Tutorial: Create an Azure Global Load Balancer.