Getting Data In

Microsoft-AzureADPasswordProtection-DCAgent

Dilsheer_P
Loves-to-Learn Lots

I ma trying to onboard the %SystemRoot%\System32\Winevt\Logs\Microsoft-AzureADPasswordProtection-DCAgent%4Admin.evtx logs

This logs is available on the eventviewer under Eventviwer-> Application and Services Logs -> Microsoft -> AzureADPasswordprotection ->DCAgent -> Admin

I have added the below inputs.conf stanza in Windows_TA addon

[WinEventLog://Microsoft-AzureADPasswordProtection-DCAgent/Admin]
disabled = false
index = wineventlog_itd
renderXml=false

&

[WinEventLog:Microsoft-AzureADPasswordProtection-DCAgent/Admin*]
disabled = false
index = wineventlog_itd
renderXml=false

Both are not working. Any thoughts ??

Labels (1)
0 Karma

anel
Explorer

Hey @Dilsheer_P , 

did you find a way that worked for you? 

Thanks!

0 Karma

PickleRick
SplunkTrust
SplunkTrust

You can't use wildcards. So assuming you have a single log and your name is ok (I don't use Azure stuff so can't verify the actual name of the channel but it looks reasonable) the first syntax should be ok.

You can use

splunk list inputstatus

to see how your inputs are doing. Check the spkunkd.log on the forwarder as well.

Does your UF have enough permissions to read that channel?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Introducing ITSI 5.0: Unified Visibility and Actionable Insights

Introducing ITSI 5.0: Unified Visibility and Actionable Insights Tuesday, July 21, 2026  |  10:00AM PT / ...

Inside Splunk Agent Observability: Understanding Agent Behavior, Tokens & Costs

Inside Splunk Agent Observability:Understanding Agent Behavior, Tokens & Costs Thursday, August 06, ...

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...