Merge pull request #222730 from SnehaSudhirG/03Jan-DocUpdateDSCNode

Added DSC node status values

Author: prmerger-automator[bot]

articles/automation/automation-dsc-getting-started.md

@@ -3,7 +3,7 @@ title: Get started with Azure Automation State Configuration
 description: This article tells how to do the most common tasks in Azure Automation State Configuration.
 services: automation
 ms.subservice: dsc
-ms.date: 04/15/2019
+ms.date: 01/03/2022
 ms.topic: conceptual
 ---
 
@@ -183,6 +183,22 @@ account in the **Nodes** tab of the State configuration (DSC) page.
 1. On the Automation account page, click **State configuration (DSC)** under **Configuration Management**.
 1. On the State configuration (DSC) page, click the **Nodes** tab.
 
+
+### DSC nodes status values
+
+The DSC node can take any of the following six values as follows:
+
+- **Failed** - This status is displayed when an error occurs while applying one or more configurations on a node.
+- **Not compliant** - This status is displayed when drift occurs on a node and it requires a close review if it is systematic.
+- **Unresponsive** - This status is displayed when a node has not been checked in for more than 24 hours.
+- **Pending** - This status is displayed when a node has a new configuration to apply and the pull server is awaiting node check in.
+- **In progress** - This status is displayed when a node applies configuration, and the pull server is awaiting status.
+- **Compliant** - This status is displayed when a node has a valid configuration, and no drift occurs presently.
+
+>[!NOTE]
+>- **RefreshFrequencyMins** - It defines the frequency of node contacting the agent service and can be provided as part of onboarding to DSC. It takes a maximum value of 10080 minutes.
+>- Node will be marked as **Unresponsive** if the node does not contact the agent service for 1440 minutes (1 Day). We recommend that you use **RefreshFrequencyMins** value < 1440 minutes, else the node would show in a false **Unresponsive** state. 
+
 ## View reports for managed nodes
 
 Each time State Configuration performs a consistency check on a managed node, the