Merge pull request #42321 from MicrosoftDocs/repo_sync_working_branch

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

Author: huypub

articles/aks/azure-disks-dynamic-pv.md

@@ -38,7 +38,7 @@ managed-premium     kubernetes.io/azure-disk   1h
 
 A persistent volume claim (PVC) is used to automatically provision storage based on a storage class. In this case, a PVC can use one of the pre-created storage classes to create a standard or premium Azure managed disk.
 
-Create a file named `azure-premimum.yaml`, and copy in the following manifest.
+Create a file named `azure-premium.yaml`, and copy in the following manifest.
 
 Take note that the `managed-premium` storage class is specified in the annotation, and the claim is requesting a disk `5GB` in size with `ReadWriteOnce` access.
 
@@ -60,7 +60,7 @@ spec:
 Create the persistent volume claim with the [kubectl apply][kubectl-apply] command.
 
 ```azurecli-interactive
-kubectl apply -f azure-premimum.yaml
+kubectl apply -f azure-premium.yaml
 ```
 
 ## Using the persistent volume
@@ -112,4 +112,4 @@ Learn more about Kubernetes persistent volumes using Azure disks.
 
 <!-- LINKS - internal -->
 [azure-files-pvc]: azure-files-dynamic-pv.md
-[premium-storage]: ../virtual-machines/windows/premium-storage.md
+[premium-storage]: ../virtual-machines/windows/premium-storage.md

articles/aks/kubernetes-walkthrough-portal.md

@@ -58,7 +58,7 @@ Select **Review + create** and then **Create** when complete.
 
 ![Create AKS cluster one](media/container-service-walkthrough-portal/aks-portal-3.png)
 
-After a short wait, the ASK cluster is deployed and ready to use. Browse to the AKS cluster resource group, select the AKS resource, and you should see the AKS cluster dashboard.
+After a short wait, the AKS cluster is deployed and ready to use. Browse to the AKS cluster resource group, select the AKS resource, and you should see the AKS cluster dashboard.
 
 ![Create AKS cluster one](media/container-service-walkthrough-portal/aks-portal-5.png)
 

articles/automation/automation-role-based-access-control.md

@@ -30,7 +30,7 @@ In Azure Automation, access is granted by assigning the appropriate RBAC role to
 | Log Analytics Contributor | The Log Analytics Contributor role allows you to read all monitoring data and edit monitoring settings. Editing monitoring settings includes adding the VM extension to VMs, reading storage account keys to be able to configure collection of logs from Azure storage, creating and configuring Automation accounts, adding solutions, and configuring Azure diagnostics on all Azure resources.|
 | Log Analytics Reader | The Log Analytics Reader role allows you to view and search all monitoring data as well as view monitoring settings. This includes viewing the configuration of Azure diagnostics on all Azure resources. |
 | Monitoring Contributor | The Monitoring Contributor role allows you to read all monitoring data and update monitoring settings.|
-| Monitoring Reader | The Montioring Reader role allows you to read all monitoring data. |
+| Monitoring Reader | The Monitoring Reader role allows you to read all monitoring data. |
 | User Access Administrator |The User Access Administrator role allows you to manage user access to Azure Automation accounts. |
 
 ## Role permissions

articles/azure-policy/azure-policy-introduction.md

@@ -67,7 +67,7 @@ accompanying effect that takes place if the conditions are met.
 In Azure Policy, we offer some built-in policies that are available to you by default. For example:
 
 - **Require SQL Server 12.0**: This policy definition has conditions/rules to ensure that all SQL servers use version 12.0. Its effect is to deny all servers that do not meet these criteria.
-- **Allowed Storage Account SKUs**: This policy definition has a set of conditions/rules that determine if a storage account that is being deployed is within a set of SKU sizes. Its effect is to deny all servers that do not adhere to the set of defined SKU sizes.
+- **Allowed Storage Account SKUs**: This policy definition has a set of conditions/rules that determine if a storage account that is being deployed is within a set of SKU sizes. Its effect is to deny all storage accounts that do not adhere to the set of defined SKU sizes.
 - **Allowed Resource Type**: This policy definition has a set of conditions/rules to specify the resource types that your organization can deploy. Its effect is to deny all resources that are not part of this defined list.
 - **Allowed Locations**: This policy enables you to restrict the locations that your organization can specify when deploying resources. Its effect is used to enforce your geo-compliance requirements.
 - **Allowed Virtual Machine SKUs**: This policy enables you to specify a set of virtual machine SKUs that your organization can deploy.
@@ -235,3 +235,4 @@ next steps:
 - [Assign a policy definition using PowerShell](assign-policy-definition-ps.md)
 - Review what a management group is with [Organize your resources with Azure Management Groups](../azure-resource-manager/management-groups-overview.md)
 - View [Govern your Azure environment through Azure Policy](https://channel9.msdn.com/events/Build/2018/THR2030) on Channel 9.
+

articles/cloud-shell/features.md

@@ -70,7 +70,7 @@ Bash in Cloud Shell includes pre-configured authentication for open-source tools
 |Go         |1.9        |
 |Java       |1.8        |
 |Node.js    |8.9.4      |
-|PowerShell |[6.0.1](https://github.com/PowerShell/powershell/releases)       |
+|PowerShell |[6.0.2](https://github.com/PowerShell/powershell/releases)       |
 |Python     |2.7 and 3.5 (default)|
 
 ## Next steps

articles/cloud-shell/quickstart-powershell.md

@@ -190,7 +190,7 @@ TestVm10   MyResourceGroup2   eastus    Standard_DS1_v2 Windows           mytest
 
   ``` PowerShell
   PS Azure:\> cd MySubscriptionName\MyResourceGroup\Microsoft.Compute\virtualMachines
-  PS Azure:\MySubscriptionName\MyResourceGroup\Microsoft.Compute\virtualMachines> Get-Item MyVM1 | Invoke-AzureRmVMCommand -Scriptblock{Get-ComputerInfo}
+  PS Azure:\MySubscriptionName\MyResourceGroup\Microsoft.Compute\virtualMachines> Get-Item MyVM1 | Invoke-AzureRmVMCommand -Scriptblock {Get-ComputerInfo}
   ```
   You see output similar to the following:
 

articles/cloud-shell/quickstart.md

@@ -91,7 +91,7 @@ exit
 
 2. Delete your resource group and any resources within it.
 ```azurecli-interactive
-Run `az group delete -n MyRG`
+az group delete -n MyRG
 ```
 
 ## Next steps

articles/cloud-shell/troubleshooting.md

@@ -1,4 +1,4 @@
----
+---
 title: Azure Cloud Shell troubleshooting | Microsoft Docs
 description: Troubleshooting Azure Cloud Shell
 services: azure
@@ -41,11 +41,6 @@ Known resolutions for troubleshooting issues in Azure Cloud Shell include:
 
 ## Bash troubleshooting
 
-### Cannot run az login
-
-- **Details**: Running `az login` will not work as you are already authenticated under the account used to sign into Cloud Shell or Azure portal.
-- **Resolution**: Utilize your account used to sign in or sign out and reauthenticate with your intended Azure account.
-
 ### Cannot run the docker daemon
 
 - **Details**: Cloud Shell utilizes a container to host your shell environment, as a result running the daemon is disallowed.

articles/cognitive-services/video-indexer/migrate-from-v1-to-v2.md

@@ -38,6 +38,8 @@ When calling the **Operations** APIs, the subscription key won't be used anymore
 
 Each request should have a valid token, matching the access level of the API you are calling. For example, operations on your user, such as getting your accounts, require a user access token. Operations on the account level, such as list all videos, require an account access token. Operations on videos, such as reindex video, require a video access token.
 
+To make things easier, you can use **Authorization** API > **GetAccounts** to get your accounts without obtaining a user token first. You can also ask to get the accounts with valid tokens, enabling you to skip an additional call to get an account token.
+
 For more information about the different access tokens, see [Use Azure Video Indexer API](video-indexer-use-apis.md).
 
 ### Locations

articles/cognitive-services/video-indexer/video-indexer-use-apis.md

@@ -54,6 +54,8 @@ Each call to the Operations API should be associated with an access token, match
 - Account level – account level access tokens let you perform operations on the account level. for example, Upload video, list all videos, create a language model, etc.
 - Video level – video level access tokens let you perform operations on specific videos. for example, get video insights, download captions, get widgets, etc. 
 
+To make things easier, you can use the **Authorization** API > **GetAccounts** to get your accounts without obtaining a user token first. You can also ask to get the accounts with valid tokens, enabling you to skip an additional call to get an account token.
+
 Access tokens expire after 1 hour. Make sure your access token is valid before using the Operations API. If expires, call the Authorization API again to get a new access token.
 
 You are ready to start integrating with the API. Find [the detailed description of each Video Indexer REST API](http://api-portal.videoindexer.ai/).