Azure Activity Data connector not getting delelet from MS Sentinel

Muhammad Rizwan 5 Reputation points
2025-02-19T12:09:04.6233333+00:00

I'm not able to delete Azure Activity data connector from MS Sentinel. I had deleted the Azure policy the one created by connector and also removed IAM role on subscription for the managed identities created by connector while adding it. After all connector is still connected and getting data from Azure Monitor, if I delete the data connector (after clicking on 3 dots) but nothing happens.

Microsoft Sentinel
Microsoft Sentinel
A scalable, cloud-native solution for security information event management and security orchestration automated response. Previously known as Azure Sentinel.
1,235 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Muhammad Rizwan 5 Reputation points
    2025-02-26T05:23:44.49+00:00

    Hi Alex,

    So I contact MS support and they gave me solution, they told me to stop sending logs to log analytic workspace from Activity log in Azure Monitor (shown in screenshot).

    But still connector is connected in Sentinel. They told that it takes 14 days to get connector in disconnect states after we stop sending the logs to workspace. Let,s see, now I'm waiting for 14 days.

    User's image

    1 person found this answer helpful.

  2. Alex Burlachenko 1,665 Reputation points
    2025-02-19T12:12:46.9533333+00:00

    Hey mate,

    If you’re stuck trying to delete the Azure Activity data connector in MS Sentinel, try that...

    Make sure you’ve got the right permissions (Sentinel Contributor). Check if there are any dependent rules or settings in Sentinel. Try deleting it via API or PowerShell if the UI isn’t working. In Azure Monitor, check if data is still being sent to the Log Analytics workspace. If all else fails, raise a ticket with Microsoft Support.

    Let me know how it goes! Cheers! 😊

    Alex


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.