Skip to content

Commit 1f65484

Browse files
committed
Link correction
1 parent e905a5f commit 1f65484

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/sentinel/connect-windows-security-events.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ The Security Events connector lets you stream all security events from your Wind
4242
> Security Events collection within the context of a single workspace can be configured from either Azure Security Center or Azure Sentinel, but not both. If you are onboarding Azure Sentinel in a workspace that is already running Azure Security Center, and is set to collect Security Events, you have two options:
4343
> - Leave the Security Events collection in Azure Security Center as is. You will be able to query and analyze these events in Azure Sentinel as well as in Azure Security Center. You will not, however, be able to monitor the connector's connectivity status or change its configuration in Azure Sentinel. If this is important to you, consider the second option.
4444
>
45-
> - [Disable Security Events collection](../security-center/security-center-enable-data-collection) in Azure Security Center, and only then add the Security Events connector in Azure Sentinel. As with the first option, you will be able to query and analyze events in both Azure Sentinel and Azure Security Center, but you will now be able to monitor the connector's connectivity status or change its configuration in - and only in - Azure Sentinel.
45+
> - [Disable Security Events collection](../security-center/security-center-enable-data-collection.md) in Azure Security Center, and only then add the Security Events connector in Azure Sentinel. As with the first option, you will be able to query and analyze events in both Azure Sentinel and Azure Security Center, but you will now be able to monitor the connector's connectivity status or change its configuration in - and only in - Azure Sentinel.
4646
4747
## Set up the Windows Security Events connector
4848

@@ -52,7 +52,7 @@ To collect your Windows security events in Azure Sentinel:
5252

5353
1. Verify that you have the appropriate permissions as described under **Prerequisites**.
5454

55-
1. Download and install the [Log Analytics agent](../azure-monitor/platform/log-analytics-agent) (also known as the Microsoft Monitoring Agent or MMA) on the machines for which you want to stream security events into Azure Sentinel.
55+
1. Download and install the [Log Analytics agent](../azure-monitor/platform/log-analytics-agent.md) (also known as the Microsoft Monitoring Agent or MMA) on the machines for which you want to stream security events into Azure Sentinel.
5656

5757
For Azure Virtual Machines:
5858

@@ -69,9 +69,9 @@ To collect your Windows security events in Azure Sentinel:
6969
>
7070
> To allow Windows systems without the necessary internet connectivity to still stream events to Azure Sentinel, download and install the **OMS Gateway** on a separate machine, using the link on the lower right, 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.
7171
>
72-
> For more information on this scenario, see the [**Log Analytics gateway** documentation](../azure-monitor/platform/gateway).
72+
> For more information on this scenario, see the [**Log Analytics gateway** documentation](../azure-monitor/platform/gateway.md).
7373
74-
For additional installation options and further details, see the [**Log Analytics agent** documentation](../azure-monitor/platform/agent-windows).
74+
For additional installation options and further details, see the [**Log Analytics agent** documentation](../azure-monitor/platform/agent-windows.md).
7575

7676
1. Select which event set ([All, Common, or Minimal](#event-sets)) you want to stream.
7777

0 commit comments

Comments
 (0)