You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Add support for Security event type for Azure Service Health alerts.
It is supported in the portal (see docs) and in ARM templates (see example below).
Currently, service_health configuration block only support the following events : Incident, Maintenance, Informational and ActionRequired (see monitor_activity_log_alert_resource.go file).
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Description
Add support for
Security
event type for Azure Service Health alerts.It is supported in the portal (see docs) and in ARM templates (see example below).
ARM template example
Currently,
service_health
configuration block only support the following events :Incident
,Maintenance
,Informational
andActionRequired
(see monitor_activity_log_alert_resource.go file).New or Affected Resource(s)
Potential Terraform Configuration
References
azurerm_monitor_activity_log_alert
- support forSecurity
event type for Azure Service Health alerts #11802The text was updated successfully, but these errors were encountered: