Update links to cloud-shell docs

Author: sdwheeler

articles/cosmos-db/how-to-container-copy.md

@@ -19,7 +19,7 @@ This article describes how to create, monitor, and manage intra-account containe
 
 ## Pre-requisites
 
-* You may use the portal [Cloud Shell](../cloud-shell/quickstart-powershell.md#start-cloud-shell) to run container copy commands. Alternately, you may run the commands locally; make sure you have [Azure CLI](/cli/azure/install-azure-cli) or [Azure PowerShell](/powershell/azure/install-az-ps-msi) downloaded and installed on your machine.
+* You may use the portal [Cloud Shell](/azure/cloud-shell/quickstart?tabs=powershell) to run container copy commands. Alternately, you may run the commands locally; make sure you have [Azure CLI](/cli/azure/install-azure-cli) or [Azure PowerShell](/powershell/azure/install-az-ps-msi) downloaded and installed on your machine.
 * Currently, container copy is only supported in [these regions](intra-account-container-copy.md#supported-regions). Make sure your account's write region belongs to this list.
 
 
@@ -51,7 +51,7 @@ Create a job to copy a container within an Azure Cosmos DB API for NoSQL account
 
 ```azurepowershell-interactive
 az cosmosdb dts copy `
-    --resource-group $resourceGroup ` 
+    --resource-group $resourceGroup `
     --account-name $accountName `
     --job-name $jobName `
     --source-sql-container database=$sourceDatabase container=$sourceContainer `

articles/cosmos-db/intra-account-container-copy.md

@@ -141,7 +141,7 @@ Currently, container copy is supported in the following regions:
 
 * Error - (Request) is blocked by your Cosmos DB account firewall settings.
 
-    The job creation request could be blocked if the client IP isn't allowed as per the VNet and Firewall IPs configured on the account. In order to get past this issue, you need to [allow access to the IP through the Firewall setting](how-to-configure-firewall.md). Alternately, you may set **Accept connections from within public Azure datacenters** in your firewall settings and run the container copy commands through the portal [Cloud Shell](../cloud-shell/quickstart-powershell.md#start-cloud-shell).
+    The job creation request could be blocked if the client IP isn't allowed as per the VNet and Firewall IPs configured on the account. In order to get past this issue, you need to [allow access to the IP through the Firewall setting](how-to-configure-firewall.md). Alternately, you may set **Accept connections from within public Azure datacenters** in your firewall settings and run the container copy commands through the portal [Cloud Shell](/azure/cloud-shell/quickstart?tabs=powershell).
 
     ```output
     InternalServerError Request originated from IP xxx.xxx.xxx.xxx through public internet. This is blocked by your Cosmos DB account firewall settings. More info: https://aka.ms/cosmosdb-tsg-forbidden

articles/databox-online/azure-stack-edge-gpu-deploy-arc-kubernetes-cluster.md

@@ -15,7 +15,7 @@ ms.author: alkohli
 
 [!INCLUDE [applies-to-GPU-and-pro-r-and-mini-r-skus](../../includes/azure-stack-edge-applies-to-gpu-pro-r-mini-r-sku.md)]
 
-This article shows you how to enable Azure Arc on an existing Kubernetes cluster on your Azure Stack Edge Pro device. 
+This article shows you how to enable Azure Arc on an existing Kubernetes cluster on your Azure Stack Edge Pro device.
 
 This procedure is intended for those who have reviewed the [Kubernetes workloads on Azure Stack Edge Pro device](azure-stack-edge-gpu-kubernetes-workload-management.md) and are familiar with the concepts of [What is Azure Arc-enabled Kubernetes (Preview)?](../azure-arc/kubernetes/overview.md).
 
@@ -31,44 +31,44 @@ Before you can enable Azure Arc on Kubernetes cluster, make sure that you have c
     1. The device has the compute role configured via Azure portal and has a Kubernetes cluster. See [Configure compute](azure-stack-edge-gpu-deploy-configure-compute.md).
 
 1. You've owner access to the subscription. You would need this access during the role assignment step for your service principal.
- 
+
 
 ### For client accessing the device
 
 1. You have a  Windows client system that will be used to access the Azure Stack Edge Pro device.
-  
+
     - The client is running Windows PowerShell 5.0 or later. To download the latest version of Windows PowerShell, go to [Install Windows PowerShell](/powershell/scripting/install/installing-powershell-core-on-windows).
-    
-    - You can have any other client with a [Supported operating system](azure-stack-edge-gpu-system-requirements.md#supported-os-for-clients-connected-to-device) as well. This article describes the procedure when using a Windows client. 
-    
-    
+
+    - You can have any other client with a [Supported operating system](azure-stack-edge-gpu-system-requirements.md#supported-os-for-clients-connected-to-device) as well. This article describes the procedure when using a Windows client.
+
+
 1. You have completed the procedure described in [Access the Kubernetes cluster on Azure Stack Edge Pro device](azure-stack-edge-gpu-create-kubernetes-cluster.md). You have:
-    
-    - Installed `kubectl` on the client.    
-    - Make sure that the `kubectl` client version is skewed no more than one version from the Kubernetes master version running on your Azure Stack Edge Pro device. 
+
+    - Installed `kubectl` on the client.
+    - Make sure that the `kubectl` client version is skewed no more than one version from the Kubernetes master version running on your Azure Stack Edge Pro device.
       - Use `kubectl version` to check the version of kubectl running on the client. Make a note of the full version.
-      - In the local UI of your Azure Stack Edge Pro device, go to **Software update** and note the Kubernetes server version number. 
-    
-        ![Verify Kubernetes server version number](media/azure-stack-edge-gpu-connect-powershell-interface/verify-kubernetes-version-1.png)      
-      
-      - Verify these two versions are compatible. 
+      - In the local UI of your Azure Stack Edge Pro device, go to **Software update** and note the Kubernetes server version number.
+
+        ![Verify Kubernetes server version number](media/azure-stack-edge-gpu-connect-powershell-interface/verify-kubernetes-version-1.png)
+
+      - Verify these two versions are compatible.
 
 
 ## Register Kubernetes resource providers
 
-Before you enable Azure Arc on the Kubernetes cluster, you will need to enable and register `Microsoft.Kubernetes` and `Microsoft.KubernetesConfiguration` against your subscription. 
+Before you enable Azure Arc on the Kubernetes cluster, you will need to enable and register `Microsoft.Kubernetes` and `Microsoft.KubernetesConfiguration` against your subscription.
 
-1. To enable a resource provider, in the Azure portal, go to the subscription that you are planning to use for the deployment. Go to **Resource Providers**. 
+1. To enable a resource provider, in the Azure portal, go to the subscription that you are planning to use for the deployment. Go to **Resource Providers**.
 1. In the right-pane, search for the providers you want to add. In this example, `Microsoft.Kubernetes` and `Microsoft.KubernetesConfiguration`.
 
     ![Register Kubernetes resource providers](media/azure-stack-edge-gpu-connect-powershell-interface/register-k8-resource-providers-1.png)
 
-1. Select a resource provider and from the top of the command bar, select **Register**. Registration  takes several minutes. 
+1. Select a resource provider and from the top of the command bar, select **Register**. Registration  takes several minutes.
 
     ![Register Kubernetes resource providers 2](media/azure-stack-edge-gpu-connect-powershell-interface/register-k8-resource-providers-2.png)
 
 1. Refresh the UI until you see that the resource provider is registered. Repeat the process for both resource providers.
-    
+
     ![Register Kubernetes resource providers 3](media/azure-stack-edge-gpu-connect-powershell-interface/register-k8-resource-providers-4.png)
 
 You can also register resource providers via the `az cli`. For more information, see [Register the two providers for Azure Arc-enabled Kubernetes](../azure-arc/kubernetes/quickstart-connect-cluster.md#register-providers-for-azure-arc-enabled-kubernetes).
@@ -85,12 +85,12 @@ You can also register resource providers via the `az cli`. For more information,
 
 1. To create a service principal, use the following command via the `az cli`.
 
-    `az ad sp create-for-rbac --name "<Informative name for service principal>"`  
+    `az ad sp create-for-rbac --name "<Informative name for service principal>"`
 
-    For information on how to log into the `az cli`, [Start Cloud Shell in Azure portal](../cloud-shell/quickstart-powershell.md#start-cloud-shell). If using `az cli` on a local client to create the service principal, make sure that you are running version 2.25 or later.
+    For information on how to log into the `az cli`, [Start Cloud Shell in Azure portal](/azure/cloud-shell/quickstart). If using `az cli` on a local client to create the service principal, make sure that you are running version 2.25 or later.
+
+    Here is an example.
 
-    Here is an example. 
-    
     ```azurecli
     PS /home/user> az ad sp create-for-rbac --name "https://azure-arc-for-ase-k8s"
     {
@@ -110,7 +110,7 @@ You can also register resource providers via the `az cli`. For more information,
     `az role assignment create --role 34e09817-6cbe-4d01-b1a2-e0eac5743d41 --assignee <appId-from-service-principal> --scope /subscriptions/<SubscriptionID>/resourceGroups/<Resource-group-name>`
 
     Here is an example.
-    
+
     ```azurecli
     PS /home/user> az role assignment create --role 34e09817-6cbe-4d01-b1a2-e0eac5743d41 --assignee xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx --scope /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/myaserg1
     {
@@ -136,22 +136,22 @@ Follow these steps to configure the Kubernetes cluster for Azure Arc management:
 
 1. Type:
 
-    `Set-HcsKubernetesAzureArcAgent -SubscriptionId "<Your Azure Subscription Id>" -ResourceGroupName "<Resource Group Name>" -ResourceName "<Azure Arc resource name (shouldn't exist already)>" -Location "<Region associated with resource group>" -TenantId "<Tenant Id of service principal>" -ClientId "<App id of service principal>"` 
-    
+    `Set-HcsKubernetesAzureArcAgent -SubscriptionId "<Your Azure Subscription Id>" -ResourceGroupName "<Resource Group Name>" -ResourceName "<Azure Arc resource name (shouldn't exist already)>" -Location "<Region associated with resource group>" -TenantId "<Tenant Id of service principal>" -ClientId "<App id of service principal>"`
+
     When this command is run, there is a followup prompt to enter the `ClientSecret`. Provide the service principal password.
 
     Add the `CloudEnvironment` parameter if you are using a cloud other than Azure public. You can set this parameter to `AZUREPUBLICCLOUD`, `AZURECHINACLOUD`, `AZUREGERMANCLOUD`, and `AZUREUSGOVERNMENTCLOUD`.
 
     > [!NOTE]
-    > - To deploy Azure Arc on your device, make sure that you are using a [Supported region for Azure Arc](https://azure.microsoft.com/global-infrastructure/services/?products=azure-arc). 
+    > - To deploy Azure Arc on your device, make sure that you are using a [Supported region for Azure Arc](https://azure.microsoft.com/global-infrastructure/services/?products=azure-arc).
     > - Use the `az account list-locations` command to figure out the exact location name to pass in the `Set-HcsKubernetesAzureArcAgent` cmdlet. Location names are typically formatted without any spaces.
-    > - `ClientId` and `ClientSecret` are required. 
-    
+    > - `ClientId` and `ClientSecret` are required.
+
     Here is an example:
-   
+
     ```powershell
     [10.100.10.10]: PS>Set-HcsKubernetesAzureArcAgent -SubscriptionId "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -ResourceGroupName "myaserg1" -ResourceName "myasetestresarc" -Location "westeurope" -TenantId "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" -ClientId "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
-    
+
     WARNING: A script or application on the remote computer 10.126.76.0 is sending a prompt request. When you are prompted,
     enter sensitive information, such as credentials or passwords, only if you trust the remote computer and the
     application or script that is requesting the data.
@@ -162,7 +162,7 @@ Follow these steps to configure the Kubernetes cluster for Azure Arc management:
     ClientSecret: **********************************
     [10.100.10.10]: PS>
     ```
-    
+
     In the Azure portal, a resource should be created with the name you provided in the preceding command.
 
     ![Go to Azure Arc resource](media/azure-stack-edge-gpu-connect-powershell-interface/verify-azure-arc-enabled-1.png)
@@ -171,7 +171,7 @@ Follow these steps to configure the Kubernetes cluster for Azure Arc management:
 
     `kubectl get deployments,pods -n azure-arc`
 
-    Here is a sample output that shows the Azure Arc agents that were deployed on your Kubernetes cluster in the `azure-arc` namespace. 
+    Here is a sample output that shows the Azure Arc agents that were deployed on your Kubernetes cluster in the `azure-arc` namespace.
 
     ```powershell
     [10.128.44.240]: PS>kubectl get deployments,pods -n azure-arc
@@ -210,13 +210,13 @@ To remove the Azure Arc management, follow these steps:
 1. 1. [Connect to the PowerShell interface](azure-stack-edge-gpu-connect-powershell-interface.md#connect-to-the-powershell-interface) of your device.
 2. Type:
 
-    `Remove-HcsKubernetesAzureArcAgent` 
+    `Remove-HcsKubernetesAzureArcAgent`
 
 
 > [!NOTE]
 > By default, when resource `yamls` are deleted from the Git repository, the corresponding resources are not deleted from the Kubernetes cluster. You need to set `--sync-garbage-collection`  in Arc OperatorParams to allow the deletion of resources when deleted from git repository. For more information, see [Delete a configuration](../azure-arc/kubernetes/tutorial-use-gitops-connected-cluster.md#additional-parameters)
 
 ## Next steps
 
-To understand how to run an Azure Arc deployment, see 
+To understand how to run an Azure Arc deployment, see
 [Deploy a stateless PHP `Guestbook` application with Redis via GitOps on an Azure Stack Edge Pro device](azure-stack-edge-gpu-deploy-stateless-application-git-ops-guestbook.md)

articles/devtest-labs/devtest-lab-vm-powershell.md

@@ -17,7 +17,7 @@ This article shows you how to create an Azure DevTest Labs virtual machine (VM)
 You need the following prerequisites to work through this article:
 
 - Access to a lab in DevTest Labs. [Create a lab](devtest-lab-create-lab.md), or use an existing lab.
-- Azure PowerShell. [Install Azure PowerShell](/powershell/azure/install-az-ps), or [use Azure Cloud Shell](../cloud-shell/quickstart-powershell.md) in the Azure portal.
+- Azure PowerShell. [Install Azure PowerShell](/powershell/azure/install-az-ps), or [use Azure Cloud Shell](/azure/cloud-shell/quickstart?tabs=powershell) in the Azure portal.
 
 ## PowerShell VM creation script
 
@@ -36,7 +36,7 @@ Param(
 [Parameter(Mandatory = $true)]   $UserName,
 [Parameter(Mandatory = $true)]   $Password
 )
- 
+
 pushd $PSScriptRoot
 
 try {
@@ -62,7 +62,7 @@ try {
     #Prepare all the properties needed for the createEnvironment call.
     # The properties are slightly different depending on the type of VM base.
     # The virtual network setup might also affect the properties.
-    
+
     $parameters = @{
        "name"      = $NewVmName;
        "location"  = $lab.Location;
@@ -93,7 +93,7 @@ try {
           })
        }
     }
-    
+
     #The following line has the same effect as invoking the
     # https://azure.github.io/projects/apis/#!/Labs/Labs_CreateEnvironment REST API
 
@@ -167,7 +167,7 @@ Creating a VM in the Azure portal generates an Azure Resource Manager (ARM) temp
 
 1. Copy and save the template to use in future PowerShell automation, and transfer the properties to the PowerShell VM creation script.
 
-   
+
 
 ### Use the DevTest Labs Azure REST API to get VM properties
 
@@ -178,7 +178,7 @@ You can also call the DevTest Labs REST API to get the properties of existing la
    - Under **labName**, enter your lab name.
    - Under **labResourceGroup**, enter the lab resource group name.
    - Under **subscriptionId**, select the lab's Azure subscription.
-1. Select **Run**. 
+1. Select **Run**.
 1. In the **Response** section under **Body**, view the properties for all the existing VMs in the lab.
 
 ## Set VM expiration date