All posts
Cybersecurity

Why Microsoft 365 backup fails against ransomware

Huma Shazia18 June 2026 at 7:42 pm6 min read
Why Microsoft 365 backup fails against ransomware

Key Takeaways

Why Microsoft 365 backup fails against ransomware
Source: BleepingComputer
  • Microsoft 365 operates under a shared responsibility model where data protection is entirely the customer's job
  • 600 million identity-based attacks target M365 environments daily, and 94% of ransomware attackers now target backups specifically
  • Native retention policies lack the granularity, immutability, and long-term storage that compliance and recovery actually require

Microsoft 365 backup does not protect your business data the way most IT teams assume. Microsoft itself doesn't claim otherwise. The platform operates under a shared responsibility model: Microsoft keeps the service running and the infrastructure secure, but backup, recovery, and data protection sit squarely on the customer's shoulders. That distinction matters when ransomware encrypts your SharePoint files and syncs the damage across every connected device before anyone notices.

600 million
Identity-based attacks against Microsoft 365 environments occur daily as of 2026

The numbers paint a stark picture. According to 2026 data, M365 environments face 600 million identity-based attacks daily. In 2024, 94% of ransomware victims reported that attackers specifically attempted to compromise their backups. And 58% of small and mid-sized businesses have no independent backup plan for their M365 data at all.

What does the shared responsibility model actually mean?

Microsoft guarantees uptime and infrastructure. If their data centers stay online and accessible, Microsoft has fulfilled its end of the deal. But if an employee accidentally deletes a critical folder, a departing worker wipes their mailbox, or ransomware encrypts your OneDrive, that's your problem. Microsoft replicates data across its infrastructure for availability, not for recovery. When encrypted files sync instantly across users and devices, that replication works against you.

Why version history won't save you from ransomware

Microsoft offers versioning and recycle bins. These features help with simple mistakes. They do not help when attackers deliberately corrupt multiple versions, or when an attack goes undetected long enough that all recovery points become unusable. Native tools cannot distinguish between safe versions and compromised ones. During a ransomware incident, that uncertainty delays restoration and forces dangerous guesswork about which data to trust.

Cloud-targeting ransomware has evolved. Attackers know that encrypting an endpoint is pointless if the victim can restore from OneDrive. So modern ransomware targets the cloud storage itself, encrypting files and letting synchronization spread the damage. By the time IT notices, the version history may contain nothing but encrypted copies.

Retention policies are not backups

Microsoft's retention policies exist for basic governance, not disaster recovery. They're rigid, lack independent storage, and often fall short of industry-specific compliance requirements. Healthcare, finance, and legal sectors frequently need data preserved for years or decades, with strict audit trails. Native retention can't provide that.

The core problem: retention policies don't enable full restoration. They preserve data in place. If an administrative account gets compromised, the attacker can often manipulate or delete that retained data. True backup means independent, point-in-time copies stored outside the production environment.

Granular recovery remains a weak point

Organizations rarely need to restore entire environments. They need a specific email from last Tuesday, a single SharePoint site from before a misconfiguration, or one user's Teams data after an accidental purge. Microsoft 365's native recovery options struggle here. The process is slow, imprecise, and often requires manual intervention that drives up downtime.

Third-party solutions address this by enabling item-level recovery across Exchange, SharePoint, Teams, and OneDrive from a centralized console. The difference between restoring a mailbox in minutes versus hours translates directly to operational cost and user productivity.

What third-party backup actually provides

  • Immutable storage that attackers cannot encrypt or delete, even with compromised admin credentials
  • AI-based ransomware detection that identifies suspicious encryption patterns before sync spreads the damage
  • Independent, customizable retention that meets compliance requirements across industries
  • Granular recovery of individual items without restoring entire environments
  • Clean, verified recovery points that eliminate guesswork during incident response

Vendors like Acronis and Veeam market specifically to this gap. Acronis Cyber Platform, for example, combines backup with active protection, using immutable storage and AI detection to ensure organizations can roll back to clean data without uncertainty. The pitch is straightforward: if you cannot restore an account to a point-in-time before an administrative account compromise, you are not truly backed up.

The IT community's verdict

On Reddit's r/msp, managed service providers regularly discuss what they call the "Microsoft 365 backup myth." The consensus: relying solely on native retention is, in their words, a "resume-generating event." Hacker News threads echo the sentiment. The top-voted comments argue that SaaS does not mean "set it and forget it." If your recovery strategy depends on Microsoft's built-in tools alone, you're betting your business data on assumptions Microsoft never made.

ℹ️

Logicity's Take

This is a sponsored article from Acronis, so the commercial angle is obvious. But the underlying point stands on its own. Microsoft's documentation explicitly states that customers own their data and its protection. The 94% statistic on backup-targeting ransomware should be the wake-up call: attackers have adapted to cloud storage, and organizations using M365 without independent backup are running on borrowed time. The question isn't whether you need third-party backup. It's whether you'll implement it before or after the first major incident.

Frequently Asked Questions

Does Microsoft 365 include backup?

No. Microsoft 365 provides version history and recycle bins, but these are not backups. Microsoft's shared responsibility model places data protection, recovery, and backup entirely on the customer.

Can ransomware encrypt OneDrive files?

Yes. Ransomware can encrypt files in OneDrive, and those encrypted versions sync instantly across connected devices. Native version history may not help if the attack corrupts multiple versions or goes undetected.

What is immutable backup storage?

Immutable storage prevents data from being modified or deleted for a defined period, even by administrators. This protects backup copies from ransomware and insider threats.

Are Microsoft 365 retention policies sufficient for compliance?

Often not. Retention policies lack the granularity, independent storage, and audit capabilities that industries like healthcare, finance, and legal require for regulatory compliance.

Which vendors offer Microsoft 365 backup solutions?

Major vendors include Acronis, Veeam, Druva, and Commvault. Each offers immutable storage, granular recovery, and compliance-focused features that native M365 lacks.

Also Read
Vaultwarden: self-host Bitwarden's vault for free

Another approach to taking data security into your own hands

ℹ️

Need Help Implementing This?

Evaluating third-party backup solutions for Microsoft 365? Logicity tracks enterprise security tools and can connect you with implementation partners. Reach out through our contact page for vendor-neutral guidance on protecting your M365 environment.

Source: BleepingComputer

H

Huma Shazia

Senior AI & Tech Writer

Related Articles