Merge pull request #24445 from MGoedtel/UpdateAAMeta9292017

updated author metadata

Author: rmca14

articles/automation/automation-azure-vm-alert-integration.md

@@ -3,7 +3,7 @@ title: " Remediate Azure VM Alerts with Automation Runbooks | Microsoft Docs"
 description: This article demonstrates how to integrate Azure Virtual Machine alerts with Azure Automation runbooks and auto-remediate issues
 services: automation
 documentationcenter: ''
-author: mgoedtel
+author: eslesar
 manager: jwhit
 editor: tysonn
 
@@ -13,16 +13,16 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services
-ms.date: 06/14/2016
+ms.date: 09/29/2017
 ms.author: csand;magoedte
 
 ---
 # Azure Automation scenario - remediate Azure VM alerts
 Azure Automation and Azure Virtual Machines have released a new feature allowing you to configure Virtual Machine (VM) alerts to run Automation runbooks. This new capability allows you to automatically perform standard remediation in response to VM alerts, like restarting or stopping the VM.
 
-Previously, during VM alert rule creation you were able to [specify an Automation webhook](https://azure.microsoft.com/blog/using-azure-automation-to-take-actions-on-azure-alerts/) to a runbook in order to run the runbook whenever the alert triggered. However, this required you to do the work of creating the runbook, creating the webhook for the runbook, and then copying and pasting the webhook during alert rule creation. With this new release, the process is much easier because you can directly choose a runbook from a list during alert rule creation, and you can choose an Automation account which will run the runbook or easily create an account.
+Previously, during VM alert rule creation you were able to [specify an Automation webhook](https://azure.microsoft.com/blog/using-azure-automation-to-take-actions-on-azure-alerts/) to a runbook in order to run the runbook whenever the alert triggered. However, this required you to do the work of creating the runbook, creating the webhook for the runbook, and then copying and pasting the webhook during alert rule creation. With this new release, the process is much easier because you can directly choose a runbook from a list during alert rule creation, and you can choose an Automation account which runs the runbook or easily create an account.
 
-In this article, we will show you how easy it is to set up an Azure VM alert and configure an Automation runbook to run whenever the alert triggers. Example scenarios include restarting a VM when the memory usage exceeds some threshold due to an application on the VM with a memory leak, or stopping a VM when the CPU user time has been below 1% for past hour and is not in use. We’ll also explain how the automated creation of a service principal in your Automation account simplifies the use of runbooks in Azure alert remediation.
+In this article, we show you how easy it is to set up an Azure VM alert and configure an Automation runbook to run whenever the alert triggers. Example scenarios include restarting a VM when the memory usage exceeds some threshold due to an application on the VM with a memory leak, or stopping a VM when the CPU user time has been below 1% for past hour and is not in use. We’ll also explain how the automated creation of a service principal in your Automation account simplifies the use of runbooks in Azure alert remediation.
 
 ## Create an alert on a VM
 Perform the following steps to configure an alert to launch a runbook when its threshold has been met.
@@ -33,14 +33,14 @@ Perform the following steps to configure an alert to launch a runbook when its t
 > 
 
 1. Log in to the Azure portal and click **Virtual Machines**.  
-2. Select one of your virtual machines.  The virtual machine dashboard blade will appear and the **Settings** blade to its right.  
-3. From the **Settings** blade, under the Monitoring section select **Alert rules**.
-4. On the **Alert rules** blade, click **Add alert**.
+2. Select one of your virtual machines.  
+3. On the VM screen, in the **Monitoring** section, click **Alert rules**.
+4. On the **Alert rules** pane, click **Add alert**.
 
-This opens up the **Add an alert rule** blade, where you can configure the conditions for the alert and choose among one or all of these options: send email to someone, use a webhook to forward the alert to another system, and/or run an Automation runbook in response attempt to remediate the issue.
+This opens up the **Add an alert rule** page, where you can configure the conditions for the alert and choose among one or all of these options: send email to someone, use a webhook to forward the alert to another system, and/or run an Automation runbook in response attempt to remediate the issue.
 
 ## Configure a runbook
-To configure a runbook to run when the VM alert threshold is met, select **Automation Runbook**. In the **Configure runbook** blade, you can select the runbook to run and the Automation account to run the runbook in.
+To configure a runbook to run when the VM alert threshold is met, select **Automation Runbook**. In the **Configure runbook** pane, you can select the runbook to run and the Automation account to run the runbook in.
 
 ![Configure an Automation runbook and create a new Automation Account](media/automation-azure-vm-alert-integration/ConfigureRunbookNewAccount.png)
 
@@ -53,7 +53,7 @@ To configure a runbook to run when the VM alert threshold is met, select **Autom
 
 After you select one of the three available runbooks, the **Automation account** drop-down list appears and you can select an automation account the runbook will run as. Runbooks need to run in the context of an [Automation account](automation-security-overview.md) that is in your Azure subscription. You can select an Automation account that you already created, or you can have a new Automation account created for you.
 
-The runbooks that are provided authenticate to Azure using a service principal. If you choose to run the runbook in one of your existing Automation accounts, we will automatically create the service principal for you. If you choose to create a new Automation account, then we will automatically create the account and the service principal. In both cases, two assets will also be created in the Automation account – a certificate asset named **AzureRunAsCertificate** and a connection asset named **AzureRunAsConnection**. The runbooks will use **AzureRunAsConnection** to authenticate with Azure in order to perform the management action against the VM.
+The runbooks that are provided authenticate to Azure using a service principal. If you choose to run the runbook in one of your existing Automation accounts, we automatically create the service principal for you. If you choose to create a new Automation account, then we automatically create the account and the service principal. In both cases, two assets are also created in the Automation account – a certificate asset named **AzureRunAsCertificate** and a connection asset named **AzureRunAsConnection**. The runbooks use **AzureRunAsConnection** to authenticate with Azure in order to perform the management action against the VM.
 
 > [!NOTE]
 > The service principal is created in the subscription scope and is assigned the Contributor role. This role is required in order for the account to have permission to run Automation runbooks to manage Azure VMs.  The creation of an Automaton account and/or service principal is a one-time event. Once they are created, you can use that account to run runbooks for other Azure VM alerts.
@@ -64,11 +64,11 @@ When you click **OK** the alert is configured and if you selected the option to
 
 ![Runbook being configured](media/automation-azure-vm-alert-integration/RunbookBeingConfigured.png)
 
-After the configuration is completed you will see the name of the runbook appear in the **Add an alert rule** blade.
+After the configuration is completed, you see the name of the runbook in the **Add an alert rule** page.
 
 ![Runbook configured](media/automation-azure-vm-alert-integration/RunbookConfigured.png)
 
-Click **OK** in the **Add an alert rule** blade and the alert rule will be created and activate if the virtual machine is in a running state.
+Click **OK** in the **Add an alert rule** page.  The alert rule is created and activate if the virtual machine is in a running state.
 
 ### Enable or disable a runbook
 If you have a runbook configured for an alert, you can disable it without removing the runbook configuration. This allows you to keep the alert running and perhaps test some of the alert rules and then later re-enable the runbook.
@@ -116,7 +116,7 @@ When the Automation webhook service receives the HTTP POST it extracts the alert
 
 ### Example runbook
 ```
-#  This runbook will restart an ARM (V2) VM in response to an Azure VM alert.
+#  This runbook restarts an ARM (V2) VM in response to an Azure VM alert.
 
 [OutputType("PSAzureOperationResponse")]
 
@@ -168,7 +168,7 @@ if ($WebhookData)
 ```
 
 ## Summary
-When you configure an alert on an Azure VM, you now have the ability to easily configure an Automation runbook to automatically perform remediation action when the alert triggers. For this release, you can choose from runbooks to restart, stop, or delete a VM depending on your alert scenario. This is just the beginning of enabling scenarios where you control the actions (notification, troubleshooting, remediation) that will be taken automatically when an alert triggers.
+When you configure an alert on an Azure VM, you now have the ability to easily configure an Automation runbook to automatically perform remediation action when the alert triggers. For this release, you can choose from runbooks to restart, stop, or delete a VM depending on your alert scenario. This is just the beginning of enabling scenarios where you control the actions (notification, troubleshooting, remediation) that are performed automatically when an alert triggers.
 
 ## Next Steps
 * To get started with Graphical runbooks, see [My first graphical runbook](automation-first-runbook-graphical.md)

articles/automation/automation-certificates.md

@@ -3,7 +3,7 @@ title: Certificate assets in Azure Automation | Microsoft Docs
 description: Certificates can be stored securely in Azure Automation so they can be accessed by runbooks or DSC configurations to authenticate against Azure and third-party resources.  This article explains the details of certificates and how to work with them in both textual and graphical authoring.
 services: automation
 documentationcenter: ''
-author: mgoedtel
+author: eslesar
 manager: stevenka
 editor: tysonn
 

articles/automation/automation-child-runbooks.md

@@ -3,7 +3,7 @@ title: Child runbooks in Azure Automation | Microsoft Docs
 description: Describes the different methods for starting a runbook in Azure Automation from another runbook and sharing information between them.
 services: automation
 documentationcenter: ''
-author: mgoedtel
+author: eslesar
 manager: jwhit
 editor: tysonn
 

articles/automation/automation-config-aws-account.md

@@ -3,7 +3,7 @@ title: Configure Authentication with Amazon Web Services  | Microsoft Docs
 description: This article describes how to create and validate an AWS credential for runbooks in Azure Automation managing AWS resources.
 services: automation
 documentationcenter: ''
-author: mgoedtel
+author: eslesar
 manager: jwhit
 editor: tysonn
 keywords: aws authentication, configure aws
@@ -14,26 +14,26 @@ ms.workload: tbd
 ms.tgt_pltfrm: na
 ms.devlang: na
 ms.topic: get-started-article
-ms.date: 04/14/2017
+ms.date: 09/29/2017
 ms.author: magoedte
 
 ---
 # Authenticate Runbooks with Amazon Web Services
 Automating common tasks with resources in Amazon Web Services (AWS) can be accomplished with Automation runbooks in Azure.  You can automate many tasks in AWS using Automation runbooks just like you can with resources in Azure.  All that is required are two things:
 
-* An AWS subscription and a set of credentials.  Specifically your AWS Access Key and Secret Key.  For more information, please review the article [Using AWS Credentials](http://docs.aws.amazon.com/powershell/latest/userguide/specifying-your-aws-credentials.html).
-* An Azure subscription and Automation account.  For more information on setting up an Azure Automation account, please review the article [Configure Azure Run As Account](automation-sec-configure-azure-runas-account.md).  
+* An AWS subscription and a set of credentials.  Specifically your AWS Access Key and Secret Key.  For more information, review the article [Using AWS Credentials](http://docs.aws.amazon.com/powershell/latest/userguide/specifying-your-aws-credentials.html).
+* An Azure subscription and Automation account.  For more information on setting up an Azure Automation account, review [Authentication planning](automation-offering-get-started.md#authentication-planning).  
 
-To authenticate with AWS, you must specify a set of AWS credentials to authenticate your runbooks running from Azure Automation. If you already have an Automation account created and you want to use that to authenticate with AWS, you can follow the steps in the following section.  If you want to dedicated an account for runbooks targetting AWS resources, you should first create a new [Automation account](automation-offering-get-started.md) (skip the option to create a service principal) and then follow the steps below.
+To authenticate with AWS, you must specify a set of AWS credentials to authenticate your runbooks running from Azure Automation. If you already have an Automation account created and you want to use that to authenticate with AWS, you can follow the steps in the following section.  If you want to dedicate an account for runbooks targeting AWS resources, you should first create a new [Automation account](automation-offering-get-started.md) (skip the option to create a service principal) and then follow the steps below.
 
 ## Configure Automation account
 For Azure Automation to communicate with AWS, you first need to retrieve your AWS credentials and store them as assets in Azure Automation.  Perform the following steps documented in the AWS document [Managing Access Keys for your AWS Account](http://docs.aws.amazon.com/general/latest/gr/managing-aws-access-keys.html) to create an Access Key and copy the **Access Key ID** and **Secret Access Key** (optionally download your key file to store it somewhere safe).
 
 After you have created and copied your AWS security keys, you need to create a Credential asset with an Azure Automation account to securely store them and reference them with your runbooks.  Follow the steps in the section **To create a new credential** in the [Credential assets in Azure Automation](automation-credentials.md#to-create-a-new-credential-asset-with-the-azure-portal) article and enter the following information:
 
 1. In the **Name** box, enter **AWScred** or an appropriate value following your naming standards.  
-2. In the **User name** box type your **Access ID** and your **Secret Access Key** in the **Password** and **Confirm password** box.   
+2. In the **User name** box, type your **Access ID** and your **Secret Access Key** in the **Password** and **Confirm password** box.   
 
 ## Next steps
-* Reivew the solution article [Automating deployment of a VM in Amazon Web Services](automation-scenario-aws-deployment.md) to learn how to create runbooks to automate tasks in AWS.
+* Review the solution article [Automating deployment of a VM in Amazon Web Services](automation-scenario-aws-deployment.md) to learn how to create runbooks to automate tasks in AWS.
 

articles/automation/automation-configure-aws-account.md

@@ -1,9 +1,9 @@
----
+---
 title: Connection assets in Azure Automation | Microsoft Docs
 description: Connection assets in Azure Automation contain the information required to connect to an external service or application from a runbook or DSC configuration. This article explains the details of connections and how to work with them in both textual and graphical authoring.
 services: automation
 documentationcenter: ''
-author: mgoedtel
+author: eslesar
 manager: jwhit
 editor: tysonn
 

articles/automation/automation-connections.md

@@ -3,7 +3,7 @@ title: Create Azure AD User Account | Microsoft Docs
 description: This article describes how to create an Azure AD User account credential for runbooks in Azure Automation to authenticate in Azure and classic Azure.
 services: automation
 documentationcenter: ''
-author: MGoedtel
+author: eslesar
 manager: jwhit
 editor: tysonn
 keywords: azure active directory user, azure service management, azure ad user account

articles/automation/automation-create-aduser-account.md

@@ -3,7 +3,7 @@ title: Create Azure Automation Run As accounts | Microsoft Docs
 description: This article describes how to update your Automation account and create Run As accounts with PowerShell, or from the portal.  
 services: automation
 documentationcenter: ''
-author: mgoedtel
+author: eslesar
 manager: carmonm
 editor: ''
 

articles/automation/automation-create-runas-account.md

@@ -3,7 +3,7 @@ title: Create standalone Azure Automation Account | Microsoft Docs
 description: Tutorial that walks you through the creation, testing, and example use of security principal authentication in Azure Automation.
 services: automation
 documentationcenter: ''
-author: mgoedtel
+author: eslesar
 manager: carmonm
 editor: ''