Don't Assume That Your Data is Backed Up With Office 365

Akins IT • February 17, 2016
Connect with us

Many organizations are recognizing the benefits of moving to Office 365. Some benefits include network accessibility anywhere at any time, easy email access both inside and outside of your organization, as well as reducing operations and management overhead. Making the move to Office 365 provides organizations with many benefits like increased end-user productivity to reduced cost and complexity of maintaining on-site hardware. Additionally, Microsoft reduces the risk of downtime substantially by running applications across highly available frameworks spread across different regions. While application downtime is reduced in Office 365, the risk of data loss due to human error is not. Office 365 does provide customers with some protection against loss of data, but the window for data recovery is short and the recovery options limited. Seeking an additional layer of protection against accidental or malicious data loss, organizations have begun to use third-party backup solutions that offer enhanced protection of Office 365 data, which include longer retention periods and more robust recovery options. 


Why Office 365 Backup is Necessary


More often than not, data is deleted and then later realize that it is still needed. While it is possible to recover deleted items from within Exchange Online and OneDrive for Business, the retention for these items is often inadequate. In Exchange Online, individual emails that are deleted by users get moved to the users’ 'Deleted Items' folder. Those items will remain in the 'Deleted Items' folder for the duration set by the administrator (usually 30 days by default). While the 'Deleted Items' folder does provide a layer of protection against end-user errors, messages can be permanently deleted if the user chooses 'Empty Deleted Items' folder. Once items are deleted from the 'Deleted Items' folder, they are then moved to the 'Recoverable Items' folder and into a subfolder named 'Deletions'. The default duration of items in this folder is 14 days, with a maximum duration of 30 days and once an item exceeds the retention setting, the item is gone forever. 


According to Microsoft, the number one cause for data loss is accidental data deletion. About 70% of all lost data is due to either accidental or malicious deletion of data by end-users. While Microsoft does takes several measures to ensure that service availability is not disrupted, the measures taken to ensure that permanent data loss does not occur are limited. Mistakes happen. Users accidentally delete files or a disgruntled employee or hacker takes malicious action in deleting or corrupting data. That is why it is important to have a third party backup solution in place to prevent data loss if you and your organization are using Office 365.

By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts