Azure Backup Review: Health, Vaults, and Cost
Overview
Azure Backup Review in Spotto shows backup coverage, backup health, vault association, and backup cost for selected Azure subscriptions. It is built for operational review: which resources are protected, which backups are failing, which Recovery Services vault or Backup vault is involved, and what the backup estate is costing.
It also lists resources that do not appear to be protected and, where pricing data is available, estimates the monthly cost of enabling backups. That turns backup review into a practical conversation instead of a scavenger hunt through vault blades, billing exports, and optimistic memory.
Why use this?
Azure backup data is usually split across several places:
- Recovery Services vault protected items and jobs.
- Azure Backup vault backup instances.
- Platform-native backup signals for services such as Azure SQL.
- Billing data for the last 30 days.
- Retail pricing data for estimated backup costs.
Backups brings those signals together so you can answer:
- Which resources are protected?
- Which resources are not protected?
- Which backup failed, when did it fail, and has it been failing since a known date?
- Which vault and policy protect the resource?
- What did existing backups cost over the last 30 days?
- What would currently unprotected resources likely cost if backups were enabled?
Turn the evidence into a decision
Select the labelled briefcase Business Value button beside Notes. The brief combines live protected, failed, unprotected, stale, and estimated-cost evidence with a priority body of work.
Live facts are deterministic; estimates remain labelled and mixed currencies are never combined. Generate tailors only the narrative for permitted users and saves it to the exact scope. Clear removes that saved narrative and immediately restores the standard Business Value content without deleting Customer Context or changing live facts. Regenerate when Spotto reports that evidence changed. Above 100 subscriptions, curated live guidance remains available without AI or persistence.
Current position and priority work
Start with the failed and unprotected workloads named in the brief, then investigate stale recovery points and prove the critical restore paths. The names come from the same ordered rows as the backup table; Spotto still asks you to confirm business criticality rather than assuming it from technical status. Coverage alone does not prove that a service can be restored within an acceptable time.
Tag resources by business criticality, recovery tier, service owner, environment, and cost allocation. This makes the protection standard and restore-test cadence explicit, and helps teams find gaps when services change ownership or new resources are deployed.
Expected change
For unprotected resources, the brief shows current protection coverage → projected coverage if every currently unprotected resource in scope is enabled. It also shows the existing estimated monthly enablement cost when the scope has one currency. Mixed-currency scopes keep estimates separate at resource level instead of creating a false total.
This completes the technical side of the case: coverage gained for the estimated recurring cost. The financial consequence of downtime or data loss remains unvalued until the customer supplies service criticality, recovery time and recovery point objectives, and an agreed cost of interruption. Failed and stale backups also remain separate work; enabling protection does not prove recoverability.
Business outcomes
Backup investment creates value when priority services can be restored within agreed recovery time and recovery point objectives. The review connects coverage and failures to operational continuity rather than treating backup configuration as the finish line.
Cost of delay
Ransomware, deletion, corruption, or a platform incident could exceed acceptable data-loss and downtime limits. Unprotected data may be permanently lost, while failed or stale backups can provide false confidence until a restore is urgently required.
Decision required
Approve the priority recovery scope, accountable service owners, required restore tests, and acceptable recovery cost.
Validate with stakeholders
When you can manage Company Notes, select any question in the portal to retain the answer in the relevant Customer Context note.
- Which services are business-critical, what are their recovery time and recovery point objectives, and how are they identified through resource tags?
- When was each critical restore path last tested successfully?
- Who accepts the trade-off between recovery cost, recovery speed, and retained history?
Where to find it
In the Spotto Portal, open a company and go to Tasks -> Review -> Backups.
Use the subscription selector at the top of the page to choose the subscriptions you want to review. The page uses the same selector behavior as other subscription-scoped pages, including URL and saved selection state.
Key capabilities
Backup posture summary
The summary cards show:
- Protected: resources with active backup or platform-native protection signals.
- Failed Backups: resources with a current failed backup signal or active failure history.
- Not Protected: backup-eligible resources that do not appear to have backup protection.
- 30 Day Backup Cost: observed backup cost from the last 30 days.
- Estimated Monthly If Enabled: estimated monthly cost if currently unprotected resources were backed up.
If selected subscriptions use different currencies, aggregate cost cards show Mixed and the table should be used for per-resource cost review.
Resource-level backup table
The table shows each evaluated resource with:
- Resource name, type, and subscription.
- Backup status.
- Latest backup or recovery point time.
- Failure summary, failed-since date, and consecutive failure count when available.
- Recovery Services vault, Backup vault, and policy details when available.
- Observed 30-day backup cost.
- Estimated monthly backup cost if the resource is not currently protected.
You can search by resource, vault, policy, subscription, status, or resource ID.
Failure review
Failed backup rows are prioritized at the top of the table. When Azure supplies job details, Spotto shows the latest failure summary and supporting timing so an operator can distinguish a one-off failure from an ongoing backup issue.
The page can show both the latest backup status and the latest failed job detail. A historical failed job does not automatically mean the resource is currently failed if the latest backup has recovered.
Backup cost review
For existing protected backups, Spotto uses billing data collected for the subscription and allocates backup-related cost where possible. Costs are shown with the subscription currency code and symbol.
For unprotected resources, Spotto estimates monthly backup cost using available resource characteristics and Azure retail pricing data. Actual-cost confidence is shown as exact, allocated, estimated, or unavailable; estimate availability is shown separately as available, partial, or unavailable.
Supported protection sources
Backups combines multiple data protection sources when they are present in the latest scan:
- Recovery Services vault protected items and backup jobs.
- Azure Backup vault backup instances.
- Platform-native backup signals for supported services, including Azure SQL where available.
- Backup-eligible resource inventory, such as virtual machines, disks, AKS, database services, and storage services supported by the current data set.
Technical reference
| Component | Details |
|---|---|
| Inputs | Azure data protection projection files, Recovery Services vault data, Backup vault data, platform-native backup metadata, resource inventory, 30-day billing data, and Azure retail pricing data. |
| Outputs | Summary cards, searchable resource rows, backup status, vault and policy details, failure detail, observed 30-day backup cost, and estimated monthly backup cost. |
| Cost handling | Existing backup cost is based on collected billing artifacts. Future backup estimates use retail pricing where a supported workload and pricing match are available. |
| Currency handling | Resource rows show the currency supplied by the projection. Aggregate cost cards are only summed when selected subscriptions share one currency. |
| Refresh | The page reflects the latest completed cloud-engine scan and data protection projection for each selected subscription. |
How it differs from Azure portal views
Azure portal backup views are useful when you already know which vault or resource to inspect. Spotto Backups is designed for cross-subscription review:
- It starts from resources and coverage, not only from vaults.
- It surfaces unprotected resources alongside protected resources.
- It combines backup health with backup cost.
- It links failure information to the protected resource and the associated vault or policy.
- It keeps subscription selection consistent with the rest of Spotto.
Troubleshooting
The page shows no backup posture data
What you're seeing: The table is empty or shows the backup posture empty state.
Likely causes:
- The selected subscriptions have not completed a data protection scan yet.
- No ready subscriptions are selected.
- The cloud account does not have enough permissions to collect the required Azure backup data.
How to fix:
- Confirm the subscription selector includes the subscriptions you expect.
- Check cloud account sync status in Connectors -> Cloud Accounts.
- Confirm the Azure cloud account has read access to backup, resource, and billing data.
- Re-check after the next scan completes.
A protected resource shows no cost
What you're seeing: A protected backup row shows N/A for 30-day cost.
Likely causes:
- The billing export did not include identifiable backup meter rows for that resource or vault.
- The backup cost was bundled or could not be allocated confidently.
- Billing data for the last 30 days is not available for the subscription.
How to fix:
- Confirm subscription cost visibility is enabled.
- Review the subscription's billing sync status.
- Check whether the vault has shared backup meters that need allocation rather than direct resource matching.
Estimated cost is unavailable
What you're seeing: An unprotected resource shows N/A or an unavailable estimate.
Likely causes:
- The resource type is not yet supported by the backup pricing model.
- Required sizing data, such as protected disk size, backup storage quantity, region, or workload shape, is missing.
- Azure retail pricing did not return a matching meter for the workload and currency.
How to fix:
- Confirm the resource has complete inventory data in Spotto.
- Check that the resource region and workload type are supported.
- Treat unavailable estimates as review items rather than zero-cost backups.
A failure looks historical
What you're seeing: A row has latest failed job details, but the latest backup status is healthy.
Likely cause: Azure can retain failed job history even after a later backup succeeds.
How to use it:
- Check the Status column first.
- Use the failure detail as context when the status is Failed or Needs Attention.
- Review the vault job history if you need the full incident timeline.
Looking to enhance your cloud setup for cost efficiency, performance, reliability, or security?
Talk to a cloud specialist. Email us or schedule a 30-minute consultation and let's optimize your cloud environment together.
Book a Free Consultation