Merge pull request #10031 from Azure/auto-dsc

Make OS Restriction in DSC Node Registration explicit

Author: markcowl

src/Automation/Automation/ChangeLog.md

@@ -19,6 +19,7 @@
 -->
 ## Upcoming Release
 * Fixed example typo in reference documentation for `Register-AzAutomationDscNode`
+* Added clarification on OS restriction to Register-AzAutomationDSCNode
 
 ## Version 1.3.2
 * Fixed miscellaneous typos across module

src/Automation/Automation/help/Register-AzAutomationDscNode.md

@@ -9,7 +9,7 @@ schema: 2.0.0
 # Register-AzAutomationDscNode
 
 ## SYNOPSIS
-Registers an Azure virtual machine as a DSC node for an Automation account.
+Registers an Azure virtual machine running Windows OS as a DSC node for an Automation account.
 
 ## SYNTAX
 
@@ -22,7 +22,7 @@ Register-AzAutomationDscNode -AzureVMName <String> [-NodeConfigurationName <Stri
 ```
 
 ## DESCRIPTION
-The **Register-AzAutomationDscNode** cmdlet registers an Azure virtual machine as an APS Desired State Configuration (DSC) node in an Azure Automation account.
+The **Register-AzAutomationDscNode** cmdlet registers an Azure virtual machine as an APS Desired State Configuration (DSC) node in an Azure Automation account. This cmdlet will only register VMs running Windows OS as an Automation DSC Node for an account.
 
 If you need to register a node to an automation account in a different subscription,
 you will need to use an ARM template rather than cmdlets.