Merge pull request #261728 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-monitor/app/opentelemetry-add-modify.md

@@ -230,10 +230,15 @@ You can collect more data automatically when you include instrumentation librari
 
 ### [ASP.NET Core](#tab/aspnetcore)
 
-To add a community library, use the `ConfigureOpenTelemetryMeterProvider` or `ConfigureOpenTelemetryTracerProvider` methods.
+To add a community library, use the `ConfigureOpenTelemetryMeterProvider` or `ConfigureOpenTelemetryTracerProvider` methods,
+after adding the nuget package for the library.
 
 The following example demonstrates how the [Runtime Instrumentation](https://www.nuget.org/packages/OpenTelemetry.Instrumentation.Runtime) can be added to collect extra metrics.
 
+```dotnetcli
+dotnet add package OpenTelemetry.Instrumentation.Runtime 
+```
+
 ```csharp
 // Create a new ASP.NET Core web application builder.
 var builder = WebApplication.CreateBuilder(args);

articles/azure-monitor/app/opentelemetry-configuration.md

@@ -702,7 +702,7 @@ You might want to enable the OpenTelemetry Protocol (OTLP) Exporter alongside th
 1. Install the [OpenTelemetry.Exporter.OpenTelemetryProtocol](https://www.nuget.org/packages/OpenTelemetry.Exporter.OpenTelemetryProtocol/) package in your project.
 
     ```dotnetcli
-    dotnet add package --prerelease OpenTelemetry.Exporter.OpenTelemetryProtocol
+    dotnet add package OpenTelemetry.Exporter.OpenTelemetryProtocol
     ```
 
 1. Add the following code snippet. This example assumes you have an OpenTelemetry Collector with an OTLP receiver running. For details, see the [example on GitHub](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/examples/Console/TestOtlpExporter.cs).

articles/cosmos-db/index-policy.md

@@ -131,7 +131,7 @@ Azure Cosmos DB, by default, won't create any spatial indexes. If you would like
 
 Queries that have an `ORDER BY` clause with two or more properties require a composite index. You can also define a composite index to improve the performance of many equality and range queries. By default, no composite indexes are defined so you should [add composite indexes](how-to-manage-indexing-policy.md#composite-index) as needed.
 
-Unlike with included or excluded paths, you can't create a path with the `/*` wildcard. Every composite path has an implicit `/?` at the end of the path that you don't need to specify. Composite paths lead to a scalar value that is the only value included in the composite index. If a path in a composite index doesn't exist in an item, a value will be added to the index to indicate that the path is undefined.
+Unlike with included or excluded paths, you can't create a path with the `/*` wildcard. Every composite path has an implicit `/?` at the end of the path that you don't need to specify. Composite paths lead to a scalar value that is the only value included in the composite index. If a path in a composite index doesn't exist in an item or leads to a non-scalar value, a value will be added to the index to indicate that the path is undefined.
 
 When defining a composite index, you specify:
 

articles/cosmos-db/table/how-to-use-nodejs.md

@@ -257,7 +257,7 @@ const entities = tableClient.listEntities({
 });
 
 let topEntities = [];
-const iterator = listResults.byPage({ maxPageSize: topN });
+const iterator = entities.byPage({ maxPageSize: topN });
 
 for await (const page of iterator) {
   topEntities = page;

articles/dev-box/dev-box-faq.yml

@@ -51,7 +51,15 @@ sections:
           For optimal latency, we recommend creating pools close to the developer’s physical location. For example, if a developer is based in India, we recommend creating a dev box in the Central India region. This is generally thought of as a best practice to improve typing speeds as developers work within their dev boxes.  
 
           Developers primarily spend their time typing and moving their mouse within their Dev Box. We recommend optimizing for typing latency, since these actions will affect development teams the most. 
-          
+      
+      - question: Can I look up in which regions I should create my pools?  
+        answer: |
+          Whether you’re creating a new pool, or choosing a pool for creating a dev box, it's important to optimize for latency and performance. It can be difficult to determine the optimal region for developers to host their dev boxes.  
+
+          For best results, we recommend that admins ask the developers to use the [Azure Virtual Desktop Experience Estimator](https://aka.ms/avd-estimator). This tool estimates the connection round trip time (RTT) from the developer’s physical location, through the Azure Virtual Desktop service, to each Azure region in which you can deploy your dev box. The highlighted region is the region with the lowest RTT from your current location. This is the region where the developer will experience optimal connectivity.  
+
+          If there isn't a pool for that region yet, we recommend that you create a new pool for that region or for the next best option according to the estimator.  
+     
       - question: How are backup, high-availability, and disaster recovery implemented in Microsoft Dev Box? 
         answer: |
           Microsoft Intune provides backup functionality for dev boxes. It automatically sets regular restore points, and enables you to create a manual restore point, just as you would for a [Cloud PC](/windows-365/enterprise/create-manual-restore-point).

articles/synapse-analytics/sql-data-warehouse/sql-data-warehouse-service-capacity-limits.md

@@ -48,6 +48,7 @@ Maximum values allowed for various components of dedicated SQL pool in Azure Syn
 | Statistics |Statistics created on columns per table. |30,000 |
 | Stored Procedures |Maximum levels of nesting. |8 |
 | View |Columns per view |1,024 |
+| Workload Classifier |User-defined classifier  |100 |
 ||||
 
 ## Loads