Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into clarLive

roygara · roygara · commit 646ef01a30c0 · 2022-07-27T15:38:17.000-07:00
diff --git a/articles/azure-arc/kubernetes/agent-upgrade.md b/articles/azure-arc/kubernetes/agent-upgrade.md
@@ -3,7 +3,7 @@ title: "Upgrading Azure Arc-enabled Kubernetes agents"
 services: azure-arc
 ms.service: azure-arc
 ms.date: 03/03/2021
-ms.topic: article
+ms.topic: how-to
 description: "Control agent upgrades for Azure Arc-enabled Kubernetes"
 keywords: "Kubernetes, Arc, Azure, K8s, containers, agent, upgrade"
 ---
diff --git a/articles/azure-arc/kubernetes/azure-rbac.md b/articles/azure-arc/kubernetes/azure-rbac.md
@@ -3,7 +3,7 @@ title: "Azure RBAC for Azure Arc-enabled Kubernetes clusters"
 services: azure-arc
 ms.service: azure-arc
 ms.date: 04/05/2021
-ms.topic: article
+ms.topic: how-to
 description: "Use Azure RBAC for authorization checks on Azure Arc-enabled Kubernetes clusters."
 ---
 
diff --git a/articles/azure-arc/kubernetes/extensions.md b/articles/azure-arc/kubernetes/extensions.md
@@ -4,7 +4,7 @@ services: azure-arc
 ms.service: azure-arc
 ms.custom: event-tier1-build-2022
 ms.date: 07/12/2022
-ms.topic: article
+ms.topic: how-to
 description: "Deploy and manage lifecycle of extensions on Azure Arc-enabled Kubernetes"
 ---
 
diff --git a/articles/azure-arc/kubernetes/troubleshooting.md b/articles/azure-arc/kubernetes/troubleshooting.md
@@ -4,7 +4,7 @@ services: azure-arc
 ms.service: azure-arc
 #ms.subservice: azure-arc-kubernetes coming soon
 ms.date: 06/13/2022
-ms.topic: article
+ms.topic: how-to
 description: "Learn how to resolve common issues with Azure Arc-enabled Kubernetes clusters and GitOps."
 keywords: "Kubernetes, Arc, Azure, containers, GitOps, Flux"
 ---
diff --git a/articles/azure-arc/kubernetes/tutorial-akv-secrets-provider.md b/articles/azure-arc/kubernetes/tutorial-akv-secrets-provider.md
@@ -4,7 +4,7 @@ description: Learn how to set up the Azure Key Vault Provider for Secrets Store
 services: azure-arc
 ms.service: azure-arc
 ms.date: 5/26/2022
-ms.topic: article
+ms.topic: tutorial
 author: mayurigupta13
 ms.author: mayg
 ---
diff --git a/articles/azure-arc/kubernetes/tutorial-arc-enabled-open-service-mesh.md b/articles/azure-arc/kubernetes/tutorial-arc-enabled-open-service-mesh.md
@@ -3,7 +3,7 @@ title: Azure Arc-enabled Open Service Mesh
 description: Open Service Mesh (OSM) extension on Azure Arc-enabled Kubernetes cluster
 ms.service: azure-arc
 ms.date: 05/25/2022
-ms.topic: article
+ms.topic: tutorial
 author: mayurigupta13
 ms.author: mayg
 ---
diff --git a/articles/azure-arc/kubernetes/use-azure-policy.md b/articles/azure-arc/kubernetes/use-azure-policy.md
@@ -4,7 +4,7 @@ services: azure-arc
 ms.service: azure-arc
 #ms.subservice: azure-arc-kubernetes coming soon
 ms.date: 11/23/2021
-ms.topic: article
+ms.topic: how-to
 description: "Apply configurations at-scale using Azure Policy"
 keywords: "Kubernetes, Arc, Azure, K8s, containers"
 ---
diff --git a/articles/azure-arc/kubernetes/use-gitops-with-helm.md b/articles/azure-arc/kubernetes/use-gitops-with-helm.md
@@ -4,7 +4,7 @@ services: azure-arc
 ms.service: azure-arc
 #ms.subservice: azure-arc-kubernetes coming soon
 ms.date: 05/24/2022
-ms.topic: article
+ms.topic: how-to
 description: "Use GitOps with Helm for an Azure Arc-enabled cluster configuration"
 keywords: "GitOps, Kubernetes, K8s, Azure, Helm, Arc, AKS, Azure Kubernetes Service, containers"
 ---
diff --git a/articles/azure-arc/kubernetes/validation-program.md b/articles/azure-arc/kubernetes/validation-program.md
@@ -3,7 +3,7 @@ title: "Azure Arc-enabled Kubernetes validation"
 services: azure-arc
 ms.service: azure-arc
 ms.date: 03/03/2021
-ms.topic: article
+ms.topic: how-to
 description: "Describes Arc validation program for Kubernetes distributions"
 keywords: "Kubernetes, Arc, Azure, K8s, validation"
 ---
diff --git a/articles/chaos-studio/chaos-studio-fault-providers.md b/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 |
diff --git a/articles/chaos-studio/chaos-studio-samples-rest-api.md b/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) |
diff --git a/articles/chaos-studio/chaos-studio-tutorial-aks-portal.md b/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.
diff --git a/articles/chaos-studio/sample-template-experiment.md b/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>"
       }
   }
 }
diff --git a/articles/cognitive-services/language-service/question-answering/includes/sdk-python.md b/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:
diff --git a/articles/communication-services/quickstarts/chat/includes/chat-swift.md b/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")
     }
diff --git a/articles/container-instances/container-instances-quickstart-portal.md b/articles/container-instances/container-instances-quickstart-portal.md
@@ -6,7 +6,7 @@ ms.author: tomcassidy
 author: tomvcassidy
 ms.service: container-instances
 services: container-instances
-ms.date: 06/17/2022
+ms.date: 07/26/2022
 ms.custom: mvc, devx-track-js, mode-ui
 ---
 
@@ -26,34 +26,51 @@ If you don't have an Azure subscription, create a [free account][azure-free-acco
 
 ## Create a container instance
 
-Select the **Create a resource** > **Containers** > **Container Instances**.
+On the Azure portal homepage, select **Create a resource**.
 
-:::image type="content" source="media/container-instances-quickstart-portal/qs-portal-01.png" alt-text="Begin creating a new container instance in the Azure portal":::
+:::image type="content" source="media/container-instances-quickstart-portal/quickstart-portal-create-resource.png" alt-text="Screenshot showing how to begin creating a new container instance in the Azure portal.":::
 
-On the **Basics** page, enter the following values in the **Resource group**, **Container name**, and **Container image** text boxes. Leave the other values at their defaults, then select **OK**.
+Select **Containers** > **Container Instances**.
+
+:::image type="content" source="media/container-instances-quickstart-portal/qs-portal-01.png" alt-text="Screenshot showing how to select a new container instance that you want to create in the Azure portal.":::
+
+On the **Basics** page, choose a subscription and enter the following values for **Resource group**, **Container name**, **Image source**, and **Container image**.
 
 * Resource group: **Create new** > `myresourcegroup`
 * Container name: `mycontainer`
 * Image source: **Quickstart images**
-* Container image: `mcr.microsoft.com/azuredocs/aci-helloworld` (Linux)
+* Container image: `mcr.microsoft.com/azuredocs/aci-helloworld:latest` (Linux)
 
 :::image type="content" source="media/container-instances-quickstart-portal/qs-portal-03.png" alt-text="Configuring basic settings for a new container instance in the Azure portal":::
 
-For this quickstart, you use default settings to deploy the public Microsoft `aci-helloworld` image. This sample Linux image packages a small web app written in Node.js that serves a static HTML page. You can also bring your own container images stored in Azure Container Registry, Docker Hub, or other registries.
+> [!NOTE]
+> For this quickstart, you use default settings to deploy the public Microsoft `aci-helloworld:latest` image. This sample Linux image packages a small web app written in Node.js that serves a static HTML page. You can also bring your own container images stored in Azure Container Registry, Docker Hub, or other registries.
+
+Leave the other values as their defaults, then select **Next: Networking**.
 
 On the **Networking** page, specify a **DNS name label** for your container. The name must be unique within the Azure region where you create the container instance. Your container will be publicly reachable at `<dns-name-label>.<region>.azurecontainer.io`. If you receive a "DNS name label not available" error message, try a different DNS name label.
 
+An auto-generated hash is added as a DNS name label to your container instance's fully qualified domain name (FQDN), which prevents malicious subdomain takeover. Specify the **DNS name label scope reuse** for the FQDN. You can choose one of these options:
+
+* Tenant
+* Subscription
+* Resource Group
+* No reuse
+* Any reuse (This option is the least secure.)
+
+For this example, select **Tenant**.
+
 :::image type="content" source="media/container-instances-quickstart-portal/qs-portal-04.png" alt-text="Configuring network settings for a new container instance in the Azure portal":::
 
-Leave the other settings at their defaults, then select **Review + create**.
+Leave all other settings as their defaults, then select **Review + create**.
 
 When the validation completes, you're shown a summary of the container's settings. Select **Create** to submit your container deployment request.
 
 :::image type="content" source="media/container-instances-quickstart-portal/qs-portal-05.png" alt-text="Settings summary for a new container instance in the Azure portal":::
 
-When deployment starts, a notification appears to indicate the deployment is in progress. Another notification is displayed when the container group has been deployed.
+When deployment starts, a notification appears that indicates the deployment is in progress. Another notification is displayed when the container group has been deployed.
 
-Open the overview for the container group by navigating to **Resource Groups** > **myresourcegroup** > **mycontainer**. Take note of the **FQDN** (the fully qualified domain name) of the container instance, as well its **Status**.
+Open the overview for the container group by navigating to **Resource Groups** > **myresourcegroup** > **mycontainer**. Make a note of the **FQDN** of the container instance and its **Status**.
 
 :::image type="content" source="media/container-instances-quickstart-portal/qs-portal-06.png" alt-text="Container group overview in the Azure portal":::
 
@@ -67,7 +84,7 @@ Congratulations! By configuring just a few settings, you've deployed a publicly
 
 Viewing the logs for a container instance is helpful when troubleshooting issues with your container or the application it runs.
 
-To view the container's logs, under **Settings**, select **Containers**, then **Logs**. You should see the HTTP GET request generated when you viewed the application in your browser.
+To view the container's logs, under **Settings**, select **Containers** > **Logs**. You should see the HTTP GET request generated when you viewed the application in your browser.
 
 :::image type="content" source="media/container-instances-quickstart-portal/qs-portal-11.png" alt-text="Container logs in the Azure portal":::
 
diff --git a/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-01.png b/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-01.png
diff --git a/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-03.png b/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-03.png
diff --git a/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-04.png b/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-04.png
diff --git a/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-05.png b/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-05.png
diff --git a/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-06.png b/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-06.png
diff --git a/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-09.png b/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-09.png
diff --git a/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-11.png b/articles/container-instances/media/container-instances-quickstart-portal/qs-portal-11.png
diff --git a/articles/container-instances/media/container-instances-quickstart-portal/quickstart-portal-create-resource.png b/articles/container-instances/media/container-instances-quickstart-portal/quickstart-portal-create-resource.png
diff --git a/articles/cosmos-db/sql/how-to-use-stored-procedures-triggers-udfs.md b/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 |
diff --git a/articles/virtual-machines/disks-types.md b/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).
 
