Microsoft 365 backups still leave tenant configuration gaps
Reviewed by Helen Jones
Tony Redmond’s 22 September analysis argues that Microsoft 365 recovery planning is still split across workload data and tenant configuration. Microsoft 365 Backup restores SharePoint, OneDrive and Exchange content, while Microsoft’s separate Entra recovery service covers selected identity objects, leaving admins to plan separately for settings, dependencies and services outside those documented scopes.
Most backup checks ask whether files, sites and mailboxes can be restored. A catastrophic tenant incident also depends on identity policies, application registrations, Teams and SharePoint settings, ownership and the order in which connected services return. That turns recovery into a configuration and dependency problem for small admin teams, not only a data-restore job. A successful restore test can still leave the organisation unable to work if nobody has a known-good record of critical settings or a rehearsed rebuild order.
Analysis
Run a one-hour tenant recovery tabletop. Put each critical service in a simple register with its backup scope, configuration record, dependencies, recovery owner and first test, then flag anything covered only by assumptions.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Microsoft 365 backups still leave tenant configuration gaps", Collab365 Spaces.