Merge pull request #111476 from BethWilke/branch117

Fixing documentation task 1707212

Author: American-Dipper

articles/automation/automation-edit-textual-runbook.md

@@ -100,4 +100,4 @@ Publish-AzAutomationRunbook -Name $runbookName -AutomationAccountName $automatio
 * [Credentials](automation-credentials.md)
 * [Schedules](automation-schedules.md)
 * [Variables](automation-variables.md)
-
+* [PowerShell cmdlet reference](https://docs.microsoft.com/powershell/module/az.automation/?view=azps-3.7.0#automation)

articles/automation/automation-faq.md

@@ -14,43 +14,44 @@ ms.date: 02/25/2020
 
 This Microsoft FAQ is a list of commonly asked questions about Azure Automation. If you have any additional questions about its capabilities, go to the discussion forum and post your questions. When a question is frequently asked, we add it to this article so that it can be found quickly and easily.
 
+>[!NOTE]
+>This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see [Introducing the new Azure PowerShell Az module](https://docs.microsoft.com/powershell/azure/new-azureps-module-az?view=azps-3.5.0). For Az module installation instructions on your Hybrid Runbook Worker, see [Install the Azure PowerShell Module](https://docs.microsoft.com/powershell/azure/install-az-ps?view=azps-3.5.0). For your Automation account, you can update your modules to the latest version using [How to update Azure PowerShell modules in Azure Automation](automation-update-azure-modules.md).
+
 ## Update Management solution
 
 ### Can I prevent unexpected OS-level upgrades?
 
-On some Linux variants, such as Red Hat Enterprise Linux, OS-level upgrades might occur through packages. This might lead to Update Management runs where the OS version number changes. Because Update Management uses the same methods to update packages that an administrator would use locally on the Linux machine, this behavior is intentional.
+On some Linux variants, such as Red Hat Enterprise Linux, OS-level upgrades might occur through packages. This might lead to Update Management runs in which the OS version number changes. Because Update Management uses the same methods to update packages that an administrator uses locally on a Linux machine, this behavior is intentional.
 
 To avoid updating the OS version through Update Management deployments, use the **Exclusion** feature.
 
-In Red Hat Enterprise Linux, the package name to exclude is redhat-release-server.x86_64.
+In Red Hat Enterprise Linux, the package name to exclude is `redhat-release-server.x86_64`.
 
 ### Why aren't critical/security updates applied?
 
-When you deploy updates to a Linux machine, you can select update classifications. This option filters the updates that are applied to the machine that meet the specified criteria. This filter is applied locally on the machine when the update is deployed.
+When you deploy updates to a Linux machine, you can select update classifications. This option filters the updates that meet the specified criteria. This filter is applied locally on the machine when the update is deployed.
 
-Because Update Management performs update enrichment in the cloud, some updates can be flagged in Update Management as having a security impact, even though the local machine doesn't have that information. As a result, if you apply critical updates to a Linux machine, there might be updates that aren't marked as having a security impact on that machine and therefore the updates aren't applied. However, Update Management might still report that machine as non-compliant because it has additional information about the relevant update.
+Because Update Management performs update enrichment in the cloud, you can flag some updates in Update Management as having a security impact, even though the local machine doesn't have that information. If you apply critical updates to a Linux machine, there might be updates that aren't marked as having a security impact on that machine and therefore aren't applied. However, Update Management might still report that machine as noncompliant because it has additional information about the relevant update.
 
-Deploying updates by update classification doesn't work on RTM versions of CentOS. To properly deploy updates for CentOS, select all classifications to make sure updates are applied. For SUSE, selecting *only* **Other updates** as the classification can cause some security updates to also be installed if security updates related to zypper (package manager) or its dependencies are required first. This behavior is a limitation of zypper. In some cases, you might be required to rerun the update deployment. To verify, check the update log.
+Deploying updates by update classification doesn't work on RTM versions of CentOS. To properly deploy updates for CentOS, select all classifications to make sure updates are applied. For SUSE, selecting ONLY **Other updates** as the classification can cause some additional security updates to be installed if security updates related to zypper (package manager) or its dependencies are required first. This behavior is a limitation of zypper. In some cases, you might be required to rerun the update deployment and then verify the deployment through the update log.
 
 ### Can I deploy updates across Azure tenants?
 
-If you have machines in another Azure tenant reporting to Update Management that you need to patch, you'll have to use the following workaround to get them scheduled. You can use the [New-AzureRmAutomationSchedule](/powershell/module/azurerm.automation/new-azurermautomationschedule) cmdlet with the `-ForUpdate` switch to create a schedule, and use the [New-AzureRmAutomationSoftwareUpdateConfiguration](/powershell/module/azurerm.automation/new-azurermautomationsoftwareupdateconfiguration
-) cmdlet and pass the machines in the other tenant to the `-NonAzureComputer` parameter. The following example shows how to do this:
+If you have machines that need patching in another Azure tenant reporting to Update Management, you must use a following workaround to get them scheduled. You can use the [New-AzAutomationSchedule](https://docs.microsoft.com/powershell/module/Az.Automation/New-AzAutomationSchedule?view=azps-3.7.0) cmdlet with the `ForUpdateConfiguration` parameter specified to create a schedule. You can use the [New-AzAutomationSoftwareUpdateConfiguration](https://docs.microsoft.com/powershell/module/Az.Automation/New-AzAutomationSoftwareUpdateConfiguration?view=azps-3.7.0) cmdlet and pass the machines in the other tenant to the `NonAzureComputer` parameter. The following example shows how to do this.
 
 ```azurepowershell-interactive
 $nonAzurecomputers = @("server-01", "server-02")
 
 $startTime = ([DateTime]::Now).AddMinutes(10)
 
-$sched = New-AzureRmAutomationSchedule -ResourceGroupName mygroup -AutomationAccountName myaccount -Name myupdateconfig -Description test-OneTime -OneTime -StartTime $startTime -ForUpdate
+$sched = New-AzAutomationSchedule -ResourceGroupName mygroup -AutomationAccountName myaccount -Name myupdateconfig -Description test-OneTime -OneTime -StartTime $startTime -ForUpdateConfiguration
 
-New-AzureRmAutomationSoftwareUpdateConfiguration  -ResourceGroupName $rg -AutomationAccountName <automationAccountName> -Schedule $sched -Windows -NonAzureComputer $nonAzurecomputers -Duration (New-TimeSpan -Hours 2) -IncludedUpdateClassification Security,UpdateRollup -ExcludedKbNumber KB01,KB02 -IncludedKbNumber KB100
+New-AzAutomationSoftwareUpdateConfiguration  -ResourceGroupName $rg -AutomationAccountName <automationAccountName> -Schedule $sched -Windows -NonAzureComputer $nonAzurecomputers -Duration (New-TimeSpan -Hours 2) -IncludedUpdateClassification Security,UpdateRollup -ExcludedKbNumber KB01,KB02 -IncludedKbNumber KB100
 ```
 
 ## Next steps
 
-If your question isn't answered here, you can refer to the following forum for additional questions and answers.
+If your question isn't answered here, you can refer to the following sources for additional questions and answers.
 
 - [Azure Automation](https://social.msdn.microsoft.com/Forums/home?forum=azureautomation&filter=alltypes&sort=lastpostdesc)
-
-For general feedback about the Update Management solution, please visit the [feedback forum](https://feedback.azure.com/forums/905242-update-management).
+- [Feedback forum](https://feedback.azure.com/forums/905242-update-management)

articles/automation/automation-first-runbook-graphical.md

@@ -94,7 +94,7 @@ The runbook that you have created is still in Draft mode. It needs to be publish
 1. Click **All Logs** to open the Streams pane for the runbook job. You should only see `Hello World` in the output stream. 
 
     Note that the Streams pane can show other streams for a runbook job, such as Verbose and Error streams, if the runbook writes to them.
-1. Close the Streams pane and the Job pane to return to the  **MyFirstRunbook-Graphical**  page.
+1. Close the Streams pane and the Job pane to return to the MyFirstRunbook-Graphical page.
 1. To view all the jobs for the runbook, select **Jobs** under **Resources**. The Jobs page lists all the jobs created by your runbook. You should see only one job listed, since you have only run the job once.
 1. Click the job name to open the same Job pane that you viewed when you started the runbook. Use this pane to view the details of any job created for the runbook.
 
@@ -120,7 +120,7 @@ Now that you have a variable to hold the subscription ID, you can configure the
 >[!NOTE]
 >For PowerShell runbooks, `Add-AzAccount` and `Add-AzureRMAccount` are aliases for `Connect-AzAccount`. Note that these aliases are not available for your graphical runbooks. A graphical runbook can only use `Connect-AzAccount`itself.
 
-1. Navigate to your runbook and select **Edit** on the **MyFirstRunbook-Graphical** page.
+1. Navigate to your runbook and select **Edit** on the MyFirstRunbook-Graphical page.
 1. You don't need the `Write Hello World to output` entry any more. Just click the ellipsis and select **Delete**.
 1. In the Library control, expand **ASSETS**, then **Connections**. Add `AzureRunAsConnection` to the canvas by selecting **Add to canvas**.
 1. Rename `AzureRunAsConnection` to `Get Run As Connection`.
@@ -135,7 +135,7 @@ Now that you have a variable to hold the subscription ID, you can configure the
 
    * **Data source** -- select **Activity output**.
    * Data source list -- select **Get Automation Connection**.
-   * **Field path** -- type `ApplicationId`. You are specifying the name of the property for the field path because the activity outputs an object with multiple properties.
+   * **Field path** -- type `ApplicationId`. You're specifying the name of the property for the field path because the activity outputs an object with multiple properties.
 
 1. Click **CERTIFICATETHUMBPRINT**, and on the Parameter Value page, make the following settings and then click **OK**.
 
@@ -179,7 +179,7 @@ Now you must add a `Start-AzVM` activity to start a virtual machine. You can pic
 
 Your runbook currently starts the VM in the resource group that you specified for the `Start-AzVM` cmdlet. The runbook will be more useful if you specify both name and resource group when the runbook is started. Let's add input parameters to the runbook to provide that functionality.
 
-1. Open the graphical editor by clicking **Edit** on the **MyFirstRunbook-Graphical** pane.
+1. Open the graphical editor by clicking **Edit** on the MyFirstRunbook-Graphical page.
 1. Select **Input and output** and then **Add input** to open the Runbook Input Parameter pane.
 1. Make the following settings in the provided fields and then click **OK**.
    * **Name** -- specify `VMName`.
@@ -237,7 +237,7 @@ You can now modify the runbook so that it only attempts to start the VM if it is
 1. For the first `Write-Output` control, click **Parameters** and change the **Label** value to **Notify VM Started**.
 1. For **InputObject**, change **Data source** to **PowerShell expression**, and type in the expression `$VMName successfully started.`.
 1. On the second `Write-Output` control, click **Parameters** and change the **Label** value to **Notify VM Start Failed**.
-1. For **InputObject**, change **Data source** to **PowerShell expression**, and type in the expression `$VMName could not start.`.
+1. For **InputObject**, change **Data source** to **PowerShell expression**, and type in the expression `$VMName could not start`.
 1. Create links from `Start-AzVM` to `Notify VM Started` and `Notify VM Start Failed`.
 1. Select the link to `Notify VM Started` and change **Apply condition** to true.
 1. For the **Condition expression**, type `$ActivityOutput['Start-AzVM'].IsSuccessStatusCode -eq $true`. This `Write-Output` control now only runs if the VM starts successfully.
@@ -252,4 +252,6 @@ You can now modify the runbook so that it only attempts to start the VM if it is
 
 * To learn more about graphical authoring, see [Graphical authoring in Azure Automation](automation-graphical-authoring-intro.md).
 * To get started with PowerShell runbooks, see [My first PowerShell runbook](automation-first-runbook-textual-powershell.md).
-* To get started with PowerShell Workflow runbooks, see [My first PowerShell workflow runbook](automation-first-runbook-textual.md).
+* To get started with PowerShell Workflow runbooks, see [My first PowerShell workflow runbook](automation-first-runbook-textual.md).
+* For a PowerShell cmdlet reference, see [Az.Automation](https://docs.microsoft.com/powershell/module/az.automation/?view=azps-3.7.0#automation
+).

articles/automation/automation-first-runbook-textual-powershell.md

@@ -71,7 +71,7 @@ Before you publish the runbook to make it available in production, you should te
 2. Click **Start** to start the test. This should be the only enabled option.
 3. Note that a [runbook job](automation-runbook-execution.md) is created and its status is displayed in the pane.
 
-   The job status starts as `Queued`, indicating that the job is waiting for a runbook worker in the cloud to become available. The status changes to `Starting` when a worker claims the job. Finally, the status becomes `Running` when the runbook actually starts to run.
+   The job status starts as Queued, indicating that the job is waiting for a runbook worker in the cloud to become available. The status changes to Starting when a worker claims the job. Finally, the status becomes Running when the runbook actually starts to run.
 
 4. When the runbook job completes, the Test pane displays its output. In this case, you see `Hello World`.
 
@@ -85,15 +85,15 @@ The runbook that you have created is still in Draft mode. It needs to be publish
 
 1. Click **Publish** to publish the runbook and then **Yes** when prompted.
 1. Scroll left to view the runbook on the Runbooks page, and note that the **Authoring Status** value is set to **Published**.
-1. Scroll back to the right to view the pane for **MyFirstRunbook-PowerShell**.
+1. Scroll back to the right to view the page for **MyFirstRunbook-PowerShell**.
 
    The options across the top allow you to start the runbook now, schedule a future start time, or create a [webhook](automation-webhooks.md) so that the runbook can be started through an HTTP call.
 1. Select **Start** and then **Yes** when prompted to start the runbook. 
 1. A Job pane is opened for the runbook job that has been created. Although you can close this pane, leave it open right now so that you can watch the job's progress. The job status is shown in **Job Summary**, and possible statuses are as described for testing the runbook.
 
    ![Job Summary](media/automation-first-runbook-textual-powershell/job-pane-status-blade-jobsummary.png)
 
-1. Once the runbook status shows `Completed`, click **Output** to open the Output page, where you can see `Hello World` displayed.
+1. Once the runbook status shows Completed, click **Output** to open the Output page, where you can see `Hello World` displayed.
 
    ![Job Output](media/automation-first-runbook-textual-powershell/job-pane-status-blade-outputtile.png)
 
@@ -104,7 +104,7 @@ The runbook that you have created is still in Draft mode. It needs to be publish
 
    ![All Logs](media/automation-first-runbook-textual-powershell/job-pane-status-blade-alllogstile.png)
 
-1. Close the Streams pane and the Job pane to return to the **MyFirstRunbook-PowerShell** page.
+1. Close the Streams pane and the Job pane to return to the MyFirstRunbook-PowerShell page.
 1. Under **Details**, click **Jobs** to open the Jobs page for this runbook. This page lists all the jobs created by your runbook. You should only see one job listed, since you have only run the job once.
 
    ![Job List](media/automation-first-runbook-textual-powershell/runbook-control-job-tile.png)
@@ -145,7 +145,7 @@ As shown in the example below, the Run As connection is made with the [Connect-A
 
    Get-AzVM -ResourceGroupName myResourceGroup -AzContext $AzureContext
    ```
-1. Open the textual editor by clicking **Edit** on the **MyFirstRunbook-PowerShell** page.
+1. Open the textual editor by clicking **Edit** on the MyFirstRunbook-PowerShell page.
 1. You don't need the `Write-Output` line any longer. Just go ahead and delete it.
 1. Type or copy and paste the following code, which handles the authentication with your Automation Run As account.
 
@@ -176,7 +176,7 @@ As shown in the example below, the Run As connection is made with the [Connect-A
 
 ## Step 6 - Add code to start a virtual machine
 
-Now that your runbook is authenticating to your Azure subscription, you can manage resources. Let's add a command to start a virtual machine. You can pick any virtual machine in your Azure subscription, and just hardcode that name in the runbook for now.
+Now that your runbook is authenticating to your Azure subscription, you can manage resources. Let's add a command to start a virtual machine. You can pick any virtual machine in your Azure subscription, and just hard-code that name in the runbook for now.
 
 1. To your runbook script, add the [Start-AzVM](https://docs.microsoft.com/powershell/module/Az.Compute/Start-AzVM?view=azps-3.5.0) cmdlet to start the virtual machine. As shown below, the cmdlet starts a virtual machine with the name `VMName` and with a resource group named `ResourceGroupName`.
 
@@ -206,7 +206,7 @@ Now that your runbook is authenticating to your Azure subscription, you can mana
 
 ## Step 7 - Add an input parameter
 
-Your runbook currently starts the virtual machine that you hardcoded in the runbook. The runbook will be more useful if you specify the virtual machine when the runbook is started. Let's add input parameters to the runbook to provide that functionality.
+Your runbook currently starts the virtual machine that you hard-coded in the runbook. The runbook is more useful if you specify the virtual machine when the runbook is started. Let's add input parameters to the runbook to provide that functionality.
 
 1. In the textual editor, modify the `Start-AzVM` cmdlet to use variables for the parameters `VMName` and `ResourceGroupName`. 
 
@@ -246,6 +246,8 @@ Your runbook currently starts the virtual machine that you hardcoded in the runb
 ## Next steps
 
 * For more information on PowerShell, including language reference and learning modules, see the [PowerShell Docs](/powershell/scripting/overview).
+* For a PowerShell cmdlet reference, see [Az.Automation](https://docs.microsoft.com/powershell/module/az.automation/?view=azps-3.7.0#automation
+).
 * To get started with graphical runbooks, see [My first graphical runbook](automation-first-runbook-graphical.md).
 * To get started with PowerShell Workflow runbooks, see [My first PowerShell Workflow runbook](automation-first-runbook-textual.md).
 * To know more about runbook types and their advantages and limitations, see [Azure Automation runbook types](automation-runbook-types.md).