The parent Traffic Manager profile must use the Geographic routing method. This method directs traffic based on the geographic origin of the DNS query, fulfilling the requirements to route North Europe traffic to the North Europe region and North America traffic to the East US region.

Each regional endpoint in the parent profile is a nested (child) Traffic Manager profile. These child profiles must use the Weighted routing method. By assigning an equal weight to each App Service instance within a region's child profile, traffic is distributed evenly among them, satisfying the equal assignment requirement. This nested configuration combines geographic steering with even load distribution.

1. Microsoft Azure Documentation

Traffic Manager routing methods. Microsoft Learn. Accessed May 20

2024.

Section: Geographic traffic-routing method: "Use this routing method to direct users to specific endpoints (Azure

External

or Nested) based on the geographic location their DNS query originates from. This method enables you to be in compliance with data sovereignty mandates

localization of content & user experience and measuring traffic from different regions."

Section: Weighted traffic-routing method: "Use this routing method to distribute traffic across a set of endpoints based on their weight. You set the weight

which is an integer from 1 to 1000

for each endpoint in the Traffic Manager profile configuration. ... If you want to use an even distribution

you set the weights for all endpoints to be the same."

2. Microsoft Azure Documentation

Nested Traffic Manager profiles. Microsoft Learn. Accessed May 20

2024.

Section: Example: Using nested profiles to mix routing methods: This document provides a specific example of a parent profile using 'Geographic' routing to direct traffic to child profiles. The child profiles then use 'Weighted' routing to distribute traffic across endpoints within their respective regions

which directly mirrors the solution required by the question.