Hello Supriya Nelluri,
As per description, we understand that you are collecting event IDs from few servers through Azure Monitor Agent to send events to Sentinel SIEM tool and once you install Defender for Endpoint, want to know which logs are replicated to Sentinel to avoid duplication.
AMA is a lightweight log collection agent, designed to consume as little resources as possible when collecting metrics and logs from your server.
Associated with a Microsoft Sentinel workspace, all logs collected form AMA-installed machines, are sent to the various Microsoft Sentinel tables, depending on the source type from which they were collected (Windows DNS, Windows security events, Firewall, IIS, Syslog, CEF, etc.).
AMA can be controlled using Data Collection Rules (DCR), enabling you to define where to collect the logs from, what data manipulations to perform with KQL transformations (enabling you filtering, parsing, enrichment and more) and where to send the logs to, whether that be a workspace, Eventhubs (for Azure VMS only), Auxiliary tier and so on. You can group machines by using different DCRs.
Ref:
Microsoft Defender for Endpoint creates alerts when suspicious security events are seen in an organization.
Fetch alerts generated in Microsoft Defender for Endpoint to Microsoft Sentinel so that you can effectively analyze security events. You can create rules, build dashboards and author playbooks for immediate response
I suggest you refer the below documentation.
https://learn.microsoft.com/en-us/azure/sentinel/connect-services-api-based
https://learn.microsoft.com/en-us/azure/sentinel/data-connectors/microsoft-defender-for-endpoint