Merge pull request #206130 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: huypub

articles/chaos-studio/chaos-studio-fault-providers.md

@@ -14,7 +14,7 @@ ms.custom: ignite-fall-2021
 
 The following are the supported resource types for faults, the target types, and suggested roles to use when giving an experiment permission to a resource of that type.
 
-| Resource Type | Target name | Suggested role assignment |
+| Resource Type | Target name/type | Suggested role assignment |
 | - | - | - |
 | Microsoft.Cache/Redis (service-direct) | Microsoft-AzureCacheForRedis | Redis Cache Contributor |
 | Microsoft.ClassicCompute/domainNames (service-direct) | Microsoft-DomainNames | Classic Virtual Machine Contributor |

articles/chaos-studio/chaos-studio-samples-rest-api.md

@@ -90,7 +90,7 @@ az rest --method delete --url "https://management.azure.com/{experimentId}?api-v
 #### Start an experiment
 
 ```azurecli
-az rest --method get --url "https://management.azure.com/{experimentId}/start?api-version={apiVersion}" --resource "https://management.azure.com"
+az rest --method post --url "https://management.azure.com/{experimentId}/start?api-version={apiVersion}"
 ```
 
 #### Get statuses (History) of an experiment
@@ -133,4 +133,4 @@ az rest --method get --url "https://management.azure.com/{experimentId}/executio
 | {experimentName.json} | JSON containing the configuration of the chaos experiment | Generated by the user |
 | {subscriptionId} | Subscription Id where the target resource is located | Can be found in the [Subscriptions Portal Blade](https://portal.azure.com/#blade/Microsoft_Azure_Billing/SubscriptionsBlade) |
 | {resourceGroupName} | Name of the resource group where the target resource is located | Can be fond in the [Resource Groups Portal Blade](https://portal.azure.com/#blade/HubsExtension/BrowseResourceGroups) |
-| {executionDetailsId} | Execution Id of an experiment execution | Can be found in the [Chaos Studio Experiment Portal Blade](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.chaos%2Fchaosexperiments) |
+| {executionDetailsId} | Execution Id of an experiment execution | Can be found in the [Chaos Studio Experiment Portal Blade](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.chaos%2Fchaosexperiments) |

articles/chaos-studio/chaos-studio-tutorial-aks-portal.md

@@ -23,6 +23,9 @@ Azure Chaos Studio uses [Chaos Mesh](https://chaos-mesh.org/), a free, open-sour
 > [!WARNING]
 > AKS Chaos Mesh faults are only supported on Linux node pools.
 
+## Limitations
+- At present Chaos Mesh faults don’t work with private clusters.
+
 ## Set up Chaos Mesh on your AKS cluster
 
 Before you can run Chaos Mesh faults in Chaos Studio, you need to install Chaos Mesh on your AKS cluster.

articles/chaos-studio/sample-template-experiment.md

@@ -119,7 +119,7 @@ In this sample, we create a chaos experiment with a single target resource and a
         "value": "eastus"
       },
       "chaosTargetResourceId": {
-        "value": "eastus"
+        "value": "/subscriptions/<subscription-id>/resourceGroups/<rg-name>/providers/Microsoft.DocumentDB/databaseAccounts/<account-name>"
       }
   }
 }

articles/cognitive-services/language-service/question-answering/includes/sdk-python.md

@@ -103,7 +103,7 @@ For information on how confident question answering is that this is the correct
 ```python
 print("Q: {}".format(question))
 print("A: {}".format(output.answers[0].answer))
-print("Confidence Score: {}".format(output.answers[0].confidence_score)) # add this line 
+print("Confidence Score: {}".format(output.answers[0].confidence)) # add this line 
 ```
 
 You will now receive a result with a confidence score:

articles/communication-services/quickstarts/chat/includes/chat-swift.md

@@ -345,7 +345,11 @@ let user = ChatParticipant(
 chatThreadClient.add(participants: [user]) { result, _ in
     switch result {
     case let .success(result):
-        (result.invalidParticipants != nil) ? print("Added participant") : print("Error adding participant")
+        if let errors = result.invalidParticipants, !errors.isEmpty {
+            print("Error adding participant")
+        } else {
+            print("Added participant")
+        }
     case .failure:
         print("Failed to add the participant")
     }

articles/cosmos-db/sql/how-to-use-stored-procedures-triggers-udfs.md

@@ -17,8 +17,6 @@ ms.custom: devx-track-python, devx-track-js, devx-track-csharp
 
 The SQL API in Azure Cosmos DB supports registering and invoking stored procedures, triggers, and user-defined functions (UDFs) written in JavaScript. Once you've defined one or more stored procedures, triggers, and user-defined functions, you can load and view them in the [Azure portal](https://portal.azure.com/) by using Data Explorer.
 
-SQL API SDKs are available for a wide variety of platforms and programming languages. If you haven't worked 
-
 You can use the SQL API SDK across multiple platforms including [.NET v2 (legacy)](sql-api-sdk-dotnet.md), [.NET v3](sql-api-sdk-dotnet-standard.md), [Java](sql-api-sdk-java.md), [JavaScript](sql-api-sdk-node.md), or [Python](sql-api-sdk-python.md) SDKs to perform these tasks. If you haven't worked with one of these SDKs before, see the *"Quickstart"* article for the appropriate SDK:
 
 | SDK | Getting started |

articles/virtual-machines/disks-types.md

@@ -130,9 +130,9 @@ Premium SSD v2 supports a 4k physical sector size by default. A 512E sector size
 
 The following table provides a comparison of disk capacities and performance maximums to help you decide which to use.
 
-|Disk Size (GiB)  |Maximum available IOPS  |Maximum available throughput (MB/s)  |
+|Disk Size  |Maximum available IOPS  |Maximum available throughput (MB/s)  |
 |---------|---------|---------|
-|1-64    |3,000-80,000 (Increases by 500 IOPS per GiB)        |125-1,200 (increases by 0.25 MB/s per set IOPS)         |
+|1 GiB-64 TiB    |3,000-80,000 (Increases by 500 IOPS per GiB)        |125-1,200 (increases by 0.25 MB/s per set IOPS)         |
 
 To deploy a Premium SSD v2, see [Deploy a Premium SSD v2 (preview)](disks-deploy-premium-v2.md).