Open the report
- Open Backup > Microsoft 365.
- Select SaaS Protection for Kaseya or Spanning Backup when several providers are available. With only one available provider, its report opens directly.
- Confirm the company selection and customers in scope.
- Expand Overall backup health to review Workload health.
- Expand Backup result trend and review Customer backup health below it.
Read coverage and status
Backed up in the last 24 hours compares backed-up services with active services in the imported snapshot. The displayed percentage weights the selected customers by their active-service counts; it is not an equal average of company percentages. Kaseya also shows Services in initial backup. For its workload summaries:
Spanning uses its reported workload health status and does not show Kaseya’s initial-backup metric. Do not apply Kaseya’s percentage thresholds to Spanning’s labels.
Overall health summarizes customer statuses. Check individual customer and workload rows even when the overall label is Healthy: a missing workload can still have no data. A percentage from an old snapshot does not establish current protection.
Last 100% successful backup summarizes available customer dates. It is not proof that every customer completed a backup at the same moment, and customers without a date require separate investigation. Last synced describes imported-data freshness, not when a backup operation ran; the header timestamp should not be assumed to prove every customer has refreshed.
Review trends and customer rows
Kaseya offers 10 days and 30 days for the trend. Spanning uses 7 days. Expand the trend and hover a plotted point to read its available percentage. The lines combine successful-service coverage by workload and day. Missing dates or a line drawn between points do not prove a backup ran during the gap. The customer table shows the portal company and mapped provider customer, health, workload ratios, and Last full success. Kaseya also shows Initial. On a narrow screen, scroll the table horizontally to reach its remaining columns. Customer rows do not open a restore or editing form.Refresh and investigate missing data
Select Refresh to reload the imported report. It does not trigger a provider sync, run a backup, or repair a failed service. Check the displayed dates after refreshing. If the report says Backup health could not be loaded, try Refresh. If the issue continues, Company users should contact their MSP. MSP staff should inspect the selected provider’s connection, sync status, company mapping, and feature access. Some shared Spanning empty/error text still mentions Kaseya; use the selected provider to identify the integration to check.Frequently asked questions
Does Refresh start a new backup?
Does Refresh start a new backup?
No. It reloads data already imported into MSPortal. Provider synchronization and backup execution are separate operations.
Why can 100% still need attention in Kaseya?
Why can 100% still need attention in Kaseya?
Services can still be in initial backup. Read the initial-backup count and individual workload status alongside the percentage.
Why is Spanning missing the 30-day selector and Initial column?
Why is Spanning missing the 30-day selector and Initial column?
Spanning uses a seven-day trend and its own reported health status. The initial-backup metric and 10/30-day choices belong to Kaseya.
Does Healthy prove that every workload has data?
Does Healthy prove that every workload has data?
No. Check individual workload results, missing values, and snapshot freshness. An overall status can coexist with missing workload data.