“Microsoft 365 backup” is the start of a scope discussion. A useful agreement names the data and identity information covered, the restore actions supported and the people responsible for performing them.
Name the data that matters
Identify the workloads, users and information your organisation needs to protect. Confirm coverage explicitly with the service provider, including additions, departures and changes to the environment.
Ask: Which workloads and data are in scope? What is excluded? How is coverage reviewed when the organisation changes?
Be precise about identity protection
Basic Entra ID backup can protect supported identity information. That description should not be treated as a promise to recreate every configuration or rebuild a complete tenant.
Ask: Which objects and attributes are included? What restore actions are supported? What permissions and dependencies are needed?
Agree retention and the restore process
Choose retention around the scenarios you need to recover from. Establish who may request a restore, who approves it and how the restored result is validated.
Ask: How far back can we go? Where does restored data go? What happens if the original account or destination is no longer available?
Validate the working relationship
A focused Microsoft 365 scope lets you experience how a managed provider onboards, communicates and performs an agreed restore. Select a representative test and record what it demonstrates.
Ask: Can we agree a first restore test? Who manages the daily service? Where is the independent backup held?
Put it to work
Bring the questions to your next review.
Download the plain-text checklist, add your evidence and agree who owns the next step.
Download checklist