The brief
A development record has to be there years after the project closes
JQZ keeps its project documentation, consultant correspondence, contracts, sales and finance records in Microsoft 365. In property development those records get asked for long after they are written, at a finance review, an audit or when the next project draws on the last one, so they need to be recoverable well beyond what Microsoft keeps by default.
We started with how JQZ stores and uses information across Exchange Online, SharePoint, OneDrive and Teams, which told us what each workload needed in coverage and retention. From there we configured independent backups and tested restores across each type of content.
What is covered
Each kind of record, and the way it comes back
Each Microsoft 365 workload feeds an independent backup with its own retention, and each kind of content has its own way back.
- Exchange Online Mailbox items and folders: email with consultants, partners and the wider team
- SharePoint Online Documents and libraries: project records and shared business documentation
- Teams files Stored in SharePoint, so files used in project and team collaboration are covered
- OneDrive User files and working documents held in individual users’ storage
- Independent copy Separate copies, kept for as long as JQZ needs them and restorable down to a single item
Before any of this went into service, we restored mailbox content and folders, user files, SharePoint content and project data to prove the recovery works.
What we delivered
What we set up
Coverage that follows the work
JQZ’s mailboxes, SharePoint libraries, OneDrive files and the files teams share in Teams told us what matters day to day, and from there we set up independent backup across Exchange Online, SharePoint Online and OneDrive for Business. Teams files sit in SharePoint, so they are covered too.
Retention that matches a project’s life
Microsoft 365’s built-in recovery has fixed retention limits, and development records are often needed long after those have passed. We set the independent backup retention well beyond them, so JQZ has a copy to go back to once the native options have expired.
Restores at the size needed
A restore can be one email, one document or a whole project library. We set up granular recovery across mailbox items and folders, user files, SharePoint documents and libraries, OneDrive content and Teams files, so JQZ gets back what it asks for and nothing else has to move.
Built for the ways records get lost
Accidental deletion, an administrator mistake, a compromised account, a disgruntled insider or files hit by a cyber incident each need a different route back. We designed the recovery around each of them, so the backup is part of how JQZ recovers from an incident.
Tested, then looked after
Each kind of content was restored before the service went live. Backup monitoring, maintenance and coverage reviews now sit inside the managed services we run for JQZ. Protection keeps up as people join, data moves and teams change how they use Microsoft 365.