Merge pull request #113516 from BethWilke/branch129

ShannonLeavitt · web-flow · commit df91792553e1 · 2020-05-01T09:27:58.000-06:00
Fixing 1709035, 1712624, latent errors
diff --git a/articles/automation/automation-connections.md b/articles/automation/automation-connections.md
@@ -35,9 +35,9 @@ Azure Automation makes the following built-in connection types available:
 
 In most cases, you don't need to create a connection resource because it is created when you create a [Run As account](manage-runas-account.md).
 
-## Windows PowerShell cmdlets to access connections
+## PowerShell cmdlets to access connections
 
-The cmdlets in the following table create and manage Automation connections with Windows PowerShell. They ship as part of the [Az modules](shared-resources/modules.md#az-modules).
+The cmdlets in the following table create and manage Automation connections with PowerShell. They ship as part of the [Az modules](shared-resources/modules.md#az-modules).
 
 |Cmdlet|Description|
 |---|---|
diff --git a/articles/automation/graphical-runbook-sdk.md b/articles/automation/graphical-runbook-sdk.md
@@ -13,7 +13,7 @@ ms.topic: conceptual
 
 ## Prerequisites
 
-Import the `Microsoft.Azure.Management.Automation.GraphicalRunbook.Model` package into your project.
+Import the [Microsoft.Azure.Management.Automation.Models](https://docs.microsoft.com/dotnet/api/microsoft.azure.management.automation.models?view=azure-dotnet) package into your project.
 
 ## Create a runbook object instance
 
diff --git a/articles/automation/shared-resources/certificates.md b/articles/automation/shared-resources/certificates.md
@@ -21,9 +21,9 @@ Certificates are stored securely in Azure Automation for access by runbooks and
 >[!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).
 
-## Windows PowerShell cmdlets to access certificates
+## PowerShell cmdlets to access certificates
 
-The cmdlets in the following table create and manage Automation certificates with Windows PowerShell. They ship as part of the [Az modules](modules.md#az-modules).
+The cmdlets in the following table create and manage Automation certificates with PowerShell. They ship as part of the [Az modules](modules.md#az-modules).
 
 |Cmdlet |Description|
 | --- | ---|
diff --git a/articles/automation/shared-resources/credentials.md b/articles/automation/shared-resources/credentials.md
@@ -23,9 +23,9 @@ An Automation credential asset holds an object that contains security credential
 
 [!INCLUDE [gdpr-dsr-and-stp-note.md](../../../includes/gdpr-dsr-and-stp-note.md)]
 
-## Windows PowerShell cmdlets used to access credentials
+## PowerShell cmdlets used to access credentials
 
-The cmdlets in the following table create and manage Automation credentials with Windows PowerShell. They ship as part of the [Az modules](modules.md#az-modules).
+The cmdlets in the following table create and manage Automation credentials with PowerShell. They ship as part of the [Az modules](modules.md#az-modules).
 
 | Cmdlet | Description |
 |:--- |:--- |
diff --git a/articles/automation/shared-resources/modules.md b/articles/automation/shared-resources/modules.md
@@ -112,15 +112,15 @@ This section includes considerations to take into account when migrating to the
 
  We don't recommend running AzureRM modules and Az modules in the same Automation account. When you're sure you want to migrate from AzureRM to Az, it's best to fully commit to a complete migration. The most important reason for this is that Azure Automation often reuses sandboxes within the Automation account to save on startup times. If you don't make a full module migration, you might start a job using only AzureRM modules, then start another job using only Az modules. The sandbox soon crashes and you receive a fatal error stating that the modules aren’t compatible. This situation results in randomly occurring crashes for any given runbook or configuration. 
 
-#### Import of Az modules into the PowerShell session
+#### Importing Az modules into the PowerShell session
 
 Importing an Az module into your Automation account doesn't automatically import the module into the PowerShell session that runbooks use. Modules are imported into the PowerShell session in the following situations:
 
 * When a runbook invokes a cmdlet from a module
 * When a runbook imports the module explicitly with the [Import-Module](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/import-module?view=powershell-7) cmdlet
 * When a runbook imports another dependent module
 
-#### Testing for your runbooks and DSC configurations prior to module migration
+#### Testing your runbooks and DSC configurations prior to module migration
 
 Be sure to test all runbooks and DSC configurations carefully in a separate Automation account before migrating to the Az modules. 
 
@@ -304,7 +304,7 @@ Your module should not depend on any unique registry settings on a host. Example
 
 Make sure that all files in the module have paths with fewer than 140 characters. Any paths over 140 characters in length cause issues with importing runbooks. Azure Automation can't import a file with path size over 140 characters into the PowerShell session with `Import-Module`.
 
-## Importing modules
+## Import modules
 
 This section defines several ways that you can import a module into your Automation account. 
 
@@ -355,7 +355,7 @@ To import a PowerShell Gallery module directly from your Automation account:
 
 ![PowerShell Gallery import from Azure portal](../media/modules/gallery-azure-portal.png)
 
-## Deleting modules
+## Delete modules
 
 If you have issues with a module or you need to roll back to a previous version of a module, you can delete it from your Automation account. You can't delete the original versions of the [default modules](#default-modules) that are imported when you create an Automation account. If the module to delete is a newer version of one of the [default modules](#default-modules), it rolls back to the version that was installed with your Automation account. Otherwise, any module you delete from your Automation account is removed.
 
diff --git a/articles/automation/shared-resources/schedules.md b/articles/automation/shared-resources/schedules.md
@@ -21,9 +21,9 @@ To schedule a runbook in Azure Automation to start at a specified time, you link
 >[!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 by using [How to update Azure PowerShell modules in Azure Automation](../automation-update-azure-modules.md).
 
-## Windows PowerShell cmdlets used to access schedules
+## PowerShell cmdlets used to access schedules
 
-The cmdlets in the following table create and manage Automation schedules with Windows PowerShell. They ship as part of the [Az modules](modules.md#az-modules).
+The cmdlets in the following table create and manage Automation schedules with PowerShell. They ship as part of the [Az modules](modules.md#az-modules). 
 
 | Cmdlets | Description |
 |:--- |:--- |
@@ -194,4 +194,4 @@ Remove-AzAutomationSchedule -AutomationAccountName $automationAccountName `
 ## Next steps
 
 * To learn more about the cmdlets used to access schedules, see [Manage modules in Azure Automation](modules.md).
-* For general information about runbooks, see [Runbook execution in Azure Automation](../automation-runbook-execution.md).
+* For general information about runbooks, see [Runbook execution in Azure Automation](../automation-runbook-execution.md).
diff --git a/articles/automation/shared-resources/variables.md b/articles/automation/shared-resources/variables.md
@@ -51,9 +51,9 @@ You can store multiple values to a single variable by creating an array or hasht
 >[!NOTE]
 >VM name variables can be a maximum of 80 characters. Resource group variables can be a maximum of 90 characters. See [Naming rules and restrictions for Azure resources](https://docs.microsoft.com/azure/azure-resource-manager/management/resource-name-rules).
 
-## Windows PowerShell cmdlets to manage variables
+## PowerShell cmdlets to access variables
 
-The cmdlets in the following table create and manage Automation variables with Windows PowerShell. They ship as part of the [Az modules](modules.md#az-modules).
+The cmdlets in the following table create and manage Automation variables with PowerShell. They ship as part of the [Az modules](modules.md#az-modules).
 
 | Cmdlet | Description |
 |:---|:---|
diff --git a/articles/automation/troubleshoot/desired-state-configuration.md b/articles/automation/troubleshoot/desired-state-configuration.md
@@ -45,7 +45,7 @@ For information on using **xDscDiagnostics**, see [Using xDscDiagnostics to anal
 
 ### 3. Ensure that nodes and the Automation workspace have required modules
 
-DSC depends on modules installed on the node. When you use Azure Automation State Configuration, import any required modules into your Automation account by following the steps in [Import Modules](../shared-resources/modules.md#importing-modules). Configurations can also have a dependency on specific versions of modules. For more information, see [Troubleshoot modules](shared-resources.md#modules).
+DSC depends on modules installed on the node. When you use Azure Automation State Configuration, import any required modules into your Automation account by following the steps in [Import Modules](../shared-resources/modules.md#import-modules). Configurations can also have a dependency on specific versions of modules. For more information, see [Troubleshoot modules](shared-resources.md#modules).
 
 ## <a name="unsupported-characters"></a>Scenario: A configuration with special characters can't be deleted from the portal
 
diff --git a/articles/automation/troubleshoot/runbooks.md b/articles/automation/troubleshoot/runbooks.md
@@ -36,7 +36,7 @@ When you receive errors during runbook execution in Azure Automation, you can us
 
 1. Ensure that your nodes and Automation workspace have the required modules.
 
-    If your runbook imports any modules, verify that they're available to your Automation account by using the steps in [Import modules](../shared-resources/modules.md#importing-modules). Update your PowerShell modules to the latest version by following the instructions in [Update Azure PowerShell modules in Azure Automation](../automation-update-azure-modules.md). For more troubleshooting information, see [Troubleshoot modules](shared-resources.md#modules).
+    If your runbook imports any modules, verify that they're available to your Automation account by using the steps in [Import modules](../shared-resources/modules.md#import-modules). Update your PowerShell modules to the latest version by following the instructions in [Update Azure PowerShell modules in Azure Automation](../automation-update-azure-modules.md). For more troubleshooting information, see [Troubleshoot modules](shared-resources.md#modules).
 
 1. If your runbook is suspended or unexpectedly fails:
 
