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-onboard-solutions-from-browse.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,12 +1,12 @@
1
1
---
2
-
title: Enable Azure Automation Update Management from Azure portal
2
+
title: Enable Azure Automation Update Management from the Azure portal
3
3
description: This article tells how to enable Update Management from the Azure portal.
4
4
services: automation
5
5
ms.date: 04/11/2019
6
6
ms.topic: article
7
7
ms.custom: mvc
8
8
---
9
-
# Enable Update Management from Azure portal
9
+
# Enable Update Management from the Azure portal
10
10
11
11
This article describes how you can enable the [Update Management](automation-update-management.md) feature for VMs by browsing the Azure portal. To enable Azure VMs at scale, you must enable an existing VM using Update Management.
Copy file name to clipboardExpand all lines: articles/automation/change-tracking-file-contents.md
+18-32Lines changed: 18 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,28 +9,14 @@ ms.topic: conceptual
9
9
10
10
# Manage Change Tracking and Inventory
11
11
12
-
Azure Automation enables the [Change Tracking and Inventory](change-tracking.md) feature for machines in your environment. The feature tracks and makes available changes in registry keys, files, contents, and the like. This article includes procedures for working with this feature.
12
+
When you add a new file or registry key to track, Azure Automation enables it for [Change Tracking and Inventory](change-tracking.md). This article describes how to configure tracking, review tracking results, and handle alerts when changes are detected.
13
13
14
-
## Enable the full Change Tracking and Inventory feature
14
+
Before using the procedures in this article, ensure that you've enabled Change Tracking and Inventory on your VMs using one of these techniques:
15
15
16
-
If you have enabled [Azure Security Center File Integrity Monitoring (FIM)](https://docs.microsoft.com/azure/security-center/security-center-file-integrity-monitoring), you can use the full Change Tracking and Inventory feature for your machines as described below. Your settings are not removed by this process.
17
-
18
-
> [!NOTE]
19
-
> Enabling the full Change Tracking and Inventory feature might cause additional charges. See [Automation Pricing](https://azure.microsoft.com/pricing/details/automation/).
20
-
21
-
1. Remove the monitoring solution by navigating to the workspace and locating it in the [list of installed monitoring solutions](../azure-monitor/insights/solutions.md#list-installed-monitoring-solutions).
22
-
2. Click on the name of the solution to open its summary page and then click on **Delete**, as detailed in [Remove a monitoring solution](../azure-monitor/insights/solutions.md#remove-a-monitoring-solution).
23
-
3. To re-enable Change Tracking and Inventory, navigate to the Automation account and select **Change tracking** or **Inventory** under **Configuration Management**.
24
-
4. Choose the Log Analytics workspace and Automation account, confirm your workspace settings, and click **Enable**.
25
-
26
-
## <aname="onboard"></a>Enable machines for Change Tracking and Inventory
27
-
28
-
To begin tracking changes, you must enable Change Tracking and Inventory in Azure Automation. Here are the recommended and supported ways to enable this feature for your machines:
29
-
30
-
*[Enable from a virtual machine](automation-onboard-solutions-from-vm.md)
31
-
*[Enable from browsing multiple machines](automation-onboard-solutions-from-browse.md)
32
-
*[Enable from your Automation account](automation-onboard-solutions-from-automation-account.md)
33
-
*[Enable in an Azure Automation runbook](automation-onboard-solutions.md)
16
+
*[Enable Change Tracking and Inventory from an Automation account](automation-enable-changes-from-auto-acct.md)
17
+
*[Enable Change Tracking and Inventory by browsing in Azure portal](automation-enable-changes-from-browse.md)
18
+
*[Enable Change Tracking and Inventory from a runbook](automation-enable-changes-from-runbook.md)
19
+
*[Enable Change Tracking and Inventory from an Azure VM](automation-enable-changes-from-vm.md)
34
20
35
21
## Track files
36
22
@@ -49,7 +35,7 @@ Use the following steps to configure file tracking on Windows computers:
49
35
|Item Name | Friendly name of the file to be tracked. |
50
36
|Group | A group name for logically grouping files. |
51
37
|Enter Path | The path to check for the file, for example, **c:\temp\\\*.txt**. You can also use environment variables, such as `%winDir%\System32\\\*.*`. |
52
-
|Path Type | The type of path. Possible values are File and Directory. |
38
+
|Path Type | The type of path. Possible values are File and Folder. |
53
39
|Recursion | True if recursion is used when looking for the item to be tracked, and False otherwise. |
54
40
|Upload file content | True to upload file content on tracked changes, and False otherwise.|
55
41
@@ -72,8 +58,8 @@ Use the following steps to configure file tracking on Linux computers:
72
58
|Enter Path | The path to check for the file, for example, **/etc/*.conf**. |
73
59
|Path Type | The type of path. Possible values are File and Directory. |
74
60
|Recursion | True if recursion is used when looking for the item to be tracked, and False otherwise. |
75
-
|Use Sudo| True to use sudo when checking for the item, and False otherwise. |
76
-
|Links | Setting that determines how to deal with symbolic links when traversing directories. Possible values are:<br> Ignore - Ignores symbolic links and doesn't include the files/directories referenced.<br>Follow - Follows the symbolic links during recursion and also includes the files/directories referenced.<br>Manage - Follows the symbolic links and allows altering of returned content.**Note**- This option isn't recommended, as it doesn't support file content retrieval. |
61
+
|Use Ludo| True to use sudo when checking for the item, and False otherwise. |
62
+
|Links | Setting that determines how to deal with symbolic links when traversing directories. Possible values are:<br> Ignore - Ignores symbolic links and doesn't include the files/directories referenced.<br>Follow - Follows the symbolic links during recursion and also includes the files/directories referenced.<br>Manage - Follows the symbolic links and allows altering of returned content.<br>**Note:**The Manage option isn't recommended, as it doesn't support file content retrieval. |
77
63
|Upload file content | True to upload file content on tracked changes, and False otherwise. |
78
64
79
65
5. Ensure that you specify True for **Upload file content**. This setting enables file content tracking for the indicated file path.
@@ -98,7 +84,7 @@ File content tracking allows you to view the contents of a file before and after
98
84
2. Click **Edit Settings** (the gear symbol).
99
85
3. Select **File Content** and click **Link**. This selection opens the Add Content Location for Change Tracking pane.
4. Select the subscription and storage account to use for storing the file contents.
104
90
@@ -118,7 +104,7 @@ Once Change Tracking and Inventory detects a change for a tracked file, you can
118
104
119
105
1. In the Azure portal, open your Automation account, and then select **Change tracking** under **Configuration Management**.
120
106
121
-
2. Choose a file in the list of changes and select **View File Content Changes** to see the contents of the file. The Change Details pane shows you the standard before and after file information.
107
+
2. Choose a file in the list of changes and select **View File Content Changes** to see the contents of the file. The change details pane shows you the standard before and after file information for each property.
@@ -147,31 +133,31 @@ You can do various searches against the Azure Monitor logs for change records. W
147
133
148
134
|Query |Description |
149
135
|---------|---------|
150
-
|ConfigurationData<br>| where ConfigDataType == "Microsoft services" and SvcStartupType == "Auto"<br>| where SvcState == "Stopped"<br>| summarize arg_max(TimeGenerated, *) by SoftwareName, Computer | Shows the most recent inventory records for Microsoft services that were set to Auto but were reported as being Stopped. Results are limited to the most recent record for the specified software name and computer. |
151
-
|ConfigurationChange<br>| where ConfigChangeType == "Software" and ChangeCategory == "Removed"<br>| order by TimeGenerated desc|Shows change records for removed software.|
136
+
|`ConfigurationData`<br>|`where ConfigDataType == "Microsoft services" and SvcStartupType == "Auto"`<br>|`where SvcState == "Stopped"`<br>|`summarize arg_max(TimeGenerated, *) by SoftwareName, Computer`| Shows the most recent inventory records for Microsoft services that were set to Auto but were reported as being Stopped. Results are limited to the most recent record for the specified software name and computer. |
137
+
|`ConfigurationChange`<br>|`where ConfigChangeType == "Software" and ChangeCategory == "Removed"`<br>|`order by TimeGenerated desc`|Shows change records for removed software.|
152
138
153
139
## Create alerts on changes
154
140
155
141
The following example shows that the file **C:\windows\system32\drivers\etc\hosts** has been modified on a machine. This file is important because Windows uses it to resolve host names to IP addresses. This operation takes precedence over DNS, and might result in connectivity issues. It can also lead to redirection of traffic to malicious or otherwise dangerous websites.
156
142
157
-

143
+

158
144
159
145
Let's use this example to discuss the steps for creating alerts on a change.
160
146
161
147
1. In your Automation account, select **Change tracking** under **Configuration Management**, then select **Log Analytics**.
162
-
2. In the Logs search, look for content changes to the **hosts** file with the query `ConfigurationChange | where FieldsChanged contains "FileContentChecksum" and FileSystemPath contains "hosts"`. This query looks for a content change for files with a fully qualified path containing the word “hosts”. You can also ask for a specific file by changing the path portion to its fully qualified form, for example, using `FileSystemPath == "c:\windows\system32\drivers\etc\hosts"`.
148
+
2. In the Logs search, look for content changes to the **hosts** file with the query `ConfigurationChange | where FieldsChanged contains "FileContentChecksum" and FileSystemPath contains "hosts"`. This query looks for a content change for files with a fully qualified path containing the word `hosts`. You can also ask for a specific file by changing the path portion to its fully qualified form, for example, using `FileSystemPath == "c:\windows\system32\drivers\etc\hosts"`.
163
149
164
-
3. After the query returns the desired results, click **New alert rule** in the log search to open the alert creation page. You can also navigate to this page through **Azure Monitor** in the Azure portal.
150
+
3. After the query returns its results, click **New alert rule** in the log search to open the alert creation page. You can also navigate to this page through **Azure Monitor** in the Azure portal.
165
151
166
152
4. Check your query again and modify the alert logic. In this case, you want the alert to be triggered if there's even one change detected across all the machines in the environment.
167
153
168
154

169
155
170
-
5. After the alert logic is set, assign action groups to perform actions in response to the alert being triggered. In this case, we're setting up emails to be sent and an IT Service Management (ITSM) ticket to be created.
156
+
5. After the alert logic is set, assign action groups to perform actions in response to triggering of the alert. In this case, we're setting up emails to be sent and an IT Service Management (ITSM) ticket to be created.
171
157
172
158

173
159
174
160
## Next steps
175
161
176
162
* If you need to search logs stored in your Log Analytics workspace, see [Log searches in Azure Monitor logs](../log-analytics/log-analytics-log-searches.md).
177
-
* To troubleshoot feature errors, see [Troubleshoot Change Tracking and Inventory issues](troubleshoot/change-tracking.md).
163
+
* To troubleshoot feature errors, see [Troubleshoot Change Tracking and Inventory issues](troubleshoot/change-tracking.md).
0 commit comments