Merge pull request #116211 from MGoedtel/UpdateAAAcountTemplate522

updated article to clarify log forwarding

Author: American-Dipper

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

@@ -6,7 +6,7 @@ ms.subservice: update-management
 ms.topic: conceptual
 author: mgoedtel
 ms.author: magoedte
-ms.date: 04/24/2020
+ms.date: 05/22/2020
 ---
 # Create an Automation account using an Azure Resource Manager template
 
@@ -21,6 +21,8 @@ The template doesn't automate the enabling of Azure or non-Azure virtual machine
 >[!NOTE]
 >Creation of the Automation Run As account is not supported when you're using an Azure Resource Manager template. To create a Run As account manually from the portal or with PowerShell, see [Manage Run As accounts](manage-runas-account.md).
 
+After you complete these steps, you need to [configure diagnostic settings](automation-manage-send-joblogs-log-analytics.md) for your Automation account to send runbook job status and job streams to the linked Log Analytics workspace. 
+
 ## API versions
 
 The following table lists the API version for the resources used in this example.
@@ -304,6 +306,4 @@ If you're new to Azure Automation and Azure Monitor, it's important that you und
 
 ## Next steps
 
-* To get started with PowerShell runbooks, see [Create a PowerShell runbook](automation-first-runbook-textual-powershell.md).
-* To get started with PowerShell workflow runbooks, see [Create a PowerShell Workflow runbook](automation-first-runbook-textual.md).
-* To get started with Python 2 runbooks, see [Create a Python runbook](automation-first-runbook-textual-python2.md).
+To forward runbook job status and job streams to your linked Log Analytics workspace, review [Forward Azure Automation job data to Azure Monitor logs](automation-manage-send-joblogs-log-analytics.md). This configures the diagnostic settings of the Automation account using Azure PowerShell commands to complete the integration for sending logs to the workspace for analysis. 

articles/automation/automation-manage-send-joblogs-log-analytics.md

@@ -3,7 +3,7 @@ title: Forward Azure Automation job data to Azure Monitor logs
 description: This article tells how to send job status and runbook job streams to Azure Monitor logs.
 services: automation
 ms.subservice: process-automation
-ms.date: 02/05/2019
+ms.date: 05/22/2020
 ms.topic: conceptual
 ---
 
@@ -41,11 +41,11 @@ To find the resource ID for your Log Analytics workspace, run the following Powe
 Get-AzResource -ResourceType "Microsoft.OperationalInsights/workspaces"
 ```
 
-If you have more than one Automation account or workspace in the output of the preceding commands, find the name that you need to configure and copy the value for the resource ID.
+If you have more than one Automation account or workspace in the output of the preceding commands, you can find the name and other related properties that are part of the full resource ID of your Automation account by performing the following:
 
-1. In the Azure portal, select your Automation account from the **Automation account** blade and select **All settings**. 
-2. From the **All settings** blade, under **Account Settings**, select **Properties**.  
-3. In the **Properties** blade, note the properties shown below.
+1. In the Azure portal, select your Automation account from the **Automation Accounts** page. 
+2. On the page of the selected Automation account, under **Account Settings**, select **Properties**.  
+3. In the **Properties** page, note the details shown below.
 
     ![Automation account properties](media/automation-manage-send-joblogs-log-analytics/automation-account-properties.png).
 
@@ -100,11 +100,11 @@ Azure Automation diagnostics create two types of records in Azure Monitor logs,
 ## Set up integration with Azure Monitor logs
 
 1. On your computer, start Windows PowerShell from the **Start** screen.
-2. Run the following PowerShell commands, and edit the values for `[your resource ID]` and `[resource ID of the log analytics workspace]` with the values from the preceding section.
+2. Run the following PowerShell commands, and edit the values for `$automationAccountId` and `$workspaceId` with the values from the preceding section.
 
    ```powershell-interactive
-   $workspaceId = "[resource ID of the log analytics workspace]"
-   $automationAccountId = "[resource ID of your Automation account]"
+   $workspaceId = "resource ID of the log analytics workspace"
+   $automationAccountId = "resource ID of your Automation account"
 
    Set-AzDiagnosticSetting -ResourceId $automationAccountId -WorkspaceId $workspaceId -Enabled 1
    ```
@@ -136,22 +136,26 @@ To see the logs, run the following query:
 
 ### Send an email when a runbook job fails or suspends
 
-One of the top customer asks is for the ability to send an email or a text when something goes wrong with a runbook job.
+The following steps show how to set up alerts in Azure Monitor to notify you when something goes wrong with a runbook job.
 
 To create an alert rule, start by creating a log search for the runbook job records that should invoke the alert. Click the **Alert** button to create and configure the alert rule.
 
 1. From the Log Analytics workspace Overview page, click **View logs**.
+
 2. Create a log search query for your alert by typing the following search into the query field: `AzureDiagnostics | where ResourceProvider == "MICROSOFT.AUTOMATION" and Category == "JobLogs" and (ResultType == "Failed" or ResultType == "Suspended")`<br><br>You can also group by the runbook name by using: `AzureDiagnostics | where ResourceProvider == "MICROSOFT.AUTOMATION" and Category == "JobLogs" and (ResultType == "Failed" or ResultType == "Suspended") | summarize AggregatedValue = count() by RunbookName_s`
 
    If you set up logs from more than one Automation account or subscription to your workspace, you can group your alerts by subscription and Automation account. Automation account name can be found in the `Resource` field in the search of `JobLogs`.
+
 3. To open the **Create rule** screen, click **New Alert Rule** at the top of the page. For more information on the options to configure the alert, see [Log alerts in Azure](../azure-monitor/platform/alerts-unified-log.md).
 
 ### Find all jobs that have completed with errors
 
 In addition to alerting on failures, you can find when a runbook job has a non-terminating error. In these cases, PowerShell produces an error stream, but the non-terminating errors don't cause your job to suspend or fail.
 
 1. In your Log Analytics workspace, click **Logs**.
+
 2. In the query field, type `AzureDiagnostics | where ResourceProvider == "MICROSOFT.AUTOMATION" and Category == "JobStreams" and StreamType_s == "Error" | summarize AggregatedValue = count() by JobId_g`.
+
 3. Click the **Search** button.
 
 ### View job streams for a job