Microsoft Protects the Platform: Why Cloud Backup Needs a Rethink

Microsoft 365 uptime does not guarantee data recovery. Explore cloud backup gaps, Entra ID protection, and practical steps to strengthen business resilience.

Écrit par
Zeus Kerravala
Zeus Kerravala
Nov 17, 2026
Microsoft Protects the Platform: Why Cloud Backup Needs a Rethink

Cloud infrastructure keeps services running, but businesses still need a recovery plan for their Microsoft 365 data and identities. Image: Unsplash.

One of the most persistent myths in enterprise IT is that moving workloads to Microsoft’s cloud transfers responsibility for protecting data. The reasoning goes like this: Microsoft operates some of the most resilient data centers in the world, so my email, files and identities must be safe.

The first half is true. The second half is an erroneous assumption.

Under Microsoft’s shared responsibility model, Microsoft owns the infrastructure and service uptime, while the customer owns its data, accounts, and identities.

If a user deletes a SharePoint library, a disgruntled admin wipes mailboxes, or ransomware encrypts OneDrive files and syncs the damage across the tenant, Microsoft has done its job: the platform kept running. Restoring the data is your problem.

Native tools are a safety net, not a strategy

Advertisement

Microsoft includes recovery features, and IT pros should understand them:

  • SharePoint: Deleted items remain in the site Recycle Bin for 93 days before permanent removal.
  • Soft-deleted objects: Microsoft’s guidance states that these are retained for 30 days before permanent removal.
  • Hard-deleted objects: These cannot be restored. You must rebuild them, and they return with a new object ID. Group memberships, Conditional Access targeting, app assignments, and role assignments may need to be reconnected manually.

That last point receives too little attention. Identity is now the security perimeter, and losing a Conditional Access policy or privileged role assignments can lock users out of the business or quietly open a door.

Entra audit logs are typically retained for only about 30 days, limiting how far back you can investigate.

Microsoft acknowledges these limits. Its own guidance tells customers to keep an external, versioned, known-good copy of tenant configuration and to consider non-Microsoft tools for longer retention, broader coverage, and recreating hard-deleted objects.

Advertisement

Recycle bins and retention policies were built for convenience and compliance. They were not built for a coordinated attack, a corrupted sync, or the need to roll back an entire tenant to a known point in time.

Why the old backup playbook falls short

Traditional backup was designed for servers in a data center, with nightly jobs and restores measured in days. SaaS does not follow that model.

The data resides in someone else’s infrastructure, is accessible only through APIs, and is tied to identity in ways a file server never was.

Attackers now deliberately target backups because a clean recovery copy removes their leverage.

AI raises the stakes further: Copilot and AI agents act on the same mail, files, and Teams conversations the business relies on, so mistakes spread faster than people can catch them.

Data is also growing rapidly. Veeam cites 451 Research figures showing that organizations expect 31% data growth over the next 12 months, and that 35% say a data-loss incident took significant effort to recover from.

Advertisement

Where Veeam Data Cloud fits

This is the gap Veeam Data Cloud is designed to close. It’s a SaaS backup service purpose-built for Microsoft 365 and Entra ID, with no backup infrastructure for IT to deploy or patch.

Microsoft 365 backup and recovery

For Microsoft 365, it covers Exchange Online, SharePoint, OneDrive, and Teams, including Teams channels, posts, tabs, and memberships.

Its backup and recovery features include:

  • Unlimited storage.
  • Azure region selection: The customer chooses an Azure region.
  • Encrypted, immutable backups: Backups are encrypted, and the primary copy is immutable, so neither administrators nor attackers can change or delete it.
  • Granular and bulk recovery: Recovery ranges from a single email or file to bulk restores for ransomware and disaster recovery scenarios.
Advertisement

Entra ID Protection

The Entra ID service is the component worth examining more closely. It backs up:

  • Users, groups, and memberships.
  • Directory roles.
  • App registrations and service principals.
  • Conditional Access policies.
  • Administrative units.
  • Intune policies.
  • Audit and sign-in logs.

A tenant-comparison feature shows what has changed relative to a known-good backup, turning a stressful forensic exercise into a targeted restore.

Veeam has also added Intelligent ResOps for Microsoft 365, which provides data context so teams can see how AI agents interact with their data and decide what to recover first.

Why managed services matter for the midmarket

Buying the technology is only part of the job. Someone still has to set policies, monitor job health, test restores, and know what to do at 2 a.m. Most small and midmarket companies don’t have staff for these tasks.

That’s where a managed services provider makes enterprise-grade resilience realistic.

Advertisement

As an example, Dataprise, a Veeam Platinum partner, now delivers fully managed Veeam Data Cloud services for Microsoft 365, Entra ID, and Salesforce. The service covers:

  • Policy configuration and retention management.
  • Continuous monitoring and alert handling.
  • Backup validation and recovery testing.
  • Documented recovery procedures.
  • Assisted restores, from a single file to an entire tenant.

Dataprise builds the service around the 3-2-1-1-0 approach: three copies of data, on two media, with one offsite, one immutable, and zero errors.

The difference is real. A backup product gives you a copy of your data. A managed service tells you whether that copy will work when you need it.

More Microsoft news

Advertisement

Advice for IT pros

Review the shared responsibility model and document what you own.

Go workload by workload — Exchange, SharePoint, OneDrive, Teams, and Entra ID — and note what Microsoft retains, for how long, and what it can’t restore.

Turn that into a one-page gap analysis for business leaders. Many executives assume “in the cloud” means “backed up,” and seeing the gaps in writing is often what gets a resilience budget approved.

Treat Entra ID as a tier-one workload.

If identity goes down, no one can sign in to restore anything else, so it must come back first.

Back up users, groups, role assignments, app registrations, and Conditional Access policies with the same rigor you apply to mail and files.

Maintain a known-good baseline of your Conditional Access settings and set alerts for permanent deletions and changes to privileged roles.

Advertisement

Require immutability and separation from your tenant.

A backup in the same tenant, under the same admin credentials as production, isn’t a recovery plan. It’s another target.

Insist on an immutable copy that no one, including your global admins, can change or delete.

Protect the backup console with phishing-resistant MFA and separate admin accounts, because attackers who gain admin rights often try to shorten retention before they strike.

Test restores on a schedule.

A “job succeeded” message indicates data was copied, not that it can be recovered in time.

Each quarter, restore more than a single file:

  • A full mailbox.
  • A SharePoint site with its permissions.
  • A Teams channel.
  • A deleted Entra ID group.

Run tabletop exercises for ransomware, a malicious admin, and a mass deletion. Measure your actual recovery time against what the business expects, not the number in the brochure.

Advertisement

Match retention to regulation, not to defaults.

Thirty- and 93-day windows rarely meet legal hold, audit, or industry requirements, especially in healthcare, financial services, and the public sector.

Work with legal and compliance to set retention by data type and confirm where backups are stored if you have data residency obligations.

Ensure you can search backups quickly enough to respond to an eDiscovery request without scrambling.

Account for AI agents.

As Copilot and other agents gain permission to create, edit, and move content, a single bad instruction can trigger thousands of changes in minutes.

Inventory which agents have write access to which data. Keep backups frequent enough to roll back an agent’s work and use tools that can restore only the affected items rather than overwriting everything.

Advertisement

Final thoughts

Moving to the cloud doesn’t eliminate the need for backup. It makes a complete data resilience strategy even more important, because data is more central, identity is more exposed, and attackers are more deliberate.

Microsoft will keep the platform running. That was never the hard part.

IT leaders should stop asking whether Microsoft protects their data. The question to ask now is how quickly, completely, and confidently they can recover it.

If the honest answer is “I’m not sure,” that is where the rethink should start.

Read more: How a widespread Microsoft 365 outage disrupted Outlook, Teams, and workplace applications.

Zeus Kerravala

Zeus Kerravala is an eWEEK regular contributor and the founder and principal analyst with ZK Research. He spent 10 years at Yankee Group and prior to that held a number of corporate IT positions. Kerravala is considered one of the top 10 IT analysts in the world by Apollo Research, which evaluated 3,960 technology analysts and their individual press coverage metrics.