Forum Discussion
Issue while deploying Sentienl Rules
Hi StefanHartmann1
I've seen this in instances where there are still traces relating to that original ID, not allowing overwriting.
Note that the ID is the Name, you can use this PS query below to see the state of the rule:
Get-AzSentinelAlertRule -ResourceGroupName <RG-Name> -WorkspaceName <LogAnalytics-Name> `
| where Name -eq "<Rule-ID>"
And the equivalent removal PS: https://learn.microsoft.com/en-us/powershell/module/az.securityinsights/remove-azsentinelalertrule?view=azps-13.0.0
Outside of that you will have three options:
- If the same GUID is not explicitly required, deploy the rule under a new ID.
- Raise a Microsoft support case
- Continue waiting.
Feel free to reply if you have any issues!
None of these options work in a detection-as-code context where you need to delete and republish rules often, as is our case. This is terrible UX and architecture, I really hope Microsoft realizes the negative impacts is has on customers and fixes this problem.