You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/automation-dsc-overview.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.service: automation
7
7
ms.subservice: dsc
8
8
author: mgoedtel
9
9
ms.author: magoedte
10
-
ms.date: 11/06/2018
10
+
ms.date: 04/15/2020
11
11
ms.topic: conceptual
12
12
manager: carmonm
13
13
---
@@ -30,9 +30,9 @@ Azure Automation State Configuration brings the same management layer to [PowerS
30
30
31
31

32
32
33
-
### Import reporting data into Azure Monitor logs
33
+
### Import reporting data into Azure Monitor Logs
34
34
35
-
Nodes that are managed with Azure Automation State Configuration send detailed reporting status data to the built-in pull server. You can configure Azure Automation State Configuration to send this data to your Log Analytics workspace. For more information, see [Forward Azure Automation State Configuration reporting data to Azure Monitor logs](automation-dsc-diagnostics.md).
35
+
Nodes that are managed with Azure Automation State Configuration send detailed reporting status data to the built-in pull server. You can configure Azure Automation State Configuration to send this data to your Log Analytics workspace. For more information, see [Forward Azure Automation State Configuration reporting data to Azure Monitor Logs](automation-dsc-diagnostics.md).
36
36
37
37
## Prerequisites
38
38
@@ -74,8 +74,7 @@ If your nodes are located in a private network, the following port and URLs are
74
74
* Global URL of US Gov Virginia: ***.azure-automation.us**
If you are using DSC resources that communicate between nodes,
78
-
such as the [WaitFor* resources](https://docs.microsoft.com/powershell/scripting/dsc/reference/resources/windows/waitForAllResource), you also need to allow traffic between nodes. See the documentation for each DSC resource to understand these network requirements.
77
+
If you are using DSC resources that communicate between nodes, such as the [WaitFor* resources](https://docs.microsoft.com/powershell/scripting/dsc/reference/resources/windows/waitForAllResource), you also need to allow communication between nodes. To understand these network requirements, see the documentation for each DSC resource.
79
78
80
79
#### Proxy support
81
80
@@ -84,7 +83,7 @@ Proxy support for the DSC agent is available in Windows version 1809 and later.
84
83
>[!NOTE]
85
84
>Azure Automation State Configuration doesn't provide DSC proxy support for earlier versions of Windows.
86
85
87
-
For Linux nodes, the DSC agent supports the proxy and uses the `http_proxy` variable to determine the URL.
86
+
For Linux nodes, the DSC agent supports a proxy server and uses the `http_proxy` variable to specify the URL.
88
87
89
88
#### Azure Automation State Configuration network ranges and namespace
0 commit comments