Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into reservations-updates-mar-2020

Author: bandersmsft

.openpublishing.redirection.json

@@ -45,7 +45,7 @@ This page is updated monthly, so revisit it regularly. If you're looking for ite
 
 We're planning to replace the current custom controls preview with an approach that allows partner-provided authentication capabilities to work seamlessly with the Azure Active Directory administrator and end user experiences. Today, partner MFA solutions face the following limitations: they work only after a password has been entered; they don't serve as MFA for step-up authentication in other key scenarios; and they don't integrate with end user or administrative credential management functions. The new implementation will allow partner-provided authentication factors to work alongside built-in factors for key scenarios, including registration, usage, MFA claims, step up authentication, reporting, and logging. 
 
-Custom controls will continue to be supported in preview alongside the new design until it reaches general availability. At that point, we'll give customers time to migrate to the new design. Because of the limitations of the current approach, we won't onboard new providers until the new design is available. We are working closely with customers and providers and will communicate the timeline as we get closer. [Learn more](https://docs.microsoft.com/azure/active-directory/conditional-access/controls).
+Custom controls will continue to be supported in preview alongside the new design until it reaches general availability. At that point, we'll give customers time to migrate to the new design. Because of the limitations of the current approach, we won't onboard new providers until the new design is available. We are working closely with customers and providers and will communicate the timeline as we get closer. [Learn more](https://techcommunity.microsoft.com/t5/azure-active-directory-identity/upcoming-changes-to-custom-controls/ba-p/1144696#).
 
 ### Identity Secure Score - MFA improvement action updates
 

articles/active-directory/fundamentals/whats-new.md

@@ -14,7 +14,8 @@
       href: kubernetes-walkthrough.md
     - name: Use the Azure portal
       href: kubernetes-walkthrough-portal.md
-    - name: Use a Resource Manager template
+    - name: Use ARM template
+      displayName: Resource Manager
       href: kubernetes-walkthrough-rm-template.md
   - name: Develop applications
     expanded: true
@@ -24,8 +25,8 @@
     - name: Azure Dev Spaces
       expanded: true
       items:
-      - name: Use Azure Dev Spaces for team development 
-        href: ../dev-spaces/quickstart-team-development.md 
+      - name: Use Azure Dev Spaces for team development
+        href: ../dev-spaces/quickstart-team-development.md
         maintainContext: true
       - name: Use Visual Studio Code
         href: ../dev-spaces/quickstart-netcore.md
@@ -37,10 +38,10 @@
         href: ../dev-spaces/quickstart-cli.md
         maintainContext: true
       - name: Use Azure Dev Spaces with Java
-        href: ../dev-spaces/quickstart-java.md 
+        href: ../dev-spaces/quickstart-java.md
         maintainContext: true
       - name: Use Azure Dev Spaces Node.js
-        href: ../dev-spaces/quickstart-nodejs.md 
+        href: ../dev-spaces/quickstart-nodejs.md
         maintainContext: true
 - name: Tutorials
   items:
@@ -73,6 +74,8 @@
     href: concepts-storage.md
   - name: Scale
     href: concepts-scale.md
+  - name: Node auto-repair
+    href: node-auto-repair.md
   - name: Best practices
     items:
     - name: Overview
@@ -159,7 +162,7 @@
     - name: NFS Server - Static
       href: azure-nfs-volume.md
     - name: Azure NetApp Files
-      href: azure-netapp-files.md      
+      href: azure-netapp-files.md
   - name: Configure networking
     items:
     - name: Create or use existing virtual network
@@ -326,25 +329,25 @@
       href: ../api-management/api-management-kubernetes.md
       maintainContext: true
   - name: Select and deploy a service mesh
-    items: 
+    items:
     - name: About Service Meshes
       href: servicemesh-about.md
     - name: Use Istio
-      items: 
+      items:
       - name: About Istio
         href: servicemesh-istio-about.md
       - name: Install and configure
         href: servicemesh-istio-install.md
       - name: Scenario - Intelligent routing and canary releases
         href: servicemesh-istio-scenario-routing.md
     - name: Use Linkerd
-      items: 
+      items:
       - name: About Linkerd
         href: servicemesh-linkerd-about.md
       - name: Install and configure
         href: servicemesh-linkerd-install.md
     - name: Use Consul
-      items: 
+      items:
       - name: About Consul
         href: servicemesh-consul-about.md
       - name: Install and configure
@@ -360,7 +363,7 @@
       href: ../devops-project/azure-devops-project-aks.md
       maintainContext: true
     - name: Deployment Center Launcher
-      href: deployment-center-launcher.md 
+      href: deployment-center-launcher.md
     - name: GitHub Actions for Kubernetes
       href: ../aks/kubernetes-action.md
   - name: Troubleshoot

articles/aks/TOC.yml

@@ -5,7 +5,7 @@ services: container-service
 ms.topic: quickstart
 ms.date: 04/19/2019
 
-ms.custom: mvc
+ms.custom: mvc,subject-armqs
 
 #Customer intent: As a developer or cluster operator, I want to quickly create an AKS cluster and deploy an application so that I can see how to run applications using the managed Kubernetes service in Azure.
 ---
@@ -16,6 +16,8 @@ Azure Kubernetes Service (AKS) is a managed Kubernetes service that lets you qui
 
 ![Image of browsing to Azure Vote](media/container-service-kubernetes-walkthrough/azure-voting-application.png)
 
+[!INCLUDE [About Azure Resource Manager](../../includes/resource-manager-quickstart-introduction.md)]
+
 This quickstart assumes a basic understanding of Kubernetes concepts. For more information, see [Kubernetes core concepts for Azure Kubernetes Service (AKS)][kubernetes-concepts].
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
@@ -66,13 +68,21 @@ Make a note of the *appId* and *password*. These values are used in the followin
 
 ## Create an AKS cluster
 
-The template used in this quickstart is to [deploy an Azure Kubernetes Service cluster](https://azure.microsoft.com/resources/templates/101-aks/). For more AKS samples, see the [AKS quickstart templates][aks-quickstart-templates] site.
+### Review the template
+
+The template used in this quickstart is from [Azure Quickstart templates](https://azure.microsoft.com/resources/templates/101-aks/).
+
+:::code language="json" source="~/quickstart-templates/101-aks/azuredeploy.json" range="1-126" highlight="86-118":::
+
+For more AKS samples, see the [AKS quickstart templates][aks-quickstart-templates] site.
+
+### Deploy the template
 
 1. Select the following image to sign in to Azure and open a template.
 
     [![Deploy to Azure](./media/kubernetes-walkthrough-rm-template/deploy-to-azure.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2F101-aks%2Fazuredeploy.json)
 
-2. Select or enter the following values.  
+2. Select or enter the following values.
 
     For this quickstart, leave the default values for the *OS Disk Size GB*, *Agent Count*, *Agent VM Size*, *OS Type*, and *Kubernetes Version*. Provide your own values for the following template parameters:
 
@@ -93,7 +103,9 @@ The template used in this quickstart is to [deploy an Azure Kubernetes Service c
 
 It takes a few minutes to create the AKS cluster. Wait for the cluster to be successfully deployed before you move on to the next step.
 
-## Connect to the cluster
+## Validate the deployment
+
+### Connect to the cluster
 
 To manage a Kubernetes cluster, you use [kubectl][kubectl], the Kubernetes command-line client. If you use Azure Cloud Shell, `kubectl` is already installed. To install `kubectl` locally, use the [az aks install-cli][az-aks-install-cli] command:
 
@@ -122,7 +134,7 @@ aks-agentpool-41324942-1   Ready    agent   6m46s   v1.12.6
 aks-agentpool-41324942-2   Ready    agent   6m45s   v1.12.6
 ```
 
-## Run the application
+### Run the application
 
 A Kubernetes manifest file defines a desired state for the cluster, such as what container images to run. In this quickstart, a manifest is used to create all objects needed to run the Azure Vote application. This manifest includes two [Kubernetes deployments][kubernetes-deployment] - one for the sample Azure Vote Python applications, and the other for a Redis instance. Two [Kubernetes Services][kubernetes-service] are also created - an internal service for the Redis instance, and an external service to access the Azure Vote application from the internet.
 
@@ -231,7 +243,7 @@ deployment "azure-vote-front" created
 service "azure-vote-front" created
 ```
 
-## Test the application
+### Test the application
 
 When the application runs, a Kubernetes service exposes the application front end to the internet. This process can take a few minutes to complete.
 
@@ -258,7 +270,7 @@ To see the Azure Vote app in action, open a web browser to the external IP addre
 
 ![Image of browsing to Azure Vote](media/container-service-kubernetes-walkthrough/azure-voting-application.png)
 
-## Delete cluster
+## Clean up resources
 
 When the cluster is no longer needed, use the [az group delete][az-group-delete] command to remove the resource group, container service, and all related resources.
 

articles/aks/kubernetes-walkthrough-rm-template.md

@@ -0,0 +1,54 @@
+---
+title: Automatically repairing Azure Kubernetes Service (AKS) nodes 
+description: Learn about node auto-repair functionality, and how AKS fixes broken worker nodes.
+services: container-service
+ms.topic: conceptual
+ms.date: 03/10/2020
+---
+
+# Azure Kubernetes Service (AKS) node auto-repair
+
+AKS continuously checks the health state of worker nodes and performs automatic repair of the nodes if they become unhealthy. This documentation describes how Azure Kubernetes Service (AKS) monitors worker nodes, and repairs unhealthy worker nodes.  The documentation is to inform AKS operators on the behavior of node repair functionality. It is also important to note that Azure platform [performs maintenance on Virtual Machines][vm-updates] that experience issues. AKS and Azure work together to minimize service disruptions for your clusters.
+
+> [!Important]
+> Noe auto-repair functionality isn't currently supported for Windows Server node pools.
+
+## How AKS checks for unhealthy nodes
+
+> [!Note]
+> AKS takes repair action on nodes with the user account **aks-remediator**.
+
+AKS uses rules to determine if a node is an unhealthy state and needs repair. AKS uses the following rules to determine if automatic repair is needed.
+
+* The node reports status of **NotReady** on consecutive checks within a 10-minute timeframe
+* The node doesn't report a status within 10 minutes
+
+You can manually check the health state of your nodes with kubectl. 
+
+```
+kubectl get nodes
+```
+
+## How automatic repair works
+
+> [!Note]
+> AKS takes repair action on nodes with the user account **aks-remediator**.
+
+This behavior is for **Virtual Machine Scale Sets**.  Auto-repair takes several steps to repair a broken node.  If a node is determined to be unhealthy, AKS attempts several remediation steps.  The steps are performed in this order:
+
+1. After the container runtime becomes unresponsive for 10 minutes, the failing runtime services are restarted on the node.
+2. If the node is not ready within 10 minutes, the node is rebooted.
+3. If the node is not ready within 30 minutes, the node is re-imaged.
+
+> [!Note]
+> If multiple nodes are unhealthy, they are repaired one by one
+
+## Next steps
+
+Use [Availability Zones][availability-zones] to increase high availability with your AKS cluster workloads.
+
+<!-- LINKS - External -->
+
+<!-- LINKS - Internal -->
+[availability-zones]: ./availability-zones.md
+[vm-updates]: ../virtual-machines/maintenance-and-updates.md

articles/aks/node-auto-repair.md

@@ -4,7 +4,7 @@ description: Describes client libraries required for client applications and too
 author: minewiskan
 ms.service: azure-analysis-services
 ms.topic: conceptual
-ms.date: 01/23/2020
+ms.date: 03/23/2020
 ms.author: owend
 ms.reviewer: minewiskan
 
@@ -18,19 +18,19 @@ Client libraries are necessary for client applications and tools to connect to A
 
 |Download  |Product version  | 
 |---------|---------|
-|[MSOLAP (amd64)](https://go.microsoft.com/fwlink/?linkid=829576)    |    15.1.21.27    |
-|[MSOLAP (x86)](https://go.microsoft.com/fwlink/?linkid=829575)     |     15.1.21.27       |
-|[AMO](https://go.microsoft.com/fwlink/?linkid=829578)     |   18.4.0.5    |
-|[ADOMD](https://go.microsoft.com/fwlink/?linkid=829577)     |    18.4.0.5     |
+|[MSOLAP (amd64)](https://go.microsoft.com/fwlink/?linkid=829576)    |    15.1.29.25    |
+|[MSOLAP (x86)](https://go.microsoft.com/fwlink/?linkid=829575)     |     15.1.29.25       |
+|[AMO](https://go.microsoft.com/fwlink/?linkid=829578)     |   18.4.8.0    |
+|[ADOMD](https://go.microsoft.com/fwlink/?linkid=829577)     |    18.4.8.0     |
 
 ## AMO and ADOMD (NuGet packages)
 
 Analysis Services Management Objects (AMO) and ADOMD client libraries are available as installable packages from [NuGet.org](https://www.nuget.org/). It's recommended you migrate to NuGet references instead of using Windows Installer. 
 
 |Package  | Product version  | 
 |---------|---------|
-|[AMO](https://www.nuget.org/packages/Microsoft.AnalysisServices.retail.amd64/)    |    18.4.0.5     |
-|[ADOMD](https://www.nuget.org/packages/Microsoft.AnalysisServices.AdomdClient.retail.amd64/)     |   18.4.0.5      |
+|[AMO](https://www.nuget.org/packages/Microsoft.AnalysisServices.retail.amd64/)    |    18.4.8.0     |
+|[ADOMD](https://www.nuget.org/packages/Microsoft.AnalysisServices.AdomdClient.retail.amd64/)     |   18.4.8.0      |
 
 NuGet package assemblies AssemblyVersion follow semantic versioning: MAJOR.MINOR.PATCH. NuGet references load the expected version even if there is a different version in the GAC (resulting from MSI install). PATCH is incremented for each release. AMO and ADOMD versions are kept in-sync.