Azure Monitor
Azure Monitor Action Groups enable you to configure how to receive notifications when an Azure Monitor Alert is triggered.
-
Provide granular Activity Log event operations
For most service providers (if not all), it is not possible to identify Create from Update operations from Activity Log events, they are all provided under a generic "write" operation, which doesn't allow proper event-driven solutions to be built.
It would be great to be able to set up granular alerts for each operation type and receive it on the webhook's payload as well.
23 votes -
Add Microsoft Teams webhook integration with Azure Alerts
Currently if an alert is triggered in Azure and you want to get a notification sent to a Teams Channel via Webhook this is not possible. You have to build a custom Logic App or Automation Runbook to post to a Microsoft Teams Channel.
Direct integration between Azure Alert and Microsoft Teams is preferred over additional setup and management of a Logic App or Automation Runbook.
12 votes -
Azure monitor - Include tags in webhook payload
It would be useful to have resource tags included in the webhook payload when generating an alert. It will add additional context.
Thanks
9 votes -
Direct integration with Slack apps
The suggested integration with Slack is requires an 'API connection' in Azure.
Slack's recommended way of integrating is via an application which exposes a web hook URL.
https://api.slack.com/start/overview
Azure DevOps already supports integration directly with such an app (we already have this working). The suggested use of a Logic App requires an additional resource definition in Azure. I'd much prefer to manage my apps in Slack and then just add a web hook as a secret to a key vault.
Rather than having to define a logic app to define the mapping between Azure common schema and Slacks schema there…
5 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
-
Include resource display name in Common Alert Schema
It would be extremely useful if the Common Alert Schema included the case sensitive name (display name) of the resources it applies to rather than just the resourceIds (in alertTargetIDs).
https://docs.microsoft.com/en-us/azure/azure-monitor/platform/alerts-common-schema-definitions2 votes -
Allow Secure Webhook to be consumed by users athorised to the app as opposed the owner
In an enterprise multiple subscription or resource group owners may with to send alerts to a central monitoring solution. This needs to utilise a secure webhooks to be able to authenticate the request. To use a secure webhook you have to create an application that is used to send the authentication header. The only people that can use the secure webhook are the Azure Application owners in Azure AD not the authorised users of the application. Hence to share a webhook across multiple subscriptions you have to make all subscription / resource group owners, owners of the Azure AD application…
1 voteThanks for your feedback and its now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.
- Don't see your idea?