 As a backup admin, it is important for me to stay on top of all critical incidents related to backup and route them to the right channels to ensure that Swift action is taken. Today, Azure Backup integrates tightly with Azure Monitor to provide a rich alerting and notification solution for the key backup related alert scenarios. I can get default alerts on destructive operations such as the deletion of backup data. I can also get alerts for backup and restore failures. Navigating to the alerts tab of any given vault lets me see all the alerts that were fired for items in this vault. These alerts are also sent to Azure Resource Graph and so I can also fetch details of these alerts programmatically. Clicking on any of these alerts lets me see more details about the alert such as the affected data source, the cost of the alert and the recommended action. I can also choose to change the state of the alert to acknowledged or closed. Now, how can I route such alerts to the relevant notification channels such as email or even custom ticketing systems used by my organization? For this, I can create an Azure Monitor action rule which provides me with a powerful way to route different alerts to different notification channels. To create an action rule, I click on manage actions and select new action rule. I can choose to apply the action rule to multiple vaults within a subscription. I can filter which alerts the action rule should apply to. For example, let's say I want to send SQL VM alerts to one channel and files backup alerts to a different channel. I can create two separate action rules with the relevant filters applied. Next, I will need to create an action group. An action group is the destination to which the notification should be sent. Let me create a new action group to show the different notification channels that Azure Monitor supports. I can configure notifications to be sent either to a specific set of email IDs or to an ARM rule such as sending an email to the subscription owner. I can also choose to send the notification to an ITSM connector such as ServiceNow or any other custom ticketing system. In case I want an automatic action to be taken when the alert is fired, I can also choose to route this alert to a logic app or a runbook to be able to remediate certain alerts without needing any manual intervention. In summary, Azure Backup along with Azure Monitor helps me proactively get alerted when issues are observed in my backup estate along with seamless experiences to help me route and address these issues.