Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instructions for Exchange Admin Audit Log Events Data Connector has incorrect log names (Exchange On-Premises Solution) #10960

Closed
leighcurranTW opened this issue Aug 12, 2024 · 4 comments · Fixed by #11049
Assignees
Labels
Connector Connector specialty review needed

Comments

@leighcurranTW
Copy link

leighcurranTW commented Aug 12, 2024

The data connector for the Exchange Admin and Audit Log Events uses 'MS Exchange Management' as the log name when it should be 'MSExchange Management'. For example: Click Add Windows event log and enter MS Exchange Management as log name.

To reproduce the issue, install the Exchange On-Premises solution and try to configure:

[Option 1] MS Exchange Management Log collection > Data Collection Rules - When the legacy Azure Log Analytics Agent is used > Configure the logs to be collected.

And

[Option 1] MS Exchange Management Log collection > Data Collection Rules - When Azure Monitor Agent is used > Option 2 - Manual Deployment of Azure Automation.

image
An example of the event name (Which is used correctly in the parsers etc through the solution already):
image
image

Line 212 and 232 in ESI-ExchangeAdminAuditLogEvents.json

@v-sudkharat v-sudkharat added the Connector Connector specialty review needed label Aug 12, 2024
@v-sudkharat
Copy link
Contributor

FYI, @v-prasadboke

@nlepagnez
Copy link
Contributor

Hi @v-prasadboke , @v-sudkharat, I confirm that the XPath information is not good. The good value is "MSExchange Management!*" So in connector documentation it has to be "MSExchange Management"

@v-prasadboke
Copy link
Contributor

Got it @nlepagnez, Working on it

@nlepagnez
Copy link
Contributor

Hi @v-prasadboke, the XPath will be corrected in the pull request #11049

@v-sudkharat v-sudkharat linked a pull request Sep 5, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Connector Connector specialty review needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants