Closed hoyapark closed 1 year ago
Much Appreciate the attention.
@hoyapark Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.
@femila Can you please check and add your comments on this doc update request as applicable.
Hi @hoyapark - in this article, the section 'Client connection sequence' details the steps for this, including step 7 "...and establishes the secure TLS 1.2 connection to the closest Azure Virtual Desktop gateway instance and passes the connection information". In addition, the diagram shows that the network traffic between session host and RD Gateway isn't going over the public internet.
Closing the loop on this - we've recently added a bit more detail to step 7 for latency and how a gateway is selected.
I wanted to submit a request to summarize how AVD client connects to AVD host that can help highlight the efficiency built into the product. Many of my clients reach out to me because there isn't an official Microsoft doc that summarizes what takes place when a user connects to an AVD host. Especially clients that have VDI users overseas who are looking for more efficient VDI solutions with lower latency to connect to the resources that can be built out anywhere in the world. A summary such as this:
"When AVD client attempts to connect, the user session is directed by Azure Front Door to the nearest AVD gateway. This is accomplished by using "anycast" which examines the source IP address of the incoming session and matches it to the closest AVD gateway. The corresponding AVD host is then connected to the same AVD gateway traveling through Microsoft backbone network and matched with the user session. This connection is far more efficient in that it utilizes the global Microsoft backbone network and avoids public internet which will add higher latency."
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.