Skip to content

Commit 3517516

Browse files
committed
More changes
1 parent 71ee940 commit 3517516

File tree

2 files changed

+49
-42
lines changed

2 files changed

+49
-42
lines changed

articles/sentinel/connect-azure-windows-microsoft-services.md

Lines changed: 39 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -129,45 +129,7 @@ You can find and query the data for each resource type using the table name that
129129

130130
## Windows agent-based connections
131131

132-
# [Log Analytics Agent (Legacy)](#tab/LAA)
133-
134-
### Prerequisites
135-
136-
- You must have read and write permissions on the Log Analytics workspace, and any workspace that contains machines you want to collect logs from.
137-
- You must have the **Log Analytics Contributor** role on the SecurityInsights (Azure Sentinel) solution on those workspaces, in addition to any Azure Sentinel roles.
138-
139-
### Instructions
140-
141-
#### Install the agent
142-
143-
1. From the Azure Sentinel navigation menu, select **Data connectors**.
144-
145-
1. Select your service (**DNS** or **Windows Firewall**) and then select **Open connector page**.
146-
147-
1. Install and onboard the agent on the device that generates the logs.
148-
149-
| Machine type | Instructions |
150-
| --------- | --------- |
151-
| **For an Azure Windows VM** | 1. Under **Choose where to install the agent**, expand **Install agent on Azure Windows virtual machine**. <br><br>2. Select the **Download & install agent for Azure Windows Virtual machines >** link. <br><br>3. In the **Virtual machines** blade, select a virtual machine to install the agent on, and then select **Connect**. Repeat this step for each VM you wish to connect. |
152-
| **For any other Windows machine** | 1. Under **Choose where to install the agent**, expand **Install agent on non-Azure Windows Machine** <br><br>2. Select the **Download & install agent for non-Azure Windows machines >** link. <br><br>3. In the **Agents management** blade, on the **Windows servers** tab, select the **Download Windows Agent** link for either 32-bit or 64-bit systems, as appropriate. <br><br>4. Using the downloaded executable file, install the agent on the Windows systems of your choice, and configure it using the **Workspace ID and Keys** that appear below the download links in the previous step. |
153-
| | |
154-
155-
> [!NOTE]
156-
>
157-
> To allow Windows systems without the necessary internet connectivity to still stream events to Azure Sentinel, download and install the **Log Analytics Gateway** on a separate machine, using the **Download Log Analytics Gateway** link on the **Agents Management** page, to act as a proxy. You will still need to install the Log Analytics agent on each Windows system whose events you want to collect.
158-
>
159-
> For more information on this scenario, see the [**Log Analytics gateway** documentation](../azure-monitor/agents/gateway.md).
160-
161-
For additional installation options and further details, see the [**Log Analytics agent** documentation](../azure-monitor/agents/agent-windows.md).
162-
163-
164-
#### Determine the logs to send
165-
166-
For the Windows DNS Server and Windows Firewall connectors, select the **Install solution** button. For the legacy Security Events connector, choose the [**event set**](windows-security-event-id-reference.md) you wish to send and select **Update**.
167-
168-
You can find and query the data for these services using the table names in their respective sections in the [Data connectors reference](data-connectors-reference.md) page.
169-
170-
# [Azure Monitor Agent (New)](#tab/AMA)
132+
# [Azure Monitor Agent](#tab/AMA)
171133

172134
> [!IMPORTANT]
173135
>
@@ -281,6 +243,44 @@ PUT https://management.azure.com/subscriptions/703362b3-f278-4e4b-9179-c76eaf41f
281243
}
282244
```
283245

246+
# [Log Analytics Agent (Legacy)](#tab/LAA)
247+
248+
### Prerequisites
249+
250+
- You must have read and write permissions on the Log Analytics workspace, and any workspace that contains machines you want to collect logs from.
251+
- You must have the **Log Analytics Contributor** role on the SecurityInsights (Azure Sentinel) solution on those workspaces, in addition to any Azure Sentinel roles.
252+
253+
### Instructions
254+
255+
#### Install the agent
256+
257+
1. From the Azure Sentinel navigation menu, select **Data connectors**.
258+
259+
1. Select your service (**DNS** or **Windows Firewall**) and then select **Open connector page**.
260+
261+
1. Install and onboard the agent on the device that generates the logs.
262+
263+
| Machine type | Instructions |
264+
| --------- | --------- |
265+
| **For an Azure Windows VM** | 1. Under **Choose where to install the agent**, expand **Install agent on Azure Windows virtual machine**. <br><br>2. Select the **Download & install agent for Azure Windows Virtual machines >** link. <br><br>3. In the **Virtual machines** blade, select a virtual machine to install the agent on, and then select **Connect**. Repeat this step for each VM you wish to connect. |
266+
| **For any other Windows machine** | 1. Under **Choose where to install the agent**, expand **Install agent on non-Azure Windows Machine** <br><br>2. Select the **Download & install agent for non-Azure Windows machines >** link. <br><br>3. In the **Agents management** blade, on the **Windows servers** tab, select the **Download Windows Agent** link for either 32-bit or 64-bit systems, as appropriate. <br><br>4. Using the downloaded executable file, install the agent on the Windows systems of your choice, and configure it using the **Workspace ID and Keys** that appear below the download links in the previous step. |
267+
| | |
268+
269+
> [!NOTE]
270+
>
271+
> To allow Windows systems without the necessary internet connectivity to still stream events to Azure Sentinel, download and install the **Log Analytics Gateway** on a separate machine, using the **Download Log Analytics Gateway** link on the **Agents Management** page, to act as a proxy. You will still need to install the Log Analytics agent on each Windows system whose events you want to collect.
272+
>
273+
> For more information on this scenario, see the [**Log Analytics gateway** documentation](../azure-monitor/agents/gateway.md).
274+
275+
For additional installation options and further details, see the [**Log Analytics agent** documentation](../azure-monitor/agents/agent-windows.md).
276+
277+
278+
#### Determine the logs to send
279+
280+
For the Windows DNS Server and Windows Firewall connectors, select the **Install solution** button. For the legacy Security Events connector, choose the [**event set**](windows-security-event-id-reference.md) you wish to send and select **Update**.
281+
282+
You can find and query the data for these services using the table names in their respective sections in the [Data connectors reference](data-connectors-reference.md) page.
283+
284284
---
285285

286286
## Next steps

articles/sentinel/data-connectors-reference.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1329,7 +1329,7 @@ If a longer timeout duration is required, consider upgrading to an [App Service
13291329
13301330
For more information, see [Insecure protocols workbook setup](./get-visibility.md#use-built-in-workbooks).
13311331
1332-
See also: [**Windows Security Events**](#windows-security-events-preview).
1332+
See also: [**Windows Security Events**](#windows-security-events-preview) connector
13331333
13341334
## SentinelOne (Preview)
13351335
@@ -1562,11 +1562,16 @@ Follow the instructions to obtain the credentials.
15621562
15631563
| Connector attribute | Description |
15641564
| --- | --- |
1565-
| **Data ingestion method** | **Azure service-to-service integration: <br>[Azure Monitor agent-based connections](connect-azure-windows-microsoft-services.md?tabs=AMA#windows-agent-based-connections)** |
1565+
| **Data ingestion method** | **Azure service-to-service integration: <br>[Azure Monitor agent-based connections](connect-azure-windows-microsoft-services.md?tabs=AMA#windows-agent-based-connections)**<br><br>[Additional instructions for deploying the Windows Forwarded Events connector](#additional-instructions-for-deploying-the-windows-forwarded-events-connector) |
1566+
| **Prerequisites** | You must have Windows Event Collection (WEC) enabled and running.<br>Install the Azure Monitor Agent on the WEC machine. |
15661567
| **Log Analytics table(s)** | SecurityEvents |
15671568
| **Supported by** | Microsoft |
15681569
| | |
15691570
1571+
### Additional instructions for deploying the Windows Forwarded Events connector
1572+
1573+
We recommend installing the [Advanced SIEM Information Model (ASIM)](normalization.md) parsers to ensure full support for data normalization. You can deploy these parsers from the [Azure Sentinel GitHub repository(link)] using the **Deploy** button in the **ASIM normalization support** section of the connector page.
1574+
15701575
## Windows Firewall
15711576
15721577
| Connector attribute | Description |
@@ -1580,11 +1585,13 @@ Follow the instructions to obtain the credentials.
15801585
15811586
| Connector attribute | Description |
15821587
| --- | --- |
1583-
| **Data ingestion method** | **Azure service-to-service integration: <br>[Connect to Windows servers to collect security events](connect-windows-security-events.md)** (Top connector article);<br>**[Azure Monitor agent-based connections](connect-azure-windows-microsoft-services.md?tabs=AMA#windows-agent-based-connections)** |
1588+
| **Data ingestion method** | **Azure service-to-service integration: <br>[Azure Monitor agent-based connections](connect-azure-windows-microsoft-services.md?tabs=AMA#windows-agent-based-connections)** |
15841589
| **Log Analytics table(s)** | SecurityEvents |
15851590
| **Supported by** | Microsoft |
15861591
| | |
15871592
1593+
See also: Legacy [**Security events**](#security-events-windows) connector
1594+
15881595
## Workplace from Facebook (Preview)
15891596
15901597
| Connector attribute | Description |

0 commit comments

Comments
 (0)