Currently separate alerts need to be created per subscription. When teams are managing dozens of subscriptions, it would be much easier to have a management group level alert or even the ability to select multiple subscriptions when creating service health alerts.43 votes
I would like to be able to simulate an alert being generated for testing. Currently you have to wait until an event happens before I can test integrations from the alerting.8 votes
It would be great to be able to select multiple subscriptions across directories when creating service health alerts. Now it is allowed to create under one subscription.6 votes
Is it possible to allow the selection of multiple resource groups when selecting services for alert notifications? i.e. alert for service 'storage' in multiple resource groups. Optionally add 'send to service owners' like Monitor options (emails owners, contributors & readers' of RGs5 votes
We’re considering this. We encourage others to vote to let us know how to prioritize.
I would like you to improve Service Health alert notification for specification changes(Planned maintenance)
I would like you to improve Service Health alert notification for specification changes (Planned maintenance),
and to guide me in a way that users will notice by some means.
<detail of request>
・information on changes to specifications has been communicated more than three months prior to the date of change.
・If I cannot follow the information from the history, please inform us again just before the specification change. (Currently, If the alert emails were sent before creating a target resource which will be planed maintenance ,
it could not receive the email which notice about planed maintenance.)4 votes
I want to run the business workflow of Microsoft Flow when the service health alert happened.
to add the issue item to the issue management system.
like ServiceNow, SharePoint list, Dynamics 365 etc.
Currently, Azure IoT Central can run the Microsoft Flow when alert happened.2 votes
Impacts ability to automate Service Health Alert creation: ActivityLogAlertLeafCondition does not support containsAny
We have automated the creation of Service Health alerts for our subscriptions.
We are finding that the ActivityLogAlertLeafCondition object (and the New-AzActivityLogAlertCondition command) do not support the -ContainsAny option. This means that we now have an inconsistent approach to creating alerts where some must be created using templates and others using powershell.
In fact, this is not supported in https://docs.microsoft.com/en-us/powershell/module/az.monitor/new-azactivitylogalertcondition?view=azps-4.1.0 nor documented in https://docs.microsoft.com/en-us/azure/templates/microsoft.insights/2017-04-01/activitylogalerts.1 vote
It would be great to be able to select multiple subscriptions across directories when creating service health alerts. Now it is allowed to create under one subscription.1 vote
Make the bottom Bar accessible at top as well as per Europe Region1 vote
I am a DBA. I want to be notified of Planned Maintenance and other Service Health Alerts for Virtual Machines, but only ones running SQL Server. I only have a few, and picking them by name would be sufficient for my needs (which is something I can do for Activity Log Alerts). I don't want to be alerted regarding our many, many other VMs.
I am sure there are many other use cases for people wanting to be notified only for a subset of the resources of any given type.1 vote
- Don't see your idea?