Skip to content

Commit 33c1b0c

Browse files
Update articles/sentinel/connect-dns-ama.md
1 parent 2c13156 commit 33c1b0c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sentinel/connect-dns-ama.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Before you begin, verify that you have:
2828
- A Log Analytics workspace enabled for Microsoft Sentinel.
2929
- The **Windows DNS Events via AMA** data connector installed as part of the **Windows Server DNS** solution from content hub.
3030
- Windows server 2016 and later supported, or Windows Server 2012 R2 with the auditing hotfix.
31-
- DNS server role installed with DNS-Server analytical event logs enabled.</br>
31+
- DNS server role installed with **DNS-Server** analytical event logs enabled.
3232
DNS analytical event logs aren't enabled by default. For more information, see [Enable analytical event logging](/windows-server/networking/dns/dns-logging-and-diagnostics#enable-analytical-event-logging).
3333

3434
To collect events from any system that isn't an Azure virtual machine, ensure that [Azure Arc](/azure/azure-monitor/agents/azure-monitor-agent-manage) is installed. Install and enable Azure Arc before you enable the Azure Monitor Agent-based connector. This requirement includes:

0 commit comments

Comments
 (0)