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

Author: TimShererWithAquent

.openpublishing.redirection.json

@@ -4040,6 +4040,11 @@
       "redirect_url": "/azure/azure-portal/azure-portal-dashboards",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/azure-resource-manager/templates/template-tutorial-create-encrypted-storage-accounts.md",
+      "redirect_url": "articles/azure-resource-manager/templates/template-tutorial-use-template-reference",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/azure-resource-manager/azure-resource-manager-security-controls.md",
       "redirect_url": "/azure/azure-resource-manager/management/azure-resource-manager-security-controls",

articles/aks/gpu-cluster.md

@@ -2,10 +2,8 @@
 title: Use GPUs on Azure Kubernetes Service (AKS)
 description: Learn how to use GPUs for high performance compute or graphics-intensive workloads on Azure Kubernetes Service (AKS)
 services: container-service
-author: zr-msft
 ms.topic: article
-ms.date: 05/16/2019
-ms.author: zarhoads
+ms.date: 03/27/2020
 
 #Customer intent: As a cluster administrator or developer, I want to create an AKS cluster that can use high-performance GPU-based VMs for compute-intensive workloads.
 ---

articles/aks/use-managed-identity.md

@@ -1,6 +1,6 @@
 ---
 title: Use managed identities in Azure Kubernetes Service
-description: Learn how to use managed identities in Azure Kubernetes Service (AKS) 
+description: Learn how to use managed identities in Azure Kubernetes Service (AKS)
 services: container-service
 author: saudas
 manager: saudas
@@ -18,7 +18,7 @@ Currently, an Azure Kubernetes Service (AKS) cluster (specifically, the Kubernet
 AKS creates two managed identities:
 
 - **System-assigned managed identity**: The identity that the Kubernetes cloud provider uses to create Azure resources on behalf of the user. The life cycle of the system-assigned identity is tied to that of the cluster. The identity is deleted when the cluster is deleted.
-- **User-assigned managed identity**: The identity that's used for authorization in the cluster. For example, the user-assigned identity is used to authorize AKS to use access control records (ACRs), or to authorize the kubelet to get metadata from Azure.
+- **User-assigned managed identity**: The identity that's used for authorization in the cluster. For example, the user-assigned identity is used to authorize AKS to use Azure Container Registries (ACRs), or to authorize the kubelet to get metadata from Azure.
 
 Add-ons also authenticate using a managed identity. For each add-on, a managed identity is created by AKS and lasts for the life of the add-on. For creating and using your own VNet, static IP address, or attached Azure disk where the resources are outside of the MC_* resource group, use the PrincipalID of the cluster to perform a role assignment. For more information on role assignment, see [Delegate access to other Azure resources](kubernetes-service-principal.md#delegate-access-to-other-azure-resources).
 

articles/azure-app-configuration/concept-github-action.md

@@ -1,6 +1,6 @@
 ---
 title: Use GitHub Actions with Azure App Configuration Sync
-description: Use GitHub Actions to trigger an update to your App Configuration instance when defined actions are performed on a GitHub repository
+description: Use GitHub Actions to trigger an update to your App Configuration instance when you update your GitHub repository
 author: lisaguthrie
 
 ms.author: lcozzens
@@ -10,13 +10,13 @@ ms.service: azure-app-configuration
 
 ---
 # Sync your App Configuration instance using GitHub Actions
-Azure App Configuration uses GitHub Actions to trigger updates to an App Configuration instance based on actions performed on a GitHub repository. GitHub workflows trigger configuration updates, enabling the integration of those updates into the same workflow used to update the app code.
 
-A GitHub Actions [workflow](https://help.github.com/articles/about-github-actions#workflow) defines an automated process in a GitHub repository. This process tells GitHub how to build and deploy your GitHub project. Azure App Configuration provides the *Azure App Configuration Sync* Action to enable updates to an App Configuration instance when changes are made to the source repository. 
+Teams that want to continue using their existing source control practices can use GitHub Actions to automatically sync their GitHub repository with their App Configuration store. This allows you to make changes to your config files as you normally would, while getting App Configuration benefits like:
+•	Centralized configuration outside of your code
+•	Updating configuration without redeploying your entire app
+•	Integration with services like Azure App Service and Functions. 
 
-A YAML (.yml) file found in the `/.github/workflows/` path of your repository defines your workflow. This definition contains the workflow's steps and parameters.
-
-GitHub events, such as a push to a repository, can trigger a GitHub Action workflow.  The *Azure App Configuration Sync* action enables you to trigger an update of an App Configuration instance when a specified GitHub action occurs. You can trigger configuration updates when pushing, reviewing, or branching app configuration files just as you do with app code.
+A GitHub Actions [workflow](https://help.github.com/articles/about-github-actions#workflow) defines an automated process in a GitHub repository. The *Azure App Configuration Sync* Action triggers updates to an App Configuration instance when changes are made to the source repository. It uses a YAML (.yml) file found in the `/.github/workflows/` path of your repository to define the steps and parameters. You can trigger configuration updates when pushing, reviewing, or branching app configuration files just as you do with app code.
 
 The GitHub [documentation](https://help.github.com/actions/automating-your-workflow-with-github-actions/configuring-a-workflow) provides in-depth view of GitHub workflows and actions. 
 

articles/azure-resource-manager/templates/deployment-tutorial-pipeline.md

@@ -244,4 +244,4 @@ Congratulations, you've finished this Resource Manager template deployment tutor
 You're ready to jump into more advanced concepts about templates. The next tutorial goes into more detail about using template reference documentation to help with defining resources to deploy.
 
 > [!div class="nextstepaction"]
-> [Utilize template reference](./template-tutorial-create-encrypted-storage-accounts.md)
+> [Utilize template reference](./template-tutorial-use-template-reference.md)