Merge pull request #214682 from SnehaSudhirG/17Oct-Docupdates-TSStatusReports

added info in possible causes section

Author: prmerger-automator[bot]

articles/automation/troubleshoot/desired-state-configuration.md

@@ -3,7 +3,7 @@ title: Troubleshoot Azure Automation State Configuration issues
 description: This article tells how to troubleshoot and resolve Azure Automation State Configuration issues.
 services: automation
 ms.subservice:
-ms.date: 04/16/2019
+ms.date: 10/17/2022
 ms.topic: troubleshooting
 ms.custom: devx-track-azurepowershell
 ---
@@ -101,9 +101,13 @@ VM has reported a failure when processing extension 'Microsoft.Powershell.DSC /
 
 ### Cause
 
-This issue is caused by a bad or expired certificate. See [Re-register a node](../automation-dsc-onboarding.md#re-register-a-node).
+The following are the possible causes:
 
-This issue might also be caused by a proxy configuration not allowing access to ***.azure-automation.net**. For more information, see [Configuration of private networks](../automation-dsc-overview.md#network-planning).
+- A bad or expired certificate. See [Re-register a node](../automation-dsc-onboarding.md#re-register-a-node).
+
+- A proxy configuration that isn't allowing access to ***.azure-automation.net**. For more information, see [Configuration of private networks](../automation-dsc-overview.md#network-planning). 
+
+- When you disable local authentication in Azure Automation. See [Disable local authentication](../disable-local-authentication.md). To fix it, see [re-enable local authentication](../disable-local-authentication.md#re-enable-local-authentication).
 
 ### Resolution