v-sudkharat

Hi @sandeep5234, We are waiting for your response on above shared solution. Thanks!

Hey @Kaloszer, We reached out to respective team for this issue, and as a response team mentioned that you need to raise a support case for this issue, as support...

Hi @roboftheblues, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 20-03-2024. Thanks!

@askvpb, Could you please let us know, which connector you have configured (AMA or MMA)? Currently we are working on repro the configuration using AMA. Thanks!

Thanks @roboftheblues / @askvpb for sharing info.

@Kaloszer, please let us know your response. Thanks!

shared response in comment -https://github.com/Azure/Azure-Sentinel/issues/10107#issuecomment-2074880736

Hi @jjbhavsar, We have responded your mail, and waiting for your response. Thanks!

Hi @jjbhavsar, We also have checked your share `syslogmessage` - 2024-03-12T17:51:51.755Z FW01 RT_FLOW - RT_FLOW_SESSION_CLOSE [xxxxxx reason="TCP FIN" source-address="xx.xx.xx.xx" source-port="xxxxx" destination-address="xx.xx.xx.xx" destination-port="xxxx" connection-tag="0" service-name="https" nat-source-address="xx.xx.xx.xx" nat-source-port="xxxx" nat-destination-address="xx.xx.xx.xx" nat-destination-port="xxx" nat-connection-tag="0" src-nat-rule-type="N/A"...

Hi @jjbhavsar, Gentle Reminder: We are waiting for your response on this issue. If you still need to keep this issue active, please respond to it in the next 2...