JQZ strengthened Microsoft 365 recovery with independent backup outside native Microsoft retention.
JQZ runs a property development environment where Microsoft 365 sits at the centre of daily operations — email, documents, project collaboration, Teams communication, executive workflows and user access. That makes Microsoft 365 a production platform, not simply a productivity tool. Native retention, recycle bins and version history were not designed for a business that depends on project records, finance workflows, consultant coordination and long-running development documentation.
Inlight IT implemented independent Microsoft 365 backup for JQZ, covering key Microsoft 365 workloads and strengthening recovery capability outside native Microsoft retention. The result was a more defensible recovery posture across email, project documents, user files and collaboration data.
- Client
- JQZ
- Industry
- Property development and construction
- Environment
- Microsoft 365 across email, project documents, user files and Teams-based collaboration
- Starting point
- Native retention, recycle bins and version history — not designed for a business that depends on project records, finance workflows, consultant coordination and long-running development documentation
- Engagement type
- Microsoft 365 backup implementation — independent backup for Exchange Online, SharePoint Online, OneDrive for Business and Teams-related data
- Recovery focus
- Accidental deletion, administrator error, compromised accounts, malicious activity and data loss discovered after native retention windows
- Outcome
- A stronger recovery posture for Microsoft 365 data, independent of native Microsoft retention and better aligned to cyber resilience expectations
JQZ — independent Microsoft 365 backup
A stronger recovery posture across email, project documents, user files and collaboration data.
One recovery layer across the workloads the business relies on every day
Exchange Online, SharePoint Online, OneDrive for Business and Teams-related file data where stored in SharePoint.
A recoverable copy of key Microsoft 365 data outside native Microsoft retention.
Retention configured beyond native Microsoft recovery windows, recycle bins and version history.
Backup posture aligned with the managed IT operating model, part of ongoing service management.
Microsoft 365 is the production environment — it still needs a recovery layer
For JQZ, Microsoft 365 supports the daily operating rhythm of property development — sales communication, project workflows, finance activity, project documentation, consultant coordination, executive communication and access to long-running development records.
The risk was not Microsoft platform availability. Microsoft runs the cloud service. The risk was business data loss inside the tenant — accidental deletion, account compromise, malicious activity, cyber attack-affected files, administrator error, or data loss discovered after native retention windows had expired.
Inlight IT strengthened the JQZ environment by implementing independent Microsoft 365 backup across the key collaboration and productivity workloads the business relies on every day.
JQZ depended on Microsoft 365 for project, finance, sales and executive workflows — native retention was not enough
Microsoft 365 provides useful native recovery tools — recycle bins, version history and short-term retention. Those tools help with routine user error. They are not the same as independent backup, and they are not designed to cover every data-loss scenario a property development business needs to defend against.
Project records needed protection beyond recycle bins
Property development records often have long lifecycles. Project documents, consultant correspondence, sales material, contract records, commercial communication and financial documentation may be needed months or years after creation. A short native retention window does not match the operating life of a property development project.
SharePoint and Teams had become operational systems
SharePoint and Teams were not side tools. They supported document access, team communication and project collaboration across users and engagements. If project libraries, Teams files or user data were deleted, encrypted or corrupted, JQZ needed a recovery path beyond native Microsoft tools.
Microsoft 365 data loss is not always discovered immediately
A deleted folder, missing mailbox item or corrupted project library may not be noticed the same day. In property development, documents can sit dormant until an audit, finance review or project milestone brings them back into focus. If the discovery happens outside native retention, Microsoft 365 alone may not provide recovery.
Admin compromise and cyber incident scenarios needed a stronger answer
A compromised account can delete, encrypt or alter cloud data. Cyber attack can affect synchronised OneDrive and SharePoint files. A malicious insider can remove important content. Independent backup gives the business a recovery path if the tenant itself becomes part of the incident.
Microsoft 365 availability is not the same as Microsoft 365 data recovery
Microsoft provides the platform, service resilience and native retention features — valuable controls, but they do not replace independent backup for customer data. The practical distinction is simple: Microsoft protects the service; the organisation remains responsible for its data.
Independent Microsoft 365 backup with coverage aligned to how the business actually uses the platform
Inlight IT implemented Microsoft 365 backup as part of JQZ's broader cyber-first managed IT and resilience posture. The objective was to give the business a recoverable copy of key Microsoft 365 data outside native Microsoft retention, with coverage aligned to how JQZ actually uses Microsoft 365.
01Workload and data review
Inlight IT reviewed how JQZ used Microsoft 365 across email, SharePoint, OneDrive and Teams. The focus was to identify which workloads were operationally important and where native Microsoft retention was not enough.
02Backup coverage across key Microsoft 365 workloads
Independent backup was configured across Exchange Online, SharePoint Online, OneDrive for Business and Teams-related file data where stored in SharePoint. Coverage was aligned to active users and business-critical collaboration data, with retention configured beyond native Microsoft recovery windows.
03Recovery path outside native retention
Item-level restore capability was established for mailbox items, folders, user files, SharePoint documents and libraries, OneDrive content and Teams-related files. The backup provided a stronger recovery option than recycle bins and version history alone.
04Protection against account compromise and deletion scenarios
The recovery model was designed for more than routine user error. The backup posture considered accidental deletion, admin error, compromised accounts, malicious insider activity and cyber attack-affected cloud data.
05Governance and operational support
A backup is only useful if it is monitored, maintained and understood. Inlight IT aligned the Microsoft 365 backup posture with the managed IT operating model, so Microsoft 365 protection became part of ongoing service management rather than a once-off configuration.
Sequenced for coverage, retention and operational fit
Select a stage to trace how the backup posture moved from workload review to ongoing managed IT support.
Native Microsoft 365 retention was not designed to cover every data-loss scenario
Microsoft 365 backup is increasingly important because the data-loss scenario is no longer just accidental deletion. A compromised account can delete, encrypt or alter cloud data. Cyber attack can affect synchronised OneDrive and SharePoint files. A malicious insider can remove important content. Microsoft protects the service; the organisation remains responsible for its data — and native recycle bins, version history and short-term retention are not the same as independent backup.
Four Microsoft 365 workloads brought under independent backup: Exchange Online, SharePoint Online, OneDrive for Business and Teams-related file data.
One independent recovery path outside native retention, recycle bins and version history.
Retention configured beyond native Microsoft recovery windows, matched to the long lifecycles of property development records.
Backup became part of ongoing service management rather than a once-off configuration.
JQZ gained a stronger recovery layer for the Microsoft 365 data the business relies on every day
The Microsoft 365 backup implementation gave JQZ a more defensible recovery posture across email, project documents, user files and collaboration data. The business reduced reliance on native retention alone and gained a clearer path to recover critical Microsoft 365 information.
Exchange Online data became independently recoverable
JQZ gained a stronger recovery option for mailbox content, folders and email data beyond short native retention windows.
SharePoint project content had a stronger recovery path
Project libraries and collaboration data became easier to recover if deleted, corrupted or affected by user or administrator error.
OneDrive data protected beyond standard recovery paths
User files stored in OneDrive gained an independent recovery path, reducing reliance on recycle bins and version history alone.
Teams-related file data included
Because Teams files are stored in SharePoint, backup coverage supported recovery of important Teams-related file content where relevant.
A stronger answer to account compromise and deletion risk
Independent backup improved JQZ's ability to recover from data-loss scenarios involving compromised accounts, malicious deletion, accidental deletion or cyber attack-affected files.
Backup became part of ongoing IT management
Microsoft 365 backup was not left as a disconnected tool. It became part of the managed service posture, with coverage, recovery and operational support considered as the environment changes.
The value was not another tool. It was a more defensible recovery posture across email, project documents, user files and collaboration data.
A Microsoft 365 backup posture shaped by how the business actually operates
Production data protected
Email, project documents, user files and collaboration data treated as recoverable business information.
Coverage across core M365 workloads
Exchange Online, SharePoint Online, OneDrive for Business and Teams-related file data considered in the backup posture.
Beyond native retention
Recovery strengthened beyond standard recycle-bin, version-history and short-term retention features.
Recovery path available
Backup configured around practical restore scenarios, not only policy compliance.
Recovery included in security posture
Microsoft 365 backup connected to the broader cyber resilience model.
Ongoing managed IT support
Backup brought into the managed service rhythm rather than left as a configuration artefact.
The work connected backup coverage, recovery pathways and ongoing managed IT support
Workload coverage
6- Microsoft 365 Backup
- Exchange Online backup
- SharePoint Online backup
- OneDrive for Business backup
- Teams-related file recovery
- Active-user coverage
Recovery pathways
7- Independent recovery path
- Item-level restore
- Mailbox and folder restore
- SharePoint document and library restore
- OneDrive content recovery
- Practical restore scenarios
- Restore pathway review
Retention & resilience
6- Retention beyond native windows
- Recycle-bin and version-history limits
- Account compromise scenarios
- Malicious deletion scenarios
- Cyber attack-affected data
- Cyber resilience posture
Operating model
6- Backup coverage review
- Monitoring and maintenance
- Managed IT alignment
- Ongoing service management
- Governance support
- Posture review as the environment changes
Microsoft runs the platform. Your business still needs a recovery layer
We test whether your Microsoft 365 data would actually recover, then close the gaps.
Discuss Backup & Disaster Recovery