Identify what must be recovered
Map the information and systems needed to continue operations, including Microsoft 365, donor databases, accounting records, shared files, websites and line-of-business applications. Record who owns each system and which vendors are involved.
Define recovery objectives
For each critical system, decide how much recent data the organization could afford to lose and how long it could operate without the system. These business decisions guide backup frequency, retention and recovery design.
Do not assume cloud services equal backup
Cloud platforms provide resilient infrastructure, but deleted, corrupted or maliciously changed information may still require a separate recovery method. Review native retention and version history, then decide whether independent Microsoft 365 or application backups are needed.
Protect backup access
Backup administration should use separate protected credentials and multi-factor authentication. Where practical, keep immutable or otherwise deletion-resistant copies so that an attacker or accidental administrator action cannot remove every recovery point.
Test real restores
A dashboard showing successful backup jobs does not prove that files, mailboxes or application data can be restored correctly. Schedule sample restores, record the results and correct failures before an emergency.
Create a simple continuity runbook
Document priority contacts, vendor support details, temporary work methods, communications responsibilities and the order in which systems should return. Review the plan after major staffing, software or infrastructure changes.
Related non-profit IT resources
Need a practical IT plan?
Outsource IT Canada helps Canadian non-profits align support, Microsoft 365, cybersecurity, backup and budgeting with their operational needs.