Cloud-to-cloud backup copies your Microsoft 365 email, OneDrive, SharePoint, and Teams data to a separate cloud, outside Microsoft’s own retention, so a dealership can restore what was deleted, encrypted, or lost when an employee left. Microsoft keeps the service running. The data, and getting it back, stays with you.
Last updated: November 20, 2026
In May 2024, UniSuper, an Australian pension fund that invests over $135 billion for more than 647,000 members, lost its private cloud subscription on Google Cloud. It was deleted. A joint statement from the two CEOs traced it to “an inadvertent misconfiguration during provisioning” and called it a “one-of-a-kind occurrence.” Google’s own incident report is blunter: Google operators left a parameter blank. One blank field. The line that matters most to you is in the joint statement: “UniSuper had backups in place with an additional service provider.” Those backups, the statement says, minimized data loss and significantly improved the ability to restore.
Read that again. The provider made the mistake, and the customer’s own second copy, kept with someone else, is what helped. The copy that counted lived somewhere else.
On a November 4 planning call with our team, I put it as plainly as I know how: “Just because your data is in the cloud doesn’t mean it’s backed up. You have to have cloud-to-cloud backup.” I’ve been doing IT for dealerships for nearly 30 years. In an earlier call with our content team, I said that with so much dealership technology now cloud-based, people “just don’t think about backups at all.” At Helion, the same team that handles managed cybersecurity for dealerships runs backup and recovery, and that’s no accident. The copy is the part that gets forgotten.
That’s a real problem.

What Is Cloud-to-Cloud Backup, Exactly?
Cloud-to-cloud backup is a scheduled copy of the data inside a cloud application, such as Microsoft 365, stored by a separate cloud service outside that application. If data in Microsoft 365 is deleted, encrypted, or purged, a backup built this way lets you restore it from the second cloud, to a point in time before the damage, without depending on Microsoft’s recycle bins. SaaS backup is the broader term: backing up a cloud application’s data, wherever the copy ends up.
The word that matters is separate. A copy that lives inside the same tenant, behind the same admin password, isn’t much of a backup if that password gets stolen. So when somebody tells you “we have backups,” ask the next question. Where?
Separate means separate.
Who Is Responsible for Your Data in Microsoft 365?
You are. Microsoft puts this in writing in its shared responsibility guidance, which lists what the customer keeps “regardless of the type of deployment,” and the first item on that list reads “Data – You’re responsible for your data.” The page covers software as a service like Microsoft 365 too. There, Microsoft handles the physical datacenter, hosts, and network, plus the operating systems underneath, and customer data sits in the customer’s column for every type of deployment. What’s in your mailboxes and folders is yours to protect. All of it.
Microsoft does hold on to deleted things for a while, and I don’t want to knock that. It’s useful. It also expires. It has an end date, and the end dates are short. Here’s what Microsoft’s own pages say.
| What happens | What Microsoft keeps | After that |
|---|---|---|
| Email is deleted and emptied from Deleted Items | The Recoverable Items folder keeps it 14 days by default, adjustable to 30 at most (Microsoft Learn) | “Removed from Exchange Online,” unless the mailbox is on a hold such as Litigation Hold |
| Someone deletes files in SharePoint or Teams | 93 days in the recycle bins (Microsoft Support) | “Permanently deleted” |
| OneDrive files are deleted, overwritten, corrupted, or hit by malware | A full OneDrive can be rolled back to an earlier date “within the last 30 days” (Microsoft Support) | The full restore can’t reach back further than 30 days |
| A departed employee’s license is removed | Exchange Online data “is held for 30 days” (Microsoft Learn) | “Deleted and can’t be recovered” |
| A user account is deleted | 30 days to restore the account (Microsoft Learn) | The user’s data is permanently deleted |
I said it this way on that same call, and it’s on our backup and disaster recovery for dealerships page: “Microsoft doesn’t guarantee you backups of all of your data. It retains it for a bit, but that’s not a backup and restore, like what you typically expect.”
Retention is a grace period. It isn’t a backup.

What Does Data Loss Look Like Without a Separate Backup?
Without a separate backup, data loss in Microsoft 365 can look like a deadline nobody knew about. The data was recoverable for a few weeks, nobody noticed it was missing, and by the time someone went looking, Microsoft’s retention had run out. Three situations show how that happens.
Somebody deletes the wrong thing
Picture a title clerk cleaning up a shared folder on a slow Friday. Some of what goes into the bin is the folder the office uses to chase payoffs and lien releases, and nobody opens it again for four months. On SharePoint, the clock started the day it was deleted. A mistake like that isn’t a security event. It’s an ordinary Friday. The question is whether you find out inside the window, and with a separate backup, the window is the retention you set.
Ransomware reaches your files in OneDrive
Being in the cloud doesn’t put files out of ransomware’s reach. Microsoft built tools for exactly this. Its ransomware detection “notifies you when your OneDrive files have been attacked,” and Microsoft warns that files “could get encrypted again” if you restore before cleaning the infected computers. The 30-day OneDrive restore can help. Only inside 30 days. Then it can’t.
Attackers know about recovery options, though. CISA’s #StopRansomware Guide tells organizations to “maintain offline, encrypted backups of critical data” and says why: “many ransomware variants attempt to find and subsequently delete or encrypt accessible backups.” If a stolen admin account can reach your recovery options, so can the attacker. Our post on ransomware at auto dealerships covers how these attacks start.
An employee leaves, and the mailbox goes with them
This is the one that catches people. A finance manager quits. It happens. Somebody removes the license so the store stops paying for it, and the mailbox with three years of lender, customer, and vendor email in it starts a 30-day countdown. Microsoft is clear about what happens after the grace period: the data “is deleted and can’t be recovered.” Then a customer disputes a deal in month four, and somebody needs those emails. Who owns that?
Microsoft does offer one way to keep it. Convert the mailbox to a shared mailbox before the license comes off, and it needs no license up to 50 GB. Somebody has to do that on purpose, every time. A separate backup that keeps former employees’ mailboxes covers the times nobody remembered, for as long as your retention policy says. Our dealership data retention policy template helps you decide how long that should be.
Thirty days goes fast.
What Should Cloud-to-Cloud Backup Cover at a Dealership?
Cloud-to-cloud backup at a dealership should cover every Microsoft 365 workload your stores use, keep the copies outside your tenant under separate credentials, and let you restore one email or a whole mailbox to a chosen point in time. Here’s what I’d check, in roughly this order.
- Every mailbox, including shared ones like sales@, service@, and the BDC inbox.
- OneDrive for every user, not only the managers.
- SharePoint sites and Teams files. Microsoft says the files on a team’s Files tab “are stored in a SharePoint site,” so check both are in the job.
- Does it keep a mailbox after the employee leaves and the license is removed? Ask that one directly.
- Retention that you set, long enough to match your own retention policy.
- Copies stored outside your Microsoft 365 tenant, under credentials a stolen admin password can’t use.
- Granular restores: one email, one folder, or the whole account, to a date you pick.
- Google Workspace too, if any store or department runs on it. Same logic, different cloud.
One more. If your DMS, CRM, or another app is hosted by a vendor, ask that vendor in writing what they back up, how often, and how you’d get your own data back if you needed it. Get the answer on paper. Then file it. Seriously.
I’m not going to name products here. The right one depends on how your stores are set up. What matters more than the brand is whether the list above is covered and whether somebody checks it.
Coverage you haven’t confirmed is coverage you don’t have.

Why Does a Restore Test Matter More Than the Backup?
A restore test shows that the backed-up data actually comes back, opens, and is complete. A job that reports success every night only shows that the job ran. CISA’s guide asks organizations to “regularly test the availability and integrity of backups in a disaster recovery scenario,” and cloud backups are no exception to that.
Restore a single email from last month. Restore a OneDrive folder from before a date. Restore a departed employee’s mailbox to a different account and open a message from it. Each one tells you something different. Start small. A problem found on a quiet afternoon is a lot easier to live with than one found on a bad day. Rex Marchant, our Vice President of Service, wrote the full walkthrough in why a restore test matters more than the backup report.
I won’t promise you a restore time in a blog post, because it depends on how much data you have, what you’re restoring, and where it’s going back to, and nobody can give you that number honestly without a test. A timed test is how you find your number, and then it’s a real number instead of a guess.
Test it before you need it.
To Be Clear, This Isn’t an Argument Against the Cloud
I’m not the guy telling you to pull your email back onto a server in the closet. The UniSuper story isn’t a reason to avoid the cloud. It’s a reason to keep a second copy somewhere else, which is exactly what UniSuper had done.
On our backup page, Helion’s Microsoft 365 backup work is laid out as a separate backup of every mailbox, restorable to a point before the damage, and a separate backup of files and sites, kept outside the tenant. Test restores run on a schedule, with the results written down where your managers can see them. If you have an IT manager on staff, our co-managed IT path keeps them in charge, and Helion’s team adds the monitoring, the offline copy, and the restore testing alongside them. The settings that keep the tenant itself locked down are on our Microsoft 365 management and security page.
The cloud is fine. The single copy is the problem.

Things Dealers Ask About Cloud Backup
We pay for Microsoft 365. Isn’t backup included?
Is SaaS backup the same thing as cloud-to-cloud backup?
What happens to a mailbox when someone leaves the dealership?
Can’t we just use the recycle bin?
How do we find out what we have today?
Find Out Where Your Second Copy Lives
Helion supports 2,000-plus dealerships, and the question I’d start with is the same at any of them: where’s the second copy? If nobody can answer, our complimentary IT and cybersecurity assessment is a no-obligation review of your current technology, security posture, and vendor spend, along with your FTC Safeguards compliance standing and how staff use AI tools, and the findings come to you in a written report.
Data in the cloud is still your data. Keep a copy of it somewhere else.

