Merge pull request #110621 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: tfosmark

articles/active-directory/develop/tutorial-v2-javascript-spa.md

@@ -346,6 +346,18 @@ Create a new .js file named `authPopup.js`, which will contain your authenticati
    function signOut() {
      myMSALObj.logout();
    }
+   
+   function callMSGraph(theUrl, accessToken, callback) {
+       var xmlHttp = new XMLHttpRequest();
+       xmlHttp.onreadystatechange = function () {
+           if (this.readyState == 4 && this.status == 200) {
+              callback(JSON.parse(this.responseText));
+           }
+       }
+       xmlHttp.open("GET", theUrl, true); // true for asynchronous
+       xmlHttp.setRequestHeader('Authorization', 'Bearer ' + accessToken);
+       xmlHttp.send();
+   }
 
    function getTokenPopup(request) {
      return myMSALObj.acquireTokenSilent(request)

articles/active-directory/hybrid/how-to-connect-sync-change-serviceacct-pass.md

@@ -79,7 +79,7 @@ Abandon the existing encryption key so that new encryption key can be created:
 
 2. Start a new PowerShell session.
 
-3. Navigate to folder: `$env:Program Files\Microsoft Azure AD Sync\bin\`
+3. Navigate to folder: `'$env:ProgramFiles\Microsoft Azure AD Sync\bin\'`
 
 4. Run the command: `./miiskmu.exe /a`
 

articles/active-directory/hybrid/how-to-connect-sync-feature-preferreddatalocation.md

@@ -46,6 +46,7 @@ The geos in Office 365 available for Multi-Geo are:
 | Japan | JPN |
 | Korea | KOR |
 | South Africa | ZAF |
+| Switzerland | CHE |
 | United Arab Emirates | ARE |
 | United Kingdom | GBR |
 | United States | NAM |

articles/active-directory/manage-apps/application-proxy-release-version-history.md

@@ -12,7 +12,7 @@ ms.devlang: na
 ms.topic: reference
 ms.tgt_pltfrm: na
 ms.workload: identity
-ms.date: 04/05/2019
+ms.date: 04/07/2020
 ms.subservice: app-mgmt
 ms.author: mimart
 
@@ -31,6 +31,22 @@ How to enable Application Proxy | Pre-requisites for enabling Application Proxy
 Understand Azure AD Application Proxy connectors | Find out more about [connector management](application-proxy-connectors.md) and how connectors [auto-upgrade](application-proxy-connectors.md#automatic-updates).
 Azure AD Application Proxy Connector Download |  [Download the latest connector](https://download.msappproxy.net/subscription/d3c8b69d-6bf7-42be-a529-3fe9c2e70c90/connector/download).
 
+## 1.5.1526.0
+
+### Release status
+
+April 07, 2020: Released for download
+
+### New features and improvements
+-	Connectors only use TLS 1.2 for all connections. See [Connector pre-requisites](application-proxy-add-on-premises-application.md#before-you-begin) for more details.
+- Improved signaling between the Connector and Azure services. This includes supporting reliable sessions for WCF communication between the Connector and Azure services and DNS caching improvements for WebSocket communications.
+- Support for configuring a proxy between the Connector and the backend application. For more information see [Work with existing on-premises proxy servers](application-proxy-configure-connectors-with-proxy-servers.md).
+
+### Fixed issues
+- Removed falling back to port 8080 for communications from the Connector to Azure services.
+- Added debug traces for WebSocket communications. 
+- Resolved preserving the SameSite attribute when set on backend application cookies.
+
 ## 1.5.612.0
 
 ### Release status

articles/aks/azure-ad-v2.md

@@ -44,11 +44,10 @@ az extension update --name aks-preview
 az extension list
 ```
 
-To install kubectl, use the following
+To install kubectl, use the following:
+
 ```azurecli
-curl -LO "https://storage.googleapis.com/kubernetes-release/release/v1.18.0-beta.2/bin/linux/amd64/kubectl"
-chmod +x ./kubectl
-sudo mv ./kubectl /usr/local/bin/kubectl
+sudo az aks install-cli
 kubectl version --client
 ```
 
@@ -94,7 +93,7 @@ The above command creates a three node AKS cluster, but the user, who created th
 Once you've created a group and added yourself (and others) as a member, you can update the cluster with the Azure AD group using the following command
 
 ```azurecli-interactive
-az aks update -g MyResourceGroup -n MyManagedCluster --enable-aad [--aad-admin-group-object-ids <id1,id2>] [--aad-tenant-id <id>]
+az aks update -g MyResourceGroup -n MyManagedCluster [--aad-admin-group-object-ids <id1,id2>] [--aad-tenant-id <id>]
 ```
 Alternatively, if you first create a group and add members, you can enable the Azure AD group at create time using the following command,
 

articles/aks/virtual-nodes-cli.md

@@ -63,7 +63,7 @@ Virtual Nodes functionality is heavily dependent on ACI's feature set. The follo
 * [Host aliases](https://kubernetes.io/docs/concepts/services-networking/add-entries-to-pod-etc-hosts-with-host-aliases/)
 * [Arguments](../container-instances/container-instances-exec.md#restrictions) for exec in ACI
 * [DaemonSets](concepts-clusters-workloads.md#statefulsets-and-daemonsets) will not deploy pods to the virtual node
-* [Windows Server nodes (currently in preview in AKS)](windows-container-cli.md) are not supported alongside virtual nodes. You can use virtual nodes to schedule Windows Server containers without the need for Windows Server nodes in an AKS cluster.
+* Virtual nodes support scheduling Linux pods. You can manually install the open source [Virtual Kubelet ACI](https://github.com/virtual-kubelet/azure-aci) provider to schedule Windows Server containers to ACI. 
 
 ## Launch Azure Cloud Shell
 

articles/app-service/environment/forced-tunnel-support.md

@@ -56,7 +56,7 @@ You can configure your ASE subnet to ignore all BGP routes.  When configured to
 To configure your ASE subnet to ignore BGP routes:
 
 * create a UDR and assign it to your ASE subnet if you did not have one already.
-* In the Azure portal, open the UI for the route table assigned to your ASE subnet.  Select Configuration.  Set BGP route propagation to Disabled.  Click Save. The documentation on turning that off is in the [Create a route table][routetable] document.
+* In the Azure portal, open the UI for the route table assigned to your ASE subnet.  Select Configuration.  Set Virtual network gateway route propagation to Disabled.  Click Save. The documentation on turning that off is in the [Create a route table][routetable] document.
 
 After you configure the ASE subnet to ignore all BGP routes, your apps will no longer be able to reach on premises. To enable your apps to access resources on-premises, edit the UDR assigned to your ASE subnet and add routes for your on premises address ranges. The Next hop type should be set to Virtual network gateway. 
 

articles/azure-resource-manager/management/resource-name-rules.md

@@ -7,7 +7,7 @@ ms.date: 03/27/2020
 
 # Naming rules and restrictions for Azure resources
 
-This article summarizes naming rules and restrictions for Azure resources. For recommendations about how to name resources, see [Ready: Recommended naming and tagging conventions](/azure/cloud-adoption-framework/ready/azure-best-practices/naming-and-tagging).
+This article summarizes naming rules and restrictions for Azure resources. For recommendations about how to name resources, see [Recommended naming and tagging conventions](/azure/cloud-adoption-framework/ready/azure-best-practices/naming-and-tagging).
 
 Resource names are case-insensitive unless specifically noted in the valid characters column.
 

articles/cognitive-services/QnAMaker/includes/quickstart-sdk-python.md

@@ -60,7 +60,7 @@ Create variables for your resource's Azure endpoint and key. If you created the
 
 |Environment variable|variable|Example|
 |--|--|--|
-|`QNAMAKER_SUBSCRIPTION_KEY`|`subscription_key`|The key is a 32 character string and is available in the Azure portal, on the QnA Maker resource, on the Quickstart page. This is not the same as the prediction endpoint key.|
+|`QNAMAKER_KEY`|`subscription_key`|The key is a 32 character string and is available in the Azure portal, on the QnA Maker resource, on the Quickstart page. This is not the same as the prediction endpoint key.|
 |`QNAMAKER_HOST`|`host`| Your authoring endpoint, in the format of `https://YOUR-RESOURCE-NAME.cognitiveservices.azure.com`, includes your **resource name**. This is not the same URL used to query the prediction endpoint.|
 
 [!code-python[Azure resource variables](~/samples-qnamaker-python/documentation-samples/quickstarts/knowledgebase_quickstart/knowledgebase_quickstart.py?name=resourcekeys)]

articles/dns/tutorial-alias-pip.md

@@ -16,8 +16,8 @@ In this tutorial, you learn how to:
 
 > [!div class="checklist"]
 > * Create a network infrastructure.
-> * Create a web server virtual machine.
-> * Create an alias record.
+> * Create a web server virtual machine with a public IP.
+> * Create an alias record that points to the public IP.
 > * Test the alias record.
 
 
@@ -44,7 +44,7 @@ First, create a virtual network and a subnet to place your web servers in.
 4. For **Settings**, select the **VNet-Servers** virtual network and the **SN-Web** subnet. For public inbound ports, select **HTTP** > **HTTPS** > **RDP (3389)**, and then select **OK**.
 5. On the **Summary** page, select **Create**.
 
-This procedure takes a few minutes to finish.
+This procedure takes a few minutes to finish. The virtual machine will have an attached NIC, which will have a basic dynamic public IP called Web-01-ip. The public IP will change every time the virtual machine is restarted.
 
 ### Install IIS