Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

3.1.4.7. Configure and Interpret Backup Reports and Alerts

3.1.4.7. Configure and Interpret Backup Reports and Alerts

💡 First Principle: Backups fail quietly. A policy that ran perfectly for months can stop when a VM is moved, an agent breaks, or someone shortens retention, and nobody notices until a restore is needed. Monitoring backup has two halves: alerts tell you now that something went wrong, and reports show you over weeks and months whether protection actually matched the policy.

Scenario: You run 40 Recovery Services vaults across three subscriptions. Management wants a monthly view of job success rates, storage growth, and items that haven't had a successful backup in a week. The security team wants an email within minutes whenever someone deletes backup data or disables soft delete, and the on-call team wants backup failures sent to its ITSM tool, not to everyone.

What It Is: Azure Backup monitoring is built on standard Azure Monitor features. Backup Reports are Azure workbooks that query vault diagnostics data in a Log Analytics workspace. Built-in Azure Monitor alerts are raised by Azure Backup itself for critical events, and you route them with alert processing rules and action groups (6.1.2).

Where You Monitor It: Resiliency

The at-scale console is now called Resiliency in the portal ("Resiliency in Azure", formerly Azure Business Continuity Center). Its Monitoring + Reporting menu holds Alerts and Reports for both Azure Backup and Site Recovery. The older Backup center is a legacy experience: it's no longer in portal search and is reached from Resiliency's Help menu. Each vault still has its own Alerts and Backup Instances views.

Setting Up Backup Reports
  1. Create or choose a Log Analytics workspace. Its region and subscription don't have to match the vaults'. Data is kept for 30 days by default, so raise the workspace or table retention if you want trend reports over months.
  2. Add a diagnostic setting on each vault (vault > Diagnostic settings > + Add diagnostic setting), select Send to Log Analytics workspace, and choose Resource specific as the destination table mode. For a Recovery Services vault, select the six events: Core Azure Backup Data, Addon Azure Backup Job Data, Addon Azure Backup Policy Data, Addon Azure Backup Storage Data, Addon Azure Backup Protected Instance Data, and Azure Backup Operations.
  3. Do this at scale with Azure Policy. Azure Backup provides a built-in policy definition that adds the diagnostic setting to every Recovery Services vault in a scope.
  4. Wait. The first data push can take up to 24 hours, and reports never show the current partial day, so Microsoft recommends looking two days after setup.

Two settings break reports silently. The new events work only in Resource specific mode; sent in Azure diagnostics mode, they never appear in Backup Reports. Don't select Addon Azure Backup Alerts, which carries the classic alerts being retired. The single legacy event, Azure Backup Reporting Data, still works for old custom queries but is on a deprecation path.

Reading Backup Reports (Resiliency > Monitoring + Reporting > Reports > Backup Reports, then select the workspaces)

TabAnswers
SummaryHow big is the estate: backup items, cloud storage, protected instances, job success rate per workload.
Backup ItemsStorage consumed per item, filterable by protection state (for example, Protection Stopped).
UsageBilling view: protected instances and storage per billing entity.
JobsFailed jobs per day and the top failure causes over time.
PoliciesEach active policy, its item count and storage.
OptimizeInactive resources with no recent successful backup, retention that's longer than needed, and databases on daily full backups.
Policy adherenceWhether every item had at least one successful backup each day (or each week for weekly policies).

You can also schedule reports by email (a logic app is deployed for you), export widgets to Excel, and see workspaces across tenants with Azure Lighthouse. Resiliency also offers out-of-box reports such as Backup Job History and Backup Configuration Status, and Site Recovery job and replication history reports.

Built-in Azure Monitor Alerts for Backup
CategoryExamplesSeverityCan you turn it off?
Security alertsDelete Backup Data, Soft Delete Disabled for Vault, MUA Disabled, policy modified to shorter retentionSev 0No. The alert is always generated; you control only who is notified.
Job failure alertsBackup Failure, Restore FailureSev 1Yes. On by default; turn off in vault Properties > Monitoring Settings.

Built-in alerts are created without any alert rule and at no charge, but they notify nobody until you add notifications. You create an alert processing rule (for example, scoped to a subscription and filtered to Microsoft.RecoveryServices/vaults) that applies an action group with the email, SMS, ITSM, or webhook receivers. Notifications beyond the free tier of 1,000 emails a month are billed. For logic built-in alerts don't cover, write log search alert rules on the Log Analytics data (some delay is acceptable), Azure Resource Graph alerts for near real-time conditions, or metric alerts on the backup health metrics (in preview).

Classic alerts: Microsoft's documentation gives 31 March 2026 as the deprecation date for classic Azure Backup alerts (the Backup Alerts tab in a Recovery Services vault). They don't appear in Resiliency. To switch, select Use only Azure Monitor alerts in the vault's Monitoring Settings, or run the guided flow in Resiliency (Monitoring + Reporting > Alerts > Manage alerts).

Practical Implementation: Alert Settings and Notification Routing with Azure CLI
# Keep job-failure alerts on and stop classic alerts for one vault
az backup vault backup-properties set --name rsv-prod-eus --resource-group rg-backup \
  --classic-alerts Disable --job-failure-alerts Enable

# Action group for the backup on-call team
az monitor action-group create --name ag-backup-oncall --resource-group rg-backup \
  --short-name bkoncall --action email oncall backup-oncall@contoso.com

# Route every Recovery Services vault alert in the subscription to that action group
# (alert-processing-rule is an Azure CLI extension command group, currently in preview)
az monitor alert-processing-rule create --name apr-backup-oncall --resource-group rg-backup \
  --rule-type AddActionGroups --scopes "/subscriptions/<subscription-id>" \
  --filter-resource-type Equals "Microsoft.RecoveryServices/vaults" \
  --action-groups "/subscriptions/<subscription-id>/resourceGroups/rg-backup/providers/microsoft.insights/actionGroups/ag-backup-oncall" \
  --enabled true
Visual: Two Monitoring Paths

⚠️ Common Pitfall: Configuring the diagnostic setting with Azure diagnostics mode, or sending it only to a storage account. The data exists, but Backup Reports stay empty because they read the resource-specific tables in Log Analytics.

⚠️ Exam Trap: Reports need diagnostic settings plus a Log Analytics workspace; built-in alerts need neither. And built-in alerts appear in the portal without notifying anyone: the missing piece is an alert processing rule with an action group, not a new alert rule. Security alerts can't be disabled at all; only job-failure alerts can.

Key Trade-Offs:
  • Built-in vs. Custom Alerts: Built-in alerts need no rules and cover critical events; log search alerts can express any condition but depend on diagnostics data that arrives with a delay.
  • Workspace Retention vs. Cost: Longer retention gives longer report trends, at a higher Log Analytics cost.
  • One Workspace vs. Many: A central workspace makes estate-wide reports simple; separate workspaces can match ownership or data-boundary rules, and reports can still read across them.

Reflection Question: If a vault's security alert fired last night but nobody was emailed, and the Backup Reports for the same vault are blank, what two separate configuration gaps would you look for?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•22 professional certifications earned