Since the Traffic Manager works at the DNS level, clients are directed to the ideal service endpoint using DNS responses. This also means that clients manage to connect directly to the service endpoint, bypassing Traffic Manager, which results in the HTTP traffic between the client and the server remaining unknown to the Traffic Manager. Furthermore, the recursive DNS service owns the source IP address of the DNS query received by the Traffic Manager instead of the client. As a result, Traffic Manager is unable to track individual clients or create sticky sessions. This constraint exists in the case of all DNS-based traffic control solutions, including Traffic Manager.
