Merge pull request #279748 from dknappettmsft/avd-remove-experience-estimator-links

AVD remove experience estimator links and references

Author: v-dirichards

articles/virtual-desktop/TOC.yml

@@ -661,8 +661,6 @@
     href: msixmgr-tool-syntax-description.md 
 - name: Resources
   items:
-  - name: User experience estimator
-    href: https://azure.microsoft.com/services/virtual-desktop/assessment/
   - name: Pricing
     items:
     - name: Azure Virtual Desktop pricing

articles/virtual-desktop/connection-latency.md

@@ -101,7 +101,6 @@ In contrast to other diagnostics tables that report data at regular intervals th
 
 - Learn more about how to monitor and run queries about connection quality issues at [Monitor connection quality](connection-quality-monitoring.md).
 - Troubleshoot connection and latency issues at [Troubleshoot connection quality for Azure Virtual Desktop](troubleshoot-connection-quality.md).
-- To check the best location for optimal latency, see the [Azure Virtual Desktop Experience Estimator tool](https://azure.microsoft.com/services/virtual-desktop/assessment/).
 - For pricing plans, see [Azure Log Analytics pricing](/services-hub/unified/health/azure-pricing).
 - To get started with your Azure Virtual Desktop deployment, check out [our tutorial](./create-host-pools-azure-marketplace.md).
 - To learn about bandwidth requirements for Azure Virtual Desktop, see [Understanding Remote Desktop Protocol (RDP) Bandwidth Requirements for Azure Virtual Desktop](rdp-bandwidth.md).

articles/virtual-desktop/index.yml

@@ -88,8 +88,6 @@ landingContent:
             url: /training/browse/?expanded=azure&products=azure-virtual-desktop&resource_type=learning%20path
       - linkListType: reference
         links:
-          - text: User experience estimator
-            url: https://azure.microsoft.com/services/virtual-desktop/assessment/
           - text: Pricing calculator
             url: https://azure.microsoft.com/pricing/calculator/
 

articles/virtual-desktop/insights-glossary.md

@@ -185,7 +185,7 @@ You can also select entries to view additional information. You can view which h
 
 ## Round-trip time (RTT)
 
-Round-trip time (RTT) is an estimate of the connection's round-trip time between the end-user’s location and the session host's Azure region. To see which locations have the best latency, look up your desired location in the [Azure Virtual Desktop Experience Estimator tool](https://azure.microsoft.com/services/virtual-desktop/assessment/).
+Round-trip time (RTT) is an estimate of the connection's round-trip time between the end-user’s location and the session host's Azure region. To see which locations have the best latency, look up your desired location in [Azure network round-trip latency statistics](../networking/azure-network-latency.md).
 
 ## Session history
 

articles/virtual-desktop/prerequisites.md

@@ -212,7 +212,7 @@ Also consider the following:
 
 - Your users might need access to applications and data that is hosted on different networks, so make sure your session hosts can connect to them.
 
-- Round-trip time (RTT) latency from the client's network to the Azure region that contains the host pools should be less than 150 ms. Use the [Experience Estimator](https://azure.microsoft.com/services/virtual-desktop/assessment/) to view your connection health and recommended Azure region. To optimize for network performance, we recommend you create session hosts in the Azure region closest to your users.
+- Round-trip time (RTT) latency from the client's network to the Azure region that contains the host pools should be less than 150 ms. To see which locations have the best latency, look up your desired location in [Azure network round-trip latency statistics](../networking/azure-network-latency.md). To optimize for network performance, we recommend you create session hosts in the Azure region closest to your users.
 
 - Use [Azure Firewall for Azure Virtual Desktop deployments](../firewall/protect-azure-virtual-desktop.md) to help you lock down your environment and filter outbound traffic.
 

articles/virtual-desktop/troubleshoot-client-windows-basic-shared.md

@@ -40,7 +40,6 @@ There are a few basic troubleshooting steps you can try if you're having issues
 
    :::image type="content" source="media/troubleshoot-client-windows-basic-shared/troubleshoot-windows-client-connection-information.png" alt-text="A screenshot showing the connection bar in the Remote Desktop client for Windows.":::
 
-1. Check the estimated connection round trip time (RTT) from your current location to the Azure Virtual Desktop service. For more information, see [Azure Virtual Desktop Experience Estimator](https://azure.microsoft.com/products/virtual-desktop/assessment/#estimation-tool)
 ::: zone-end
 
 ::: zone pivot="windows-365"

articles/virtual-desktop/troubleshoot-connection-quality.md

@@ -30,9 +30,9 @@ To reduce round trip time:
 
 - Check your compute resources by looking at CPU utilization and available memory on your VM. You can view your compute resources by following the instructions in [Configuring performance counters](../azure-monitor/agents/data-sources-performance-counters.md#configure-performance-counters) to set up a performance counter to track certain information. For example, you can use the Processor Information(_Total)\\% Processor Time counter to track CPU utilization, or the Memory(\*)\\Available Mbytes counter for available memory. Both of these counters are enabled by default in Azure Virtual Desktop Insights. If both counters show that CPU usage is too high or available memory is too low, your VM size or storage may be too small to support your users' workloads, and you'll need to upgrade to a larger size.
 
-## Optimize VM latency with the Azure Virtual Desktop Experience Estimator tool
+## Optimize VM latency by reviewing Azure network round-trip latency statistics
 
-The [Azure Virtual Desktop Experience Estimator tool](https://azure.microsoft.com/services/virtual-desktop/assessment/) can help you determine the best location to optimize the latency of your VMs. We recommend you use the tool every two to three months to make sure the optimal location hasn't changed as Azure Virtual Desktop rolls out to new areas.
+Round-trip time (RTT) latency from the client's network to the Azure region that contains the host pools should be less than 150 ms. To see which locations have the best latency, look up your desired location in [Azure network round-trip latency statistics](../networking/azure-network-latency.md). To optimize for network performance, we recommend you create session hosts in the Azure region closest to your users. We recommend you review the statistics every two to three months to make sure the optimal location hasn't changed as Azure Virtual Desktop rolls out to new areas.
 
 ## My connection data isn't going to Azure Log Analytics
 

articles/virtual-desktop/virtual-desktop-fall-2019/index.yml

@@ -79,8 +79,6 @@ landingContent:
             url: /training/browse/?expanded=azure&products=azure-virtual-desktop&resource_type=learning%20path
       - linkListType: reference
         links:
-          - text: User experience estimator
-            url: https://azure.microsoft.com/services/virtual-desktop/assessment/
           - text: Pricing calculator
             url: https://azure.microsoft.com/pricing/calculator/
 

articles/virtual-desktop/whats-new.md

@@ -1106,8 +1106,6 @@ We've optimized performance by reducing connection latency in the following Azur
 - Switzerland
 - Canada
 
-You can now use the [Experience Estimator](https://azure.microsoft.com/services/virtual-desktop/assessment/) to estimate the user experience quality in these areas.
-
 ### Azure Government Cloud availability
 
 The Azure Government Cloud is now generally available. Learn more at [our blog post](https://azure.microsoft.com/updates/windows-virtual-desktop-is-now-generally-available-in-the-azure-government-cloud/).
@@ -1137,8 +1135,6 @@ Here's what changed in September 2020:
     - Germany
     - South Africa (for validation environments only)
 
-You can now use the [Experience Estimator](https://azure.microsoft.com/services/virtual-desktop/assessment/) to estimate the user experience quality in these areas.
-
 - We released version 1.2.1364 of the Windows Desktop client for Azure Virtual Desktop. In this update, we made the following changes:
     - Fixed an issue where single sign-on (SSO) didn't work on Windows 7.
     - Fixed an issue that caused the client to disconnect when a user who enabled media optimization for Teams tried to call or join a Teams meeting while another app had an audio stream open in exclusive mode.
@@ -1163,9 +1159,7 @@ Here's what changed in August 2020:
     - Norway
     - South Korea
 
-   You can use the [Experience Estimator](https://azure.microsoft.com/services/virtual-desktop/assessment/) to get a general idea of how these changes affect your users.
-
-- The Microsoft Store Remote Desktop Client (v10.2.1522+) is now generally available! This version of the Microsoft Store Remote Desktop Client is compatible with Azure Virtual Desktop. We've also introduced refreshed UI flows for improved user experiences. This update includes fluent design, light and dark modes, and many other exciting changes. We've also rewritten the client to use the same underlying remote desktop protocol (RDP) engine as the iOS, macOS, and Android clients. This lets us deliver new features at a faster rate across all platforms. [Download the client](https://www.microsoft.com/p/microsoft-remote-desktop/9wzdncrfj3ps?rtc=1&activetab=pivot:overviewtab) and give it a try!
+- The Microsoft Store Remote Desktop Client is now generally available. This version of the Microsoft Store Remote Desktop Client is compatible with Azure Virtual Desktop. We've also introduced refreshed UI flows for improved user experiences. This update includes fluent design, light and dark modes, and many other exciting changes. We've also rewritten the client to use the same underlying remote desktop protocol (RDP) engine as the iOS, macOS, and Android clients. This lets us deliver new features at a faster rate across all platforms. [Download the client](https://www.microsoft.com/p/microsoft-remote-desktop/9wzdncrfj3ps?rtc=1&activetab=pivot:overviewtab).
 
 - We fixed an issue in the Teams Desktop client (version 1.3.00.21759) where the client only showed the UTC time zone in the chat, channels, and calendar. The updated client now shows the remote session's time zone instead.