Skip to content

Commit 3942c2d

Browse files
authored
Update connect-dns-ama.md
1 parent e70ec22 commit 3942c2d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/sentinel/connect-dns-ama.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ Before you begin, verify that you have:
8080
- The Microsoft Sentinel solution enabled.
8181
- A defined Microsoft Sentinel workspace.
8282
- Windows Server 2012 R2 with auditing hotfix and later.
83-
- A Windows DNS Server with analytical logs enabled.
83+
- A Windows DNS Server.
8484
- To collect events from any system that isn't an Azure virtual machine, ensure that [Azure Arc](../azure-monitor/agents/azure-monitor-agent-manage.md) is installed. Install and enable Azure Arc before you enable the Azure Monitor Agent-based connector. This requirement includes:
8585
- Windows servers installed on physical machines
8686
- Windows servers installed on on-premises virtual machines
@@ -333,4 +333,4 @@ Review these considerations for [using wildcards](#use-wildcards).
333333
In this article, you learned how to set up the Windows DNS events via AMA connector to upload data and filter your Windows DNS logs. To learn more about Microsoft Sentinel, see the following articles:
334334
- Learn how to [get visibility into your data, and potential threats](get-visibility.md).
335335
- Get started [detecting threats with Microsoft Sentinel](detect-threats-built-in.md).
336-
- [Use workbooks](monitor-your-data.md) to monitor your data.
336+
- [Use workbooks](monitor-your-data.md) to monitor your data.

0 commit comments

Comments
 (0)