Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into ds-pr106158

Author: davidsmatlak

.openpublishing.redirection.json

@@ -26594,6 +26594,21 @@
       "redirect_url": "/azure/virtual-machines/linux/tutorial-lamp-stack",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/vpn-gateway/nva-working-remotely-support.md",
+      "redirect_url": "/azure/vpn-gateway/nva-work-remotely-support",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/expressroute/working-remotely-support.md",
+      "redirect_url": "/azure/expressroute/work-remotely-support",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/bastion/working-remotely-support.md",
+      "redirect_url": "/azure/bastion/work-remotely-support",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/vpn-gateway/vpn-gateway-site-to-site-create.md",
       "redirect_url": "/azure/vpn-gateway/vpn-gateway-howto-site-to-site-classic-portal",

articles/active-directory/develop/reference-app-manifest.md

@@ -14,7 +14,7 @@ ms.topic: reference
 ms.tgt_pltfrm: 
 ms.workload: identity
 ms.subservice: report-monitor
-ms.date: 11/13/2018
+ms.date: 03/24/2020
 ms.author: markvi
 ms.reviewer: dhanyahk
 
@@ -29,7 +29,7 @@ In this article, you learn about the data retention policies for the different a
 | Azure AD Edition | Collection Start |
 | :--              | :--   |
 | Azure AD Premium P1 <br /> Azure AD Premium P2 | When you sign up for a subscription |
-| Azure AD Free <br /> Azure AD Basic | The first time you open the [Azure Active Directory blade](https://ms.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) or use the [reporting APIs](https://aka.ms/aadreports)  |
+| Azure AD Free| The first time you open the [Azure Active Directory blade](https://ms.portal.azure.com/#blade/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/Overview) or use the [reporting APIs](https://aka.ms/aadreports)  |
 
 ---
 
@@ -62,19 +62,19 @@ For security signals, the collection process starts when you opt-in to use the *
 
 **Activity reports**	
 
-| Report                 | Azure AD Free | Azure AD Basic | Azure AD Premium P1 | Azure AD Premium P2 |
-| :--                    | :--           | :--            | :--                 | :--                 |
-| Audit logs             | 7 days        |  7 days        | 30 days             | 30 days             |
-| Sign-ins               | N/A           |  N/A           | 30 days             | 30 days             |
-| Azure MFA usage        | 30 days       |  30 days       | 30 days             | 30 days             |
+| Report                 | Azure AD Free | Azure AD Premium P1 | Azure AD Premium P2 |
+| :--                    | :--           | :--                 | :--                 |
+| Audit logs             | 7 days        | 30 days             | 30 days             |
+| Sign-ins               | 7 days        | 30 days             | 30 days             |
+| Azure MFA usage        | 30 days       | 30 days             | 30 days             |
 
 You can retain the audit and sign-in activity data for longer than the default retention period outlined above by routing it to an Azure storage account using Azure Monitor. For more information, see [Archive Azure AD logs to an Azure storage account](quickstart-azure-monitor-route-logs-to-storage-account.md).
 
 **Security signals**
 
-| Report         | Azure AD Free | Azure AD Basic | Azure AD Premium P1 | Azure AD Premium P2 |
-| :--            | :--           | :--            | :--                 | :--                 |
-| Users at risk  | 7 days        | 7 days         | 30 days             | 90 days             |
-| Risky sign-ins | 7 days        | 7 days         |  30 days            | 90 days             |
+| Report         | Azure AD Free | Azure AD Premium P1 | Azure AD Premium P2 |
+| :--            | :--           | :--                 | :--                 |
+| Users at risk  | 7 days        | 30 days             | 90 days             |
+| Risky sign-ins | 7 days        | 30 days             | 90 days             |
 
 ---

articles/active-directory/reports-monitoring/reference-reports-data-retention.md

@@ -216,7 +216,7 @@ This section walks you through running the sample Ansible playbook presented in
 
 1. Create a file (to contain your playbook) named `azure_create_complete_vm.yml`, and open it in the VI editor, as follows:
 
-   ```azurecli-interactive
+   ```bash
    vi azure_create_complete_vm.yml
    ```
 

articles/ansible/ansible-create-vm.md

@@ -29,7 +29,7 @@ In this section, you use Ansible to deallocate (stop) an Azure virtual machine.
 
 1. Create a file named `azure-vm-stop.yml`, and open it in the editor:
 
-    ```azurecli-interactive
+    ```bash
     code azure-vm-stop.yml
     ```
 
@@ -82,7 +82,7 @@ In this section, you use Ansible to start a deallocated (stopped) Azure virtual
 
 1. Create a file named `azure-vm-start.yml`, and open it in the editor:
 
-    ```azurecli-interactive
+    ```bash
     code azure-vm-start.yml
     ```
 

articles/ansible/ansible-manage-linux-vm.md

@@ -24,7 +24,7 @@ We are going to use following two components:
 
 1. We will first create an Azure AAD service principal and assign it `Monitoring Reader` access over Application Gateway's resource group. 
 
-    ```bash
+    ```azurecli
         applicationGatewayGroupName="<application-gateway-group-id>"
         applicationGatewayGroupId=$(az group show -g $applicationGatewayGroupName -o tsv --query "id")
         az ad sp create-for-rbac -n "azure-k8s-metric-adapter-sp" --role "Monitoring Reader" --scopes applicationGatewayGroupId

articles/application-gateway/ingress-controller-autoscale-pods.md

@@ -87,13 +87,13 @@ important. The resource group required in the command below is *not* the one ref
 the resource group of the `aks-agentpool` virtual machines. Typically that resource group starts with `MC_` and contains
  the name of your AKS. For instance: `MC_resourceGroup_aksABCD_westus`
 
-    ```bash
+    ```azurecli
     az identity create -g <agent-pool-resource-group> -n <identity-name>
     ```
 
 1. For the role assignment commands below we need to obtain `principalId` for the newly created identity:
 
-    ```bash
+    ```azurecli
     az identity show -g <resourcegroup> -n <identity-name>
     ```
 
@@ -102,7 +102,7 @@ look something like this: `/subscriptions/A/resourceGroups/B/providers/Microsoft
 
     Get the list of Application Gateway IDs in your subscription with: `az network application-gateway list --query '[].id'`
 
-    ```bash
+    ```azurecli
     az role assignment create \
         --role Contributor \
         --assignee <principalId> \
@@ -112,7 +112,7 @@ look something like this: `/subscriptions/A/resourceGroups/B/providers/Microsoft
 1. Give the identity `Reader` access to the Application Gateway resource group. The resource group ID would look like:
 `/subscriptions/A/resourceGroups/B`. You can get all resource groups with: `az group list --query '[].id'`
 
-    ```bash
+    ```azurecli
     az role assignment create \
         --role Reader \
         --assignee <principalId> \
@@ -125,7 +125,7 @@ It is also possible to provide AGIC access to ARM via a Kubernetes secret.
 1. Create an Active Directory Service Principal and encode with base64. The base64 encoding is required for the JSON
 blob to be saved to Kubernetes.
 
-```bash
+```azurecli
 az ad sp create-for-rbac --subscription <subscription-uuid> --sdk-auth | base64 -w0
 ```
 

articles/application-gateway/ingress-controller-install-existing.md

@@ -16,7 +16,7 @@ installed in an environment with no pre-existing components.
 
 ## Required Command Line Tools
 
-We recommend the use of [Azure Cloud Shell](https://shell.azure.com/) for all command line operations below. Launch your shell from shell.azure.com or by clicking the link:
+We recommend the use of [Azure Cloud Shell](https://shell.azure.com/) for all command-line operations below. Launch your shell from shell.azure.com or by clicking the link:
 
 [![Embed launch](https://shell.azure.com/images/launchcloudshell.png "Launch Azure Cloud Shell")](https://shell.azure.com)
 
@@ -25,7 +25,7 @@ Alternatively, launch Cloud Shell from Azure portal using the following icon:
 ![Portal launch](./media/application-gateway-ingress-controller-install-new/portal-launch-icon.png)
 
 Your [Azure Cloud Shell](https://shell.azure.com/) already has all necessary tools. Should you
-choose to use another environment, please ensure the following command line tools are installed:
+choose to use another environment, please ensure the following command-line tools are installed:
 
 * `az` - Azure CLI: [installation instructions](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)
 * `kubectl` - Kubernetes command-line tool: [installation instructions](https://kubernetes.io/docs/tasks/tools/install-kubectl)
@@ -38,7 +38,7 @@ choose to use another environment, please ensure the following command line tool
 Follow the steps below to create an Azure Active Directory (AAD) [service principal object](https://docs.microsoft.com/azure/active-directory/develop/app-objects-and-service-principals#service-principal-object). Please record the `appId`, `password`, and `objectId` values - these will be used in the following steps.
 
 1. Create AD service principal ([Read more about RBAC](https://docs.microsoft.com/azure/role-based-access-control/overview)):
-    ```bash
+    ```azurecli
     az ad sp create-for-rbac --skip-assignment -o json > auth.json
     appId=$(jq -r ".appId" auth.json)
     password=$(jq -r ".password" auth.json)
@@ -47,7 +47,7 @@ Follow the steps below to create an Azure Active Directory (AAD) [service princi
 
 
 1. Use the `appId` from the previous command's output to get the `objectId` of the new service principal:
-    ```bash
+    ```azurecli
     objectId=$(az ad sp show --id $appId --query "objectId" -o tsv)
     ```
     The output of this command is `objectId`, which will be used in the Azure Resource Manager template below
@@ -80,7 +80,7 @@ This step will add the following components to your subscription:
     ```
 
 1. Deploy the Azure Resource Manager template using `az cli`. This may take up to 5 minutes.
-    ```bash
+    ```azurecli
     resourceGroupName="MyResourceGroup"
     location="westus2"
     deploymentName="ingress-appgw"
@@ -97,22 +97,22 @@ This step will add the following components to your subscription:
     ```
 
 1. Once the deployment finished, download the deployment output into a file named `deployment-outputs.json`.
-    ```bash
+    ```azurecli
     az group deployment show -g $resourceGroupName -n $deploymentName --query "properties.outputs" -o json > deployment-outputs.json
     ```
 
 ## Set up Application Gateway Ingress Controller
 
-With the instructions in the previous section we created and configured a new AKS cluster and
+With the instructions in the previous section, we created and configured a new AKS cluster and
 an Application Gateway. We are now ready to deploy a sample app and an ingress controller to our new
 Kubernetes infrastructure.
 
 ### Setup Kubernetes Credentials
-For the following steps we need setup [kubectl](https://kubectl.docs.kubernetes.io/) command,
+For the following steps, we need setup [kubectl](https://kubectl.docs.kubernetes.io/) command,
 which we will use to connect to our new Kubernetes cluster. [Cloud Shell](https://shell.azure.com/) has `kubectl` already installed. We will use `az` CLI to obtain credentials for Kubernetes.
 
 Get credentials for your newly deployed AKS ([read more](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough#connect-to-the-cluster)):
-```bash
+```azurecli
 # use the deployment-outputs.json created after deployment to get the cluster name and resource group name
 aksClusterName=$(jq -r ".aksClusterName.value" deployment-outputs.json)
 resourceGroupName=$(jq -r ".resourceGroupName.value" deployment-outputs.json)
@@ -268,7 +268,7 @@ Kubernetes. We will leverage it to install the `application-gateway-kubernetes-i
    > The `identityResourceID` and `identityClientID` are values that were created
    during the [Create an Identity](https://github.com/Azure/application-gateway-kubernetes-ingress/blob/072626cb4e37f7b7a1b0c4578c38d1eadc3e8701/docs/setup/install-new.md#create-an-identity)
    steps, and could be obtained again using the following command:
-   > ```bash
+   > ```azurecli
    > az identity show -g <resource-group> -n <identity-name>
    > ```
    > `<resource-group>` in the command above is the resource group of your Application Gateway. `<identity-name>` is the name of the created identity. All identities for a given subscription can be listed using: `az identity list`

articles/application-gateway/ingress-controller-install-new.md

@@ -167,7 +167,7 @@ It can take up to 30 minutes for Azure to create the application gateway. After
 
 Although Azure doesn't require an NGINX web server to create the application gateway, you installed it in this quickstart to verify whether Azure successfully created the application gateway. To get the public IP address of the new application gateway, use `az network public-ip show`. 
 
-```azurepowershell-interactive
+```azurecli-interactive
 az network public-ip show \
   --resource-group myResourceGroupAG \
   --name myAGPublicIPAddress \

articles/application-gateway/quick-create-cli.md

@@ -123,7 +123,7 @@ az vmss extension set \
 
 To get the public IP address of the application gateway, you can use [az network public-ip show](/cli/azure/network/public-ip). Copy the public IP address, and then paste it into the address bar of your browser.
 
-```azurepowershell-interactive
+```azurecli-interactive
 az network public-ip show \
   --resource-group myResourceGroupAG \
   --name myAGPublicIPAddress \