Monitor Backup and Recovery Readiness

MSPControl brings Veeam, Veeam for Microsoft 365, and Azure backup reports into customer-scoped and platform-wide views. Use these pages to identify warning or failed activity, inspect the affected workload, and confirm what recovery evidence the backup source reported.

Monitoring does not create a backup

MSPControl reports the backup state received from the configured provider. A clean dashboard does not prove that every required workload is protected, and reviewing a restore point is not the same as completing a restore test.

Choose a backup view

Veeam backupsUnderstand organization-level Veeam reporting, settings, quotas, and agent delivery.

Veeam DashboardReview cross-customer Veeam results, health metrics, jobs, sessions, copies, and restore points.

Azure backupsUnderstand organization-level Azure backup reporting and settings.

Azure Backups DashboardReview cross-customer Azure backup events and protected-item details.

What technicians can investigate

Veeam

• Calendar results grouped by virtual machine, category, or job.
• Success, warning, and error outcomes filtered by customer and date.
• License, offline-server, database-connection, low-space, and not-seen metrics.
• Reported job sessions, storage, copies, object history, and restore points.
• Veeam for Microsoft 365 jobs, sessions, and protected-object records.

Azure

• Calendar results filtered by customer and date.
• Reported protected items and their result, category, status, and restore-point counts.
• Detail views for supported Azure workload types, including virtual machines, SQL databases, storage, Azure file shares, replication items, backup agents, and DPM.
• Per-item backup settings where the current user and plan allow changes.

Native Microsoft 365 Backup

Versions containing the dedicated Microsoft 365 Backup subsystem provide separate protection views for service state, policies and protected units. Do not look for these records in the current Azure backup calendar. Confirm the installed version, tenant connection, permissions and protected scope; unreadable data does not establish protection.

The native protection monitor evaluates current state and compares successful snapshots. It is registered as an available administrator task without a schedule. Configure its execution and customer scope, add recipients for alert email, and inspect task results. In versions containing the ticket workflow, enabled ConnectWise follow-up can attempt ticket creation for new critical findings when the integration and company mapping are configured. An existing matching open company ticket can suppress another; neither automatic closure nor universal repair is implied.

Native protection and restore actions are separate authorized workflows in supported versions. A submitted restore request is not a verified recovery. Veeam reporting remains distinct from executing a restore in Veeam.

Notifications and follow-up

Both backup dashboards expose email notification settings for success, warning, and error results. When the ConnectWise integration and backup-failure automation are configured, MSPControl can also create follow-up tickets for supported Azure Backup and Veeam failure categories.

Recovery boundary

The current dashboard interfaces expose backup evidence and restore-point information. They do not establish a verified, provider-independent restore procedure. Follow the underlying Veeam or Azure recovery process and validate restores in an appropriate test environment.

Related Microsoft 365 backup review

For the customer review that separates Veeam reporting, native protection monitoring, missing data and recovery validation, see Microsoft 365 backup monitoring. Confirm provider scope, installed version, report freshness and the result of any follow-up.