Agree the data scope
Identify the users, mailboxes, sites and other supported services that need protection. Record how new users and shared areas enter the backup scope, and who decides when information should remain after a person leaves.
Review the recovery needs behind your Microsoft 365 data. We help you define backup scope, retention and restore testing for the services you use, with responsibilities that your organisation can understand and verify.
Business information in Microsoft 365 can include email, shared documents and files that people use every day. The important question is what happens when the information you need is deleted, changed, inaccessible or affected by an incident. Different retention and recovery features serve different purposes.
We start with your recovery requirements and the services that hold important information. We then review existing protection and suitable backup options, including the practical work of finding and restoring data. Product coverage and limitations are checked for the selected solution rather than assumed across every Microsoft 365 workload.
Identify the users, mailboxes, sites and other supported services that need protection. Record how new users and shared areas enter the backup scope, and who decides when information should remain after a person leaves.
Agree how long the selected backup copies should be retained and who can request access to recovered information. Align these decisions with the business’s information requirements and documented retention responsibilities.
Plan how a file, mailbox item or other supported data set would be recovered. Identify the approvals, destination and checks required, especially where restored information contains personal or confidential business material.
Agree who checks backup operation and how failures are investigated. Use planned restoration exercises to gather evidence that the chosen approach can recover the information the business expects it to protect.
Map important information and existing recovery arrangements. Clarify acceptable data loss and the time the business can tolerate without particular information.
Select and implement the agreed backup approach. Check account access, scope and the process for including new users or services.
Carry out appropriate restore tests and record the outcome. Review scope, retention and permissions when the Microsoft 365 environment changes.
Your proposal sets out the systems, deliverables, responsibilities and service arrangements included. We agree these before work begins.
Something else on your mind?
Talk to usSynchronisation and backup have different purposes and behaviours. We review the services you use and the recovery situations you need to handle, rather than treating the presence of a synchronised copy as proof of suitable protection.
Coverage depends on the selected product and configuration. The proposal should name the supported workloads, data types, retention and exclusions so your organisation understands exactly what is protected.
The available restore options depend on the backup service and the protected workload. We review those options against your requirements and include representative recovery checks in the agreed testing plan.
Read the related guide online, or request a printable help sheet for your team.
Explore the related help sheetExplore how support, protection and ongoing improvements can form part of one coordinated plan for your business.
Meet Strata MomentumTell us about your current setup and what you want to improve. We will help you define a practical starting point.