Merge branch 'MicrosoftDocs:main' into master

jsaurezlee-msft · web-flow · commit 1a9c42c206b9 · 2023-01-06T12:46:43.000-06:00
diff --git a/articles/active-directory/develop/active-directory-jwt-claims-customization.md b/articles/active-directory/develop/active-directory-jwt-claims-customization.md
@@ -1,5 +1,5 @@
 ---
-title: Customize app JSON Web Token (JWT) claims
+title: Customize app JSON Web Token (JWT) claims (Preview)
 description: Learn how to customize the claims issued by Microsoft identity platform in the JSON web token (JWT) token for enterprise applications.
 services: active-directory
 author: davidmu1
@@ -13,11 +13,11 @@ ms.author: davidmu
 ms.custom: aaddev
 ---
 
-# Customize claims issued in the JSON web token (JWT) for enterprise applications
+# Customize claims issued in the JSON web token (JWT) for enterprise applications (Preview)
 
 The Microsoft identity platform supports single sign-on (SSO) with most enterprise applications, including both applications pre-integrated in the Azure AD app gallery and custom applications. When a user authenticates to an application through the Microsoft identity platform using the OIDC protocol, the Microsoft identity platform sends a token to the application. And then, the application validates and uses the token to log the user in instead of prompting for a username and password.
 
-These JSON Web tokens (JWT) used by OIDC & OAuth applications contain pieces of information about the user known as *claims*. A *claim* is information that an identity provider states about a user inside the token they issue for that user.
+These JSON Web tokens (JWT) used by OIDC & OAuth applications (preview) contain pieces of information about the user known as *claims*. A *claim* is information that an identity provider states about a user inside the token they issue for that user.
 
 In an [OIDC response](v2-protocols-oidc.md), *claims* data is typically contained in the ID Token issued by the identity provider in the form of a JWT.
 
diff --git a/articles/cost-management-billing/reservations/reserved-instance-purchase-recommendations.md b/articles/cost-management-billing/reservations/reserved-instance-purchase-recommendations.md
@@ -55,6 +55,7 @@ Reservation purchase recommendations are available in Azure Advisor. Keep in min
 - The recommendations quantity and savings are for a three-year reservation, where available. If a three-year reservation isn't sold for the service, the recommendation is calculated using the one-year reservation price.
 - The recommendation calculations include any special discounts that you might have on your on-demand usage rates.
 - If you purchase a shared-scope reservation, Advisor reservation purchase recommendations can take up to five days to disappear.
+- Azure classic compute resources such as classic VMs are explicitly excluded from reservation recommendations. Microsoft recommends that users avoid making long-term commitments to legacy services that are being deprecated.
 
 ## Other expected API behavior
 
diff --git a/articles/cost-management-billing/reservations/troubleshoot-reservation-recommendation.md b/articles/cost-management-billing/reservations/troubleshoot-reservation-recommendation.md
@@ -7,7 +7,7 @@ ms.subservice: reservations
 ms.author: banders
 ms.reviewer: nitinarora
 ms.topic: troubleshooting
-ms.date: 12/06/2022
+ms.date: 01/06/2023
 ---
 
 # Troubleshoot Azure reservation recommendations
@@ -30,7 +30,9 @@ It's also important to understand how the scope selection affects recommendation
 
 Azure might recommend purchasing a reservation for certain terms, and not for others, based on the cost savings identified. Specifically, three-year terms have larger discounts than one-year terms. It's more likely that Azure will find savings for a three-year term than it will for a one-year term.
 
-If you want to understand why Azure recommends a specific resource size and quantity, select **&lt;Quantity&gt; See details** for an in-depth, visualization showing potential savings over time.
+Azure classic compute resources such as classic VMs are explicitly excluded from reservation recommendations. Microsoft recommends that users avoid making long-term commitments to legacy services that are being deprecated.
+
+If you want to understand why Azure recommends a specific resource size and quantity, select **\<Quantity\> See details** for an in-depth, visualization showing potential savings over time.
 
 :::image type="content" source="./media/troubleshoot-reservation-recommendation/see-details-link.png" alt-text="Example showing the reservation recommendation See details link" lightbox="./media/troubleshoot-reservation-recommendation/see-details-link.png" :::
 
diff --git a/articles/virtual-desktop/TOC.yml b/articles/virtual-desktop/TOC.yml
@@ -81,7 +81,7 @@
         href: rdp-bandwidth.md
       - name: Proxy support guidelines
         href: proxy-server-support.md
-      - name: Determine user connection quality
+      - name: Analyze user connection quality
         href: connection-latency.md
       - name: Azure Private Link
         href: private-link-overview.md
@@ -343,6 +343,8 @@
     href: drain-mode.md
   - name: Network connectivity
     items:
+    - name: Collect and query user connection quality data
+      href: connection-quality-monitoring.md
     - name: Check access to required URLs
       href: required-url-check-tool.md
     - name: Configure RDP Shortpath
diff --git a/articles/virtual-desktop/connection-latency.md b/articles/virtual-desktop/connection-latency.md
@@ -1,57 +1,33 @@
 ---
-title: Azure Virtual Desktop user connection quality - Azure
+title: Analyze connection quality in Azure Virtual Desktop - Azure
 description: Connection quality for Azure Virtual Desktop users.
 author: Heidilohr
 ms.topic: conceptual
-ms.date: 09/26/2022
+ms.date: 01/05/2023
 ms.author: helohr
 manager: femila
+ms.custom: engagement-fy23
 ---
-# Connection quality in Azure Virtual Desktop
+# Analyze connection quality in Azure Virtual Desktop
 
 >[!IMPORTANT]
 >The Connection Graphics Data Logs are currently in preview. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
-Azure Virtual Desktop helps users host client sessions on their session hosts running on Azure. When a user starts a session, they connect from their end-user device, also known as a "client," over a network to access the session host. It's important that the user experience feels as much like a local session on a physical device as possible. In this article, we'll talk about how you can measure and improve the connection quality of your end-users.
+Azure Virtual Desktop helps users host client sessions on their session hosts running on Azure. When a user starts a session, they connect from their local device over a network to access the session host. It's important that the user experience feels as much like a local session on a physical device as possible. In this article, we'll talk about how you can measure your connection network and connection graphics to improve the connection quality of your end-users.
 
-There are currently two ways you can analyze connection quality in your Azure Virtual Desktop deployment: Azure Log Analytics and Azure Front Door. This article will describe how to use each method to optimize graphics quality and improve end-user experience.
+You can analyze connection quality in your Azure Virtual Desktop deployment by using Azure Log Analytics. This article will tell you how you can use Azure Log Analytics to optimize graphics quality and improve end-user experience.
 
-## Monitor connection quality with Azure Log Analytics
+Azure Virtual Desktop uses [Azure Front Door](https://azure.microsoft.com/services/frontdoor/) to redirect the user connection to the nearest Azure Virtual Desktop gateway based on the source IP address. Azure Virtual Desktop will always use the Azure Virtual Desktop gateway that the client chooses.
 
-If you're already using [Azure Log Analytics](diagnostics-log-analytics.md), you can monitor network and graphics data for Azure Virtual Desktop connections. The connection network and graphics data Log Analytics collects can help you discover areas that impact your end-user's graphical experience. The service collects data for reports regularly throughout the session. Azure Virtual Desktop connection network data reports have the following advantages over RemoteFX network performance counters:
+The connection network and graphics data that [Azure Log Analytics](diagnostics-log-analytics.md) collects can help you discover areas that impact your end-user's graphical experience. The service collects data for reports regularly throughout the session. You can also use [RemoteFX network performance counters](remotefx-graphics-performance-counters.md) to get some graphics-related performance data from your deployment, but they're not quite as comprehensive as Azure Log Analytics. Azure Virtual Desktop connection network data reports have the following advantages over RemoteFX network performance counters:
 
 - Each record is connection-specific and includes the correlation ID of the connection that can be tied back to the user.
 
 - The round trip time measured in this table is protocol-agnostic and will record the measured latency for Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) connections.
 
-To start collecting this data, you’ll need to make sure you have diagnostics and the **Network Data Logs** and **Connection Graphics Data Logs Preview** tables enabled in your Azure Virtual Desktop host pools.
-
->[!NOTE]
->Normal storage charges for Log Analytics will apply. Learn more at [Azure Monitor Logs pricing details](../azure-monitor/logs/cost-logs.md).
-
-To check and modify your diagnostics settings in the Azure portal:
-
-1. Sign in to the Azure portal, then go to **Azure Virtual Desktop** and select **Host pools**.
-
-2. Select the host pool you want to collect network data for.
-
-3. Select **Diagnostic settings**, then create a new setting if you haven't configured your diagnostic settings yet. If you've already configured your diagnostic settings, select **Edit setting**.
-
-4. Select **allLogs** or select the names of the diagnostics tables you want to collect data for, including **Network Data Logs** and **Connection Graphics Data Logs Preview**. The *allLogs* parameter will automatically add new tables to your data table in the future.
-
-5. Select where you want to send the collected data. Azure Virtual Desktop Insights users should select a Log Analytics workspace. 
-
-6. Select **Save** to apply your changes.
+## Connection network data
 
-7. Repeat this process for all other host pools you want to measure.
-
-8. Make sure the network data is going to your selected destination by returning to the host pool's resource page, selecting **Logs**, then running one of the queries in [Sample queries for Azure Log Analytics](#sample-queries-for-azure-log-analytics-network-data). In order for your query to get results, your host pool must have active users who have been connecting to sessions. Keep in mind that it can take up to 15 minutes for network data to appear in the Azure portal.
-   
-   To check network data, return to the host pool's resource page, select **Logs**, then run one of the queries in [Sample queries for Azure Log Analytics](connection-latency.md#sample-queries-for-azure-log-analytics-network-data). In order for your query to get results, your host pool must have active users who've connected to sessions before. Keep in mind that it can take up to 15 minutes for network data to appear in the Azure portal.
-
-### Connection network data
-
-The network data you collect for your data tables includes the following information:
+The network data you collect for your data tables using the NetworkData table includes the following information:
 
 - The **estimated available bandwidth (kilobytes per second)** is the average estimated available network bandwidth during each connection time interval.
 
@@ -65,13 +41,13 @@ The network data you collect for your data tables includes the following informa
 
 - The **source system**, **Subscription ID**, **Tenant ID**, and **type** (table name).
 
-#### Frequency
+### Frequency
 
 The service generates these network data points every two minutes during an active session.
 
-### Connection graphics data (preview)
+## The ConnectionGraphicsData table (preview)
 
-You should consult the Graphics data table (preview) when users report slow or choppy experiences in their Azure Virtual Desktop sessions. The Graphics data table will give you useful information whenever graphical indicators, end-to-end delay, and dropped frames percentage fall below the "healthy" threshold for Azure Virtual Desktop. This table will help your admins track and understand factors across the server, client, and network that could be contributing to the user's slow or choppy experience. However, while the Graphics data table is a useful tool for troubleshooting poor user experience, since it's not regularly populated throughout a session, it isn't a reliable environment baseline.
+You should consult the ConnectionGraphicsData table (preview) when users report slow or choppy experiences in their Azure Virtual Desktop sessions. The ConnectionGraphicsData table will give you useful information whenever graphical indicators, end-to-end delay, and dropped frames percentage fall below the "healthy" threshold for Azure Virtual Desktop. This table will help your admins track and understand factors across the server, client, and network that could be contributing to the user's slow or choppy experience. However, while the ConnectionGraphicsData table is a useful tool for troubleshooting poor user experience, since it's not regularly populated throughout a session, it isn't a reliable environment baseline.
 
 The Graphics table only captures performance data from the Azure Virtual Desktop graphics stream. This table doesn't capture performance degradation or "slowness" caused by application-specific factors or the virtual machine (CPU or storage constraints). You should use this table with other VM performance metrics to determine if the delay is caused by the remote desktop service (graphics and network) or something inherent in the VM or app itself.
 
@@ -109,7 +85,7 @@ The graphics data you collect for your data tables includes the following inform
 
 - The **source system**, **Subscription ID**, **Tenant ID**, and **type** (table name).
 
-#### Frequency
+### Frequency
 
 In contrast to other diagnostics tables that report data at regular intervals throughout a session, the frequency of data collection for the graphics data varies depending on the graphical health of a connection. The table won't record data for "Good" scenarios, but will recording if any of the following metrics are recorded as "Poor" or "Okay," and the resulting data will be sent to your storage account. Data only records once every two minutes, maximum. The metrics involved in data collection are listed in the following table:
 
@@ -122,105 +98,12 @@ In contrast to other diagnostics tables that report data at regular intervals th
 >[!NOTE]
 >For end-to-end delay per frame, if any frame in a single second is delayed by over 300 ms, the service registers it as "Bad". If all frames in a single second take between 150 ms and 300 ms, the service marks it as "Okay."
 
-## Sample queries for Azure Log Analytics: network data
-
-In this section, we have a list of queries that will help you review connection quality information. You can run queries in the [Log Analytics query editor](../azure-monitor/logs/log-analytics-tutorial.md#write-a-query).
-
->[!NOTE]
->For each example, replace the *userupn* variable with the UPN of the user you want to look up.
-
-### Query average RTT and bandwidth
-
-To look up the average round trip time and bandwidth:
-
-```kusto
-// 90th, 50th, 10th Percentile for RTT in 10 min increments
-WVDConnectionNetworkData
-| summarize RTTP90=percentile(EstRoundTripTimeInMs,90),RTTP50=percentile(EstRoundTripTimeInMs,50),RTTP10=percentile(EstRoundTripTimeInMs,10) by bin(TimeGenerated,10m)
-| render timechart
-// 90th, 50th, 10th Percentile for BW in 10 min increments
-WVDConnectionNetworkData
-| summarize BWP90=percentile(EstAvailableBandwidthKBps,90),BWP50=percentile(EstAvailableBandwidthKBps,50),BWP10=percentile(EstAvailableBandwidthKBps,10) by bin(TimeGenerated,10m)
-| render timechart
-```
-To look up the round-trip time and bandwidth per connection:
-
-```kusto
-// RTT and BW Per Connection Summary
-// Returns P90 Round Trip Time (ms) and Bandwidth (KBps) per connection with connection details.
-WVDConnectionNetworkData
-| summarize RTTP90=percentile(EstRoundTripTimeInMs,90),BWP90=percentile(EstAvailableBandwidthKBps,90),StartTime=min(TimeGenerated), EndTime=max(TimeGenerated) by CorrelationId
-| join kind=leftouter (
-WVDConnections
-| extend Protocol = iff(UdpUse in ("0","<>"),"TCP","UDP")
-| distinct CorrelationId, SessionHostName, Protocol, ClientOS, ClientType, ClientVersion, ConnectionType, ResourceAlias, SessionHostSxSStackVersion, UserName
-) on CorrelationId
-| project CorrelationId, StartTime, EndTime, UserName, SessionHostName, RTTP90, BWP90, Protocol, ClientOS, ClientType, ClientVersion, ConnectionType, ResourceAlias, SessionHostSxSStackVersion
-```
-
-### Query data for a specific user
-
-To look up the bandwidth for a specific user:
-
-```kusto
-let user = "alias@domain";
-WVDConnectionNetworkData
-| join kind=leftouter (
-    WVDConnections
-    | distinct CorrelationId, UserName
-) on CorrelationId
-| where UserName == user
-| project EstAvailableBandwidthKBps, TimeGenerated
-| render columnchart  
-```
-
-To look up the round trip time for a specific user:
-
-```kusto
-let user = "alias@domain";
-WVDConnectionNetworkData
-| join kind=leftouter (
-WVDConnections
-| distinct CorrelationId, UserName
-) on CorrelationId
-| where UserName == user
-| project EstRoundTripTimeInMs, TimeGenerated
-| render columnchart  
-```
-
-To look up the top 10 users with the highest round trip time:
-
-```kusto
-WVDConnectionNetworkData
-| join kind=leftouter (
-    WVDConnections
-    | distinct CorrelationId, UserName
-) on CorrelationId
-| summarize AvgRTT=avg(EstRoundTripTimeInMs),RTT_P95=percentile(EstRoundTripTimeInMs,95) by UserName
-| top 10 by AvgRTT desc
-```
-
-To look up the 10 users with the lowest bandwidth:
-
-```kusto
-WVDConnectionNetworkData
-| join kind=leftouter (
-    WVDConnections
-    | distinct CorrelationId, UserName
-) on CorrelationId
-| summarize AvgBW=avg(EstAvailableBandwidthKBps),BW_P95=percentile(EstAvailableBandwidthKBps,95) by UserName
-| top 10 by AvgBW asc
-```
-
-## Azure Front Door
-
-Azure Virtual Desktop uses [Azure Front Door](https://azure.microsoft.com/services/frontdoor/) to redirect the user connection to the nearest Azure Virtual Desktop gateway based on the source IP address. Azure Virtual Desktop will always use the Azure Virtual Desktop gateway that the client chooses.
-
 ## Next steps
 
+- 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 Virtual Desktop pricing](https://azure.microsoft.com/pricing/details/virtual-desktop/).
+- For pricing plans, see [Azure Log Analytics pricing](/services-hub/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).
 - To learn about Azure Virtual Desktop network connectivity, see [Understanding Azure Virtual Desktop network connectivity](network-connectivity.md).
diff --git a/articles/virtual-desktop/connection-quality-monitoring.md b/articles/virtual-desktop/connection-quality-monitoring.md
