Sentinel Built-In Windows Rules Never Fire on Forwarded Events: WindowsEvent vs SecurityEvent
By Mirko Peters ·
Forwarded Windows events reach Microsoft Sentinel, yet the built-in Windows Security Events rules stay silent. The cause is the table: forwarded events land in WindowsEvent, the rules read SecurityEvent.
The Windows Event Collector works. Events 1102 and 4732 show up in Microsoft Sentinel. You turn on the built-in near-real-time rules for those events, create a test event, and nothing happens. No alert, no incident.
Key points
- Microsoft Learn says events collected through Windows Event Forwarding go to the WindowsEvent table, not to SecurityEvent, even when they come from the Security log.
- Many built-in Windows Security Events rules, including some near-real-time rules, query SecurityEvent only, so they cannot match data that sits only in WindowsEvent.
- Learn offers two fixes: use the Windows Security Events via AMA connector, or adapt the rule queries to WindowsEvent or supported ASIM parsers.
- Routing forwarded events into SecurityEvent with a DCR transformation was described by Microsoft staff in a 2026 thread, but no official documentation was found for it.
This exact case was described in a Microsoft Community Hub thread from July 2026. The setup had Windows Event Forwarding to a collector, Azure Arc, the Azure Monitor Agent, and the Windows Forwarded Events connector. The thread did not end with a marked solution. But the cause is documented on Microsoft Learn, and the replies agree with it. This article is a troubleshooting guide, not an official Microsoft procedure.
Symptoms
- The events appear when you query the
WindowsEventtable. - A query on
SecurityEventfor the same event IDs returns nothing for those machines. - Rules from the Windows Security Events solution in the Content Hub are enabled, but they never raise alerts for those machines.
Why it happens
Microsoft Learn explains this on the page about Windows agent-based connectors, updated in August 2026. Events collected through Windows Event Forwarding go into the WindowsEvent table. That includes events forwarded from the Windows Security log. They are not written to SecurityEvent.
Learn also warns that many built-in Windows Security Events rules, including some near-real-time rules, query SecurityEvent and do not match data stored only in WindowsEvent. A second Learn page, on Windows security event sets, repeats this: if forwarded events do not trigger a built-in rule, check which table the rule queries.
In the thread, an MCT and another community member gave the same explanation. A rule only evaluates the tables its KQL names.
Step 1: Prove the table split
In Logs, run both queries with the same event ID and time range:
``kql WindowsEvent | where EventID == 4732 | take 10 ``
``kql SecurityEvent | where EventID == 4732 | take 10 ``
If the first returns rows and the second does not, you have the case described here. If both are empty, the problem is the collection, not the rules.
Step 2: Read the rule you expected to fire
In the Defender portal, expand Microsoft Sentinel, then Configuration, and select Analytics. Learn's steps for creating a rule from a template use the Rule templates tab, and active rules appear under Active rules. In the Azure portal, the same page is under the Configuration menu of Microsoft Sentinel. Learn notes that after March 31, 2027, Microsoft Sentinel will be available only in the Defender portal.
Open the rule and read its query. If it starts from SecurityEvent, you have found the reason.
Step 3: Choose one of the options
Option A: collect the Security channel with the AMA connector. Learn says to use the Windows Security Events via AMA connector if you need those rules without modification. It also states that, for systems that are not Azure virtual machines, Azure Arc must be installed and enabled before you enable the AMA-based connector. This option changes your collection design, so check it against why you chose forwarding in the first place.
Option B: adapt the rule. Learn says to adapt the rule queries to use WindowsEvent or supported ASIM parsers. In the thread, two community members (one of them an MCT) described the practical work:
- Run a query on
WindowsEventto see which fields the events carry for the IDs you need. - Clone the rule into a custom rule that queries
WindowsEvent, so the original template stays as it was. One reply suggested a scheduled rule if NRT does not acceptWindowsEvent. - Filter on the event ID and rewrite the field extraction, because the schemas differ. For event 4732 one reply mapped the group and member values from
EventData. - If you use an ASIM parser, test it before you rely on it. One reply said ASIM is not an automatic bridge.
- My own addition, not from the thread: check the entity mapping of the copied rule against the new fields.
Learn's page on ASIM says you can write analytics rules with ASIM, but I found no Windows-specific parser name on it, so I name none here. The thread's replies also did not give the field names. Look at the EventData column in your own results.
If the rule is a near-real-time rule, remember the limits on the NRT rules page: at most 50 rules per customer, queries run once per minute, and up to 30 single-event alerts per run. Learn also says an NRT query may reference more than one table. In theory this allows one rule to read both tables in a mixed estate. I did not test that.
For new detections, Learn's page on creating NRT rules says Custom detections is now the best way to create new rules across Microsoft Sentinel and Microsoft Defender XDR. Check whether that fits your data before you build more rules on the Sentinel side.
Option C: change the data collection rule so the events go to SecurityEvent. A Microsoft staff member said in the thread that they had seen this approach used but had found no official documentation for it. The reply proposed getting forwarding to work first and then changing the data collection rule, and named two schema changes: rename Provider to EventSourceName, and convert EventData from dynamic to string. The same reply asked whether anyone had tried this recently with the current AMA and DCR implementation, and nobody answered. Treat this as unsupported until you confirm it with Microsoft. A support case is the right place for that question.
Option D: split the collection. One community member described a proof of concept: forwarded events go to WindowsEvent through one connector, while a second connector reads the Forwarded Events channel with an XPath filter for Security events to fill SecurityEvent. They said it works but that they were not confident enough for production, and asked whether others had tried it. Nobody answered that. Learn does not describe this design.
Step 4: Avoid duplicates
Learn does not discuss running both connectors for the same events. Two community replies warned about enabling both paths for the same data, because of duplicate ingestion and duplicate alerts. Before you add a second path, list which event IDs go where and exclude them from the other path.
Step 5: Test the fix
- Create a harmless test event on a pilot server, for example a membership change that produces event 4732 in a test group.
- Check that the event is in the table your rule queries.
- Wait. NRT rules run every minute and, per Learn, with a two-minute delay. Scheduled rules follow their own schedule.
- Look in Incidents for the alert, and in Active rules for the rule state.
If a rule is later shown with AUTO DISABLED at the start of its name, Learn's analytics rule troubleshooting page says Sentinel does this after repeated permanent failures, for example a deleted table or an invalid function, and adds the reason to the rule description. Fix that cause before you re-enable the rule.
What remains open
- The thread had no accepted answer and no confirmation from the poster.
- Option C and Option D are not covered by Learn. Each rests on a single reply, and nobody in the thread reported testing either.
- Which table future built-in templates will use for forwarded events is not stated in the sources I read.
Related
Sources
- Microsoft Learn: Connect Microsoft Sentinel with a Windows agent-based data connector
- Microsoft Learn: Windows security event sets that can be sent to Microsoft Sentinel
- Microsoft Learn: Create a rule from a template
- Microsoft Learn: Near-real-time analytics rules
- Microsoft Learn: Create NRT rules
- Microsoft Learn: Advanced Security Information Model (ASIM)
- Microsoft Learn: Troubleshoot analytics rules
- Microsoft Community Hub: Windows Forwarded Events connector with Windows Security Events NRT rules (July 2026)